Turn Day 1 Conflicts into Better Guardrails for Day 2
Integrate the first breakout results, expose conflicts across roadmap layers, use leadership for choices only they can make, and manage overnight work as a visible decision queue. Reopen Day 2 from an explicit Planning Adjustment so no room continues from yesterday’s invalid assumptions.
- Fast exercise
- 5 minutes
- Full exercise
- 25–45 minutes
- Input
- Day 1 deltas + conflicts
- Output
- Updated guardrails + Day 2 focus
- Deck basis
- Slides 55–56
Understanding Alignment
Convergence makes conflict usable
Alignment is not a sequence of breakout presentations. It is the point where locally coherent outputs are overlaid, incompatible assumptions become visible, decision rights are activated, and the second day receives a changed basis for work.
Convergence, Not Reporting
Five linked stages turn a draft into a new starting point
Overlay roadmap deltas, objectives, capacity, foundations, risk, and decisions.
Use the authority prepared in Step 2; do not reopen choices the room already owns.
Assign a small queue of bounded work with owners, evidence, deadlines, and fallbacks.
Communicate decisions, guardrails, risks, invalidated assumptions, and Day 2 focus.
Route refined questions, roadmap gaps, organization hypotheses, and required validation.
Day 2 Needs New Truth
A Planning Adjustment is a delta briefing with consequences
The morning reset names what changed since the first breakout phase and how that change affects the roadmap, available options, capacity assumptions, risks, room design, and required decision makers.
State the decision, decider, reasoning boundary, date, and affected artifact.
Budget, priority, evidence, supplier, architecture, policy, or deadline boundaries.
Show the invalidated premise and which rooms, options, estimates, or roadmap entries change.
New risk, treatment, owner, trigger, escalation, or accepted exposure.
Prioritized refinement questions, organization hypotheses, validation needs, and decision windows.
Rooms, people, sequence, timebox, artifact, or fallback must reflect the new truth.
If nothing in the morning update changes work, the Alignment Block probably produced status rather than integration.
Running the Exercise
Five moves from breakout deltas to a changed Day 2 basis
-
1
Approximately 5–10 minutes
Overlay the Draft Across Its Decision Layers
Bring Day 1 outputs into one shared view. Inspect deltas and collisions across objectives, Flow problems, shared foundations, tactical capacity, external constraints, risk, and open decisions.
Objectives Outcomes, milestones, deadlines, strategic themes, and value hypotheses.
Flow problems Problem measures, causal hypotheses, intended leverage, and unresolved blockers.
Shared foundations Architecture, platform, DevOps, cyber, compliance, data, quality, and change roadmaps.
Capacity Committed work, KTLO, maintenance, compliance, learning, buffer, flex, and displacement.
External reality Supplier, contract, legal, procurement, operations, release, evidence, and lead-time constraints.
Risk and decisions Choices made, options open, confidence, conflicts, owners, escalation, and next sync.
Draft Overlay Review Roadmap element Day 1 change Conflict / contradiction Affected decision Authority needed Route Compliance milestone sequence B proposed supplier slot fixed scope or fund capacity Business Owner leadership window Platform rollout phase 1 expanded ART flex overstated reduce or enable LPM + ART leads overnight evidence Review discipline: Inspect change and collision—not every unchanged roadmap item.
Speaker Notes
Facilitator intentIntegrate Day 1 outputs into one shared view and inspect only meaningful deltas, collisions, confidence changes, and open decisions across the roadmap layers.
How to facilitate
- Overlay Day 1 outputs across objectives, Flow problems, shared foundations, capacity, external reality, risk, and decisions.
- Use the Draft Overlay Review to capture change, conflict, affected decision, authority needed, and route.
- Focus on changes and collisions, not every unchanged roadmap item. The goal is new truth for Day 2.
Listen and watch for
- Report-outs that summarize activity rather than identifying changed roadmap assumptions.
- Conflicts between layers: objective ambition versus capacity, foundation roadmap versus supplier lead time, or risk appetite versus evidence reality.
- Decisions made in one breakout that silently invalidate another breakout's assumptions.
Avoid
- Reviewing the whole draft line by line. That burns energy and hides the important deltas.
- Letting each breakout defend its local output instead of integrating it into the whole system.
- Postponing contradictions because they feel uncomfortable. The Alignment Block exists to expose them.
-
3
Approximately 5–10 minutes
Open a Leadership Decision Window, Not a Management Readout
Sequence only the conflicts that genuinely need leadership authority. Give each one a concise decision packet and a fixed outcome path: decide, bound, delegate, request focused evidence, or explicitly defer.
Question One choice with decision deadline and consequence of no decision.
Why now Objective, Flow impact, urgency, and downstream work waiting.
Trade-space Hard constraints, guardrails, commitments, assumptions, and reversibility.
Options Credible alternatives, recommendation, cost, capacity, risk, and consequence.
Voices Driver, decider, required agreement, contributors, dissent, and affected performers.
Closure Decision record, artifact updates, owner, communication, and review trigger.
Leadership Decision Window Window Decision question Driver Decider Options ready Artifact Outcome / fallback 18:00–18:20 Fund test capacity or reduce scope? V&V lead Portfolio sponsor 3 investment + roadmap decide / scope cap 18:20–18:35 Accept supplier risk? Supplier PM Business Owner 2 risk + milestone accept / evidence by 08:00 Speaker Notes
Facilitator intentUse the leadership decision window to close only the choices that breakouts could not decide and that materially change Day 2 guardrails.
How to facilitate
- Prepare a short leadership queue: decision question, options, evidence, consequence, required artifact update, and time boundary.
- Keep leadership focused on choices that change guardrails, capacity, priority, risk acceptance, supplier route, or agenda focus.
- Document each answer as accept, adjust, defer with owner, escalate, or return to breakout with a clearer boundary.
Listen and watch for
- Leaders reviewing every breakout output instead of deciding the conflicts that require leadership authority.
- Decisions given verbally without updating roadmap, risk log, guardrail, or Day 2 focus backlog.
- A desire to avoid hard trade-offs by asking for more analysis that cannot arrive before Day 2.
Avoid
- Turning the window into a steering committee status review.
- Letting leaders solve details that belong to the affected people in Day 2 breakouts.
- Closing the window without telling the facilitation team exactly what changes tomorrow morning.
-
4
Approximately 5–8 minutes
Build a Small Overnight Decision Queue
Overnight work is a constrained queue, not a second hidden conference. Pull only gaps that can realistically close before Day 2 and whose closure changes the agenda or roadmap.
Overnight Decision Queue Open decision Smallest missing input Owner Due Reviewer / decider Artifact Agenda effect Fallback Supplier sequence confirm certification slot Supplier PM 07:30 BO milestone view Day 2 theme A/B assume late slot Platform capacity validate 2 specialist weeks Platform lead 08:00 LPM capacity view fund / reduce cap phase 1 Limit WIPPull only agenda-changing work A long queue hides the few items that truly need morning closure.
Define doneSpecify the minimum usable evidence “Analyze further” is not a deliverable; name the fact, option, validation, or decision needed.
Protect peopleDo not normalize heroic overwork Use available owners, time zones, prepared data, and explicit deferral when the window is unrealistic.
Set fallbackDay 2 must still start Predefine the safe assumption, scope cap, reversible option, escalation, or deferred theme.
Overnight queue policy If an item cannot be completed, reviewed, recorded, and communicated before Day 2, route it to refinement instead of pretending the night will solve it.Speaker Notes
Facilitator intentBuild the overnight queue for evidence, decisions, and artifact updates that must be ready before Day 2 starts with a changed basis.
How to facilitate
- Convert unresolved Day 1 items into overnight work only when the answer can realistically change Day 2.
- Assign owner, source, minimum quality, deadline, fallback, and artifact update for every queue item.
- Keep the queue small. It should protect Day 2, not become a hidden second conference.
Listen and watch for
- Overnight tasks that require unavailable people or data; they will produce false confidence in the morning.
- Important decisions assigned to 'leadership' or 'the team' rather than a named owner.
- Evidence gathered but not translated into updated guardrail, roadmap item, risk, or focus topic.
Avoid
- Letting participants believe everything will be solved overnight. Only route what can be finished or narrowed.
- Adding work that is merely interesting. The queue serves Day 2 readiness.
- Failing to define fallback if the overnight answer does not arrive.
-
5
Approximately 4–7 minutes
Reset Day 2 with a Planning Adjustment
Prepare a concise morning delta that participants can inspect. Update the artifacts first, then explain the changes, invite only necessary clarification, and show exactly how the Day 2 agenda has changed.
What changed?Decision and evidence delta New choices, facts, constraints, risks, confidence, and invalidated assumptions.
What is now true?Current guardrails What is fixed, negotiable, unresolved, deferred, and safe to assume for today’s work.
What changed in the draft?Artifact delta Roadmap, capacity, risk, decision log, ownership, or operating-model updates.
What changes in the agenda?Day 2 focus Rooms, questions, people, decision windows, timeboxes, outputs, and fallbacks.
What still needs challenge?Visible uncertainty Dissent, low confidence, open evidence, assumptions, and validation owners.
Morning reset sentence Since yesterday, [decision or evidence] changed [guardrail or assumption], so [artifact] now shows [delta], and Day 2 will focus on [work] with [people and authority].Alignment Block release rule READYmaterial conflicts are decided or routed, overnight work is bounded, shared artifacts reflect the change, and Day 2 starts from explicit current truth
NOT READYthe block is a report-out, leadership receives unframed problems, or morning participants must infer what changed
Speaker Notes
Facilitator intentReset Day 2 with the new truth from Alignment and Planning Adjustment: changed guardrails, revised focus topics, open decisions, risks, and updated artifacts.
How to facilitate
- Open Day 2 with a concise Planning Adjustment: what changed, what is now true, what remains open, and what Day 2 must solve.
- Update room assignments, timeboxes, participants, and contracts when the Day 1 evidence changes the plan.
- Make confidence visible: which assumptions improved, which got weaker, and which need validation by affected people.
Listen and watch for
- Day 2 starting with the original agenda despite Day 1 contradictions.
- People missing from Day 2 rooms because the new guardrail changed who is affected.
- Participants confused about whether yesterday's draft, overnight update, or current board is the source of truth.
Avoid
- Using the morning reset as a long recap. It should change work, not narrate work.
- Hiding unresolved decisions to preserve energy. Open items need owners and routes.
- Moving to Day 2 breakouts before the updated basis is accepted by the room.
Facilitation
Make authority visible without turning leadership into the integration team
Ask only for decisions, deltas, conflicts, risk, and help needed. Let participants inspect the shared artifacts asynchronously.
Return them to strategic or global choices, guardrails, resources, and escalation. Preserve local authority.
Name the incompatible assumptions, options, consequences, authority, and deadline explicitly.
Limit work in progress. Pull only items that can close and materially change Day 2.
Pause closure until the decision record and affected roadmap, risk, capacity, or guardrail artifact have owners.
Show the artifact delta first, then the decision and consequence. Update the agenda in front of the room.
Ready to Move On?
Alignment is ready when Day 2 can work from a shared current truth
- Day 1 deltas are integrated into one shared draft rather than separate reports.
- The review inspects changed roadmap layers and collisions, not unchanged detail.
- Conflicts are routed by decision authority, evidence, urgency, and reversibility.
- Leadership receives bounded decision packets instead of open-ended problems.
- Locally owned decisions remain decentralized.
- Every leadership outcome updates a decision record and affected source of truth.
- The overnight queue contains only realistic, agenda-changing work.
- Every overnight item has minimum evidence, owner, deadline, reviewer, artifact, and fallback.
- Decisions, guardrails, invalid assumptions, risks, and confidence changes are explicit.
- The Planning Adjustment shows both artifact and agenda deltas.
- Day 2 rooms, questions, participants, outputs, and decision windows reflect the new truth.
Source Foundation
This page distills slides 55–56 of 05 Value_Stream_Conference.pptx. Conflict routing, bounded leadership decision packets, the Overnight Decision Queue, explicit fallbacks, and artifact-first Planning Adjustments are facilitator extensions that keep the convergence phase decision-capable.