How do you create a capability map?

Prepare Scope, Sponsorship, and Team

Define map boundary—whole enterprise, division, or business unit—and secure sponsor who will use map in planning. Assemble cross-functional team: business leaders, business architects, enterprise architects, PMO representative. Gather strategy documents, org charts, existing process models, and application inventories as inputs—not substitutes for workshops.

Select approach: top-down from strategy and industry reference models, bottom-up synthesis from processes and systems, or hybrid most common. Plan four to eight weeks for first usable version depending on size.

Larkinized LLC schedules executive kickoff clarifying decisions the map must support—portfolio cuts, transformation scope, M&A integration—to keep workshops focused.

Pre-workshop interviews with quiet stakeholders capture concerns dominant voices might suppress in large sessions—improve map completeness.

Facilitate Discovery Workshops

Start Level 1 domains in executive session—typically eight to twelve domains covering full enterprise without overlap. Use sticky notes or digital whiteboards; enforce naming conventions and no application names rule.

Break out by domain for Level 2 and Level 3 capabilities with subject matter experts. Ask what must this business always be able to do regardless of how we organize? Capture definitions and business owners tentatively.

De-duplicate aggressively in consolidation sessions—synonyms erode trust. Resolve boundary disputes between domains with sponsor arbitration documented.

Devil’s advocate reviews challenge orphan capabilities neither supporting strategy nor operations—prune ruthlessly after validation.

Define, Structure, and Validate

Document each capability with ID, name, definition, outcomes, owner, and related KPIs where known. Structure hierarchy in repository tool—ArchiMate capability notation, specialized BA tools, or governed spreadsheets initially.

Validation walks strategy line-by-line: does capability set cover strategic priorities? Stakeholders review for omissions—regulatory, shared services, innovation. Pilot overlay on one planning question—where is customer onboarding capability maturity?—to test usefulness.

Iterate definitions based on feedback; perfection is enemy of adoption—target decision-grade over academic completeness.

Multilingual enterprises define canonical capability names in primary language with approved translations in glossary.

Publish, Integrate, and Overlay

Publish map in accessible repository linked from architecture portal. Train portfolio managers and product owners on usage. Map applications to capabilities using workshops or inventory analysis—first overlay most organizations need.

Integrate capability IDs into project intake forms and architecture review criteria. Connect to TOGAF Phase B deliverables and migration planning in Phase F.

Add maturity or heat overlays as data becomes available; avoid empty scores—honest unknown better than fabricated three-out-of-five.

Map publication includes FAQ addressing common objections—why not org chart, why not systems list—reducing repetitive explanations.

Govern and Evolve

Establish change control: who approves new capabilities, how often map refreshes, how versions communicate to users. Community of practice shares use cases reinforcing behavior.

Evolution triggers include acquisitions—merge capability taxonomies—new business models, and major reorganizations. Retire obsolete capabilities with archive notes for historical portfolio analysis.

Successful maps grow with organization—first publication is milestone one, not finish line.

Annual map health check scheduled alongside strategic planning refresh—calendar invite beats ad hoc neglect.

Workshop Facilitation Tips for Capability Mapping

Larkinized LLC facilitators enforce parking lot for application and org debates—capture but defer to maintain capability focus. Time-box domain breakouts; unresolved Level 3 items become action assignments with owners due within two weeks rather than infinite workshop.

Remote workshops use digital sticky tools with anonymous dot voting on contentious capability boundaries—reduces hierarchy bias in hybrid rooms.

Pilot overlay within two weeks of draft map—maturity scores for five capabilities executives already debate—proves map usefulness before polish perfection.

Common Workshop Failure Modes

Failure mode: wrong participants—only IT attends. Fix: executive mandate for business SME attendance. Failure mode: endless Level 3 debate. Fix: time-box and assign offline follow-up. Failure mode: no publication date. Fix: commit to draft release within ten days regardless of imperfections.

Record workshops for absent stakeholders with summary action lists—transparency reduces rear-guard politics post-workshop.

Validate maps with frontline employees who execute work daily—executives alone miss operational nuance.

Link map publication to internal communications campaign explaining why capabilities matter to everyone’s work.

Practical Guidance from Larkinized LLC

Larkinized LLC runs workshops with business SMEs mandated by executive sponsor—IT-only attendance produces IT-shaped maps rejected by operations leaders who were not in the room.

Pre-interviews with quiet stakeholders capture concerns dominant voices suppress—improves completeness before large sessions where politics peak.

Time-box Level 3 debates; assign offline follow-up for unresolved granularities—perfectionism delays publication beyond useful decision windows.

Publish draft within ten days of workshop—momentum beats waiting for perfect consensus that never arrives; version maps explicitly.

Validate with frontline employees executing work daily—executives alone miss workarounds and exceptions that define real capability performance.

