Capability-Based Planning
What is Capability-Based Planning?
Capability-based planning is an approach to strategic and investment planning that organizes decisions around the business capabilities an organization needs to improve, rather than around individual projects or departments.
Updated November 2026 · 5 min read
Capability-based planning starts with a simple question: which capabilities must the organization improve to achieve its strategy? Instead of evaluating dozens of separate project requests, leaders first agree on the capabilities that matter most and the level of performance each needs. Projects are then judged by how much they improve those capabilities. The approach grew out of defense planning, where it was used to decide which military capabilities to develop, and has since been widely adopted in enterprise architecture.
The approach brings discipline to investment decisions. Projects that do not improve a priority capability are hard to justify, while several projects affecting the same capability can be coordinated or combined. Because capabilities are stable and understood by business leaders, the conversation stays focused on business outcomes rather than technology details. For IT strategy and finance, capability-based planning links budgets directly to the strategic priorities they are meant to serve.
Definition of Capability-Based Planning
Capability-based planning is a planning method that uses business capabilities as the unit for setting priorities, allocating investment and measuring progress. It relies on a business capability model that defines each capability and records its current and target performance.
TOGAF describes capability-based planning as a technique for linking architecture work to business planning, and it is widely used alongside IT portfolio management.
Key Concepts
Current maturity describes how well a capability performs today, often on a scale from one to five covering people, process, information and technology. Assessing all four dimensions matters, since a capability with strong technology but untrained people or poor data will still perform badly.
Target maturity describes the level the capability needs to reach to support the strategy. The difference between current and target is the capability gap. Not every capability needs to reach the highest level, and setting realistic targets prevents overinvestment in areas that are good enough.
Increments are stages of improvement, each delivered by one or more projects, that move a capability toward its target over time. Each increment should produce a measurable improvement, so that progress is visible before the target is reached.
Capability owners are business leaders accountable for each capability's performance and for the investments that improve it.
How It Differs From Project-Based Planning
In project-based planning, each project competes for funding on its own merits, often with little connection to other projects or to strategy.
In capability-based planning, funding is first allocated to priority capabilities, then to the projects that improve them. Projects are compared within the context of the capability they affect.
This shift makes it easier to see when several projects target the same capability, when a priority capability has no projects at all and when projects improve capabilities that are not priorities. It also changes the conversation with business leaders from defending individual projects to agreeing on outcomes.
Importance of Capability-Based Planning in Enterprise Architecture
Capability-based planning connects strategy to investment. Every funded project can be traced to a capability and every capability to a strategic goal.
It reduces fragmented spending. Coordinating projects by capability reveals overlaps and dependencies that separate project reviews would miss. It also exposes capabilities that receive steady funding year after year without measurable improvement.
It also improves measurement. Progress is tracked by changes in capability performance, which is closer to business outcomes than measures such as projects completed on time.
Linking Capabilities to Budgets
When technology costs are mapped to capabilities, leaders can see current spending on each capability alongside its strategic importance and maturity gap.
This supports deliberate shifts in spending, such as reducing investment in mature, low-priority capabilities to fund improvements in critical ones.
Finance teams can build budgets by capability, with run costs and change investment shown separately. Frameworks such as run, grow, transform can be applied within each capability.
Over time, comparing investment with maturity gains shows which capabilities have improved most for the money spent.
Common Challenges
Maturity assessments can be subjective. Clear criteria and input from several people improve consistency. Supporting evidence, such as cycle times, error rates or customer measures, makes ratings more credible.
Many projects affect several capabilities, which complicates allocation. Most organizations assign each project a primary capability and record secondary effects separately.
Shifting from project-based to capability-based funding requires changes to budgeting processes and to the way business leaders request investment, which takes time and executive support.
How to Implement Capability-Based Planning
Implementing capability-based planning involves building the capability model, assessing maturity, setting priorities and targets, and organizing investment around them.
Many organizations start by applying the approach to one planning cycle or one business area before extending it.
Assessing and Prioritizing
Build or adopt a business capability map at levels one and two, with a definition and owner for each capability.
Assess the current maturity of each capability using agreed criteria, and set target maturity levels based on the strategy.
Identify the priority capabilities with the largest gaps between current and target maturity. Map current spending to capabilities so leaders can see where money goes today.
Planning and Funding
Ask capability owners to propose increments and projects that will close their capability gaps, with costs, benefits and timing. Owners should also state how they will measure improvement, so that results can be checked after delivery.
Allocate funding to priority capabilities first, then select projects within each, coordinating those that share dependencies.
Track capability maturity, spending and project progress, and review priorities each planning cycle. Reassess maturity after major increments are delivered, rather than waiting for the annual cycle. Feed the resulting plan into the enterprise architecture roadmap.
Examples of Capability-Based Planning in Enterprise Architecture
The examples below show capability-based planning shaping investment.
Both use illustrative figures. The first redirects a technology budget, and the second coordinates overlapping projects.
In each, organizing decisions by capability made trade-offs clearer.
Redirecting a Budget
A logistics company's strategy focuses on real-time tracking and dynamic pricing. A maturity assessment rates both capabilities at level two, with a target of level four.
Mapping spending shows that these two capabilities receive $3 million of the $40 million change budget, while internal reporting, rated level three with a target of three, receives $6 million.
The next plan reduces internal reporting investment to $2 million, trims several other low-priority capabilities by a combined $2 million and raises investment in the two priority capabilities to $9 million, within the same total budget.
Coordinating Overlapping Projects
A university receives 14 project requests in one planning cycle, five of which affect student onboarding.
Reviewing them by capability shows that the five projects overlap significantly and depend on the same student records system.
The university combines them into one program with a single owner, reducing the combined estimate from $4.6 million to $3.1 million and avoiding conflicting changes to the student records system.
Conclusion
Capability-based planning organizes strategic and investment decisions around the business capabilities an organization needs to improve. It uses current and target maturity, capability gaps, increments and capability owners to guide funding.
In enterprise architecture, capability-based planning connects strategy to investment, reduces fragmented spending and measures progress in business terms. Building a capability model, assessing maturity consistently, prioritizing the largest gaps, allocating funding by capability and tracking results help organizations invest in the capabilities their strategy depends on.
Related terms
Business Capability Model
A business capability model is a structured, defined set of an organization's capabilities, with their hierarchy, descriptions and relationships, used as a stable reference for planning, analysis and investment decisions.
TOGAF
TOGAF, The Open Group Architecture Framework, is a widely used enterprise architecture framework that provides a method, called the ADM, along with guidance and standard deliverables for developing and managing architectures.
IT Portfolio Management
IT portfolio management is the practice of managing an organization's technology investments, including projects, applications and infrastructure, as a single portfolio balanced against strategy, value, cost and risk.
Business Capability Map
A business capability map is a structured view of everything an organization must be able to do to carry out its strategy, organized into levels and independent of who performs the work or how.