Speed to meet changing business needs

Marketers must attempt to anticipate all required program capabilities and system functionality in a Business Requirements document before any design or development. This typically adds many nice-to-have ancillary features because:

• There is  only "one chance" to define the system.
• Features providing the most value are undetermined

This approach results in:

• Overbuilt systems
• Late-to-market systems
• Increased difficultly to respond to changing business needs.

Determine the most valuable program elements and system functionality to roll out in two weeks.

Two weeks later the most valuable program elements from your priorities are in production.

The EcoWay results in:

• Elegantly simple systems with only the highest value functionality
• First-to-market impact
• Rapid response to changing business requirements.

Improve alignment of sales and marketing

Determine all requirements up-front with limited understanding of cost implications. Expectations to deliver all envisioned program elements and system functionality within a pre-set budget.

Scope/requirements are typically fixed at the end of the requirements phase.

This approach results in:

• Dissatisfied sales and marketing users even when the system is built according to requirements.

Users drives scope.

Scope/requirements can and do change throughout project lifecycle to meet changing needs of sales, marketing and  customers.

The EcoWay results in:

• Users see and experience rapid innovation around their program, and steer the direction of innovation.

Ability to monitor solution progress and improve accountability

Progress tracked against up-front plan.

Documents used as interim deliverables and serve as proxy measurement of progress.

The approach results in:

• Development teams building buffer into the project .
• Low accountability.

Progress measured based upon completed deliverables.

The EcoWay results in:

• Development risks are understood and mitigated early in project lifecycle.

Ability to justify constant innovation

Large investment typically required up-front to support year/multi-year efforts based on projected costs/benefits.

The approach results in:

• Political and funding positioning

Gates established every release for management to determine if continued investment is warranted based on delivered program innovation and functionality.

The EcoWay results in:

• Measureable results to justify innovation.