Monthly FTE demand
Stack active initiative demand over time and compare the total with a visible capacity line.
Capacity and strategic feasibility
Resource-aware roadmapping software
Put FTE and budget constraints into the roadmap conversation so sequencing and priorities can change before commitments exceed capacity.
Designed for
A shared planning surface for the people who hold different parts of the answer.
- Portfolio leaders
- Strategy teams
- Finance partners
- Resource owners
The practitioner problem
Every roadmap eventually meets a capacity limit
Roadmaps are often developed around strategic attractiveness and reconciled with capacity later. By that point, dates and initiatives may already have acquired political commitment even though the organisation cannot deliver them together.
Resource-aware roadmapping makes feasibility visible while choices are still open. Monthly FTE demand can expose periods where too many initiatives need the same people. Cumulative budget can show when the planned pathway crosses an investment boundary.
The numbers will be uncertain, especially for early initiatives. Their purpose is not to manufacture precision. Their purpose is to surface assumptions, reveal incompatible plans and support explicit choices about sequencing, scope, partnership and stopping.
Decision structure
Questions the roadmap needs to connect
The useful unit is not an isolated item. It is an item whose purpose, evidence, relationships and implications can be examined.
- 01
Which capacity pool does each FTE estimate draw from?
- 02
Is budget recorded as a total or a recurring monthly amount?
- 03
Which roadmap swimlanes or business areas should be included?
- 04
Which linked initiatives share the same enabling work?
- 05
Where are values missing, stale or based on weak assumptions?
- 06
Which combination of moving, reducing, partnering or stopping restores feasibility?
Working cycle
Move from framing to a governed roadmap
- 01
Define the resource model
Agree what FTE and budget values mean, which time interval applies and where portfolio caps come from.
- 02
Estimate transparently
Add values to roadmap items and retain the source, confidence, owner and update reason behind each estimate.
- 03
Inspect different scopes
Compare all swimlanes, selected areas, own initiative demand and the unique footprint of linked dependencies.
- 04
Change the roadmap
Use the constraint to revise sequencing, scope, sourcing or priorities, then record why the decision changed.
Worked structure
Illustrative example: a shared data capability
Three product initiatives depend on a common data platform. A resource-aware view can distinguish:
- The FTE and budget owned directly by each product initiative
- The common platform investment connected upstream
- The unique linked footprint without counting the platform three times
- The months where engineering demand exceeds available capacity
- The sequencing choices that become possible when the shared dependency is visible
This is an invented example. It demonstrates why linked totals need deduplication and why a capacity breach should lead to a decision, not merely a red chart.
What the software should preserve
Keep the strategic logic usable between reviews
Cumulative budget
Spread item budgets across active periods and compare cumulative portfolio spend with an agreed cap.
Swimlane filtering
Focus the resource view on selected technologies, products, programmes or other roadmap areas.
Linked footprint
Compare own resources with unique connected demand so shared dependencies are not counted repeatedly.
Research and practice basis
Claims that can be traced
These sources support the roadmapping method and practitioner problem. They are not evidence that software alone produces successful outcomes.
Implementation research treats resource allocation as part of the technology roadmapping process, not as an unrelated calculation after the roadmap has been created. [1]
The published ABB and IfM Engage energy-management work describes reviewing resources and capabilities as part of developing purposeful change pathways. [2]
T-Plan also frames implementation and keeping the roadmap alive as part of the roadmapping challenge, which makes review of changing capacity and assumptions essential. [3]
- [1]Gerdsri, N., Vatananan, R.S. and Dansamasatid, S. (2009). Dealing with the dynamics of technology roadmapping implementation: A case study. Technological Forecasting and Social Change, 76(1), 50–60. Source ↗
- [2]ABB and IfM Engage (2022). Institute for Manufacturing at the University of Cambridge teams up with ABB to lead the future of energy management. ABB global press release. Source ↗
- [3]Phaal, R., Farrukh, C.J.P. and Probert, D.R. (2001). T-Plan: The fast start to Technology Roadmapping - planning your route to success. Institute for Manufacturing, University of Cambridge. Source ↗
Continue exploring
Method, evidence and connected capabilities
Resource-aware roadmapping
Read the Strategy Atlas explanation of capacity, uncertainty and false precision.
Open resourceRoadmapping software
See how resources fit with dependencies, evidence, history and table views.
Open resourceWhy roadmaps die after the workshop
Explore the governance problem behind maintaining a credible roadmap.
Open resourceFrequently asked questions
Questions about this roadmapping use case
How is FTE represented in the roadmap?
Each roadmap item can carry an average monthly FTE value. Active items are stacked across their date ranges and compared with a portfolio capacity value.
Can resource charts focus on selected roadmap areas?
Yes. Swimlane filters can isolate areas such as technologies, products or programmes, while own and linked modes change which connected initiatives contribute to the total.
Should early estimates be treated as commitments?
No. Early estimates should remain identifiable as estimates and be reviewed as evidence develops. Their immediate value is exposing trade-offs and missing assumptions.
Build a roadmap that survives the next decision.
Explore InnovationFlow free for 30 days, or discuss the structure, facilitation and governance of your roadmapping process with a practitioner.