Apply the strategic disciplines of story clarification, asset networking, and environment survey to maximize participant creativity, contributions, and commitments and feed your online direction.

Use the cultural disciplines of meaning making, practice engineering, and message cycling to design a value-nurturing framework that will embody your identity as you plant, grow and mature your solution.

Work with project participants to map out production and establish your project management processes and objectives. Open dialog to clarify the story of production and adjust for consistency in terms of assets and environmental factors before committing to production. For long production cycles, engineer story-assets-environment checkpoints along the way.

Create a cross-sectional learning community (internal and external participants) of early-adopters to test alpha versions and begin adopting the solution in preparation for launch and promotion. Establish rhythms of meaning making, practice engineering, and message cycling within this community.

Scale adoption and promotion discoveries from your learning community for all users. Refine and roll out learning pathways, incentivized best practices (best behavior = highest value), support assets, and cultural/marketing symbols to help both you and the community to spread the word.

Encourage cycles of dialog with the growing community of external and internal users.. Use this to inform enterprise support for the community as well as the solution(s) and to inspire the design of value measurement tools and next versions.

Create a brand experience strategy for internal and external participants across your mix of New Media, Web Presence, and Productivity & Apps.

Audit solution options: type (Socail Media, CMS, CRM, ERP, PM, VLE/LMS); source (custom, open source, proprietary); delivery (SaaS, hosted/cloud, site-integrated, and self-hosted); and promotion strategies. Match these with resources, capacities, and culture for a consistent experience of enterprise identity for all participants.

Divide production – both design and functionality – to be as modular as possible, adding small well-crafted pieces together organically to form bigger units. These small units are more digestible and can be sorted according to intended value and engaged by small groups of participants for feel, usability, and reliability. As cellular units are knit into tissues, tissue into organs, and organs into systems, the community as a whole can maximize the unity and quality of the whole.

When alpha versions come online, begin catalyzing internal and external early-adopters to build a knowledge base and develop practices informed by the strategy and culture of the entire enterprise and community. Position these assets as close to the solution as possible to maximize context and accessibility.

Mature your BETA version through internal and external troubleshooting, usage evaluation, and feature planning (next version) including both the solution and support systems. Place high emphasis on progress towards a more open, clear, and consistent user experience.

Review development and maintenance and compare costs with value generation (present and projected). Develop processes to optimize your solution with contributions from the internal and external participants of the user community.