Comprehensive Guide

Capability-Based Planning Handbook

Capability-based planning aligns investments to business abilities—not projects alone. Map capabilities, assess heat, and fund roadmaps executives understand.

Executive Summary. Capability-based planning (CBP) prioritizes investments by identifying which business abilities need strengthening to execute strategy—not by loudest project sponsor or legacy maintenance inertia. This handbook explains capability mapping, heat assessment, investment categorization, and linkage to architecture roadmaps. Larkinized LLC enables finance and business leaders to participate in IT planning with shared vocabulary and transparent trade-offs.

What Capability-Based Planning Is

CBP organizes planning around business capabilities—stable building blocks of enterprise function—rather than org charts or project lists.

It answers: which capabilities must improve to achieve strategic goals, and what investments are required?

CBP integrates with EA, portfolio management, and financial planning cycles.

Without capabilities, strategies devolve into disconnected IT projects.

Building the Capability Model

Start from industry reference models tailored to your context—not blank slate workshops lasting months.

Three levels: L1 executive, L2 planning, L3 analysis optional.

Define capability outcomes and KPIs at L2 minimum.

Govern capability naming and ownership in repository.

Capability Heatmap

Matrix of capabilities vs. strategic importance and current performance with investment priority coloring.

Diagram: Capability Heatmap

Heat Assessment Techniques

Rate strategic importance (from strategy maps) and current performance (KPIs, maturity, risk).

Heat = gap between importance and performance—prioritize hot cells.

Use facilitated calibration sessions to avoid grade inflation.

Refresh heat before annual planning lock.

Investment Categories

Categorize investments: sustain, enhance, transform, retire per capability.

Sustain funding prevents collapse; transform funding drives strategy; retire releases cash.

Map projects and applications to capabilities—expose orphan projects.

Finance sees capability-aligned budget narratives.

Linking to Architecture Roadmaps

Capability gaps become architecture initiatives with target states and tranches.

Application and technology roadmaps roll up to capability outcomes.

Dependencies across capabilities sequence funding—identity before customer portal.

Roadmaps published with business KPI targets, not tech milestones alone.

Operating Cadence with Finance and BUs

Annual planning: capability heat refresh, investment proposals, executive committee decisions.

Quarterly: progress on capability KPIs and roadmap tranche status.

Business unit presidents co-own capability performance metrics.

Architecture facilitates; business decides trade-offs.

Tools and Data

Capability repository in EA tool or SPM platform with links to apps, projects, costs.

Import financial actuals where possible for cost-to-serve analysis.

Avoid duplicate capability models in Excel islands per BU.

Automate heatmap dashboards for executives.

Common Pitfalls

Capabilities too granular or synonymous with departments.

Heatmaps without KPI grounding become opinion polls.

Plans not funded—capabilities listed but projects unchanged.

Consultant-delivered models without internal ownership decay quickly.

Case Patterns from Larkinized LLC

Manufacturers link supply chain capabilities to IoT and ERP investments.

Insurers map product lifecycle capabilities to policy admin modernization.

Healthcare providers prioritize patient access capabilities for digital front door programs.

Patterns adapt to industry while method stays consistent.

Get Started

Pilot CBP on one strategic theme with 15–25 L2 capabilities.

Run heat workshop with BU and finance leaders; fund one enhance and one retire decision.

Contact Larkinized LLC for capability modeling and planning facilitation.

Key Takeaways

  • CBP invests in business capabilities—not project noise.
  • Use tailored reference models; three levels maximum for executives.
  • Heatmaps combine strategic importance with performance gaps.
  • Categorize spend: sustain, enhance, transform, retire.
  • Architecture roadmaps roll up to capability KPI outcomes.
  • Finance and BU leaders co-own capability performance.
  • Repository links capabilities to apps, projects, and costs.
  • Pilot on one strategy theme before enterprise-wide rollout.

Need Expert Guidance?

Larkinized LLC helps organizations design, govern, and execute enterprise architecture programs that deliver measurable business outcomes.

Scroll to Top