Close with a Credible Draft and a Go-Refine Path
Review one shared Value Stream Roadmap, let Business Owners accept or challenge the strategic and technical guardrails, inspect confidence at the scopes where refinement will happen, own risks and open decisions, and finish with an explicit handoff—not the fiction that two conference days produced a finished execution plan.
- Fast exercise
- 5 minutes
- Full exercise
- 25–45 minutes
- Input
- Integrated draft + hypotheses
- Output
- Owned go-refine package
- Deck basis
- Slides 59–60
Understanding Final Alignment
Closure should increase credibility, not certainty theatre
The final block makes the state of the draft explicit. It separates directional acceptance from feasibility refinement, visible risk from hidden hope, and a shared starting point from a commitment that only downstream planning can responsibly create.
Credible Draft, Not False Certainty
Label what the conference actually achieved
Strategic intent and major guardrails hold; the roadmap can enter structured refinement.
Specific capacity, dependency, architecture, supplier, evidence, or organization questions need validation.
A material decision, authority, evidence gap, or unresolved conflict prevents responsible progression.
Objectives, milestones, shared foundations, capacity envelope, dependencies, risks, and decisions.
What is believed, at which scope, against which question, and why.
Unknowns, options, validation, risk treatment, organization hypotheses, and decisions.
Owners, artifacts, minimum evidence, due dates, next syncs, review criteria, and planning destinations.
Confidence Needs Scope
Ask a question that the voters can legitimately answer
A single all-room vote can hide local feasibility concerns or invite people to judge work they do not understand. Choose the confidence scope from the decision and refinement ownership, then record what low confidence means and how it changes the plan.
Use when local skills, workload, interfaces, or delivery feasibility remain decisive.
Use when several teams share a problem space, dependency, or validation path.
Use when capacity, sequence, integration, risk, or train-specific dependencies matter.
Use for end-to-end alignment, cross-train trade-offs, shared foundations, and major risks.
Use for direction, funding guardrails, global constraints, and major strategic exposure.
What exactly are people expressing confidence in?
Who has enough knowledge, accountability, or performance responsibility to answer?
What do scores mean, and what threshold triggers discussion or rework?
How will low confidence, dissent, uncertainty, and minority views be captured safely?
Which adjustment, owner, risk, validation, or decision follows the result?
Running the Exercise
Five moves from integrated draft to owned refinement
-
2
Approximately 5–8 minutes
Let Business Owners Accept or Challenge the Direction
Business Owners do not approve every task. They inspect whether the draft is directionally useful, consistent with business and technical accountability, and safe to refine under the current strategic, investment, governance, and compliance guardrails.
Strategic fitDoes the draft advance the intended outcomes? Challenge local optimization, missing customer value, and work that no longer supports strategic intent.
Investment logicAre the major trade-offs directionally responsible? Inspect capacity, enabling investment, scope displacement, timing, opportunity cost, and risk exposure.
Governance and complianceCan the path meet its obligations? Check evidence, safety, audit, quality, contract, legal, operational, and policy consequences.
Decision boundariesWhat remains fixed, delegated, or open? Clarify guardrails without pulling legitimate local decisions upward.
Risk appetiteWhich exposure can be accepted? Name the accountable owner, consequence, trigger, monitoring, and escalation.
Refinement mandateWhat must be proven before commitment? Define the questions, people, evidence, artifacts, deadlines, and next decision windows.
Business Owner Acceptance and Challenge Log Roadmap element Accept / adjust / challenge Reason / guardrail Decision owner Artifact update Refinement required Next decision Compliance sequence accept direction date fixed; scope flexible BO roadmap guardrail team feasibility Final VS Sync Platform expansion adjust investment cap LPM capacity + roadmap adoption slices Portfolio Sync Speaker Notes
Facilitator intentAsk Business Owners and relevant decision authorities to accept, challenge, or route the guardrails that shape the draft roadmap.
How to facilitate
- Use acceptance as a directional signal: do guardrails, objective priorities, investment boundaries, and non-negotiables still support the draft?
- Separate accept, challenge, adjust, defer, and escalate. Each response should update the roadmap, guardrail, risk, or decision backlog.
- Name who owns any challenged guardrail and by when it must be resolved for refinement.
Listen and watch for
- Business Owner acceptance interpreted as ART commitment. Those are different anchors.
- Guardrails accepted because leaders are tired, while capacity or evidence contradictions remain visible.
- Challenges voiced without owner, consequence, or route.
Avoid
- Forcing consensus on unresolved strategic constraints.
- Treating acceptance as ceremonial approval. It must change or confirm the refinement path.
- Letting challenged guardrails remain as vague concerns after the conference.
-
3
Approximately 4–8 minutes
Choose Confidence Scopes and Response Rules
Select only the votes or confidence pulses that can reveal useful information. Define the question, population, scale, privacy or psychological-safety needs, threshold, and response before asking people to vote.
Confidence Design Canvas Scope Question Who answers Method Low-confidence threshold Response Artifact Value Stream coherent enough to refine? all participants 1–5 + reason ≤2 or strong dissent name conflict + owner refinement backlog ART A capacity hypothesis plausible? ART representatives fist of five ≤2 targeted feasibility work ART roadmap Portfolio strategic guardrails hold? Business Owners / LPM accept / adjust / challenge challenge decision window guardrail log High confidenceProceed to refinement Preserve assumptions and review triggers; confidence is not immunity from learning.
Mixed confidenceExpose the boundary Segment by scope, ask for reasons, and identify where evidence or feasibility differs.
Low confidenceCreate owned work Adjust the draft, reduce scope, add validation, route a decision, or mark the element blocked.
DissentKeep consequential minority views visible Record the concern, evidence, owner, review trigger, and condition that would prove it material.
Confidence rule Never ask for confidence unless you are prepared to change the roadmap, refinement work, or decision path in response.Speaker Notes
Facilitator intentChoose confidence scopes that reveal where the draft is strong or weak: whole room, portfolio, value stream, train, Solution Area, team, or topic-specific confidence.
How to facilitate
- Pick confidence votes based on what the draft needs to learn: capacity, dependencies, architecture, compliance, supplier, Solution Area, ART, or portfolio guardrails.
- Ask participants to anchor their confidence in evidence and specific concerns, not mood.
- Record confidence deltas as refinement backlog items, decision items, or risk owners.
Listen and watch for
- One global confidence vote hiding a weak area that will later derail planning.
- Many votes producing theater without different action paths.
- Low confidence without a named reason, owner, and refinement route.
Avoid
- Using confidence votes to pressure agreement. They are diagnostic signals.
- Ignoring who is qualified to express confidence on a topic. Some votes should be scoped.
- Ending the vote with a number only. The why and next action matter more.
-
4
Approximately 5–10 minutes
ROAM Material Risks and Owner Every Open Decision
Use the final block to confirm risk treatment and decision ownership already developed throughout the event. Do not leave risk and open choices as an exhausted end-of-day batch.
ResolvedNo longer threatens the draft Record the resolution and update the affected artifact.
OwnedA named person actively manages it Define treatment, trigger, due date, monitoring, and escalation.
AcceptedAccountable authority accepts the exposure Record consequence, appetite, monitoring, and revisit condition.
MitigatedAction reduces probability or impact Name the action, owner, evidence, residual risk, and completion point.
Risk and Open Decision Closure Board Risk / decision State Owner / decider Next action or treatment Due Artifact Next sync / trigger Supplier slot risk Owned Supplier PM reserve alternate lab T+5 days risk + roadmap Supplier Sync Enablement funding Open decision LPM compare two adoption slices Final VS Sync decision backlog Portfolio Sync Question One bounded choice and consequence of no decision.
Authority Driver, decider, agreement, delegate, and escalation.
Missing work Evidence, option, validation, negotiation, or refinement required.
Flow commitment Owner, due date, artifact, status, next sync, and fallback.
Speaker Notes
Facilitator intentROAM risks and own open decisions so the draft leaves the room with clear responsibility, routing, and next synchronization points.
How to facilitate
- For each major risk, decide whether it is Resolved, Owned, Accepted, or Mitigated, with a real owner and review trigger.
- Build the Decision / Owner Backlog for unresolved choices: question, owner, due date, artifact, next sync, and escalation path.
- Separate risks from open decisions. Risks can be accepted or mitigated; decisions need closure or routing.
Listen and watch for
- ROAM used as a labeling exercise with no owner or follow-up.
- Accepted risks that no Business Owner or authority has actually accepted.
- Open decisions hidden inside action items, making them look smaller than they are.
Avoid
- Trying to resolve every risk in the final block. Some need refinement or higher authority.
- Assigning risk ownership to groups. Name the person or explicit role.
- Leaving the next sync undefined. An owned item without a review point often disappears.
-
5
Approximately 5–10 minutes
Close with Retrospective and a Go-Refine Contract
Separate improvement of the conference system from refinement of its outputs. Use a short retrospective to create one or two owned improvements, then publish the roadmap, decision, risk, hypothesis, and refinement package with explicit next syncs.
Draft state Directionally accepted, targeted refinement needed, blocked, contested, or superseded.
Refinement question What must be learned, tested, decided, sliced, sequenced, or made feasible?
Owner Who drives the work and who has authority to close or escalate it?
Minimum evidence What is enough to support the next decision without over-preparing?
Artifact Which roadmap, backlog, decision, risk, capacity, interface, or operating-model source changes?
Due / trigger Date, milestone, decision age, risk threshold, supplier event, or readiness state.
Next sync Final Value Stream Sync, Portfolio Sync, Solution Train Sync, PI Planning, community, or another forum.
Exit criterion What makes the item refined enough to decide, plan, implement, experiment, or remove?
Go-Refine Handoff Board Roadmap item / decision State Refinement work Owner Evidence / exit Due Next sync Artifact Compliance path accepted direction team feasibility + test slots V&V lead ART forecasts validated T+10 Final VS Sync VS + ART roadmaps Integration Solution Area hypothesis affected-person design + trial STE one-PI test contract T+15 ST Sync operating model KeepWhat accelerated useful decisions? Preserve the preparation, participation, interaction, artifact, or facilitation pattern.
ChangeWhere did decision Flow stall? Inspect missing authority, evidence, unclear outputs, room collisions, tooling, or delayed updates.
TryWhat is the smallest improvement experiment? Name one owner, next conference, observable signal, and review point.
Closing sentence We did not finish the plan. We created a shared starting point for refinement—with owners, evidence, artifacts, and next decisions.Final Alignment release rule READYthe draft state is honest, confidence produced responses, risks and decisions are owned, and every refinement item has an artifact and next sync
NOT READYacceptance is vague, dissent is hidden, open decisions lack owners, or the roadmap leaves the room without a maintenance path
Speaker Notes
Facilitator intentClose with a clear go-refine handoff: draft roadmap, owners, risks, open decisions, artifact update responsibilities, and path to the next refinement and sync cadence.
How to facilitate
- Use the closing sentence from the deck: we did not finish the plan; we created a shared starting point for refinement.
- Publish the handoff package: draft roadmap, decision log, risk log, refinement backlog, owner map, next syncs, and artifact owners.
- Name the immediate next events: refinement sessions, Final Sync, Solution Train or ART handoffs, and who updates what before then.
Listen and watch for
- Participants leaving with different expectations about whether the roadmap is committed, draft, or aspirational.
- Follow-up work assigned but not connected to a cadence or artifact update.
- Retrospective comments treated as logistics only, missing improvements to the conference decision system.
Avoid
- Overclaiming certainty to end on a high note. Credibility comes from clarity about what is still open.
- Sending only a slide deck afterward. The working artifacts and decision records matter more.
- Closing without telling downstream ARTs, Solution Trains, and shared foundation owners what to refine next.
Facilitation
Close the conference without erasing uncertainty
Walk the shared artifact and stop only for deltas, conflicts, decisions, confidence, risk, or missing ownership.
Return to outcome, investment, governance, compliance, major risk, and strategic guardrails. Preserve downstream planning authority.
Split the question by knowledge and responsibility: team, Solution Area, train, Value Stream, or portfolio.
Collect reasons before identities where needed, invite minority evidence, and demonstrate that low confidence changes work rather than punishes people.
Confirm and summarize treatment continuously; use the closing only for material unresolved risk and ownership checks.
Name question, owner, evidence, artifact, due or trigger, next sync, and exit criterion before closure.
Ready to Move On?
Final Alignment is complete when the draft can enter a real refinement system
- The room reviews one integrated, editable Value Stream Roadmap.
- The walkthrough follows value and time rather than departmental reports.
- Directionally accepted, refinement-needed, blocked, and contested states are explicit.
- Business Owners accept or challenge strategic, investment, governance, compliance, and major technical guardrails.
- Local and downstream planning authority remains intact.
- Every confidence check has a clear question, legitimate population, scale, threshold, and response.
- Low confidence and consequential dissent create adjustments, validation, risk, or owned decisions.
- Material risks are Resolved, Owned, Accepted, or Mitigated with real accountability.
- Every open decision has a driver or owner, decider, due date, artifact, next sync, and fallback.
- Organization hypotheses have affected-person validation and review paths.
- The retrospective produces one or two owned improvements to the conference system.
- The Go-Refine handoff names work, evidence, owners, artifacts, triggers, next syncs, and exit criteria.
Source Foundation
This page distills slides 59–60 of 05 Value_Stream_Conference.pptx. Explicit outcome states, scoped Confidence Contracts, dissent handling, continuous risk treatment, and the Go-Refine Contract are facilitator extensions that make the closing credible and operational.