Objective inventory
Which business objectives are on the table — local, shared, strategic, regulatory or technical?
Exercise 1B
Capture Business Objectives
Create a first inventory of the outcomes the Value Stream is expected to deliver — then mark which objectives need cross-stream coordination.
What we produce
A rough objective inventory that is good enough to identify where coordination matters.
Exercise 1A showed who belongs to the Value Stream context. Exercise 1B asks what this Value Stream is trying to achieve together — and which objectives should shape invitees, artifacts, agenda blocks and follow-up syncs.
Scope picture
Which ARTs, trains, suppliers, central functions or shared initiatives are affected?
Coordination signal
Where is the objective hard to move because many units must align, decide or sequence work?
Conference input
Which objectives should shape invitees, prepared artifacts, agenda blocks and follow-up syncs?
Key distinction
Business priority is not coordination priority.
The portfolio may tell us what matters most. Exercise 1B reveals what needs the most coordination. Two objectives can be equally important and still create completely different conference needs.
How important is this objective for the company?
Usually decided or provided by portfolio, sponsors or business owners.
How difficult is it to move this objective through the Value Stream?
Usually revealed by affected units, dependencies, decision gates and capacity conflicts.
Working rule
Never use this exercise to overrule portfolio priority. Use it to decide where the conference must create alignment.
Objective altitude
Capture objectives at the right altitude.
A useful objective describes an outcome worth coordinating. It is not a single task, and it is not a vague strategy poster.
- Implement feature X
- Write interface spec
- Run workshop
- Buy tool license
- Launch OTA update capability
- Reduce diagnostic turnaround
- Meet safety compliance window
- Enable vehicle data platform
- Become digital
- Improve customer value
- Win the market
- Be more agile
Useful formulation
By [time horizon], we want to achieve [observable business outcome] for [customer / market / internal stakeholder], and it involves [affected units].
Facilitation flow
Run it as a fast objective sketch.
Suggested 15-minute version for a 90-minute workshop. Stop after step 4 if time is tight; the optional ranking can be completed later by the facilitation team.
Frame
Explain that the exercise reveals coordination demand, not portfolio priority.
Collect objectives
Write objectives that are already known — real, anonymized or fictionalized.
Mark scope
Use the Exercise 1A landscape. Which units must contribute or are impacted?
Signal coordination need
Mark dependencies, decision gates, shared foundations, supplier or capacity conflicts.
Rank
Sort only when useful: which objectives need the most Value Stream coordination?
Close as input
Turn top objectives into questions for invitees, artifacts, agenda and cadence.
Primary canvas
Business Objective Inventory Canvas
List all objectives first. Local objectives are useful too; they reveal what does not need stream-wide coordination. Do not filter too early.
| Business objective | Source / owner | Outcome | Time horizon | Affected units | Shared? | Portfolio priority input | Coordination need | Open question |
|---|---|---|---|---|---|---|---|---|
| OTA 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? |
Canvas use
This is the primary working canvas. Encourage rough wording and rough priority signals; refinement comes later.
Canvas
Objective Scope Map
For one objective, mark where it touches the Value Stream landscape. The result is not a dependency model; it is a fast conversation starter.
Business objective
Write objective here
ART / Team
Who directly contributes?
Solution Train
Is a larger solution system involved?
Supplier / Partner
External commitment or lead time?
Central Function
Finance, legal, HR, procurement, governance?
Shared Initiative
Architecture, DevOps, cyber, AI/data, platform?
Traditional Unit
Project org, line department, PMO or service function?
Optional canvas
Objective Coordination Ranking Canvas
Use only if the group needs a fast order of where coordination should start. Rank by coordination demand, not by business value.
| Objective | Affected units | Coupling | Shared foundation | Supplier / external | Governance gate | Capacity conflict | Total signal | Rank |
|---|---|---|---|---|---|---|---|---|
| OTA compliance | 5 | high | cyber + test | test lab | regulatory | medium | high | 1 |
| Data platform rollout | 7 | high | platform + cloud | cloud partner | security | high | high | 2 |
| Cockpit UX refresh | 1 | low | none | none | none | low | low | local |
Snippet cards
Prompts for objective discovery.
The card labels are prompts, not mandatory categories. Let participants name objectives in their own language, then attach one or two tags.
Business objective types
- Market / Launch Window
- Regulatory / Safety
- Product Capability
- Platform Capability
- Quality / Reliability
- Cost / Efficiency
- AI / Data Capability
- Operational Resilience
Automotive examples
- OTA Compliance Readiness
- SDV Platform Rollout
- ADAS Feature Increment
- Cyber Evidence Chain
- Cloud Telemetry Loop
- Supplier Integration Window
- Diagnostic Turnaround
- Charging Ecosystem Readiness
Scope patterns
- ART-local objective
- Multi-ART objective
- Solution Train objective
- Whole Value Stream objective
- Supplier-dependent objective
- Central-function objective
- Shared-foundation objective
- Portfolio guardrail objective
Coordination signals
- Many affected units
- Reciprocal dependency
- Shared architecture
- Platform bottleneck
- Supplier lead time
- Compliance gate
- Capacity conflict
- Decision rights unclear
- Artifact mismatch
Multiple choice aids
Check categories first; add detail where it helps the conference design.
Participants often know the category before they know the perfect wording. Use the checklists to keep speed without losing structure.
Objective source
- □ Portfolio epic / initiative
- □ Business Owner objective
- □ ART / Product objective
- □ Regulatory obligation
- □ Customer commitment
- □ Transformation roadmap
Who is affected?
- □ Agile Release Trains # ___
- □ Solution Trains # ___
- □ Solution Areas # ___
- □ Suppliers / partners # ___
- □ Architecture / DevOps / Cyber
- □ Finance / HR / Legal / Procurement
Coordination challenge
- □ One ART / unit
- □ 2–3 ARTs / units
- □ Whole Value Stream
- □ Reciprocal dependency
- □ Decision rights unclear
- □ Supplier or compliance gate
Alternative canvas
Business Objective Card Canvas
Use one card per objective when the group works visually in Miro, Mural or PowerPoint. Attach tags for scope, coordination signals and optional rank.
Objective name
Outcome / success signal
Portfolio / source
Time horizon
Affected units
Coordination need
Why can this not stay local?
Dependencies · decision gates · capacity constraints
Conference implication
Who must be represented? What input is needed? Which decision may be required?
Open questions
What is unclear? Who can answer? By when do we need this?
Debrief
Turn objectives into conference-preparation input.
Do not end with the table alone. End with a spoken synthesis: what are we trying to achieve, and where does coordination become the problem?
Objective list
Which objectives are now visible — including local and shared objectives?
Coordination candidates
Which objectives most need Value Stream-level coordination?
Preparation needs
Which roadmaps, capacity views, constraints or decisions must be prepared?
Unknowns
Which objectives need follow-up interviews, owner clarification or better data?
Handoff
Where do shared initiatives and CoPs become visible for Exercise 1C?
Output statement
“For the first Value Stream Conference, our known Business Objectives are: [list]. The strongest coordination candidates are: [top objectives]. Portfolio priority is provided by [source]. We still need follow-up on [unknowns].”
Next handoff
Objectives reveal where shared work starts.
Exercise 1B feeds directly into Exercise 1C: shared initiatives and CoPs become visible where objectives need architecture, DevOps, cyber, platform, AI/data or transformation work.