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 a triggering stakeholder obtains the whole stream’s value proposition through stage value items, 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 stages as business-level abstractions of value-creating activities and stakeholder interactions, with meaningful increments of stakeholder value; keep detailed task sequences in process models
- Give every stage a name, explicit definition, participating stakeholders, value item or items, observable entry and exit criteria, and useful measures; distinguish successful completion, continued recovery, and termination without fulfillment
- Trace every stage’s value items to the whole stream’s value proposition and check that their combined value fulfills the triggering stakeholder’s need; do not treat recovery or unfulfilled termination as success
- 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
- Stage cards with definitions, participants, value items, and 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.
Northstar · Apply the method
Make customer value the test of the stage.
Evidence: Northstar names VS-01 “Restore Equipment Availability.” Its ST-02 stage, “Define service promise,” moves an accepted need toward an understood, feasible commitment. C-110 uses scheduling and parts signals to support that commitment.
Apply the method: The customer operations manager triggers the whole stream to obtain restored availability. ST-02 delivers a credible commitment accepted by the customer. That value item contributes to the proposition alongside the other stages’ value items. Test which capabilities enable that contribution.
Keep this boundary: A stage is an abstraction of value-creating activities and stakeholder interactions. Use a process model for the detailed sequence; a capability cross-map is not that sequence.
The whole stream and its stages
Restore Equipment Availability
- Triggering stakeholder
- Customer operations manager
- Triggering need
- Equipment is unavailable or at risk, prompting a request for service.
- Value proposition
- Usable equipment availability restored for the customer operations manager and confirmed against the agreed service commitment.
The value stream is the whole. It decomposes into value stream stages, each delivering value items that accrue toward the value proposition.
- Identify needValue item: An accepted, actionable need
- Define service promiseValue item: A credible commitment accepted by the customer
- Prepare serviceValue item: Service ready to execute
- Perform serviceValue item: Restored equipment condition, or explicit evidence that further recovery is required
- Confirm outcomeValue item: Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise
How the value accumulates: an accepted need leads to a credible commitment, prepared service, and an equipment result. Together with customer confirmation, those contributions fulfill the proposition of restored availability. A completed visit or a recovery handoff alone does not.
At each stage, participating stakeholders contribute to or receive value. Capabilities enable the stage; entry and exit criteria govern navigation, including recovery. The order illustrates a typical progression, not a detailed task sequence or a required five-stage pattern.
Explore the whole stream and its stages in the Atlas → · Download this explanation
Archive: earlier workbook example
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 | Stage definition | Value items |
|---|---|---|---|---|---|
| ST-02 | Define service promise | Need is accepted but timing is uncertain | A feasible commitment is understood and accepted | Establish and communicate a feasible commitment using the service need, resource signals, and applicable policy. | A credible commitment accepted by the customer |
| ST-03 | Prepare service | Commitment exists but work is not ready | Work is ready to execute | Coordinate prerequisites and resource confirmations so the promised service can proceed. | Service ready to execute |
| ST-05 | Confirm outcome | Service occurred but value is unconfirmed | Equipment availability is restored and the customer confirms the agreed outcome | Verify the customer’s receipt of restored availability, reconcile it to the commitment, and determine success, further recovery, or termination without fulfillment. | Confirmed restored availability on success; a documented outstanding obligation or unfulfilled termination otherwise |
| 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 restored availability and customer acceptance, or retain an open recovery obligation. Authorize successful closure only with fulfilled value; record unsuccessful termination separately. Does not perform the work or define enterprise measures. |
A stage abstracts value-creating activities and stakeholder interactions around an increment of value. Define it explicitly and test capability contributions against its criteria. Restored availability and customer confirmation establish successful completion; an owned recovery path requires continued work, or explicit termination without fulfillment.
Explore the relationships in the Atlas
Define the stage, then test its boundaries.
A stage abstracts value-creating activities and stakeholder interactions. Record its name, definition, participating stakeholders, value item or items, and observable entrance and exit criteria. State progression is a useful shorthand for the result; it is not the whole definition.
Five to eight stages is an author’s starting heuristic for this template, not a BIZBOK requirement. Expand the stage cards and corresponding cross-map columns when the business case requires it.
Basis: BIZBOK Guide v11.0, section 2.4, pages 149–159 and 171. Success fulfills the value proposition; continued recovery and termination without fulfillment must remain distinct.
Reusable Excel template
Value-stream stage card and capability cross-map
Define the whole stream’s triggering stakeholder and value proposition, then its stages, value items, criteria, and enabling capabilities.
Inside the workbook
- Read me and distinction tests
- Stage cards
- Capability-stage cross-map
- Coverage checks
Use it with your own evidence
- Name the whole stream, triggering stakeholder, triggering need, and value proposition. Use the Stage Cards header’s Primary stakeholder field for the triggering stakeholder.
- Use five to eight stages as an author’s starting heuristic for this template, not a BIZBOK requirement; expand the cards and cross-map when needed.
- Define each stage’s abstract value-creating activities, participants, value items, and observable entry and exit criteria.
- Trace how the stage value items collectively fulfill the value proposition, preserving recovery and unfulfilled termination.
- 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.
Start with the blank worksheets and your own evidence. Northstar’s worked examples are available separately and contain the case answers.
Optional: work through this method with AI
Describe your question in SCALE, the AI-assisted business architecture approach, and copy a complete starter into your chosen AI. Supply the source evidence there and add this method when useful. Check the evidence, challenge the explanation, and correct the result.
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