The decision
Build a value stream without slipping into process
The “value stream” becomes a swimlane full of activities, systems, functions, and handoffs, obscuring the progression through which a stakeholder actually receives value.
- Decision supported
- How stakeholder value progresses from a triggering need to an observable outcome and which capabilities enable each stage.
- Start with
- A stakeholder, triggering need, value proposition, end outcome, representative scenarios, and the decision the value view must support.
- Boundary
- Defines stable value progression; it does not replace a customer journey, process model, service blueprint, or operating procedure.
When to use this method
- Stakeholders disagree about who receives value or where value delivery begins and ends
- Process maps are too detailed or implementation-specific for strategic analysis
- Initiatives optimize local activity without showing an improved stakeholder outcome
- Capability, information, organization, or product analysis needs an end-to-end value context
Evidence to bring
- Decision, scope, audience, and representative scenarios
- Stakeholder, triggering need, value proposition, and expected outcome
- Products, services, channels, policies, and material variants
- Existing process, journey, capability, information, measure, and organization evidence
- Business owners and subject-matter experts who understand normal and exception value delivery
The method
Work through the decision.
- State the decision and identify the stakeholder whose need triggers the value stream and whose outcome defines completion
- Describe the value proposition in observable business terms without embedding a process, organization, or product feature list
- Set the trigger, boundary, terminal outcome, and exclusion rules before naming stages
- Define a small number of outcome-oriented stages that represent meaningful changes in stakeholder or business state rather than work performed
- Give every stage observable entry and exit criteria, value contribution, measures, and material business objects or state changes
- Map the primary and supporting capabilities that enable each stage without turning capabilities into sequential activities
- Identify participating organizations, stakeholders, policies, products, information dependencies, and decision rights only to the depth required by the decision
- Test the stream against normal, exception, channel, product, and organizational variants; model legitimate variation without multiplying the stable core unnecessarily
- Validate the stream with the accountable value owner, record sources and unresolved issues, and direct activity, handoff, control, or timing questions to a process model when needed
What the work should produce
- Governed value-stream definition and boundary
- Outcome-oriented stage cards with entry and exit criteria
- Capability-to-stage cross-map
- Stakeholder, information, organization, product, policy, and measure relationships
- Scenario variations and unresolved evidence needs
When to stop
Stop when the stakeholder, trigger, value proposition, stages, criteria, enabling capabilities, and material variations are sufficient for the decision. If a stage must be explained as a task sequence, move that detail to a process model rather than weakening the value-stream view.
Worked example · Northstar v1.1
Follow the customer’s changing state.
Northstar v1.1 uses the value stream “Restore Equipment Availability.” These stages distinguish an accepted service promise, readiness to do the work, and a confirmed customer outcome. The selected capability definitions below provide part of the vocabulary for cross-mapping those stages.
| ID | Stage | Stakeholder state entering | Stakeholder state exiting |
|---|---|---|---|
| ST-02 | Define service promise | Need is accepted but timing is uncertain | A feasible commitment is understood and accepted |
| ST-03 | Prepare service | Commitment exists but work is not ready | Work is ready to execute |
| ST-05 | Confirm outcome | Service occurred but value is unconfirmed | Customer accepts the outcome or a recovery path is owned |
| ID | Capability | Decision-relevant definition and boundary |
|---|---|---|
| C-110 | Service Promise Management | Propose, validate, communicate, monitor, and change a customer commitment. Uses resource signals but does not plan work, reserve parts, assign technicians, or confirm final customer value. |
| C-120 | Work Planning | Translate an accepted need into authorized work scope, method, and prerequisites. Does not assign capacity or execute work. |
| C-160 | Service Outcome Management | Reconcile promise and work outcomes, confirm customer acceptance, initiate recovery, and authorize outcome closure. Does not perform the work or define enterprise measures. |
A stage is a change in stakeholder value, not a department or a list of tasks. Test capability contributions against its entry and exit criteria, and preserve dependencies on other abilities such as resource scheduling and parts availability.
Editable template · Version 1.1
Value-stream stage card and capability cross-map
Define outcome-oriented value-stream stages, entry and exit criteria, measures, and enabling capabilities while keeping process activity out of the strategic view.
Inside the workbook
- Read me and distinction tests
- Stage cards
- Capability-stage cross-map
- Coverage checks
- Completed Northstar example
Use it with your own evidence
- Name the stakeholder, need, and value outcome.
- Define five to eight outcome-oriented stages.
- Set observable entry and exit criteria.
- Mark primary and supporting capability enablement and review uncovered stages.
Does not replace a process, journey, operating procedure, service blueprint, or control design when activity and handoff detail is required.
Continue the work
What information, organizations, capabilities, or initiative impacts must be mapped across the stages?
Related Field Notes
- Start Small, Build for the Enterprise: A Practical Guide to Standing Up a Business Architecture Practice
- The Visible Hand and Business Architecture: What a 1977 Classic Still Teaches Us About Enterprise Design
Reference material
- TOGAF Series Guide: Value Streams ↗The Open Group · Account required
- Value Creation, Value Consumption, and Navigation ↗Business Architecture Guild · Guild member
- Value Streams and Business Processes ↗Business Architecture Guild · Guild member