For the CIO
Your technology roadmap may be based on yesterday's software economics.
Your backlog is a record of yesterday's constraints. It reflects what could be staffed, estimated, and approved under a cost model that has materially changed.
The move
Re-read the roadmap against current execution economics.
- What was deferred
- Items removed for cost or duration reasons deserve a second reading. Some were only wrong at the old price.
- What was outsourced by default
- Work sent outside because internal capacity did not exist may now be a capability-building opportunity instead.
- What is in flight
- Large in-flight implementations were scoped under the same assumptions. The delivery model is worth challenging before the next milestone commitment.
Questions to ask now
Useful questions to put to your own organization — and to any provider.
- 01
Which backlog items were deferred primarily because of engineering cost or capacity?
- 02
Which initiatives are expensive because of coordination rather than intrinsic complexity?
- 03
Where has vendor dependency become an operating constraint?
- 04
Which projects could establish useful evidence before the next major commitment?
- 05
Where could Co-Build increase internal execution capacity?