By Daniel Lambert

​​​​​​

Organizations invest significant time defining strategies, establishing priorities, and setting ambitious business objectives. They also spend considerable effort preparing annual budgets and deciding which projects and initiatives should receive funding.

​

Yet strategy and budgeting are often managed through separate processes. Strategy defines where the organization wants to go, while budgeting determines where the money goes. When the connection between the two is weak, organizations can end up funding projects that have compelling individual business cases but make limited contributions to their most important strategic priorities.

​

Business capabilities can provide the missing link, as shown in Figure 1 above. A capability-based budgeting approach connects strategic objectives to the business capabilities required to achieve them, identifies gaps in those capabilities, and directs investments toward the improvements that will generate the greatest business value. It creates end-to-end traceability:

​

Strategy → Business Outcomes → Business Capabilities → Capability Gaps →

Investment Priorities → Initiatives → Budget → Measurable Outcomes

​

Rather than asking only, "Which projects should we fund?", executives can ask a more fundamental question:

​

"Which business capabilities must we strengthen to execute

our strategy, and where should we invest to strengthen them?"

​

1. The Missing Link Between Strategy and Budget

​

Most organizations do not intentionally disconnect strategy from investment. The disconnect often results from how planning and budgeting processes have evolved. Enterprise strategy may be established by executives, while budgets are developed by business units, functions, cost centers, programs, or technology departments. Each group submits investment requests according to its responsibilities and priorities.

​

This creates several challenges. Investments become associated with organizational ownership rather than enterprise priorities. An initiative may be classified as a finance, operations, marketing, or IT project even though the business capability being improved crosses multiple organizational boundaries.

​

Executives can also be confronted with dozens or hundreds of competing investment proposals without a consistent way to compare their contribution to strategy. Technology investments are particularly susceptible to this problem. Discussions can quickly focus on replacing applications, implementing AI, modernizing infrastructure, migrating to the cloud, or adopting new platforms rather than the business outcomes these investments are intended to achieve.

​

Organizational structures also change. Executives move, departments are reorganized, projects end, and technologies are replaced.

​

Business capabilities are comparatively stable.

​

This makes them useful anchors for connecting strategy with investment planning. Instead of beginning with projects and determining which strategic objectives they might support, organizations can reverse the process:

​

Strategy → Required Capabilities → Capability Gaps → Investment Priorities

​

This puts strategy at the beginning of the investment decision rather than using it later to justify a proposed project.

​

2. What Is Capability-Based Budgeting?

​

A business capability describes what an organization must be able to do to deliver value or achieve a business outcome. Examples include Customer Management, Product Development, Supply Chain Management, Fraud Management, Regulatory Compliance, Workforce Management, and Financial Management. Capability-based budgeting uses these capabilities as a business-oriented structure for investment decisions.

​

This does not mean simply allocating existing costs to capabilities. Understanding the cost of a capability can certainly be valuable, but capability-based budgeting goes further by establishing traceability between strategic objectives, capability requirements, investments, and expected outcomes.

​

Consider an organization whose strategy includes substantially increasing customer retention. A traditional planning process might produce several independent investment proposals:

​

• Replace the CRM platform.

• Implement customer analytics.

• Improve contact-center technology.

• Automate customer-service processes.

• Provide additional employee training.

​

Viewed independently, these initiatives compete for funding. A capability-based approach starts differently. It asks instead, “Which capabilities are necessary to improve customer retention?” They might include Customer Insight, Customer Relationship Management, Customer Experience Management, Customer Service Management, and Customer Analytics.

​

The organization can assess those capabilities, identify weaknesses, and determine which combination of people, process, information, application, and technology improvements is required. The investment discussion therefore changes from:

"We need $3 million to replace our CRM platform."

to:

"Customer Relationship Management is strategically critical but is currently

unable to support our targeted customer-retention outcomes.

These investments address the identified capability gaps."

​

The second statement provides considerably more context for an investment decision.

​

3. Identify the Business Capabilities That Enable the Strategy

​

Capability-based budgeting should always begin with strategy, not with the capability map.

Organizations should first identify their most important strategic objectives and the measurable business outcomes associated with them. Typical objectives might include:

​

• Increase customer retention.

• Enter new geographic markets.

• Reduce operating costs.

• Accelerate product development.

• Increase digital revenue.

• Improve regulatory compliance.

• Improve supply-chain resilience.

​

Each objective depends on a particular combination of business capabilities. Enterprise and business architects can map strategic objectives to the capabilities required to achieve them. Some capabilities will have a direct and critical relationship with a strategic objective, while others will provide supporting functions.

​

The result can be represented through a strategy-to-capability heatmap. This exercise is important because organizations may have hundreds of documented business capabilities. Attempting to improve all of them simultaneously is neither practical nor financially responsible. Only a subset will usually require significant investment during a particular strategic planning cycle.

​

For example, an organization pursuing aggressive digital growth might identify Digital Channel Management, Customer Analytics, Personalization, Product Management, and Customer Identity Management as strategically critical.

​

Facilities Management may remain necessary for the organization to operate but require little transformational investment. This distinction allows management to separate capabilities that must simply operate effectively from those that must become sources of strategic advantage or transformation.

​

Business capabilities also create a common vocabulary between executives, finance, business leaders, portfolio managers, and technology teams. Each group can examine investments through the same business-oriented structure.

​

4. Assess Capability Maturity, Performance, and Gaps

​

Strategic importance alone should not determine investment. A highly strategic capability that already performs exceptionally well may require relatively little incremental investment. Conversely, a strategically important capability performing substantially below the required level may warrant significant funding.

​

Organizations therefore need to understand both the strategic importance and the current condition of their capabilities. A capability assessment can examine several dimensions:

​

• Business performance: Is the capability producing the expected outcomes?

• Maturity: How developed, standardized, measured, and governed is it?

• Processes: Are processes efficient, consistent, and appropriately automated?

• People: Does the organization have the required skills, capacity, roles, and expertise?

• Information: Is required information accurate, available, timely, and properly governed?

• Applications: Do existing applications adequately enable the capability?

• Technology: Is the underlying technology secure, resilient, scalable, and cost-effective?

• Risk and compliance: Does the capability create unacceptable operational, cybersecurity, regulatory, or financial exposure?

​

The objective is to compare the current state with the required future state. 

 

For example, Customer Analytics might currently operate at maturity level 2 on a five-level scale. Based on the organization's strategy, management determines that level 4 is required. That difference represents a capability gap. But knowing that a gap exists is not enough. Architects and business leaders need to understand why it exists.

​

Poor capability performance might result from outdated technology, but it could equally result from fragmented processes, inadequate data, insufficient skills, unclear accountability, or ineffective governance. Buying another application will not necessarily solve those problems. A capability assessment helps organizations diagnose the actual problem before committing significant investment.