The situation
More than 35 concurrent technology initiatives competed for the same engineers, each with a persuasive sponsor and no common basis for comparison.
Every initiative looked important in isolation
The portfolio mixed foundational infrastructure, customer-facing products and operational improvements. Each had a sponsor, a business case and a plausible claim on the same constrained engineering capacity.
The failure mode was not bad judgement. It was that no two proposals expressed value the same way, so leadership was comparing narratives rather than options, and the most persuasive sponsor tended to win.
A common language for difficult trade-offs
Working sessions made assumptions explicit and converted them into shared criteria: expected return, technical risk, dependency load, strategic alignment and confidence in the underlying evidence.
The output was deliberately not a ranking. Rankings break the moment capacity changes. Instead the model produced investment scenarios, so leadership could see which initiatives moved when engineering capacity or strategic emphasis shifted.
The output was a decision process
The CTO and eight senior leaders adopted the model as their primary portfolio governance tool within six weeks. Speed of adoption mattered as much as the analysis — a prioritisation artefact that arrives after the planning cycle has no effect on anything.
The immediate result was a defensible sequence. The durable result was a repeatable way to revisit that sequence as evidence changed, which shifted the conversation away from which sponsor argued hardest.