The decision
Scope an initiative with a capability–value impact grid
Initiative scope is expressed as features, applications, workstreams, or a project charter with no defensible explanation of which business outcomes, value stages, capabilities, information, organization, policies, or products must actually change.
- Decision supported
- Which architecture changes and dependencies belong in an initiative and which scope should be excluded, deferred, or separately authorized.
- Start with
- A measurable outcome, affected stakeholders and value streams, a governed baseline, and the initiative scope or solution currently proposed.
- Boundary
- Frames business impact and scope; it does not approve funding, estimate delivery, design a solution, or prove that mapped scope will realize value.
When to use this method
- A proposal crosses functions, products, channels, legal entities, or value-stream stages
- Benefits are broad while delivery scope is narrow or technology-led
- Leaders need a consistent basis for comparing initiative impact and dependencies
- An existing initiative requires reframing before decomposition, release design, or requirements work
Evidence to bring
- Problem, intended outcomes, measures, sponsor, decision rights, and time horizon
- Affected stakeholders, value streams, products, services, and representative scenarios
- Governed capability, information, organization, policy, and performance baselines
- Known systems, processes, initiatives, constraints, commitments, and dependencies
- Current scope, exclusions, benefit assumptions, cost or capacity constraints, and evidence confidence
The method
Work through the decision.
- Restate the initiative as the measurable business outcome and change hypothesis rather than its project, platform, or workstream name
- Identify the stakeholders and value-stream stages where the problem occurs and where value must materially improve
- Map the capabilities that the initiative must create, improve, sustain, constrain, or retire at one consistent decision-relevant level
- Trace material business-object states, policies, products, organizational participation, decision rights, processes, measures, and enabling technology across the affected path
- Distinguish primary business change from supporting dependency, adjacent opportunity, inherited commitment, and work that does not trace to the outcome
- Record baseline condition, target condition, evidence, confidence, accountable owner, and material assumptions for each impact
- Test normal, exception, transition, and cross-business-unit scenarios to expose omitted operating or control obligations
- Compare credible scope options using outcome coverage, dependency exposure, adoption burden, risk, capacity, reversibility, and timing
- Present the impact grid with explicit scope, non-scope, decision gates, measures, unresolved issues, and the authority that must disposition them
What the work should produce
- Capability–value initiative impact grid
- Required scope, explicit non-scope, and option boundaries
- Information, organization, policy, product, process, and technology dependency view
- Outcome measures, assumptions, ownership, and confidence register
- Architecture, portfolio, and delivery decision points
When to stop
Stop when every material scope item traces to a business outcome and affected architecture relationship, dependencies and operating obligations are visible, and decision makers can select a bounded option. Untraceable scope must be removed, deferred, or retained through an explicit exception.
Northstar · Apply the method
Trace a platform proposal into the operating change.
Evidence: E-004 describes a controlled product demonstration without a live reservation feed, representative rural work, or an adoption test. E-007 retains a broad operating experiment and a narrower integration among the possible responses.
Apply the method: Trace the intended customer outcome through promise policy, part and skill signals, exception authority, measurement, and capacity. Compare which obligations each option actually addresses before selecting scope.
Keep this boundary: A working field check in a demonstration establishes functionality. It does not establish Northstar adoption, source quality, or customer benefit.
Archive: earlier workbook example
Worked example · Northstar v1.1
Turn a platform request into a bounded operating change.
Northstar v1.1 begins with a proposed scheduling platform. Its first decision analysis identifies these change packages for a bounded first release. They remain proposed at this stage; funding a release does not approve every policy or ownership decision within it.
| ID | Change package | Outcome | Principal dependencies |
|---|---|---|---|
| CP-01 | Promise definition and policy | One usable rule for creating, changing, cancelling, and recovering customer commitments | O-01/O-02/O-03, BO-02, Operations and Customer approval |
| CP-02 | Parts and skills confirmation | Dispatcher can distinguish confirmed, provisional, and unavailable prerequisites | BO-05 owner/source decision; skill-data validation |
| CP-03 | Scheduling and branch-exception practice | Promise reflects geography and capacity while legitimate local discretion remains usable | POL-01, M-07, the one-shift exception criterion, and named escalation authority |
The scope now includes promise policy, reliable confirmation signals, and usable exception authority. Those dependencies give leaders something concrete to fund, condition, or defer before committing to a platform.
Explore the relationships in the Atlas
Reusable Excel template
Initiative impact and smallest-useful-release workbook
Trace initiative scope to value-stream stages, capabilities, information, policy, organization, measures, and dependencies, then compare bounded release options.
Inside the workbook
- Read me and scope rules
- Initiative frame
- Architecture impact grid
- Release option comparison
- Measure sheet
Use it with your own evidence
- State the intended outcome and current decision.
- Record required architecture impacts and dependencies.
- Separate required scope from adjacent opportunity.
- Compare release options by value coverage, evidence, reversibility, and dependency exposure.
Does not replace funding approval, delivery estimation, solution design, backlog management, or benefits-realization ownership.
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 constraints must improve, how must the operating model change, and what is the smallest useful release?
Related Field Notes
- The Case for Impact Assessment
- The Smallest Useful Piece
- The Operating Model Is the Architecture of How Work Gets Done
Reference material
- Business Architecture Metamodel Guide v2.1 ↗Business Architecture Guild · Registration closed
- Extended Mapping Knowledge ↗Business Architecture Guild · Account required
- Value Creation, Value Consumption, and Navigation ↗Business Architecture Guild · Guild member