The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
organization, people, leadership & hr framework
Map stable business capabilities by domain and maturity/heat.
quick answer
Business Capability Map is a capability map / taxonomy for Enterprise architecture. It turns the decision into named fields, evidence, and a visible business capability map worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Map stable business capabilities by domain and maturity/heat.
Use TOGAF ADM when its output is closer to the conversation you need: Develop architecture through ADM phases with requirements management.
worked example
A filled example is easier to understand than a blank template. Use it to see the shape before applying the framework to your own case.
A filled example so you can see the shape before applying Business Capability Map to your own context.
A filled example so you can see the shape before applying Business Capability Map to your own context.
generate yours
Start Ask PL with the framework, required inputs, and your context. It will ask for missing details, render the capability map / taxonomy, and explain what decision the output should change.
Apply Business Capability Map to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the Business Capability Map structure: - Business capability hierarchy: - level 1/2/3: - heat/status overlays: Ask only for missing inputs that would change the output. Then render the capability map / taxonomy and name the decision it should change.
how to use it
Use the framework to change a decision, not to fill a worksheet. Start narrow, add evidence, then inspect what the business capability map worksheet / visual makes clearer.
Write the concrete enterprise architecture choice, tradeoff, or conversation the framework should change.
Fill the important slots: Business capability hierarchy, level 1/2/3, heat/status overlays.
Mark what is measured, what comes from customers, and what is still judgment.
End with the next move, the riskiest assumption, or the evidence that would change the business capability map worksheet / visual.
quality check
Use this check after the artifact is filled. Blank fields are not failure; they are the next research question. Look for concrete evidence, missing constraints, and assumptions that would change the next move.
The framework needs a concrete decision. Broad intent turns it into a worksheet, not a decision aid.
Good framework output makes assumptions visible enough for someone else to challenge.
The diagram is useful only if it changes the next product conversation.
common mistakes
Do not use Business Capability Map as a worksheet. Name the choice, conversation, or tradeoff the output should change.
Separate measured facts, customer evidence, and leadership judgment so weak assumptions stay visible.
If the diagram does not match the decision, switch frameworks instead of stretching the boxes.
The framework should clarify the next move. It should not replace strategy, sequencing, or judgment.
use something else when
Develop architecture through ADM phases with requirements management.
Classify enterprise architecture artifacts by interrogatives and perspectives.
Define processes, people, technology, governance and performance for operations.
faq
Map stable business capabilities by domain and maturity/heat.
Business context; objectives; available evidence; stakeholder judgment
Business Capability Map worksheet / visual
Use Business Capability Map when the decision matches this job: Map stable business capabilities by domain and maturity/heat.
Avoid it when you need TOGAF ADM's output instead: Develop architecture through ADM phases with requirements management.
It is both: a structure for thinking and a visible capability map / taxonomy that makes the decision easier to inspect.
A good input names the real decision, uses concrete evidence, and separates facts from assumptions.
Use the business capability map worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use TOGAF ADM when the real output you need is closer to: Develop architecture through ADM phases with requirements management.
Yes. Describe your context and Ask PL can ask for missing inputs, render the capability map / taxonomy, and explain what decision it should change.