Capability Roadmap: Template, Maturity Heatmap and Worked Example
9 min read ยท 2026-10-25
A capability roadmap shows which business capabilities your organization will build or improve, in what order and through which initiatives, so it can deliver its strategy. A capability is what the business does, such as order management, demand forecasting or customer onboarding, regardless of who does it or which system supports it. The roadmap links each capability's current and target maturity to the projects that close the gap, with dates and owners.
Enterprise architects, strategy and transformation leads, and PMO heads use it to decide where to invest and to explain those choices to the executive team. The template below runs over 12 months in six phases. It includes how to score maturity, how to choose the few capabilities that matter most, a worked example and how to present the result in two slides.
The roadmap at a glance
Goal: Within 12 months, five priority capabilities move from their assessed maturity to an agreed target level, each through funded initiatives with a named business owner and a quarterly progress review. Duration: 12 months
Link strategy to capabilities (Weeks 1-3)
Start from the strategy so the roadmap answers the questions leadership is already asking.
- Collect the current strategy, annual goals and the main business outcomes leadership wants in the next two to three years.
- Interview four to six executives on the outcomes they own and what blocks them today.
- Write three to five strategic themes in plain language, such as faster order fulfillment or a single view of the customer.
- Agree on the scope: the whole enterprise, one business unit or one value stream.
Milestone: A one-page strategy brief with the strategic themes and scope, approved by the sponsor.
Build the capability map (Weeks 3-7)
Describe what the business does in a stable, shared structure.
- Draft level 1 capabilities (for example, Sell, Deliver, Serve, Manage Finance) and break each into level 2 capabilities.
- Name capabilities as nouns or noun phrases (Order Management, Supplier Onboarding), not as departments, systems or projects.
- Review the draft in workshops with business leads from each area and remove overlaps.
- Store the map in a shared place, such as an enterprise architecture tool, Visio, Miro or a PowerPoint slide.
Milestone: A reviewed capability map with level 1 and level 2 capabilities, each with a short definition and a business owner.
Assess current maturity (Weeks 7-11)
Score each capability on the same scale so gaps can be compared.
- Choose a simple 1 to 5 maturity scale and write what each level means for people, process, data and technology.
- Score each level 2 capability with its owner and one or two practitioners, using evidence rather than opinion.
- Rate each capability's importance to the strategic themes on a simple high, medium or low scale.
- Color the map as a heatmap: importance against the maturity gap.
Milestone: A capability heatmap with current maturity, importance and evidence notes for every level 2 capability.
Set targets and choose priorities (Weeks 11-14)
Decide which few capabilities to improve first and how far.
- Shortlist capabilities that are high importance with a large gap, and challenge any that leadership adds without evidence.
- Set a target maturity and a date for each priority capability, with what the target level will look like in practice.
- Check dependencies: a capability like Demand Forecasting may need Product Data Management to improve first.
- Pick five to seven priority capabilities for the next 12 months and park the rest with a review date.
Milestone: A priority list of five to seven capabilities with current level, target level, target date and dependencies, signed off by the executive sponsor.
Plan and sequence initiatives (Weeks 14-20)
Turn each capability gap into initiatives that can be funded and scheduled.
- List the changes needed per capability across people, process, data and technology.
- Group changes into initiatives, check them against projects already running and merge duplicates.
- Sequence initiatives by dependency and team capacity, and place them on a quarterly timeline.
- Write a short business case per initiative with outcome, rough effort, owner and the metric that proves progress.
Milestone: A capability roadmap with initiatives by quarter, each linked to a capability and a strategic theme, approved in the portfolio or investment review.
Deliver, measure and refresh (Weeks 20-52)
Run the initiatives and show capability progress, not just project status.
- Hand each initiative to a delivery owner and track it in the portfolio tool you already use, such as Jira, Azure DevOps or Smartsheet.
- Reassess the maturity of priority capabilities each quarter with the same scale and evidence rules.
- Hold a quarterly capability review with the sponsor: maturity change, metrics, blockers and reprioritization.
- Refresh the map and the roadmap once a year as part of strategic planning.
Milestone: Four quarterly reviews held, with maturity scores and outcome metrics reported for every priority capability.
Capability roadmap vs technology or product roadmap
A technology roadmap shows systems, platforms and upgrades over time. A product roadmap shows features for a product and its customers. A capability roadmap sits above both. It shows what the business must be able to do better, and only then which projects, systems or process changes will get it there.
That difference matters in the executive room. Leaders rarely care that the warehouse system moves to a new version in Q2. They care that the business can promise next-day delivery in more regions. A capability roadmap lets you say both in one view: the capability, its target level and the initiatives (including the system upgrade) that get you there.
How to score maturity without endless debate
Maturity scoring fails when each person uses their own idea of good. Write a one-line description for each level before any workshop, and score against four dimensions: people and skills, process, data and technology. A capability takes the lowest of its dimension scores or a simple average, as long as you use the same rule everywhere.
Ask for evidence for every score, such as a process document, a metric, a system report or a recent incident. Limit each capability to 15 minutes in the workshop. If people disagree by more than one level, note both views and settle it with data after the session.
- Level 1, ad hoc: done differently by each person, little documentation, mostly manual.
- Level 2, repeatable: basic process exists in some teams, results depend on individuals.
- Level 3, defined: one documented process across the organization, supported by systems.
- Level 4, managed: measured with agreed metrics, data is reliable, performance is reviewed.
- Level 5, optimized: improved continuously, largely automated, used as a strength in the market.
Example: a filled-in roadmap for a mid-size retailer
Picture a retailer with stores and a growing online channel. Its strategy has two themes: one view of the customer and reliable delivery promises. After the heatmap, five capabilities stand out as high importance with a large gap.
Notice the order. Product Data Management comes first because forecasting and order promising both depend on clean product data. Each quarter has a business owner and a checkable result, which keeps the roadmap from turning into a list of IT projects.
- Q1, Product Data Management, level 2 to 3 (owner: head of merchandising): one product data standard, data cleanup of top-selling items, a data steward per category. Milestone: product records meet the standard for the agreed item range.
- Q2, Customer Data Management, level 1 to 3 (owner: CRM lead): single customer record across store and online, consent rules agreed with legal. Milestone: matched customer records live in the CRM.
- Q2-Q3, Inventory Visibility, level 2 to 3 (owner: supply chain director): store stock feeds updated several times a day instead of overnight. Milestone: online channel shows store stock from the new feed.
- Q3-Q4, Order Promising, level 2 to 4 (owner: head of e-commerce): delivery dates based on real stock and carrier cutoffs. Milestone: promise accuracy measured weekly and reviewed monthly.
- Q4, Demand Forecasting, level 2 to 3 (owner: planning manager): forecasts by store and week using clean product data. Milestone: forecast accuracy reported for the pilot categories.
Who owns what
Every capability needs a business owner, not an IT owner. The business owner decides the target level, accepts the result and reports on it. IT, data and process teams deliver many of the changes, but they cannot judge whether the business is now able to do something better.
Keep the governance light. A quarterly review is enough for most organizations, with a monthly check inside the portfolio meeting for initiatives at risk.
- Executive sponsor: approves priorities and funding, settles conflicts between business units.
- Enterprise architect or strategy lead: owns the map, the maturity method and the roadmap view.
- Capability owners (business leads): set targets, provide evidence and accept results.
- PMO or portfolio manager: links initiatives to capabilities and tracks delivery status.
- Initiative or project managers: deliver the changes and report progress against milestones.
- Finance partner: checks business cases and tracks spending by capability.
How to present it to the executive team
Use two slides. The first is the heatmap: the capability map colored by maturity gap, with the priority capabilities outlined. Executives understand it in seconds and it shows why you chose those five, not the ones their own teams asked for. The second slide is the timeline: capabilities as rows, quarters as columns, initiatives as bars, and a marker for each target maturity date.
Leave out the full scoring detail and the list of every level 3 capability. Bring them as backup. End with the decisions you need: approval of the priority list, funding for the first two quarters and confirmation of the capability owners. In later reviews, show maturity movement and outcome metrics first, and project status only where it explains a delay.
How to build it in PowerPoint or a whiteboard tool
For the heatmap, draw level 1 capabilities as wide boxes in a row and stack their level 2 capabilities inside each one. In PowerPoint, use Insert, then Shapes, then Rectangle, and use the Align options on the Shape Format tab to keep the grid even. Fill each box with one of three or four colors that match the maturity gap, and add a small legend in a corner.
For the timeline, add a table with quarters as columns and priority capabilities as rows, then draw initiatives as rounded rectangles on top. Put a small diamond where each capability should reach its target level. In Miro or Mural, the same layout works with sticky notes for capabilities and connectors for dependencies. Keep one master file and update it after each quarterly review.
Common mistakes to avoid
- Naming capabilities after departments or systems ties the map to today's org chart, so name them for what the business does, such as Order Management.
- Mapping every capability down to level 4 takes months and stalls the roadmap, so stop at level 2 and go deeper only for priority capabilities.
- Scoring maturity on opinion alone sparks endless arguments, so define each level in advance and ask for evidence for every score.
- Trying to raise twenty capabilities at once spreads funding too thin, so pick five to seven priorities and park the rest with a review date.
- Letting IT own every capability turns the roadmap into a system plan, so give each capability a business owner who sets the target and accepts the result.
- Reporting only project status hides whether the business improved, so reassess maturity and outcome metrics for each priority capability every quarter.
Frequently asked questions
What is a capability roadmap?
It is a plan that shows which business capabilities will be built or improved over time, from what current level to what target level, and through which initiatives. It links strategy to investment decisions. Each capability has a business owner and a target date.
What is the difference between a capability map and a capability roadmap?
A capability map is a static picture of everything the business does, grouped in levels. A capability roadmap adds time and change: which capabilities you will improve, in what order, how far and through which projects. You usually build the map first, then the roadmap.
How do you prioritize capabilities?
Score each capability on its importance to the strategy and on the gap between current and target maturity. Prioritize those with high importance and a large gap. Then check dependencies, because some capabilities must improve before others can.
Who should own a capability roadmap?
The enterprise architect or strategy lead usually owns the roadmap and the method. Each capability on it is owned by a business leader who sets its target and accepts the result. An executive sponsor approves priorities and funding.
How often should a capability roadmap be updated?
Review progress every quarter and refresh the full map and priorities once a year, ideally during annual planning. Update sooner if the strategy changes, for example after an acquisition or a new market entry.