Open the Problem-Solving Space Without Losing the Roadmap
Design Day 1 breakouts around the strongest Flow problems and trade-offs. Choose structured rooms, an open market, or a deliberate hybrid based on uncertainty—and require every session to leave a usable decision, roadmap delta, owner, risk, capacity assumption, or escalation.
- Fast exercise
- 5 minutes
- Full exercise
- 25–45 minutes
- Input
- Problem backlog + Vision signals
- Output
- Day 1 Breakout architecture
- Deck basis
- Slides 53–54
Understanding Day 1 Breakouts
Divergence needs freedom inside an explicit container
Day 1 opens the room for cross-unit problem-solving. Participants need enough choice to follow the real work and enough structure to leave evidence that can be integrated at the end of the day.
Divergence with Output Discipline
A conversation becomes conference work when it changes an artifact
Record context, decision, decider, consequence, date, and affected artifacts.
Edit the shared roadmap or prepare a clearly owned change proposal.
Name the person, mandate, next action, due date, and review point.
Capture probability, impact, response, owner, trigger, and next review.
State the capacity source, displacement, constraint, confidence, and validation need.
Frame the choice, missing authority or evidence, consequence of delay, and decision window.
Choose Mode by Uncertainty
The problem backlog determines how much agenda can be fixed in advance
Name the problem, room, required authority, prepared evidence, expected output, and timebox before the conference.
Use when the decision backlog is clear and readiness is high.Participants propose topics within a clear theme, self-organize around contribution, and publish outcomes using one shared contract.
Use when the room holds knowledge the preparation team could not predict.Protect decision-ready rooms first, then open capacity for emergent topics—or reserve a continuous open lane beside structured work.
Use when must-solve items and discovery both matter.Can the challenge and trade-space be framed before the event?
Can the right decider or escalation path support the room?
Do participants have enough input to work rather than merely discover missing facts?
How likely is the room to surface important topics that preparation missed?
Running the Exercise
Five moves from problem backlog to harvestable breakout work
-
1
Approximately 4–7 minutes
Classify the Work Before Choosing Rooms
Start with priority Decision Contracts, Flow problems, Vision questions, and readiness status. Distinguish work that can decide now from work that needs framing, discovery, or escalation.
Decision-readyChoose now Bounded question, options, evidence, authority, participants, and editable artifact are ready.
Problem-framingMake the problem decidable Clarify mechanism, evidence, scope, owner, consequence, and next decision question.
ExplorationSurface options and hidden work Use an open or inclusive interaction to discover perspectives, possibilities, and validation needs.
EscalationPrepare authority, not theatre Frame the missing choice, impact, time boundary, evidence, and required decision window.
Day 1 Breakout Candidate Backlog Problem / trade-off Class Readiness Required output Authority / owner Suggested mode Compliance integration sequence Decision-ready Green roadmap delta Business Owner structured Hidden platform bottlenecks Exploration Yellow problem + options Platform owner open market Speaker Notes
Facilitator intentClassify Day 1 work before choosing rooms so the conference distinguishes decision-ready work, problem framing, exploration, and escalation.
How to facilitate
- Start with Decision Contracts, Flow problems, Vision questions, and readiness status. Put each candidate into one work class before assigning a room.
- Ask whether the work can decide now, needs better framing, needs discovery, or needs authority prepared elsewhere.
- Use classification to choose facilitation format and output, not to judge importance. A high-impact topic can still be unready for a decision room.
Listen and watch for
- Decision-ready labels applied to topics with no authority, options, evidence, or editable artifact.
- Exploration topics disguised as decisions, which causes rooms to argue without enough information.
- Escalations framed as a dramatic appeal rather than a bounded missing choice with evidence and consequence.
Avoid
- Creating rooms directly from organizational areas or favorite topics.
- Treating all breakout work as the same kind of collaboration. Different work classes need different contracts.
- Forcing every problem into a decision room just because the conference should be action-oriented.
-
2
Approximately 5–10 minutes
Choose the Breakout Logic and Topic Menu
Use the deck’s cards to seed the design without assuming every card belongs in the event. Select only topics that connect to the priority problem backlog, then add the real Value Stream’s missing work.
Structured Problem Slots Top problems receive named rooms, owners, evidence, and required outputs.
Open Market Participants self-organize around emergent or hidden topics inside the conference purpose.
Roadmap Trade-off Scope versus sequence versus capacity: what should move, split, stop, or wait?
Supplier / Legal Contracts, external commitments, supplier cadence, rights, and escalation paths.
Security Evidence Cross-unit evidence chain, auditability, safety, and threat-model needs.
Toolchain Standard Shared tools, integration Flow, Definition of Done, quality gates, and automation.
Platform Dependency Capabilities, API contracts, consumption model, service levels, and bottlenecks.
Capacity Conflict Where are units overloaded, and which work is deferred, split, sequenced, or enabled?
Architecture Decision Interfaces, standards, technical runway, integration, and cross-unit design choices.
Refinement Cadence What must happen between this conference, Final Sync, and PI Planning?
Risk / ROAM Prework Which risks need leadership review, treatment, evidence, or named owners?
Open Topic Card Add a problem the real Value Stream cannot ignore.
Hybrid design option Protect must-solve structured rooms, reserve an open lane for emergence, and use one output contract for both.Speaker Notes
Facilitator intentChoose structured, open-market, or hybrid breakout logic based on problem clarity, authority readiness, evidence readiness, and emergence value.
How to facilitate
- Use structured slots for known top problems with owners and required outputs; use open market when hidden topics and discovery value matter.
- Use hybrid when must-solve items and emergence both matter: structure first, open later, or reserve a continuous open lane.
- Decide parallelism by representation capacity. Parallel sessions work only if decision roles and knowledge can split without breaking outputs.
Listen and watch for
- Open market chosen because it feels agile, not because emergence is valuable.
- Structured rooms chosen because preparation is strong while participants still hold unknown perspectives that need discovery.
- Parallel rooms that require the same scarce decision maker, architect, supplier, or roadmap owner.
Avoid
- Copying a template agenda without testing uncertainty and authority readiness.
- Equating more rooms with more progress. More rooms can create more integration debt.
- Letting room format become ideological. The right mode is the one that creates useful outputs for this conference.
-
3
Approximately 5–10 minutes
Allocate Rooms, Authority, and Scarce Expertise
A parallel agenda fails when the same decider, architect, supplier representative, or artifact owner is required in several rooms. Model participant capacity and use decision windows or standby agreements instead of assuming unlimited availability.
Parallel Room Capacity Map Room / session Problem Core participants Decision window Standby Artifact owner Collision / fallback A · Integration sequence ART A/B, Architect BO 11:00–11:20 Legal 15 min Roadmap owner move BO window B · Platform capacity Platform + consumers LPM 11:20–11:40 Finance 20 min Platform PM prepare escalation Open market emergent self-selected none by default SME pool topic convenor route decision Can people split? Parallel rooms need independent representation or deliberately sequenced decision windows.
Can artifacts split? Define edit ownership, versioning, and integration when several rooms touch the same roadmap.
Can authority wait? Use a decision window, named delegate, standby response time, or explicit escalation.
Can the room recover? Include movement, technology, delayed experts, overruns, and integration buffers.
Speaker Notes
Facilitator intentAllocate rooms, people, and standby access so each breakout has enough authority, expertise, representation, and artifact ownership to produce a usable output.
How to facilitate
- For each room, name the problem or trade-off, participants, required output, artifact to update, and timebox.
- Check scarce roles across rooms: deciders, Business Owners, architects, compliance, supplier, platform, and roadmap owners cannot be in two places at once.
- Use decision windows and standby paths where full attendance would overload the room but response time still matters.
Listen and watch for
- Rooms with participants who can discuss but not decide, update, validate, or escalate.
- Key performers excluded from rooms that will change their work, creating low trust and poor feasibility later.
- Expert-heavy rooms missing business or capacity reality.
Avoid
- Allocating by headcount balance rather than decision need.
- Sending all senior leaders to one room and leaving other rooms without authority.
- Ignoring the integration burden that will follow if rooms make incompatible decisions.
-
4
Approximately 5–10 minutes
Write a Breakout Contract for Every Room
Give structured and open sessions the same minimum contract. Open participation does not mean an undefined purpose, invisible work, or an optional harvest.
Challenge One problem, trade-off, question, or theme linked to the Value Stream purpose.
Ready input Decision Contract, roadmap slice, evidence, options, constraints, and known dissent.
Participation Convenor, core roles, decider, artifact owner, standby experts, and open attendance.
Interaction Structured problem-solving, Open Space, 1-2-4-All, option comparison, or another explicit pattern.
Timebox Working time, check-ins, decision window, harvest, transition, and fallback.
Output Decision, roadmap delta, owner, risk, capacity assumption, escalation, or validation plan.
Artifact Editable source of truth, template, permissions, version, and integration point.
Closure Definition of done, unresolved-item route, next sync, and reporting sentence.
Breakout contract We will work [challenge] with [people and authority] using [interaction] for [timebox] to produce [output], update [artifact], and route open work to [next sync].Speaker Notes
Facilitator intentWrite a contract for every Day 1 breakout so participants know the question, inputs, roles, output, artifact, and harvest format before they begin.
How to facilitate
- Use a standard contract: purpose, decision or problem, required inputs, participants, output type, artifact update, decision rights, and timebox.
- Make the output discipline visible: decision, roadmap entry, owner, risk, capacity assumption, escalation item, or validation backlog item.
- Pre-load each room with the relevant Vision Block signals, Decision Contract, Flow problem evidence, and prepared artifacts.
Listen and watch for
- Breakouts beginning with a generic prompt and then inventing their own scope.
- Outputs defined as discuss or align rather than an artifact or decision signal.
- Rooms that lack a recorder or artifact steward; harvest quality drops immediately.
Avoid
- Writing overly narrow contracts that suppress useful learning. Leave room for evidence and dissent.
- Letting every room use a different harvest shape; integration becomes much harder.
- Sending people into breakouts without knowing how leadership will consume their output.
-
5
Approximately 4–8 minutes
Design the Harvest into the Shared Draft
Do not wait for a final report-out to discover incompatible outputs. Let rooms update their owned sections, publish compact change cards, and surface collisions to the integration owner throughout the breakout period.
Work in room→Update owned artifact→Publish delta card→Integration owner checks collision→Route conflict to AlignmentDay 1 Harvest Board Room Decision / learning Artifact updated Owner Conflict / risk Alignment action Next sync A sequence option B VS roadmap Roadmap owner supplier window leadership decision Day 1 Alignment B capacity gap capacity view Platform PM funding missing overnight queue Day 2 Adjustment Day 1 Breakout release rule READYeach room has a contract, feasible participation, an editable artifact, a required output, and an integration route
NOT READYsessions are named by department, share scarce people invisibly, or depend on post-event reconciliation
Speaker Notes
Facilitator intentHarvest Day 1 outputs in a form that can be overlaid, reviewed, routed, and turned into new guardrails for Day 2.
How to facilitate
- Collect outputs in a consistent structure: decision, roadmap change, owner, risk, capacity assumption, unresolved question, and artifact updated.
- Ask each room what changed from the prepared draft and what still needs leadership, evidence, or Day 2 refinement.
- Convert unresolved items into the Alignment Block input rather than letting them remain room-local notes.
Listen and watch for
- Outputs that sound positive but do not update roadmap, decision log, risk log, or refinement backlog.
- Room-level confidence hiding a cross-room contradiction.
- Parking lot items with no owner, route, or decision window.
Avoid
- Ending Day 1 breakouts with report-outs only. The next block needs integratable deltas.
- Accepting verbal agreement as finished. If the artifact is not updated, the decision is fragile.
- Letting unresolved conflicts wait until Final Alignment; many belong in the end-of-Day-1 Alignment Block.
Facilitation
Let participants self-organize around work—not around ambiguity
Return to Flow problems and decisions. Name rooms by challenge or trade-off, not by department.
Fix the theme, time, output contract, integration artifact, and immovable givens; leave topic creation and movement open.
Generate options and evidence, then prepare a decision window. Do not manufacture consensus that cannot bind the system.
Sequence rooms, create office hours, agree standby service levels, use delegates, or provide reusable evidence.
Use a clear selection method, keep minority options visible, and translate the result into an owner or next decision.
Publish change cards and inspect only conflicts, decisions, risks, and roadmap deltas in plenary.
Ready to Move On?
Day 1 Breakouts are ready when freedom and integration can coexist
- Priority Flow problems, Decision Contracts, and Vision questions are classified as decision, framing, exploration, or escalation work.
- Structured, open, or hybrid logic is chosen from problem, evidence, authority, and emergence needs.
- Every planned topic traces to the Value Stream purpose rather than an organizational silo.
- Parallel rooms respect the real availability of participants, deciders, experts, and artifact owners.
- Decision windows, standby response times, delegates, collisions, and fallbacks are explicit.
- Every room has a Breakout Contract and a named convenor.
- Open-market topics use the same minimum output and artifact discipline as structured rooms.
- Every session produces a decision, roadmap delta, owner, risk, capacity assumption, escalation, or validation plan.
- Rooms can edit or clearly propose changes to the relevant source of truth.
- Delta cards and an integration owner expose collisions before final report-out.
- Unresolved conflicts have an Alignment action and next sync.
Source Foundation
This page distills slides 53–54 of 05 Value_Stream_Conference.pptx. Work classification, participant-capacity modeling, Breakout Contracts, delta cards, and continuous harvest are facilitator extensions. Open Space and Liberating Structures are offered as interaction options, not mandatory conference frameworks.