Capability Map: [Organization / Business Unit Name]

Capability Map: [Organization / Business Unit Name]

TOGAF Business/IT Capability Mapping Phase: B (Business Architecture) / C (Information Systems Architecture) Date: [YYYY-MM-DD] Status: [Draft | Reviewed | Approved]

Purpose

This capability map documents the organization's business capabilities and their supporting IT capabilities. It serves as a foundation for gap analysis, investment planning, and architecture decision-making.

Scope

  • Organization: [Name of the organization or business unit being mapped]
  • Domain: [Business domain(s) covered — e.g., "Sales and Marketing," "Full enterprise"]
  • Level of detail: [L0 strategic / L1 operational / L2 detailed]

Business Capability Map

Level 0 — Strategic Capabilities

[List the top-level capability groups. These represent the major areas of business activity.]

ID Capability Description Strategic Priority
BC-01 [e.g., Customer Management] [What this capability enables the business to do] [High / Medium / Low]
BC-02 [e.g., Product Development] [Description] [Priority]
BC-03 [e.g., Order Fulfillment] [Description] [Priority]
BC-04 [e.g., Financial Management] [Description] [Priority]

Level 1 — Operational Capabilities

[Break each L0 capability into its component parts.]

ID Parent Capability Description Maturity
BC-01.1 BC-01 [e.g., Customer Acquisition] [Description] [Initial / Developing / Defined / Managed / Optimized]
BC-01.2 BC-01 [e.g., Customer Retention] [Description] [Maturity]
BC-01.3 BC-01 [e.g., Customer Service] [Description] [Maturity]
BC-02.1 BC-02 [e.g., Product Design] [Description] [Maturity]

[Continue for each L0 capability.]

IT Capability Map

Applications Supporting Business Capabilities

[Map IT systems and applications to the business capabilities they support.]

Business Capability Application(s) Technology Status Notes
BC-01.1 Customer Acquisition [e.g., Salesforce CRM, Marketing Hub] [SaaS / On-prem / Hybrid] [Active / Retiring / Planned] [Key notes — e.g., "primary system of record"]
BC-01.2 Customer Retention [Application names] [Technology] [Status] [Notes]
BC-01.3 Customer Service [Application names] [Technology] [Status] [Notes]

Technology Capabilities

[Map underlying technology capabilities that support the application layer.]

ID Technology Capability Description Current State Target State
TC-01 [e.g., Integration Platform] [What this technology capability provides] [Current technology/product] [Target technology/product or "Retain"]
TC-02 [e.g., Data Platform] [Description] [Current] [Target]
TC-03 [e.g., Identity and Access] [Description] [Current] [Target]

Capability Assessment

Heat Map — Business Capability Maturity

[Rate each capability across key dimensions to identify areas needing investment.]

Capability Strategic Importance Current Maturity IT Support Quality Gap Severity
BC-01.1 Customer Acquisition [1-5] [1-5] [1-5] [Critical / Significant / Moderate / Minor / None]
BC-01.2 Customer Retention [1-5] [1-5] [1-5] [Gap]
BC-01.3 Customer Service [1-5] [1-5] [1-5] [Gap]

Rating scale:

  • 1 = Very Low / Initial
  • 2 = Low / Developing
  • 3 = Medium / Defined
  • 4 = High / Managed
  • 5 = Very High / Optimized

Gap Severity = mismatch between Strategic Importance and Current Maturity:

  • Critical: High importance, low maturity — immediate attention required
  • Significant: Notable gap affecting business outcomes
  • Moderate: Gap exists but manageable in the short term
  • Minor: Small gap, improvement would be beneficial
  • None: Maturity matches or exceeds strategic need

Gap Analysis Summary

[Summarize the most significant gaps identified in the capability assessment.]

Rank Capability Gap Description Recommended Action Priority
1 [Capability with largest gap] [What is missing or inadequate] [Add / Replace / Enhance / Consolidate] [Immediate / Next quarter / Next year]
2 [Next capability] [Gap description] [Action] [Priority]

Dependencies and Relationships

[Document key dependencies between capabilities.]

Capability Depends On Relationship Impact if Dependency Fails
[Downstream capability] [Upstream capability] [e.g., "requires data from," "triggers process in"] [Business impact description]

Recommendations

[Based on the capability assessment and gap analysis, provide architecture recommendations.]

  1. [Recommendation title] — [Description of what should change and why, referencing specific gaps]
  2. [Recommendation title] — [Description]
  3. [Recommendation title] — [Description]

Produced by: [Digital talent name / role] Stakeholder review: [Names and dates] Next review: [Date]