Applied business architecture · Recipe 02

Business Capability Mapping: Method & Excel Template

A business capability map describes what an enterprise must be able to do. Its usefulness depends on definitions that survive changes to departments, processes, and systems. Begin with the decision the map needs to support, then build only the detail that helps answer it.

  • Free · No registration
  • Editable Excel
  • Instructions and blank worksheets

The decision

Build a capability map without drawing the org chart

The enterprise needs a stable view of what it must be able to do, but the first draft mirrors departments, applications, products, process steps, or a borrowed reference model instead of enduring business abilities.

Decision supported
What stable capability vocabulary and level of detail are sufficient for the current enterprise decision?
Start with
A named decision, representative scenarios, business-model context, and existing capability, organization, process, and technology evidence.
Boundary
Creates a capability baseline; it does not assess performance, reproduce a reference model, or encode the current organization and application landscape.

When to use this method

  • The enterprise has no governed capability baseline for a real decision
  • Existing maps differ by business unit, initiative, consultant, or tool
  • Capability names are dominated by organizational or technology labels
  • Strategy, portfolio, operating-model, or impact analysis needs a common business vocabulary

Evidence to bring

  • Decision, scope, scenarios, audience, and required level of precision
  • Business model, products and services, stakeholders, and value propositions
  • Representative value streams, business objects, policies, outcomes, and measures
  • Existing organization, process, application, initiative, and reference-model material as evidence rather than structure
  • Business content owners, subject-matter experts, modeling rules, and repository constraints

The method

Work through the decision.

  1. State the decision the map must support and limit initial depth to the branches needed for that decision
  2. Describe what the enterprise must be able to do independently of who performs it, how work flows, or which technology enables it
  3. Name each capability with a business object plus an action expressed as an ability, using a noun construct such as Agreement Management; define the object boundary before arranging hierarchy or assigning color
  4. Separate capabilities from organizations, roles, processes, activities, products, business objects, outcomes, applications, and projects while preserving those terms as related evidence
  5. Define each capability once for the enterprise; give each child one decomposition parent, keep it within the parent business-object boundary, and require children collectively to explain the parent without an only-child restatement
  6. Normalize synonyms, near-duplicates, mixed abstraction levels, and borrowed terms whose meaning does not fit the enterprise context
  7. Test every material capability across more than one value stream, product, organization, or scenario, including a plausible reorganization or technology change
  8. Assign stable identifiers, sources, status, steward, effective date, confidence, and unresolved issues before assessment or initiative mapping
  9. Validate the decision-relevant baseline with business content owners and publish the level contract, naming rules, and deferred-decomposition backlog

What the work should produce

  • Decision-scoped capability map and level contract
  • Capability definitions, identifiers, sources, and stewardship
  • Classification and modeling rules
  • Scenario validation and duplicate-term findings
  • Governed issues and deferred-decomposition backlog

When to stop

Stop when the map provides a stable, governed vocabulary at sufficient depth for the stated decision and the next level would not change assessment, investment, accountability, dependency, sequence, scope, or risk. Do not complete every branch merely for visual symmetry.

Northstar · Apply the method

Keep the promise separate from its enabling resources.

Evidence: The Decision 1 architecture fragments distinguish C-110 (Service Promise Management in the packet; Customer Promise Management in the Atlas), Resource Scheduling (C-130), and Parts Availability Management (C-140). E-003 describes commitments made while reservation meaning and rural capacity remain uncertain.

Apply the method: Define each ability separately, then connect the promise to the resource signals it uses. This keeps the map stable while making the dependencies worth investigating visible.

Keep this boundary: Those relationships do not establish which constraint causes the greatest share of missed promises. Do not turn an observed dependency into a causal verdict.

Inspect the source evidence · Follow the guided lessons

Archive: earlier workbook example

Worked example · Northstar v1.1

Separate the promise from the resources that enable it.

In the fictional Northstar v1.1 case, a scheduling-platform proposal prompts a closer look at service promises. These selected capability definitions keep customer commitments distinct from scheduling people and reserving parts.

Northstar v1.1 · Selected capability definitions
IDCapabilityDecision-relevant definition and boundaryAccountable executive
C-110Service Promise ManagementPropose, validate, communicate, monitor, and change a customer commitment. Uses resource signals but does not plan work, reserve parts, assign technicians, or confirm final customer value.EVP Service Operations
C-130Resource SchedulingMatch authorized demand to qualified people, time, geography, and capacity. Does not establish part status or own the customer promise.VP Field Service
C-140Parts Availability ManagementDetermine, reserve, position, consume, release, and expire required part availability. Does not assign technicians or make customer commitments.VP Supply Operations

