2A · Portfolio
Strategic intent, guardrails and funding.
Exercise 2E
Supplier & External Partner Contributions
Decide which suppliers, partners and external firms must contribute to the Value Stream Conference — and what they must bring: roadmaps, capacity, lead times, contracts, interfaces and decision rights.
Chapter 2 · Getting able to decide
Where Exercise 2E fits.
Exercise 2 builds a decision-capable conference package from the outputs of Exercise 1. After portfolio, initiatives, executing units and central functions are mapped, Exercise 2E asks which external organizations can block, accelerate, validate or commit a key part of the Value Stream Roadmap.
2B · Value Stream Initiatives
Shared foundations and initiative roadmaps.
2C · Executing Units
Capacity, contribution and feasibility.
2D · Central Functions
Constraints, support and governance.
2E · Suppliers / Partners
External commitments, lead times and contracts.
2F · Facilitation
Decision process and readiness system.
Exercise 2E
What counts as external contribution?
A supplier contribution is any external capability, commitment, evidence gate or lead time that the Value Stream must coordinate to deliver business objectives. Use a broad definition: if an external organization changes flow, capacity, risk, quality or sequencing, it belongs in this exercise.
Product supplier
Provides product increments, components, modules or domain capabilities that become part of delivered value.
Engineering partner
Contributes design, development, testing, integration or specialist expertise.
Platform / cloud provider
Provides shared technical services, environments, API capabilities or operations support.
Integration partner
Connects systems, suppliers, environments or release trains and owns critical handoffs.
Validation / assessor
Provides test capacity, certification, safety case, audit or regulatory evidence.
Customer / ecosystem partner
Represents pilots, fleets, ecosystem interfaces, field feedback or customer commitments.
Why this matters
External dependencies often dominate the real flow.
A Value Stream Conference that ignores suppliers may create a roadmap that looks aligned internally but fails at contracts, lead times, interfaces or evidence gates.
Lead-time traps
Hardware orders, certification slots, contract changes or test-lab capacity may exceed one PI.
Contract friction
Fixed-scope contracts, late change requests and approval gates can neutralize agile collaboration.
Interface ambiguity
APIs, specs, data ownership, test environments and acceptance criteria are often not jointly owned.
Evidence gaps
Safety, security, compliance or quality evidence arrives too late.
Explicit inputs
2E makes clear who represents each dependency, what they bring, what they can decide and when they are needed.
Exercise logic
From flow problem to external contribution.
Start with the prioritized flow problem backlog. Do not invite suppliers generally; invite them for a concrete decision, constraint, interface, milestone or risk.
Flow problem
Which top flow problem has an external component?
External party
Which supplier, vendor or partner owns part of it?
Contribution
What roadmap, capacity, contract, evidence or interface must they bring?
Presence mode
In room, standby window, prep-only, async review or not needed?
Decision
What can change during the conference?
Shortcut question
Which external dependency would most likely make the conference roadmap wrong if we ignored it?
Contribution model
What suppliers must bring to the party.
The useful external contribution is a prepared input that makes trade-offs possible. “We will check after the conference” is usually too late.
Supplier roadmap
Milestones, releases, API changes, integration windows and committed increments.
Capacity plan
Available people, skills, test slots, delivery windows, support capacity and known overload.
Lead-time map
Long poles: procurement windows, sample availability, certification lead time and environment setup.
Interface agreement
Ownership, API/spec, acceptance criteria, versioning, data and integration responsibilities.
Contract constraints
Change clauses, procurement gates, cost impacts, legal limits and renegotiation windows.
Escalation path
Who can decide what, by when, and with which fallback options.
Checklist 1
Which external parties are relevant?
Run a fast scan. Mark whether each external party is needed in the room, on standby, prep-only or not relevant for the current conference.
| External party | In room | Standby | Prep only | Not needed | Why / artifact needed |
|---|---|---|---|---|---|
| Key product supplier | □ | □ | □ | □ | roadmap · commitment · capacity |
| Software supplier | □ | □ | □ | □ | delivery plan · dependencies |
| Hardware / component supplier | □ | □ | □ | □ | samples · lead time · integration |
| Platform / cloud provider | □ | □ | □ | □ | service roadmap · constraints |
| Integration partner | □ | □ | □ | □ | interface plan · handoffs |
| Test lab / validation partner | □ | □ | □ | □ | slots · evidence · bottlenecks |
| Certification / assessor | □ | □ | □ | □ | gates · audit timing |
| Toolchain vendor | □ | □ | □ | □ | roadmap · migration impact |
| Customer / pilot partner | □ | □ | □ | □ | field feedback · launch commitments |
Checklist 2
Why do we need them?
The inclusion reason should point to a decision or artifact. Otherwise the partner can usually be handled asynchronously.
| External inclusion reason | Yes | Maybe | No | Example decision / question |
|---|---|---|---|---|
| Can block a Business Objective | □ | □ | □ | change scope, sequence, or date? |
| Owns a critical interface | □ | □ | □ | API/spec decision needed? |
| Capacity is scarce or uncertain | □ | □ | □ | commitment or lead-time decision? |
| Contract limits collaboration | □ | □ | □ | change clause or renegotiation? |
| Quality gate depends on them | □ | □ | □ | acceptance criteria or SLA? |
| Evidence / certification gate matters | □ | □ | □ | what proof, by when? |
| Supplier roadmap changes ours | □ | □ | □ | align release windows? |
| Escalation path is unclear | □ | □ | □ | who can decide immediately? |
Snippet cards
Roles, partners and artifacts.
Use these cards to select external contributors because they affect one of your top flow problems, not because the supplier list should look complete.
Supplier roles
- Supplier Product Lead
- Supplier Engineering Lead
- Supplier Program / Delivery Lead
- Supplier Interface Owner
- Supplier Quality Lead
- Supplier Security / Safety Lead
- Supplier Commercial Owner
- Supplier Executive Sponsor
External partner types
- System integrator
- Platform / cloud provider
- Test lab / validation partner
- Certification / assessor
- Toolchain vendor
- Data / AI service provider
- Customer / pilot partner
- Own external card
Supplier artifacts
- Supplier Roadmap
- Capacity / Lead-Time Map
- Interface Agreement
- Contract Constraint View
- Quality / SLA View
- Evidence Plan
- Risk / Issue Log
- Escalation Path
Decision tests
- Can decide, escalate or commit?
- Can shorten the external decision loop?
- Can update the artifact?
- Can clarify contract, interface or evidence constraints?
Presence modes
In room, standby, prep-only or not needed?
Use modes to reduce over-attendance without creating decision latency. Good design keeps the conference small and the decision loop short.
In room
Needed for active trade-off decisions, roadmap updates or contract/capacity commitments.
Standby window
Available in a defined conference window; called in only if the decision needs them.
Prep-only input
Prepares artifact and named escalation path; no live participation needed.
Async review
Reviews draft after the conference; suitable only for low-risk dependencies.
Not needed
No relevant flow problem, decision, artifact or external constraint in current scope.
Escalation-only
Senior supplier contact is not in the room but can resolve priority conflicts quickly.
Checklist 3
External readiness check.
For every critical external dependency, assess whether the minimum input is ready enough for the conference.
| Input / readiness item | Ready | Draft | Missing | Owner / due date |
|---|---|---|---|---|
| Supplier roadmap or milestone plan | □ | □ | □ | |
| Capacity / lead-time forecast | □ | □ | □ | |
| Interface or API agreement | □ | □ | □ | |
| Contract / commercial constraint view | □ | □ | □ | |
| Quality / SLA / acceptance criteria | □ | □ | □ | |
| Evidence / certification plan | □ | □ | □ | |
| Risk / issue / dependency log | □ | □ | □ | |
| Escalation path and standby contacts | □ | □ | □ |
Checklist 4
Contract and collaboration friction.
Supplier flow problems often sit in the gap between agile intent and traditional commercial structures. This checklist can be run by Procurement, Legal and the supplier owner before the conference.
| Question | Yes | Maybe | No | Implication for preparation |
|---|---|---|---|---|
| Contract allows scope trade-offs? | □ | □ | □ | bring change clauses / commercial owner |
| Supplier backlog can change during PI? | □ | □ | □ | define decision window |
| Acceptance criteria are shared? | □ | □ | □ | prepare interface / quality agreement |
| Supplier cadence is aligned? | □ | □ | □ | map supplier events and syncs |
| IP / data / security constraints known? | □ | □ | □ | bring legal/security view |
| Escalation path is fast enough? | □ | □ | □ | name decision-capable contacts |
| Roadmap changes affect cost? | □ | □ | □ | bring cost impact model |
| Standby window is reserved? | □ | □ | □ | block calendar / no other meetings |
Exercise 2E Canvas
Supplier / Partner Contribution Board.
Use one row per external party that matters for the top flow problems or business objectives. The output is an external invite and contribution hypothesis for the conference package.
| Supplier / partner | Affected objective / initiative | Invitee / representative | Artifact brought | Decision needed | Presence mode |
|---|---|---|---|---|---|
| Supplier A | |||||
| Supplier B | |||||
| Integration partner | |||||
| Platform / cloud provider | |||||
| Test / validation partner | |||||
| Certification / advisor | |||||
| Customer / pilot partner |
Exercise 2E Canvas
Supplier Roadmap & Capacity Input.
Capture the minimum supplier forecast needed to make the Value Stream Roadmap realistic. Use rough data: the goal is visibility, not contractual precision.
| External party | Roadmap / milestones | Capacity unit | Lead time | Known bottleneck | Confidence |
|---|---|---|---|---|---|
| Supplier A | people / team weeks / slots | High · Med · Low | |||
| Supplier B | High · Med · Low | ||||
| Test lab | test slots / samples | High · Med · Low | |||
| Cloud provider | service capacity / support | High · Med · Low | |||
| Certification advisor | review capacity / gates | High · Med · Low | |||
| Own partner | High · Med · Low |
Exercise 2E Canvas
Interface & Integration Board.
Many supplier delays are interface delays. Make ownership, maturity and test needs visible.
| Interface / deliverable | Internal owner | External owner | Maturity | Environment / test need | Decision / gate |
|---|---|---|---|---|---|
| API / data contract | Idea · Draft · Agreed | ||||
| Hardware sample | Idea · Draft · Agreed | ||||
| Integration environment | Idea · Draft · Agreed | ||||
| Security evidence | Idea · Draft · Agreed | ||||
| Acceptance criteria | Idea · Draft · Agreed | ||||
| Own interface | Idea · Draft · Agreed |
Exercise 2E Canvas
Contract, Constraint & Escalation Backlog.
If a supplier constraint can block the Value Stream Roadmap, give it an owner and a decision path. Prioritize by Value Stream impact: what could invalidate the roadmap or delay an important business objective?
| Constraint / risk | Supplier owner | Internal owner | Affected item | Decision needed | Rank |
|---|---|---|---|---|---|
| Contract change window | |||||
| Procurement lead time | |||||
| Supplier capacity conflict | |||||
| Quality / SLA risk | |||||
| Security / IP restriction | |||||
| Certification timing | |||||
| Own constraint |
Exercise 2E Canvas
Invite & Standby Mode Matrix.
Keep the room small while keeping the supplier decision loop short. Standby means real availability: no other meeting during the decision window.
| External party | In room | Standby window | Prep only | Escalation contact | Why this mode? |
|---|---|---|---|---|---|
| Supplier A | □ | ||||
| Supplier B | □ | ||||
| Integration partner | □ | ||||
| Test lab | □ | ||||
| Certification advisor | □ | ||||
| Customer / pilot | □ | ||||
| Own partner | □ |
Fast workshop mode
10-minute supplier contribution scan.
Use this when the workshop timebox is tight. It creates a useful first hypothesis without over-analyzing supplier governance.
Mark external parties
Use Checklist 1. Only mark parties connected to top flow problems.
Pick artifact cards
Roadmap, capacity, interface, contract, quality, evidence, escalation.
Choose presence mode
In room, standby, prep-only, async review or not needed.
Top 3 contributors
Artifacts needed and named internal owners for follow-up.
Use longer canvases selectively
Only for external parties that are truly decision-relevant.
Examples
Typical supplier contribution patterns.
Use these patterns as prompts. Replace them with your actual external dependencies.
Traditional supplier contract
Change requests are slow. Bring change clauses, negotiation window and commercial owner.
External test bottleneck
Validation slots constrain release timing. Bring capacity, sample needs and evidence plan.
Cloud platform dependency
Shared platform roadmap shifts. Bring API roadmap and operational constraints.
Component lead time
Samples or hardware arrive too late. Bring lead-time map and fallback options.
Cyber / safety evidence
Certification evidence is missing. Bring gates and evidence expectations.
Pilot customer deadline
Field trial window is fixed. Bring acceptance logic and launch constraints.
Debrief 2E
Is the supplier contribution decision-capable?
Close the exercise by testing whether external dependencies are now visible enough for conference preparation.
Coverage
Which top flow problems have relevant external contributors?
Representation
Who can represent each supplier or partner with enough decision power?
Artifacts
Which external roadmaps, capacity forecasts, contracts, evidence plans or interfaces are needed?
Mode
Who is in the room, who is on standby, who only prepares input?
Escalation
Where is the supplier decision path still too slow?
Owner
Who owns each missing external input before the conference?
Next · Exercise 2F
From external dependencies to a runnable conference system.
After portfolio, initiatives, executing units, central functions and suppliers are mapped, the facilitation team turns the decision backlog, invite map, input roadmap stack and readiness gaps into a conference that can actually run.