Annual health checks scheduled with strategic planning refresh—calendar invites beat ad hoc neglect when new leaders arrive unaware maps exist.

Executive sponsors open workshops with why maps matter this quarter—context prevents participants treating sessions as optional IT exercises.

Larkinized LLC connects guidance on how do you create a capability map to named portfolio decisions within the current fiscal year so architecture work is legible in funding systems executives already use. Workshop outputs publish to the repository within two weeks with owners assigned, preventing loss of context when facilitators rotate or consultants depart after initial engagement.

Cross-functional participation includes operations staff who execute daily processes—not only senior leaders whose high-level views omit workarounds that define real performance. Their input grounds models in operational truth and reduces downstream rejection when delivery teams claim architecture ignored how work actually happens.

Education scales beyond central architects through micro-learning for product owners, procurement staff, and engineers, reducing exceptions driven by ignorance rather than genuine strategic conflict. Office hours and internal communities of practice keep guidance current as cloud, agile, and AI practices evolve faster than annual training cycles.

Measurement pairs business KPIs—cycle time, cost per transaction, error rates, regulatory findings—with architecture metrics such as repository usage, review SLA compliance, and portfolio alignment scores. Improvements tied to architecture interventions build executive trust more reliably than model counts alone.

Regulatory and audit stakeholders increasingly expect traceability; viewpoint-specific views linked to repository entities produce evidence in days rather than weeks during examinations. Proactive documentation reduces fire drills, punitive findings, and leadership distraction from core transformation priorities.

M&A, divestiture, and market expansion stress-test architecture assets—scenario playbooks updated annually let leadership pivot with cost and timeline estimates instead of panic discovery after announcements. Capability maps and application inventories become due diligence assets before deals close, not afterthought spreadsheets.

Governance forums for how do you create a capability map should meet on a predictable cadence tied to portfolio and release planning—not ad hoc when crises force attention. Larkinized LLC recommends standing architecture review slots with published intake criteria, SLA targets, and escalation paths so delivery teams know how to engage without treating architecture as unpredictable gatekeeping that rewards political access over merit of design.

Traceability from strategy statements to capability or architecture elements to funded initiatives to deployed solutions closes the loop executives expect when they approve EA funding. Without traceability, architecture remains a parallel documentation universe. Link charters, requirements, design records, and operational inventories in one searchable repository so auditors, product managers, and engineers retrieve consistent answers instead of conflicting spreadsheets maintained in silos.

Risk management benefits when how do you create a capability map practices identify concentration risks—single vendor platforms, fragile integrations, key-person dependencies, regions without failover—and map mitigations into migration plans with owners and dates. Risk registers integrated with architecture repositories beat oral tradition during incidents when leadership demands answers within hours and teams cannot afford heroic manual discovery across dozens of systems.

Innovation programs need explicit guardrails within how do you create a capability map so experiments proceed safely: sandbox environments, data masking rules, time-boxed pilots, and kill criteria before production commitments. Architecture enables innovation velocity by stating what teams may try without enterprise approval versus what requires board-level review because customer data, financial reporting, or safety-critical operations are affected.

Global enterprises localizing how do you create a capability map should tier standards: mandatory worldwide, recommended regional, optional local—documented in governance charters to prevent both harmful divergence and rejection of valid regional regulatory requirements. Regional architects on a council synchronize proposals before they become de facto standards that conflict with enterprise principles approved by executive sponsors accountable to the board.

Quality assurance for architecture artifacts includes peer review, automated validation where schemas exist, and executive readability checks before publication. Larkinized LLC teaches teams to reject diagrams that look complete but lack definitions, owners, and measures—hallmarks of documentation theater that erodes trust faster than publishing fewer, higher-quality views updated on schedule.

Stakeholder onboarding for how do you create a capability map never ends; annual refreshers for new leaders, rotating product managers, and engineers hired from acquisitions prevent repeated violations caused by ignorance rather than defiance. Micro-learning, office hours, and annotated examples in repositories scale literacy without requiring week-long courses that busy executives and engineers will not attend consistently.

Ultimately how do you create a capability map succeeds when leaders reference architecture evidence in routine decisions—funding, hiring, vendor selection, incident response—not only during transformations. Larkinized LLC measures cultural adoption through decision log sampling: what percentage of major investments cited architecture assets in approval packets last quarter? Rising percentages indicate durability; flat or falling percentages signal sponsorship or relevance problems requiring honest retrospective, not additional templates.

Larkinized LLC closes each engagement on How do you create a capability map with a written adoption plan: owners, refresh dates, metrics, and executive checkpoints—so architecture value persists after consultants depart and survives leadership changes that otherwise reset informal progress.

References & Further Reading

• Business Architecture Guild, BIZBOK Guide — Capability Mapping Technique
• The Open Group, TOGAF Phase B — Business Capability Mapping Workshop
• Gartner, Building Business Capability Models