The boundaries make the dependency visible: improving scheduling alone does not establish who owns the customer promise or whether part availability can be trusted. Keep those relationships in the architecture without merging them into one capability.

Explore the relationships in the Atlas
Advanced: modeling checks and the full capability hierarchy

BIZBOK alignment checks

  • Use a business object plus an action in a noun construct, and define each capability once for the enterprise.
  • Give each child one decomposition parent; keep its finer ability within the parent’s business-object boundary.
  • Check that children collectively explain the parent and avoid an only-child restatement.
  • Keep customer and product types in the information model. Cross-map organizations, processes, systems, and value stages.
  • Stop at the depth needed for the decision; a selected view keeps the capabilities’ actual hierarchy levels.

Basis: BIZBOK Guide v11.0, section 2.2, pages 64–67, 79, and 86–87. The workbook’s formula checks support review; they do not establish semantic correctness.

Northstar capability hierarchy

Seven selected enterprise branches with explicit object boundaries. This is an authored hierarchy for the fictional case, not a complete enterprise map or a BIZBOK reference model. Original C-100–C-180 IDs remain stable; original decision labels are retained as aliases. The added parents, siblings, names, and levels are modeling additions, not evidence of approval in Decisions 1–3.

L1 identifies an object-centered business ability. L2 identifies a finer ability within that same object boundary; the shown children collectively cover the stated parent definition. Every child has one parent and every decomposed parent has multiple distinct children. Object types, organizations, processes, applications, and dependencies are cross-mapped separately.

