Roadmapping

A roadmap is a sequence of bets about where to spend finite capacity. Its permanent tension is between shipping visible value now and investing in the platform and quality that make future value possible. Starve the platform and velocity decays under accumulating debt and toil. Over-invest and the business goes hungry for value it can see. The competency is holding the balance deliberately. That means allocating capacity explicitly so that foundational work is not deferred for ever, and treating the roadmap as a living instrument of trade-offs, framed around outcomes, instead of a list of dated promises. It also means separating near-term commitments from directional bets, and saying what is not being done. The platform never asks for capacity and the business always does, so the balance holds only when a manager holds it on purpose. The examinations test this through the product partner who wants no reduction in feature output, the roadmap that is the union of everyone's requests, the internal team funded by inertia, and the two-year bet started on borrowed patience.

1. Allocate capacity explicitly. Set a standing share of the team's capacity for platform, reliability and debt, state it and defend it, so that foundational work is a decision and not whatever happens to be left over. Zero is a decision too, and it has a date on which it fails.
2. The roadmap is bets, not promises. Near-term commitments are firm. Directional bets carry confidence levels. Both are framed as outcomes. A roadmap presented as dated promises is a list of future disappointments.
3. Argue foundations in business terms. Platform investment is justified by what its absence costs in velocity, incidents and features that cannot be built. Engineering aesthetics are no justification.
4. Admission is by outcome contribution. An initiative gets onto the roadmap by its expected contribution to stated outcomes, weighed against cost and risk. Which team wants it, or which stakeholder asked last, does not count.
5. Say what is not being done. The non-goals tell a reader more than any other section of a roadmap, and they are the section most often missing.
6. Long bets are staged, protected, and funded by subtraction. A multi-year platform investment needs intermediate value where possible, an honest estimate of the near-term sacrifice, secured commitment before it starts, and a defence against the quiet nibbling of "temporary" reallocations. An existential new priority is funded by explicitly clearing something out. Adding it to everyone's full plate does not fund it.

Roadmapping is practitioner work. One of the biases underneath it has a research literature, and is graded accordingly.

Explicit capacity allocation practice

This is a discipline, not a named model, and the unit treats it as fundamental: a stated fraction of capacity for platform, reliability and debt, held under pressure. It has no author. Every organisation that keeps its platform alive has arrived at it. Without it the trajectory is predictable. Feature pressure consumes everything until velocity collapses, and then the platform gets a crisis budget that costs more than the standing share would have.

The three horizons practice

Mehrdad Baghai, Stephen Coley and David White, The Alchemy of Growth: Practical Insights for Building the Enduring Enterprise (1999) offers this framework for balancing a portfolio over time. It separates the current business, the emerging businesses that will matter in a few years, and the options that might disrupt everything. Applied to an engineering roadmap it becomes an executive question: how much capacity serves today's product, how much builds the platform the strategy needs in two years, and how much explores. The exact proportions depend on context. The value lies in making the mix of horizons an explicit decision, owned at executive level, so that it is not an accident of whoever shouted loudest this quarter.

Sunk-cost discipline research

Hal R. Arkes and Catherine Blumer, The Psychology of Sunk Cost (1985) found that people keep investing in a course of action because of what they have already spent, even when the forward-looking comparison says stop. In roadmapping this governs the half-done migration, the championed bet and the legacy team funded by inertia. Money already spent argues for nothing. The only thing that counts is the value remaining against the cost remaining, compared with the alternatives. The opposite error also happens: abandoning a sound long bet the moment a fashionable alternative appears. What separates the two is that changed fundamentals justify switching and novelty does not. SV-4 Engineering economics covers the general case.

Staged bets and checkpoints practice

This is a practice, not a named model. A long investment is structured to deliver intermediate value where it can, to state its near-term cost honestly, and to include explicit checkpoints for doubling down or folding. That structure is how a two-year platform bet survives a quarter's urgency. It is also how a bet on a disruptive technology is sized to teach, since a bet too small to matter and one too big to survive being wrong are both errors.

The stated balance

The team's capacity split between features, platform and reliability, and debt is written down as percentages, agreed with the product partner and reviewed each quarter. When pressure arrives, the conversation is about changing the number, explicitly and for a stated period. Whether the platform work can wait just this once is not the question on the table.

The investment case in business terms

Any platform investment larger than a sprint is argued as a business case. It covers what the absence of the work costs now (incidents, cycle time, blocked features), what it enables, and what happens if the current trajectory continues. It uses numbers where they exist and names its assumptions where they do not. Engineering elegance has no place in it.

