Skip to main content

Capability Mapping

Summary​

Capability mapping translates enterprise AI strategy into a practical investment sequence. It helps teams decide which capabilities to fund first, who owns each capability, and which dependencies must be resolved before scaling.

Who Should Read This​

  • Enterprise architects and transformation leads defining delivery order.
  • Product and platform owners aligning outcomes to capability investments.
  • PMO teams coordinating dependencies across business units.

Why This Matters​

  • Teams often launch initiatives without a shared dependency map, causing delays and rework.
  • Capability-level planning makes funding and ownership decisions defensible.
  • Cross-team visibility reduces sequencing mistakes in multi-quarter programs.

Core Concepts​

  • Capability inventory: business, platform, governance, and operations capabilities.
  • Dependency scoring: identify blockers that prevent downstream delivery.
  • Ownership matrix: assign accountable owner and supporting teams for each capability.
  • Sequencing logic: prioritize by value, readiness, and risk reduction.

Use this flow to set decision order, gate criteria, and rollout readiness before implementation starts.

Diagram​

Implementation Steps​

  1. List target capabilities for the next 12-month roadmap.
  2. Score each capability for business value, readiness, risk, and dependencies.
  3. Group capabilities into near-term, mid-term, and scale-phase waves.
  4. Assign accountable owner, supporting teams, and required evidence per capability.
  5. Review sequencing monthly and adjust as dependencies change.

Worked Example​

  • Support copilot rollout capability set:
    • Shared retrieval platform (owner: platform team).
    • Prompt and policy controls (owner: governance team).
    • Domain playbooks and workflow integration (owner: customer operations).
  • Sequencing decision: deliver retrieval and governance controls before domain automation expansion.

Realistic Example​

A global enterprise mapped 18 capabilities across platform, governance, and business delivery. The first roadmap draft prioritized business-facing features too early. After dependency scoring, the team shifted shared retrieval, observability, and policy controls into phase one, reducing downstream blockers.

Senior Tech vs Dev Conversation​

Senior Tech: What is the first failure mode for Capability Mapping? Dev: Teams list capabilities but ignore cross-team dependencies and ownership gaps. Senior Tech: What prevents that? Dev: Score dependencies explicitly and require named owners before roadmap approval.

UX/UI Checklist​

  • Show capability status by phase, owner, and dependency state.
  • Display blocked capabilities with root-cause dependency reason.
  • Link capability outcomes to business KPI targets.
  • Provide executive and delivery views with consistent definitions.

Common Pitfalls​

  • Prioritizing visible features before shared control capabilities.
  • Assigning owners without delivery authority.
  • Freezing roadmap sequences despite changing dependency conditions.

References and Next Steps​