2A · Portfolio
Strategic intent, guardrails and funding.
Exercise 2F
Facilitation & Readiness System
Design the people, artifacts, rooms, boards and decision choreography that make the Value Stream Conference runnable — before, during and after the event.
Chapter 2 · Getting able to decide
Where Exercise 2F fits.
Exercise 2 builds a decision-capable conference package from contribution sources. Exercise 2F asks who organizes and facilitates the conference so that all prepared contributions become decisions, roadmap updates and refinement actions.
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 · Facilitators
Event design, readiness and decision process.
Exercise output
A facilitation team map, conference preparation backlog and runbook for the event.
Exercise 2F
What does the facilitation system create?
The facilitation system turns a set of invitees and inputs into a coherent working event. It prepares decision readiness, participant modes, artifact workflows, rooms, flow and follow-up before the conference starts.
Decision readiness
Expected decisions are known, owned and prepared before the conference starts.
Participant readiness
In-room, standby and prep-only roles are clear enough to keep the room small and decision-capable.
Artifact readiness
Roadmaps, boards, canvases, decision logs and input packs exist in usable form.
Room readiness
Physical, virtual and breakout spaces make collaboration fast, visible and low-friction.
Flow readiness
Timeboxes, breakout logic and convergence rituals guide the group from divergence to decisions.
Follow-up readiness
Owners, syncs, action logs and update rules are ready before the event ends.
Why this matters
Facilitation is the conference operating system.
A Value Stream Conference can fail even when the right people are invited. Weak input quality, unclear decision rights, missing artifact updates or no follow-up path will turn it into status theater.
Before
Interviews, input requests, readiness criteria, pre-brief pack and board setup.
During
Agenda flow, timeboxes, breakouts, decision capture and artifact updates.
After
Decision log, action owners, roadmap versioning, sync cadence and retro insights.
Always
Protect psychological safety, keep neutrality and help the group decide.
Neutral process
Facilitators do not decide the content. They design the process so experts and decision makers can decide well.
Exercise logic
From contribution package to runnable conference.
Use outputs from 2A–2E as input. Then define who prepares, hosts, captures, updates and follows up.
Input stack
Portfolio, initiatives, executing units, central functions and supplier inputs.
Decision backlog
Top flow problems and expected trade-offs that require conference decisions.
Facilitation team
Named roles for readiness, event flow, artifacts, rooms and communication.
Conference runbook
Agenda blocks, breakout logic, decision rules and standby windows.
Follow-up system
Roadmap updates, owners, sync cadence and readiness gaps.
Core test
If a decision is made in the room, does somebody immediately know which artifact changes and who owns the follow-up?
Preparation questions
The facilitation team answers three questions.
The facilitation team does not replace contribution owners. It makes the contribution system visible and usable.
Decisions
Which decisions, trade-offs and artifact updates must the conference be able to produce?
People
Who must be in the room, on standby, in breakouts or prep-only to make that possible?
Preparation
Which inputs, boards, templates, spaces and decision rules must exist before the event?
Workstreams
Before · during · after the conference.
A runnable conference needs a team that covers all three phases — not just people with sticky notes during the event.
Before
Pre-interviews, input quality checks, invite / standby map, agenda choreography, room and board setup, pre-brief pack.
During
Timeboxing, breakout hosting, decision capture, artifact updates, parking lot triage and participant energy.
After
Decision log, action ownership, roadmap versioning, sync handoff, retro insights and readiness gaps.
Role families
Who can help organize and run it?
Use these role families as a starting point. One person can hold several roles in a small conference; one role may need a small team in a large conference.
Process hosts
Lead Facilitator, co-facilitators, breakout facilitators and timekeeper.
System designers
Organizational Architect, operating-model designer and collaboration map owner.
Artifact owners
Roadmap Owner, Decision Backlog Owner, Artifact Steward and scribe.
Readiness team
Interview Lead, input quality checker, pre-brief owner and source coordinators.
Room & tooling
Room Lead, tooling host, virtual/hybrid host and technical support.
Communication
Participant comms, standby coordinator, leadership briefing and follow-up owner.
Team design principle
Every critical event function has an owner and a backup.
Decision choreography
The facilitator protects the path to decisions.
The conference should alternate between shared context, focused divergence, decision-ready convergence and artifact updates.
Context
Short input and shared frame.
Divergence
Breakouts and options.
Convergence
Trade-offs and decisions.
Artifact update
Roadmap and logs.
Handoff
Owners and syncs.
Design question
Which block of the agenda produces which artifact update — and who owns that update live in the room?
Snippet cards
Roles, artifacts and facilitation techniques.
Choose roles by responsibility gaps, not by job titles. Add the smallest structure that helps the next decision.
Facilitation roles I
- Lead Facilitator
- Co-Facilitator
- Organizational Architect
- Roadmap Owner
- Decision Backlog Owner
- Artifact Steward
- Interview Lead
- Readiness Manager
Facilitation roles II
- Breakout Facilitator
- Scribe / Decision Logger
- Timekeeper / Flow Host
- Room / Tooling Host
- Standby Coordinator
- Participant Comms Lead
- Retro / Learning Lead
Readiness artifacts
- Pre-Brief Pack
- Decision Backlog
- Invite / Standby Map
- Input Roadmap Stack
- Artifact Update Rules
- Readiness Checklist
- Conference Runbook
- Follow-Up Cadence
Technique cards
- Pre-Interviews
- Open Market
- Structured Breakouts
- Planning Adjustment
- ROAM / Risk Triage
- Confidence Pulse
- Decision Owner Assignment
- Parking Lot Triage
Checklist
Do we have the right facilitation roles?
Use this as a fast coverage scan before naming individuals. The result is a first facilitation team design with visible role gaps.
| Responsibility | Needed? | Owner known? | Backup? | Notes / risk if missing |
|---|---|---|---|---|
| Overall conference flow | □ | □ | □ | |
| Decision backlog ownership | □ | □ | □ | |
| Roadmap / board ownership | □ | □ | □ | |
| Input readiness checks | □ | □ | □ | |
| Pre-interviews / pre-briefing | □ | □ | □ | |
| Breakout facilitation | □ | □ | □ | |
| Decision logging / scribing | □ | □ | □ | |
| Room / tooling / hybrid tech | □ | □ | □ | |
| Standby coordination | □ | □ | □ | |
| Follow-up cadence / action log | □ | □ | □ |
Checklist
Conference readiness checklist.
Before the conference starts, check whether the event can actually produce decisions. A missing input is acceptable only if it has an owner and does not block the first useful decision.
| Readiness item | Missing | Draft | Ready | Owner / next action |
|---|---|---|---|---|
| Purpose and expected decisions are clear | □ | □ | □ | |
| Top flow problems are translated into decision questions | □ | □ | □ | |
| Invite / standby map exists | □ | □ | □ | |
| Input roadmaps are available enough | □ | □ | □ | |
| Capacity and constraints are visible | □ | □ | □ | |
| Boards / canvases / templates are prepared | □ | □ | □ | |
| Decision rules and escalation paths are explicit | □ | □ | □ | |
| Breakout rooms have owners and outputs | □ | □ | □ | |
| Pre-brief pack sent to participants | □ | □ | □ | |
| Follow-up syncs and owners are pre-booked | □ | □ | □ |
Checklist
In-conference execution checklist.
Use this during the event to keep the room from drifting into updates without decisions. If nothing changes in the visible artifact, ask whether the block was useful.
| During the conference | Yes | No | Action |
|---|---|---|---|
| Every agenda block has a visible output? | □ | □ | |
| Each breakout knows its decision question? | □ | □ | |
| Decision makers are in room or on standby? | □ | □ | |
| Artifacts are updated live or immediately after? | □ | □ | |
| Open decisions get owner + next sync? | □ | □ | |
| Risks are ROAMed or owned? | □ | □ | |
| Parking lot is actively triaged? | □ | □ | |
| Timeboxes are protected? | □ | □ | |
| Participants know what changed? | □ | □ | |
| End of block creates a handoff? | □ | □ |
Checklist
After-conference follow-up checklist.
The conference is not complete until decisions, roadmap changes and refinement work have owners.
| Follow-up item | Done? | Owner | Due / sync |
|---|---|---|---|
| Decision log cleaned and published | □ | ||
| Roadmap version frozen and shared | □ | ||
| Open decisions assigned to next sync | □ | ||
| Action log has accountable owners | □ | ||
| Readiness gaps become preparation backlog items | □ | ||
| Input owners know what to refine next | □ | ||
| Standby participants receive outcomes relevant to them | □ | ||
| Conference retro insights captured | □ | ||
| Next Value Stream Sync / Final Sync scheduled | □ | ||
| Learning fed back into next conference design | □ |
Closing rule
No orphan decisions, no orphan artifacts, no orphan actions.
Exercise 2F Canvas
Facilitation Team Map.
Name roles, owners, backups and decision areas. One person may own several rows in a smaller setting.
| Facilitation role | Person / team | Backup | Decision area supported | Before / during / after | Risk if missing |
|---|---|---|---|---|---|
| Lead Facilitator | |||||
| Organizational Architect | |||||
| Roadmap Owner | |||||
| Decision Backlog Owner | |||||
| Artifact Steward | |||||
| Interview / Readiness Lead | |||||
| Room / Tooling Host | |||||
| Breakout Facilitators |
Exercise 2F Canvas
Conference Preparation Backlog.
Capture the work the facilitation team must finish before the conference is safe to run. Use this as the preparation Kanban for the facilitation team.
| Preparation item | Owner | Input source | Minimum quality | Due / trigger | Status |
|---|---|---|---|---|---|
| Pre-interviews | Missing · Draft · Ready | ||||
| Decision Backlog | Missing · Draft · Ready | ||||
| Invite / standby map | Missing · Draft · Ready | ||||
| Input roadmap stack | Missing · Draft · Ready | ||||
| Conference runbook | Missing · Draft · Ready | ||||
| Breakout design | Missing · Draft · Ready | ||||
| Canvases / boards | Missing · Draft · Ready | ||||
| Follow-up workflow | Missing · Draft · Ready |
Exercise 2F Canvas
Agenda Block Facilitation Design.
Define how each block creates output and which facilitator owns the flow. Every block should answer what changes in the shared understanding, roadmap or decision backlog.
| Agenda block | Purpose | Facilitation pattern | Output artifact | Owner | Risk / fallback |
|---|---|---|---|---|---|
| Vision / context | |||||
| Breakouts Day 1 | |||||
| Alignment / review | |||||
| Planning adjustment | |||||
| Breakouts Day 2 | |||||
| Final alignment | |||||
| Retro / go-refine |
Exercise 2F Canvas
Room, Tooling & Standby System.
Design the physical and virtual environment before the event, including standby windows.
| Need | Room / tool | Owner | When needed | Failure mode | Fallback |
|---|---|---|---|---|---|
| Main room | |||||
| Breakout rooms | |||||
| Roadmap board | |||||
| Decision log | |||||
| Risk / ROAM board | |||||
| Hybrid audio / video | |||||
| Standby contact channel | |||||
| Recording / photo protocol |
Standby system test
Can the room reach the right person within minutes when a decision needs them?
Exercise 2F Canvas
Decision Capture & Artifact Update Board.
Make sure every decision has a visible artifact consequence. This is the minimum viable audit trail for conference decisions.
| Decision / trade-off | Artifact updated | Owner | Decision status | Follow-up sync | Open risk |
|---|---|---|---|---|---|
| Decision 1 | Decided · Owner · Escalated | ||||
| Decision 2 | Decided · Owner · Escalated | ||||
| Decision 3 | Decided · Owner · Escalated | ||||
| Roadmap change | Decided · Owner · Escalated | ||||
| Capacity assumption | Decided · Owner · Escalated | ||||
| Supplier / function constraint | Decided · Owner · Escalated | ||||
| Own decision | Decided · Owner · Escalated |
Exercise 2F Canvas
Facilitator Coverage by Agenda Block.
Check that critical blocks have a host, scribe, artifact owner and backup.
| Block | Host | Scribe | Artifact owner | Standby roles | Backup |
|---|---|---|---|---|---|
| Opening / vision | |||||
| Breakout 1 | |||||
| Alignment review | |||||
| Planning adjustment | |||||
| Breakout 2 | |||||
| Final review | |||||
| Retro / handoff |
Reality check
If one person is host, scribe and artifact owner at the same time, verify that this is realistic.
Fast workshop mode
15-minute facilitation readiness scan.
Use this when time is tight. It creates a strong first hypothesis and exposes dangerous gaps quickly.
Pick role cards
Select the minimum roles needed to make the conference runnable.
Run readiness checklist
Mark missing, draft or ready for decisions, invitees, inputs and boards.
Fill two canvases
Team Map and Preparation Backlog. Capture owner and next action for every gap.
Find failure modes
What could make the conference fail even if the right participants show up?
First hypothesis
Facilitation roles, missing inputs, top preparation risks and owners.
Debrief 2F
Is the conference runnable?
Close Exercise 2F by checking whether facilitation makes the conference decision-capable.
Roles
Which facilitation roles are covered and where do we still have gaps?
Readiness
Which inputs, roadmaps, constraints or artifacts are not ready enough yet?
Decision flow
Can each agenda block produce decisions or artifact updates?
Room system
Can people find the right room, board, template and standby role quickly?
Follow-up
Are open decisions, actions and roadmap changes owned after the event?
Learning
How will we inspect and adapt the conference system after the first run?
Exercise 2 complete
Turn preparation into a conference that can actually decide.
Exercise 2F closes the contribution design: the sources are known, the roles are mapped, the artifacts are prepared, and the event has a runbook for decisions, updates and follow-up.