Turn Preparation into a Managed Decision System
Form a facilitation team that owns decision quality, participant pathways, input readiness, artifact updates, and follow-through. Convert missing information and authority into a visible preparation backlog before designing the detailed agenda.
- Fast exercise
- 5 minutes
- Full exercise
- 20–35 minutes
- Input
- Modules 2.1–2.5
- Output
- Decision-capable conference package
- Next guide step
- Conference Agenda
Understanding Facilitation
Facilitation owns the decision process—not the decisions
The facilitation team creates the conditions for good choices: a clear question, the right authority and input, visible trade-space, prepared artifacts, focused interaction, a usable record, and a path from decision to refinement.
Interview, frame, curate, validate, schedule, design participation, and surface gaps.
Protect purpose, evidence, dissent, time, decision rights, convergence, and artifact updates.
Publish decisions, update sources of truth, route refinement, track owners, and test outcomes.
Preparation Is Managed Work
Visualize readiness instead of relying on reminders
Every missing decider, roadmap, option, evidence item, interview, or standby agreement is a preparation work item with an owner, due date, status, and risk if missing.
Running the Exercise
Five moves from contribution boards to a runnable conference package
-
1
Approximately 3–5 minutes
Form the Facilitation Team
Assign responsibilities by outcome. One person may hold several roles in a small conference; larger settings need explicit handoffs and a shared preparation board.
Lead FacilitatorDecision choreography Purpose, agenda Flow, timeboxes, participation, divergence, convergence, and closure.
Roadmap OwnerShared source of truth Input stack, integration logic, edit rights, versioning, and draft-roadmap update.
Decision Backlog OwnerQuestion quality Top problems, Decision Contracts, priority, readiness, status, and routing.
Interview LeadContext and gaps Pre-interviews, stakeholder reality, conflict, missing authority, and preparation signals.
Artifact StewardUsable records Templates, evidence links, decision log, canvases, update ownership, and archive.
Tooling / Room LeadInteraction reliability Boards, rooms, hybrid access, breakout support, permissions, backup, and timing cues.
Team working agreement Who owns readiness? Who can stop an unready decision? Who records the choice? Who updates the roadmap? Who follows the action after the room closes?Speaker Notes
Facilitator intentForm a facilitation team that owns decision readiness, decision Flow, artifact updates, preparation backlog, and follow-through—not the substantive business decisions themselves.
How to facilitate
- Assign roles by outcome: lead facilitator, roadmap owner, decision backlog owner, interview lead, artifact steward, and tooling or room lead.
- Use the team working agreement questions to clarify who can stop an unready decision, record the choice, update the roadmap, and follow action after the room closes.
- In smaller conferences, combine roles explicitly; in larger ones, define handoffs and a shared preparation board.
Listen and watch for
- Facilitation treated as logistics only. The team also owns decision process, input quality, and artifact truth.
- No one accountable for the decision backlog or roadmap update; that creates a beautiful meeting and a weak artifact.
- Tooling and room design discovered late, especially for hybrid windows, breakout boards, permissions, and backup.
Avoid
- Letting facilitators decide content trade-offs. They protect the process and escalation path, not the business call.
- Assuming one facilitator can carry interview design, artifact curation, agenda flow, boards, and follow-up alone in a complex conference.
- Skipping the working agreement because everyone is experienced. Experienced facilitators still need explicit handoffs.
-
2
Approximately 5–10 minutes
Write Decision Contracts for the Priority Backlog
Start with the highest-leverage items. A Decision Contract is the unit of preparation: it connects the problem, choice, authority, evidence, participation, artifact, and review.
Decision Contract Backlog Decision question Decider Due Inputs ready Participation ready Artifact Status Which integration sequence protects Q3 compliance? Portfolio sponsor Day 1 Yellow Green VS roadmap Yellow Do we fund shared test capacity or reduce scope? LPM Day 2 Red Yellow investment + capacity view Red Speaker Notes
Facilitator intentWrite Decision Contracts for the priority backlog so every major choice has a bounded question, authority, trade-space, options, evidence, participation, artifact update, and review path.
How to facilitate
- Start with the highest-leverage Flow problems and create one Decision Contract per bounded choice.
- Fill all contract fields: need, question, authority, trade-space, options, evidence, participation, and update plus review.
- Use readiness colors honestly. Red means the conference should not pretend the choice is ready without changing scope, timing, or preparation.
Listen and watch for
- Questions that combine multiple decisions; split them until one decider and one artifact update are plausible.
- Options without consequences, capacity impact, or dissent. The conference needs trade-offs, not preferred answers.
- Authority mapped to titles rather than people who can actually make or route the decision in the conference window.
Avoid
- Trying to write a contract for every issue. Prioritize the decisions that shape the conference agenda.
- Letting contracts become bureaucracy. A contract is useful only if it improves preparation and closure.
- Proceeding to agenda design with red decision contracts hidden in the backlog.
-
3
Approximately 4–8 minutes
Curate and Quality-check the Roadmap Input Stack
Connect each artifact to the decision it supports. Remove redundant presentation material, expose contradictions, and agree which editable artifacts become the conference’s working sources.
RelevantSupports a named choice The artifact changes an option, constraint, consequence, or confidence level.
OwnedHas a responsible steward A named person can explain, validate, edit, and maintain it.
CurrentUses a meaningful version Version date, source, horizon, and known changes are visible.
ComparableCan participate in a trade-off Time horizon, capacity, milestones, dependencies, and assumptions can be related.
EditableCan become the new truth The conference can update the roadmap, decision log, capacity view, or agreement.
Confidence-awareDoes not hide uncertainty Evidence, estimates, assumptions, dissent, and validation gaps are marked.
PortfolioIntent + guardrails Objectives, epics, investment, deadlines, and strategic risks.
Shared foundationsSystem coherence Architecture, platform, DevOps, security, compliance, data, and change.
TacticalContribution + capacity Roadmaps, committed work, flex, dependencies, risks, and cannot-absorb boundaries.
Integration canvasEditable Value Stream draft Objectives, problem removal, foundations, capacity envelope, decisions, and owners.
Contradiction rule: Do not reconcile every conflict before the conference. Convert material contradictions into explicit Decision Contracts.
Speaker Notes
Facilitator intentCurate the roadmap input stack so every artifact supports a named choice, has an owner and version, exposes confidence, and can become the editable source of truth after the conference decision.
How to facilitate
- Evaluate each artifact against the six quality checks: relevant, owned, current, comparable, editable, and confidence-aware.
- Remove redundant presentation material and convert material contradictions into Decision Contracts.
- Identify the working source of truth for portfolio intent, shared foundations, tactical contribution, and the integrated Value Stream draft.
Listen and watch for
- Input decks that inform but cannot be updated in the room.
- Contradictions being reconciled offline by facilitators without decision authority.
- Artifacts with different horizons, units, or assumptions that make trade-offs look cleaner than they are.
Avoid
- Treating all prepared material as equally important. The question is which artifact changes a choice.
- Hiding uncertainty to make the package look polished.
- Forgetting artifact permissions, versioning, edit ownership, or publication path.
-
4
Approximately 5–10 minutes
Build and Pull the Readiness Backlog
Record everything that could prevent a useful choice. Limit preparation WIP, prioritize by decision date and impact, and make blockers visible early enough to change the agenda.
Pre-interviews Context, conflict, authority, risk, missing perspective, and expectation.
Decision backlog Question, scope, decider, priority, due date, and status.
Invite / standby map Participation mode, window, response time, delegate, and fallback.
Input roadmap stack Artifact, owner, version, minimum quality, and decision supported.
Agenda and breakouts Decision sequence, divergence, integration, timing, and authority availability.
Canvases / boards Editable source, permissions, templates, links, and backup.
Follow-up workflow Decision publication, artifact update, refinement routing, and review.
Risk and fallback What happens if the owner, input, authority, technology, or room fails?
Facilitation Preparation Backlog Preparation item Decision supported Owner Minimum quality Due / trigger Risk if missing Status Supplier interface options integration sequence Supplier Tech Lead 3 options + impact T−5 days cannot close Day 1 Yellow Test capacity evidence fund or reduce scope V&V lead slots + lead time T−7 days false capacity plan Red Standby agreement contract change Procurement 30-min response T−3 days decision waits Green Speaker Notes
Facilitator intentVisualize preparation as managed work: missing interviews, inputs, authority, options, standby agreements, boards, follow-up paths, and risks become owned backlog items with due dates.
How to facilitate
- Create one backlog item for every missing condition that could prevent a useful choice.
- Limit preparation WIP. Pull by decision date, impact, dependency, and risk if missing rather than by who shouts loudest.
- Track minimum quality, due or trigger, owner, status, and fallback so a late item can change the agenda before it damages the conference.
Listen and watch for
- Preparation reminders living in private chats or memory instead of the visible backlog.
- Many yellow items close to the event with no fallback; yellow without a path is often red in disguise.
- Input quality problems discovered during the conference because nobody tested artifact usability beforehand.
Avoid
- Treating readiness as all-or-nothing. Some decisions can be routed, deferred, or narrowed if preparation is incomplete.
- Overloading the preparation team with too many simultaneous unowned tasks.
- Building the agenda before the backlog reveals which decisions are actually ready.
-
5
Approximately 3–6 minutes
Publish the Decision-capable Conference Package
Create one versioned package that the agenda designers, facilitators, participants, and artifact owners can use. It should make unready decisions visible rather than disguising them with more content.
01Decision backlog Priority questions, owners, dates, readiness, and routing.
02Decision Contracts Authority, trade-space, options, evidence, participation, and review.
03Invite / standby map Core, windows, standby, preparation-only, Inform-after, delegates, and fallbacks.
04Input roadmap stack Portfolio, shared foundation, tactical, function, and partner artifacts.
05Artifact update map Which source changes, who edits it, and when the update is complete.
06Readiness backlog Gaps, owners, due dates, blockers, risks, and agenda consequences.
07Facilitation ownership Before, during, and after responsibilities plus technology and room support.
08Handoff to Agenda Decision sequence, required context, breakout need, integration point, and time window.
Package release rule GREEN decisionsenter the agenda as decision windows
YELLOW decisionsenter only with a named closing action, owner, deadline, and fallback
RED decisionsare escalated, deferred, reframed, or converted into a preparation outcome—not staged as theatre
Decision AgeHow long has an open choice waited? Use age to expose neglected or blocked decisions.
Decision Lead TimeHow long from need to usable choice? Include preparation, authority, and artifact update.
Ready RatioHow many planned decisions were actually ready? Use the ratio to improve preparation, not to game the agenda.
Reopen RateHow often does missing input reverse the choice? Trace recurrence to preparation or authority gaps.
Artifact Update TimeHow fast does the source of truth change? A decision is not operational until the relevant artifact reflects it.
Speaker Notes
Facilitator intentPublish a versioned decision-capable conference package that links decision backlog, contracts, invite and standby map, roadmap input stack, readiness gaps, and artifact-update responsibilities.
How to facilitate
- Bundle the package as a working system, not a document dump: decision backlog, contracts, invite map, input stack, update owners, gaps, and follow-up workflow.
- Use a version date and package owner. Everyone should know which package is current and what changed since the previous version.
- Mark unready decisions visibly and define whether they are deferred, narrowed, prepared with risk, or routed elsewhere.
Listen and watch for
- A package that looks complete because it contains many slides but does not say who decides what and which artifact changes.
- Readiness gaps without owners and dates, especially missing authority, external evidence, capacity view, or artifact edit rights.
- The package not being used by agenda designers, which causes Exercise 3 to drift into a timetable exercise.
Avoid
- Overclaiming. The package makes the conference runnable; it does not guarantee the final roadmap is execution-ready.
- Publishing only to leaders. Artifact owners, facilitators, and participant groups need the same decision context.
- Ending without a bridge to Conference Agenda: every decision needs a place in the agenda flow.
Facilitation
Keep the preparation system honest, selective, and easy to update
Connect every input to a Decision Contract and minimum quality criterion. Decline material that has no job.
Return authority to the named decider. Facilitation owns process quality, visibility, and closure.
Reframe it as an escalation, evidence, option-generation, or preparation outcome—or remove it.
Fix access and ownership before the event. A screenshot cannot become the new source of truth.
Prioritize by decision date, Flow impact, and conference leverage. Limit work and finish the highest-value gaps.
Inspect missing evidence, absent authority, hidden constraints, weak consequence analysis, and late artifact updates.
Ready to Move On?
Ability to Decide is complete when the agenda can be designed around real decision windows
- The facilitation team owns preparation, decision Flow, artifact updates, and follow-through without taking decision authority.
- Priority decisions have bounded, versioned Decision Contracts.
- Deciders, drivers, required agreement, contributors, performers, and information paths are explicit.
- Participation modes, windows, standby response times, delegates, and fallbacks are agreed.
- Portfolio, shared foundation, tactical, central-function, and external artifacts are connected to decisions.
- Inputs are relevant, owned, current, comparable, editable, and confidence-aware.
- Material contradictions are visible as decisions rather than silently reconciled.
- Preparation work has owners, minimum quality, due dates, status, and risk if missing.
- Green, yellow, and red decisions have explicit agenda consequences.
- Every decision names its source-of-truth update and review path.
- The conference package is versioned, accessible, and understandable to all owners.
- The package is ready to drive Conference Agenda design.
Source Foundation
This page follows the intended Exercise 2F sequence in slides 44, 46, and 47 of 2026-07-13_Value_Stream_Conference.pptx. Slide 45 repeats the supplier-card content from the preceding exercise; the page resolves that duplication with facilitation-preparation prompts consistent with the surrounding 2F slides. Decision Contracts, readiness Flow, and update-time measures are explicit facilitator extensions.