When roadmaps meet budgets
Connect strategic priorities to funding decisions when resources sit in separate budget pots.
A technology team can produce a thoughtful roadmap while investment decisions continue to follow departmental budgets. The roadmap describes what the organisation needs; the funding process determines what it can actually do. The connection between them deserves explicit attention.
This is one of the discrepancies Clemens Chaskel has highlighted from his roadmapping and innovation-management experience. His IfM Engage article with John Saiz also discusses the need to connect innovation to business goals and carry strategy through into implementation.
Follow one priority into a real decision.
Start with a priority that depends on more than one team. Trace its route from the roadmap into a business case, a funding decision and a delivery commitment. At each step, ask who decides, what evidence they use and which constraints they can change.
A manufacturer wants to reduce customer downtime through remote diagnostics. Engineering can fund the sensor work, but the service team has no allocation for the data integration and support process. Engineering progresses its part; the intended service remains out of reach.
The issue is the dependency between the investments. Funding one component does not fund the outcome. A joint review could consider the whole service, a smaller trial, a revised sequence or an explicit deferral.
A budget constraint can be legitimate. The useful question is whether it reflects an intentional trade-off against the strategic priority, and whether that choice is visible to the people maintaining the roadmap.
Bring the dependency into the funding conversation.
For each priority, record the intended outcome, the activities it depends on, the resources required and the owner of the investment decision. Include staffing and operational support: a project can have money and still lack the people needed to deliver it.
Then review what would be funded, delayed or stopped under different resource limits. Avoid a roadmap that assumes every initiative will proceed. Make the trade-offs visible and reflect the agreed decision back into the plan.
Use this in your next review.
- Which strategic outcome does this spending support?
- Which unfunded dependency could prevent that outcome?
- What other work would need to move, stop or wait?
- Who has authority to resolve the trade-off?
- Where will we record the decision and update the roadmap?
Leave with a decision, an owner and a review point. If the investment is deferred, record the reason and the conditions under which it should be reconsidered.
To carry this into a maintained plan, see the guide to resource-aware roadmapping and how R&D roadmaps connect investment and capability choices.