Make the Coordination Demand Behind the Objectives Visible
Build a rough objective inventory that is good enough to show which outcomes need several units to align, decide, or sequence work—and which objectives can remain local.
- Fast exercise
- 5 minutes
- Full exercise
- 10–15 minutes
- Input
- Value Stream Landscape
- Output
- Objective inventory + coordination demand
- Next stage
- Value Stream Initiatives
Understanding Business Objectives
Use objectives to design coordination—not to repeat portfolio prioritization
A Value Stream Conference needs to know what the value stream is trying to make true. The purpose of this stage is not to approve or reprioritize strategy. It is to discover how each objective changes the coordination system.
Decide business priority
Portfolio strategy and investment decisions remain authoritative inputs to the conference.
Expose coordination demand
Show what must be aligned across the value stream to achieve each objective reliably enough.
Running the Exercise
Four moves from objective list to conference input
-
1
Approximately 1 minute
Open the Objective Space
Ask for every objective that may shape work in the selected value stream: strategic, customer, regulatory, operational, technical, and learning objectives. Local objectives belong in the first inventory too.
StrategicPortfolio intent Strategic themes, epics, investment choices, or market moves.
CustomerOutcome and experience Adoption, service quality, user need, or commercial result.
RegulatoryReadiness and evidence Compliance, safety, audit, certification, or launch windows.
OperationalRun and sustain Reliability, cost, resilience, support, or decommissioning.
TechnicalCapability and health Architecture, platform, data, security, quality, or modernization.
LearningReduce uncertainty Experiments, discovery, customer feedback, or feasibility proof.
List first. Filter later. A local objective helps reveal what does not need value-stream-wide coordination.
Speaker Notes
Facilitator intentOpen a broad but bounded inventory of objectives so the group can see what the value stream is trying to make true before deciding which outcomes create real cross-unit coordination demand.
How to facilitate
- Start from the Value Stream Landscape and ask which strategic, customer, regulatory, operational, technical, or learning objectives may affect the selected value stream.
- Invite rough wording. Objectives can be real, anonymized, or fictionalized, as long as the outcome, horizon, and affected scope remain useful for conference design.
- Keep local objectives in the first inventory. They help the group distinguish what can stay local from what truly needs value-stream-wide coordination.
Listen and watch for
- Participants offering project names, epics, or initiatives without naming the outcome they are meant to create.
- The group filtering too early because an objective appears local, politically sensitive, or not fully formulated.
- Objectives that are really constraints or solutions in disguise, such as implement tool X, migrate team Y, or adopt process Z.
Avoid
- Turning this into a portfolio prioritization meeting. Portfolio priority is an input; the exercise asks how the current objective changes coordination.
- Forcing perfect objective wording before the group understands the coordination system behind it.
- Ignoring technical, regulatory, operational, or learning objectives because they are not phrased as classic business outcomes.
-
2
Approximately 2–5 minutes
Capture the Objective Inventory
Use short wording and rough horizons. The canvas needs enough detail to locate coordination demand without becoming a portfolio database.
Business Objective Canvas Business objective Source / owner Outcome Time horizon Affected units Shared? Portfolio priority Coordination need Open question Over-the-air compliance Portfolio / BO Regulatory readiness Q3 ART A, Security, Legal yes high high evidence chain? Cockpit UX refresh ART B PM Customer experience next PI ART B no medium low dependencies? Data platform rollout Platform owner Telemetry capability 2 PIs 3 ARTs, Cloud, Supplier yes high high lead times? Examples may be real, anonymized, or fictionalized. Preserve only the detail needed to design the next coordination step.
Speaker Notes
Facilitator intentTurn the objective conversation into a lightweight canvas that preserves source, outcome, horizon, affected units, sharedness, priority signal, coordination need, and open questions without becoming a portfolio database.
How to facilitate
- Use the canvas columns from the reference deck: business objective, source or owner, outcome, time horizon, affected units, shared, portfolio priority, coordination need, and open question.
- Ask for enough detail to design the next coordination step, not enough detail to fully approve the objective.
- For each row, connect affected units back to the Value Stream Landscape. This makes the inventory operational instead of aspirational.
Listen and watch for
- High-priority objectives without an owner or source. That may be valid, but it is a preparation gap, not a fact to hide.
- Affected units listed as departments rather than contributors to an outcome, evidence chain, interface, capacity constraint, or decision path.
- Open questions that point to missing conference preparation: evidence chain, supplier lead time, architecture boundary, capacity envelope, or decision rights.
Avoid
- Letting the canvas turn into a complete portfolio backlog. It is a conference-preparation artifact for coordination demand.
- Deleting local objectives from the canvas. Mark them local later; do not lose them before the comparison exists.
- Treating the example rows as content to copy. They demonstrate the level of detail, not the expected objective set.
-
3
Approximately 2–4 minutes
Test the Coordination Demand
For each objective, trace the affected units on the landscape. Then classify the minimum coordination scope.
Local One unit can decide and deliver Keep the objective visible but out of the value-stream-wide conference unless a wider dependency appears.
Shared Several units must align Sequence, capacity, interface, evidence, or policy decisions cross organizational boundaries.
Unknown The coordination path is unclear Record the uncertainty and assign a validation owner rather than guessing.
Ask four questions- Which units contribute to or constrain the outcome?
- Where must work, evidence, or decisions be sequenced?
- Which shared capability or scarce capacity is involved?
- What happens if the units optimize locally?
Speaker Notes
Facilitator intentClassify each objective by the minimum coordination scope it really requires so the future conference focuses on objectives that need cross-unit alignment, decisions, sequencing, or shared capacity.
How to facilitate
- Take one objective at a time and trace its affected units on the Value Stream Landscape before classifying it as local, shared, or unknown.
- Use the four questions on the slide to locate the mechanism: contributors, sequencing, shared capability or scarce capacity, and the risk of local optimization.
- Ask what would change in the conference because of this objective: invitees, prepared artifacts, agenda blocks, decision rights, or follow-up syncs.
Listen and watch for
- Everything being marked shared because many people care about it. Shared coordination means several units must align, decide, sequence, or resolve dependencies.
- A local objective with hidden shared constraints, such as compliance evidence, supplier access, platform dependencies, or central function approval.
- Unknown coordination paths. Do not guess; record the uncertainty and name who can validate it.
Avoid
- Equating business priority with conference relevance. A lower-priority objective may still have high coordination demand, and a high-priority objective may be locally manageable.
- Expanding every shared objective into solution design. The goal is to identify coordination demand, not to solve the coordination problem yet.
- Creating false precision with a scoring model before the group has a clear causal claim about coordination.
-
4
Approximately 2–4 minutes
Prepare the Conference Input
Translate the strongest coordination demands into practical implications for later conference design. Keep the objective authoritative; treat the coordination design as a hypothesis.
PeopleWho must represent outcome and delivery reality? Objective owner, affected units, experts, operations, supplier, or governance roles.
ArtifactsWhat must be prepared? Objective evidence, milestone view, architecture, capacity, risk, or customer signal.
AgendaWhat must be aligned or decided? Sequencing, trade-off, ownership, interface, evidence, or escalation.
CadenceWhat needs follow-up? Which roadmap or synchronization point will keep the decision alive?
Objective sourceAffected unitsCoordination claimConfidence H/M/L/?Validation ownerWe know what the value stream is trying to make true—and where coordination will be hardest.
Speaker Notes
Facilitator intentConvert the strongest coordination demands into concrete Value Stream Conference preparation inputs: people, artifacts, agenda decisions, cadence implications, confidence, and validation ownership.
How to facilitate
- For each high-demand objective, ask what the conference must be able to decide or align that ordinary local planning cannot handle well enough.
- Translate the coordination claim into four preparation fields: people, artifacts, agenda, and cadence.
- Add confidence and validation ownership. An objective can be authoritative while the coordination design around it remains a hypothesis.
Listen and watch for
- Invitee implications hidden inside vague statements such as we need alignment or business input.
- Artifact gaps: objective evidence, milestone view, capacity data, architecture constraints, customer signal, risk view, or supplier lead times.
- Cadence implications that will matter after the conference, especially if the objective needs repeated synchronization before PI Planning.
Avoid
- Leaving the exercise with only an objective list. The output should say how objectives change conference preparation.
- Treating objective input as frozen when the affected units or coordination claim are still low confidence.
- Forgetting the next handoff: strong coordination demands become inputs to Value Stream Initiatives, Capacity, Flow Problems, and Ability to Decide.
Facilitation
Keep the conversation on outcomes and coordination
Ask what outcome, behavior, readiness condition, or business result the project is meant to create.
Capture the concern as an input for portfolio governance. Return to how the current priority changes coordination.
Ask who can decide and deliver independently. Keep work local wherever the value stream does not gain from broader coordination.
Anonymize the wording while preserving horizon, affected units, and coordination mechanics.
Keep the inventory, then mark the objectives that materially change conference people, artifacts, or decisions.
Record “owner?” as a diagnostic signal. Do not silently assign accountability in a five-minute exercise.
Ready to Move On?
The inventory is useful when it changes the coordination picture
Do not require perfect objective wording. Require enough clarity to connect outcomes to shared work.
- Strategic, customer, regulatory, operational, technical, and learning objectives were considered.
- Local objectives remain visible rather than being filtered out prematurely.
- Every material objective has a source or owner where known.
- Outcome and rough time horizon are understandable.
- Affected units are traced to the Value Stream Landscape.
- Local, shared, and unknown coordination demand are distinguished.
- High-demand objectives have at least one concrete coordination claim.
- Important unknowns have a validation owner or follow-up path.
- Conference implications for people, artifacts, agenda, or cadence are visible.
Source Foundation
This page distills Exercise 1B, slides 10–11 of 05 Value_Stream_Conference.pptx. Public SAFe sources are included as examples of how strategic intent, portfolios, and value-stream funding can provide authoritative inputs without turning this exercise into portfolio reprioritization.