Defined parents and children · Original case IDs preserved
ID / parentLevelCapabilityObject and boundary
C-010RootL1Service Request ManagementService Request (BO-01). Establish and maintain a recognized equipment-service need, then govern its disposition against the requested customer outcome.
C-100Parent: C-010L2Service Request QualificationCase alias: Customer Need ManagementService Request (BO-01). Identify, accept, qualify, and maintain a service need; exclude the customer commitment and authorization of work.
C-160Parent: C-010L2Service Request ResolutionCase alias: Service Outcome ManagementService Request (BO-01). Reconcile the request, promise, and work result; confirm restored availability and customer acceptance, retain open recovery obligations, or record termination without fulfillment.
C-110RootL1Customer Promise ManagementCase alias: Service Promise ManagementCustomer Promise (BO-02). Establish, validate, communicate, monitor, and revise a governed customer commitment; use resource evidence without planning work or owning resource allocations or final customer-value acceptance.
C-111Parent: C-110L2Customer Promise DefinitionCustomer Promise (BO-02). Specify the proposed commitment, its scope, timing, and terms.
C-112Parent: C-110L2Customer Promise ValidationCustomer Promise (BO-02). Assess the proposed commitment against policy and the available feasibility evidence.
C-113Parent: C-110L2Customer Promise CommunicationCustomer Promise (BO-02). Communicate the commitment and its status to the parties who rely on it.
C-114Parent: C-110L2Customer Promise MonitoringCustomer Promise (BO-02). Determine the commitment’s current standing and whether its terms are being met.
C-115Parent: C-110L2Customer Promise ChangeCustomer Promise (BO-02). Revise, cancel, or supersede the commitment while retaining its history and obligations.
C-030RootL1Work Order ManagementWork Order (BO-03). Specify and authorize a unit of service work, perform and record it, then reconcile and close its work record; exclude customer-value acceptance and resource ownership.
C-120Parent: C-030L2Work Order PlanningCase alias: Work PlanningWork Order (BO-03). Translate an accepted need into authorized work scope, method, and prerequisites; exclude capacity assignment and execution.
C-150Parent: C-030L2Work Order ExecutionCase alias: Field Service ExecutionWork Order (BO-03). Perform and record the authorized equipment intervention and its exceptions; exclude customer acceptance and promise policy.
C-151Parent: C-030L2Work Order ClosureWork Order (BO-03). Reconcile recorded work, consumption, and exceptions and determine administrative closure or cancellation; closure alone does not prove delivered customer value.
C-040RootL1Human Resource ManagementHuman Resource. Govern the identity and engagement of people whose work the enterprise uses, their qualifications and availability, and their assignment to demand; cross-map agreements, payments, and organizational units.
C-131Parent: C-040L2Human Resource EngagementHuman Resource. Establish and maintain a person’s working relationship with the enterprise, including entry, changes, and exit.
C-132Parent: C-040L2Human Resource QualificationHuman Resource. Establish and maintain the evidence of a person’s skills and qualifications.
C-133Parent: C-040L2Human Resource AvailabilityHuman Resource. Determine the person’s available time, location, and capacity constraints.
C-130Parent: C-040L2Human Resource SchedulingCase alias: Resource SchedulingHuman Resource. Match authorized demand to qualified people, time, geography, and capacity; govern the resulting assignments without owning parts or customer commitments.
C-050RootL1Part ManagementPart. Define and acquire physical components used in equipment service, govern their availability and use, and retire unusable or obsolete components; cross-map suppliers, payments, and equipment assets.
C-141Parent: C-050L2Part DefinitionPart. Establish and maintain the identity, specification, and permitted use of a physical service component.
C-142Parent: C-050L2Part AcquisitionPart. Obtain and accept components that satisfy the defined service need.
C-140Parent: C-050L2Part Availability ManagementCase alias: Parts Availability ManagementPart. Determine, reserve, position, consume, release, and expire availability of service components; exclude technician assignments and customer commitments.
C-143Parent: C-050L2Part RetirementPart. Determine and govern withdrawal or disposal of unusable or obsolete components.
C-170RootL1Performance Measure ManagementCase alias: Service Performance ManagementPerformance Measure (M-* register). Define business measures and guardrail thresholds, determine their observed values, and interpret and govern their use; exclude source transactions and operational remediation.
C-171Parent: C-170L2Performance Measure DefinitionPerformance Measure (M-* register). Specify a measure’s meaning, calculation, population, period, and guardrail thresholds.
C-172Parent: C-170L2Performance Measure DeterminationPerformance Measure (M-* register). Calculate and substantiate the measure’s value from governed evidence.
C-173Parent: C-170L2Performance Measure ReviewPerformance Measure (M-* register). Interpret, explain, review, and govern use of the measure and any decision implications.
C-180RootL1Information Definition GovernanceCase alias: Business Information GovernanceBusiness Information Definition. Establish shared business meaning, semantic accountability, quality requirements, and controlled changes to information definitions; exclude the operational decisions represented by that information.
C-181Parent: C-180L2Information Definition StructuringBusiness Information Definition. Specify a concept’s meaning, category, types, states, and typed relationships.
C-182Parent: C-180L2Information Definition StewardshipBusiness Information Definition. Assign and maintain accountable owners and stewards for the definition.
C-183Parent: C-180L2Information Quality Rule DefinitionBusiness Information Definition. Specify the quality rules and thresholds associated with the definition.
C-184Parent: C-180L2Information Definition Change ControlBusiness Information Definition. Evaluate, authorize, version, and communicate changes in shared business meaning.

Download a blank capability-validation template

Hierarchy source and earlier workbook

Authored Northstar v1.1 teaching model; BIZBOK Guide v11.0, section 2.2, pages 64–67, 79, 86–87. Corrected October 6, 2026. This structural model does not establish funding approval or results from the practice decisions.

Download the earlier completed hierarchy workbook · Read its original case guide

Reusable Excel template

Capability definition, decomposition, and validation workbook

Create stable capability definitions, test decomposition depth, expose orphaned or weak records, and structure a validation workshop without reproducing the organization chart.

Inside the workbook

  • Read me and modeling rules
  • Capability register
  • Formula-driven decomposition QA
  • Validation workshop record

Use it with your own evidence

  1. Define the decision and scenarios first.
  2. Use business-object-plus-action names, one definition per capability, and one decomposition parent per child.
  3. Review automated QA flags and check that children collectively cover the parent object boundary without an only-child restatement.
  4. Validate definitions, levels, ownership, and scenario coverage with business experts.

Does not provide an authoritative industry reference model or prove that a capability belongs at a particular level without enterprise context and governance.

Start with the blank worksheets and your own evidence. Northstar’s worked examples are available separately and contain the case answers.

Optional: work through this method with AI

Describe your question in SCALE, the AI-assisted business architecture approach, and copy a complete starter into your chosen AI. Supply the source evidence there and add this method when useful. Check the evidence, challenge the explanation, and correct the result.

Use SCALE with your own question

Continue the work

Which branches require decomposition, validation, assessment, or connection to value and information?

Related Field Notes

Reference material

Find this method in the full library