Business
Direction, value creation, customer needs, products, and the operating model.
- Strategy
- Value streams
- Business design
Business capability framework
Capabilities that Move Business Forward
A business capability is an enduring ability an organization needs to perform, manage, improve, or change work. This page explains that model. It is not a list of approved services.
The foundation
What is a business capability?
A business capability is an enduring ability an organization needs to perform, manage, improve, or change work.
It is supported by the relevant combination of people, process, information, technology, governance, and resources. The ability can stay stable when tools, teams, or projects change. A capability is not a service, a solution, or a guaranteed outcome.
A whole-business view
Several layers work as one system.
A business capability rarely sits within one team or tool. These layers are a shared way to see what may need to work together. A layer name is not an approved service.
People
Roles, skills, leadership, and the capacity required to deliver priorities.
- Workforce
- Skills
- Learning
Technology
Applications, platforms, infrastructure, and tools that enable work.
- Applications
- Cloud
- AI and automation
Data
Information assets, data practices, and insight used to make decisions.
- Data quality
- Analytics
- Information access
Operations
Processes that carry plans into repeatable work.
- Process design
- Service operations
- Continuity
Governance
Decision rights, controls, accountability, and oversight for responsible performance.
- Risk
- Compliance
- Performance
Partner Ecosystem
External providers and collaborators that contribute to a capability where appropriate.
- Dependencies
- Interfaces
- Shared responsibilities
Explore the framework
A map for seeing the whole system.
Select a layer to move to its place in the framework. The map is a starting point for discussion, not a fixed organization chart.
Capabilities can cross functions, business units, and external boundaries. Their scope should reflect the intended outcome under consideration.
Connected by design
Change in one capability affects others.
A change in technology may affect process, roles, information needs, and controls. Those relationships can run in more than one direction. Seeing them shows the scope of a question before a response is chosen.
Start with the need
Business challenges point to capability questions.
A challenge is a useful entry point, not a preferred tool. The useful response depends on the cause, what already exists, and the work the organization needs to perform, manage, improve, or change.
Growth or a new directionConsider business design, workforce capacity, technology, data, and partner dependencies.
Technology or AI adoptionConsider architecture, data readiness, security, operating processes, and skills.
Operational complexity or cost pressureConsider process design, service operations, automation, and governance.
Risk, compliance, or continuity concernsConsider accountability, controls, data practices, resilience, and execution capacity.
Skills or capacity gapsConsider role design, workforce planning, learning, technology, and how work is organized.
Connect capability to purpose
Capabilities matter when they support an intended outcome.
Start with the change that matters to a defined stakeholder. Then identify capabilities that may contribute, and how that change could be observed. An intended outcome is not a measured result until evidence and attribution are defined.
People + learning
Can support role readiness, skill development, and more informed workforce planning.
Technology + data
Can support access to useful information, connected platforms, and better-grounded decisions.
Process + operations
Can support consistent execution, service continuity, and clearer process ownership.
Governance + compliance
Can support accountable decisions, defined controls, and visibility of obligations.
These are possible contributions, not guaranteed outcomes. The relationship should be assessed against the organization’s context and evidence.
Capability assessment
Build a shared view before choosing a response.
In this framework, an assessment is a structured evaluation against agreed criteria, using available evidence and stated limitations. This description is not an approved assessment service, a certification, or a universal score.
Align
Set the business question, scope, stakeholders, and intended use of the findings.
Map
Describe relevant capabilities, interfaces, dependencies, and current evidence.
Assess
Compare the current state with agreed needs; record assumptions and limitations.
Prioritize
Identify options and sequence decisions around value, feasibility, and risk.
Findings support decisions. They do not imply a score, benchmark, or outcome unless those measures are explicitly defined and supported by evidence.
Plan for change
Capabilities evolve with the business.
A capability definition should stay stable while operating needs and evidence change. Future options remain choices until they are validated. They are not commitments.
CurrentUnderstand how the organization works today, including strengths, constraints, dependencies, and evidence gaps.
EmergingTrack changes in strategy, customer expectations, technology, regulation, and operating conditions.
FutureExplore scenarios and options, then validate priorities before treating them as commitments.
Make the next decision with context
Discuss Your Capability Strategy
Share the business question you are working through. We can explore the capabilities involved and what a useful next step could be.
Discuss a Business Need