Business Capability Map Audit Worksheet

Purpose

Feeds into capability map improvement roadmaps, governance framework updates, and business case development for platform investments or consulting engagements.

How to Use

Schedule a 90-minute workshop with your core business architecture team and 2-3 capability owners. Before starting, gather your current capability map, recent heat maps, and any cross-mapping artifacts. Work through each section systematically, scoring each item 1-3 (1=needs work, 2=adequate, 3=excellent). Post-workshop, use the scored results to prioritize improvement initiatives and present findings to your architecture governance board within 2 weeks.

Map Structure & Completeness

Evaluates the foundational integrity of your capability hierarchy, naming conventions, and coverage across your operating model.

Capability Hierarchy Depth

Assess whether your map has consistent depth (typically L1-L4) without going too granular. Good maps stop at the level where capabilities can be meaningfully owned and invested in separately. Avoid mixing processes or applications into capability names.

Naming Convention Consistency

Evaluate whether capability names follow consistent patterns (noun-based, outcome-focused, business language not technical). Check for process verbs (-ing words) or technology references that indicate capability/process confusion.

Business Domain Coverage

Identify any major business areas missing from your map. Compare against your operating model, org chart, and value streams to find gaps. Consider support functions, regulatory capabilities, and emerging business areas.

Abstraction Level Appropriateness

Check whether capabilities are at the right level of abstraction for decision-making. Too high-level provides no insight; too detailed becomes process documentation. Capabilities should represent meaningful investment decisions.

Relationship Clarity

Assess how well parent-child relationships are defined and whether peer capabilities at the same level have clear boundaries. Look for overlapping scope or unclear ownership boundaries between sibling capabilities.

Ownership & Governance

Examines whether clear accountability exists for each capability and how well the map is maintained as an authoritative enterprise asset.

Capability Ownership Assignment

Evaluate what percentage of capabilities have clearly assigned business owners (not IT owners). Owners should be accountable for capability performance and investment decisions. Document any ownership gaps or disputes.

Governance Process Maturity

Assess the formal process for capability map changes, version control, and approval workflows. Good governance includes regular review cycles, change impact assessment, and stakeholder notification processes.

Business Owner Engagement

Evaluate how actively business owners participate in capability discussions, heat mapping exercises, and investment planning. Measure their understanding of their accountability for capability performance.

Authority and Decision Rights

Assess whether the capability map is recognized as the authoritative view for investment decisions, org design, and technology planning. Check if senior leadership references it in strategic discussions.

Update Frequency and Triggers

Examine how often the map is updated and what triggers changes. Effective maps evolve with business strategy but maintain stability for ongoing decision-making. Balance currency with consistency.

Cross-Mapping Quality

Evaluates how well your capability map connects to other architecture artifacts like value streams, applications, and organizational elements.

Value Stream Integration

Assess whether capabilities clearly map to value streams and whether this relationship helps identify capability gaps or redundancies. Check if value stream performance issues trace back to specific capability weaknesses.

Application Portfolio Alignment

Eva