Admission criteria

A department roadmap comes with a written statement of how initiatives get onto it: expected contribution to stated outcomes, cost, risk and dependencies. A request that does not meet the criteria is answered by pointing to the criteria, which is different from a no.

Reading over-commitment from flow

The signs are mechanical and are checked monthly. Everything is in progress and nothing is finishing; there is no capacity for the unplanned; dates are missed in bulk; there is no slack for discovery. If any of them is present, the answer is to cut work. Exhortation will not help.

The mandate check

Every standing investment, such as an internal tools team or a long-running platform group, should be able to state its strategic value and how its success is measured. One that cannot is assessed against the strategy. It gets a clear mandate if the value is real, and its people are redeployed if it is not. Another year of funding because it has always existed is not on the list of options.

Leading a sunset

Retiring a product line that the teams built and love has to be led. That means giving the honest rationale, respecting what the work achieved, and laying a deliberate path for the people and for the users. The failure is to strangle it quietly by cutting its funding.

At team scope the manager is responsible for one team's roadmap and its platform debt, and holds the stated balance against pressure. At organisational scope the roadmap becomes a portfolio with admission criteria. Over-commitment is read from flow signals and corrected by cutting, chronic drains such as unplanned work are made visible and gated, and every standing investment has to state its mandate. At executive scope the question becomes the balance of horizons: how much capacity serves the current business, how much builds the platform the strategy needs, and how much explores. Long bets are staged, committed to before they start and defended from erosion, and existential priorities are funded by explicit subtraction. The pattern is in How Judgment Scales, and ranking the portfolio is covered in DE-1 Prioritisation under constraint.

• Protects a stated share of capacity for foundational work and holds it under pressure. team
• Justifies platform investment in business terms. team
• Presents the roadmap as adaptable bets with confidence levels instead of dated promises. team
• Names what is deferred and what is not being done. team
• Failure mode: feature pressure consuming all capacity until velocity collapses. team
• Failure mode: gold-plating the platform. team
• Failure mode: roadmap as promise. team
• Failure mode: infrastructure justified purely on engineering grounds. team
• Admits initiatives to the department roadmap by outcome contribution against cost and risk. org
• Reads over-commitment from flow signals and corrects it by cutting. org
• Makes chronic unplanned work visible, gates and owns intake, and either budgets explicit interrupt capacity or routes the rest into planning. org
• Requires every standing investment to state its mandate and success measures. org
• Leads a sunset with honesty and respect, and with a path for the people. org
• Failure mode: a roadmap that is the union of stakeholder requests. org
• Failure mode: treating chronic unplanned work as weather. org
• Failure mode: legacy teams funded by inertia. org
• Failure mode: sunsets communicated as an afterthought. org
• Owns an explicit mix of time horizons at executive level. exec
• Stages a long platform bet for intermediate value, sizes the near-term sacrifice honestly, and secures real commitment before starting. exec
• Makes the case for a long investment again, in current business terms, when short-term pressure threatens it; offers staged options; refuses the quiet nibbling of "temporary" reallocations. exec
• Sizes a bet on a disruptive technology to teach, with explicit checkpoints to double down or fold. exec
• Funds an existential new priority by explicitly clearing something out instead of adding it to everyone's plate (see TJ-5 AI-assisted engineering). exec
• Failure mode: endless near-term optimisation while the platform ages into a crisis. exec
• Failure mode: long bets launched without secured commitment. exec
• Failure mode: token innovation spend. exec
• Failure mode: adding the existential priority as everyone's tenth job. exec

Now versus later. Every unit of capacity spent on the platform is a unit not spent on visible value this quarter. Every unit spent on features is borrowed from a future that will send the bill with interest. The stated balance resolves this. The judgment is in choosing the number, and in changing it explicitly instead of letting it erode.

Commitment versus adaptability. Stakeholders want the roadmap to be a promise, and reality makes it a forecast. Separating near-term commitments from directional bets, and labelling which is which, lets both be true.

Admission criteria versus relationships. A roadmap with criteria turns down requests from people the manager needs. A roadmap without them becomes the union of their wishes. When the criteria are applied visibly and explained in the requester's terms, a refusal is about the work and leaves the relationship intact.

Persistence versus sunk cost. A long bet needs protecting from every quarter's urgency, and a bad bet needs stopping whatever has been spent on it. What separates the two is whether the fundamentals have changed, along with the honesty to apply that test to a bet one has championed.

