shaping-capabilities

To decompose large strategic changes, you break work into named capabilities with defined benefits, success criteria, and boundaries. Each capability increment is paired with hypotheses and architecture considerations to enable incremental delivery and validated learning.

A capability brief is a structured planning artifact capturing a named capability's benefits, success criteria, upstream and downstream dependencies, architectural questions, data and security needs, and links to candidate features for major initiatives.

Yes, this capability planning approach applies directly to value streams, epics, portfolios, and major initiatives requiring structured capability planning, dependency mapping, and architectural guidance for large-scale strategic changes.

You map dependencies and architecture questions by capturing upstream and downstream dependencies, architectural questions, data and security needs, and linking them to candidate features within each capability brief before progressing to specific feature candidates.

The best way to enforce a gating process is to require completed capability briefs capturing dependencies and architecture questions before allowing progression to specific feature candidates, ensuring structured capability planning and validated learning occur first.

You should avoid capability decomposition for epic planning when work does not require structured capability planning, dependency mapping, or architectural guidance. Smaller changes lacking measurable learning objectives or incremental delivery needs may not warrant this staged approach.