Mission Planning Lab
Making work visible is how an organization climbs out of its silos, and every modern planning tool exists to do it, whether that is Miro, Mural, Microsoft Whiteboard, Jira, Azure DevOps, or a wall of sticky notes. The Mission Planning Lab goes one step further and makes conditions visible. You inherit a real organization, triage last quarter's unfinished work, then build a quarter under a hard capacity cap. To commit any card you name the one condition it depends on and its owner. The quarter can only hold so much, so choosing what to do forces choosing what to drop. The discipline carries into whichever tool your teams already use.
The Mission Planning HierarchyThe standard, a containment tree, and how it maps to Jira, Azure DevOps, SAFe, and Scrum. Tap to open.
The Mission Planning Hierarchy™
The standardA fixed planning language. Recognizable enough to grasp at once, distinct enough to remember.
- 1Outcome · What must become different?
A measurable organizational change.
- 2Initiative · What investment creates that change?
A coordinated investment intended to achieve an outcome.
- 3Epic · What major body of work is required?
A major body of work that advances an initiative.
- 4Capability · What meaningful capability will exist?
A usable business or technical capability that delivers value.
- 5Work Package · What is the smallest commitment before hand-off?
The smallest planning commitment leadership makes before handing work to delivery teams.
◇ Milestone. A checkpoint that attaches to any level: funding approved, architecture approved, pilot complete, go / no-go, launch. It marks a point in time, not a container of work.
Leaders decide Outcomes, Initiatives, Epics, and Capabilities. Teams determine Stories and Tasks.
What contains whatThe containment tree. Tap to open.
The flow above teaches progression; this tree teaches containment.
Outcome └ Initiative ├ Epic │ ├ Capability │ │ ├ Work Package │ │ │ └ Story / Task (delivery teams, in Jira or Azure DevOps) │ │ └ Work Package │ └ Capability └ Epic
How it maps to your frameworkJira, Azure DevOps, SAFe, Scrum. Tap to open.
The standard stays fixed. Pick the framework you already use to see how its vocabulary translates onto it.
Frameworks carry fewer executive levels than the standard, so some terms map onto the same level. These are nearest equivalents, for education, not configuration. The Lab always speaks the standard.
A system of judgment, not a system of record. Jira and Azure DevOps store and organize the work; Miro helps you draw it. The Mission Planning Lab helps you decide which work deserves to exist, what to fund, protect, defer, or stop, before it ever reaches those tools.