Focus versus exploration. Capacity spent exploring what might disrupt everything is capacity taken from what pays today, and an organisation that never explores gets disrupted by one that did. The mix of horizons should be decided, never left as whatever remains, and on both sides the failure is letting it happen by accident.

A team's manager is in quarterly planning with their product partner. Over two quarters the team's velocity has fallen by a third. The cause is known. Every feature touches a data layer that nobody has had the capacity to fix, so each feature now costs more and breaks more. The product partner's roadmap for the coming quarter takes up the whole team, and they have said, reasonably from where they sit, that the business cannot afford any reduction in feature output this quarter.

One pull is to agree and hope: accept the full feature roadmap, promise to fit the data-layer work in "around the edges", and watch it fail to happen for a third quarter. The other is to declare a quarter of technical debt, which the business cannot afford and the partner will not accept.

The manager makes the case in the partner's terms. They show what the data layer costs now: cycle time up by a third, two incidents last quarter traced to it, and one roadmap feature that could not be built as specified because of it. They show the trajectory: at the current rate of decay, next quarter's roadmap will deliver less than this quarter's with the same headcount. Then they propose a stated balance in place of a pause. For the next two quarters, 25% of the team's capacity goes to the data layer. The work is staged so that the first six weeks deliver the change that unblocks the feature the partner wants most. The feature roadmap is worked out again to fit what the remaining 75% can deliver, and the partner chooses what moves.

The partner pushes back on the 25%. The manager keeps the number and changes the period instead: two quarters at 25%, then back to a standing 15%, reviewed quarterly. They also name what the team will not do. Two lower-priority features are deferred explicitly, so nothing is quietly dropped and the roadmap's non-goals are visible.

The partner agrees. The case was made in terms of delivered outcomes instead of engineering health, and the first stage delivers something the partner wanted. The manager did not accept the full roadmap and try to fit the platform work around it, because that decision produced the last two quarters.

• SV-1 Engineering strategy: the strategy for which the roadmap is the current sequence of bets.
• DE-1 Prioritisation under constraint: ranking the portfolio, and finishing fewer things.
• SV-4 Engineering economics: the economics of an investment case, and sunk cost in full.
• TJ-2 Technical debt: technical debt as the platform investment most often deferred.
• TJ-5 AI-assisted engineering: the existential AI priority, and funding it by subtraction.

1. What happens to a team with zero capacity allocated to platform and debt?
   Answer

   Velocity decays under accumulating debt and toil until it collapses. At that point the platform gets a crisis budget that costs more than a standing share would have. Zero is a decision, and it has a date on which it fails.
2. How is a platform investment argued to a product partner?
   Answer

   In business terms. The case covers what the absence of the work costs now (cycle time, incidents, features that cannot be built), what the work enables, and the trajectory without it. Engineering elegance has no place in it.
3. Name three flow signals of an over-committed department roadmap, and what correcting them requires. org
   Answer

   Everything in progress and nothing finishing; no capacity for the unplanned; dates missed in bulk. A fourth is no slack for discovery. Correcting them requires cutting work, and exhortation will not do it.
4. A long-running internal tools team cannot state its strategic value. What does it get? org
   Answer

   An assessment against the strategy. If the value is real, it gets a clear mandate and success measures; if it is not, its people are redeployed. It does not get another year of funding because it has always existed.
5. Why does a two-year platform bet need staged value and explicit executive commitment before it starts? exec
   Answer

   Without intermediate value, "temporary" reallocations made under each quarter's pressure will nibble it to death. Without secured commitment, it starts on borrowed patience that runs out before it delivers.
6. How is a disruptive-technology bet sized? exec
   Answer

   To teach. It should be big enough to build real capability and learn fast, with explicit checkpoints to double down or fold. A bet too small to matter and one too big to survive being wrong are both errors.
7. An existential capability must be built and the organisation is full of committed work. What is the funding move? exec
   Answer

   Explicit subtraction: clear something out to pay for focused bets and capability-building. Piling the priority onto everyone's full plate makes it everyone's tenth job and nobody's first.

• Mehrdad Baghai, Stephen Coley and David White, The Alchemy of Growth: Practical Insights for Building the Enduring Enterprise (1999): the three horizons of a portfolio.
• Hal R. Arkes and Catherine Blumer, The Psychology of Sunk Cost (1985): the psychology of sunk cost.