Keep Execution Adaptive Without Turning the Organization into a Meeting Machine
Design the sync system that keeps portfolio, value-stream, solution-train, ART, Solution Area, and team execution aligned during the PI—while keeping refinement for the next PI visible and avoiding duplicate cadences.
- Source
- Slides 86–106
- Fast path
- 5 × 5 minutes
- Input
- Refinement cadence hypothesis + PI commitments
- Output
- Execution sync cadence hypothesis
- Core test
- Fast realignment with minimum overhead
Understanding Execution Cadence
Refinement and execution run in the same PI
The deck uses a two-PI view as a thinking aid: first design the path into PI Planning, then design the sync system for execution. In reality, both logics run in every PI. Current execution produces signals, blockers, risks, demos, customer feedback, and capacity drift while the next PI is already being refined.
Use the two-PI view to separate the questions, then merge the cadences where purpose, participants, and artifacts can safely share one sync.
Every sync needs a reason: realignment, escalation, risk treatment, artifact update, or feedback into refinement.
Planning boards, roadmaps, risk logs, decision logs, dependency views, and objective deltas must change when execution reality changes.
Cadence follows volatility: event-triggered, daily, weekly, once per iteration, mid-PI, or IP review.
More syncs are not the goal. Faster realignment with minimum overhead is the goal.
Running the Exercise
Seven moves from execution signals to an integrated cadence map
Use the deck’s snippet cards as options. Keep only the syncs that can update a decision, artifact, or realignment path.
-
1
Setup · Two-PI View
Separate the Two Logics Before You Merge Them
Place the current PI execution syncs and the next-PI refinement syncs on the same timeline. Mark which syncs respond to execution signals, which harden next-PI inputs, and which can serve both purposes without losing focus.
Current PI execution Realign fast
React to blockers, risks, dependency shifts, customer signals, capacity drift, and objective changes.
Output: updated boards, owners, decisions, and escalationsNext PI refinement Harden future inputs
Refine roadmaps, objectives, dependencies, guardrails, contribution forecasts, and readiness assumptions.
Output: plan-ready inputs for PI PlanningIntegrated cadence Merge where useful
Use one sync only when purpose, participants, artifact owner, and decision rhythm genuinely overlap.
Output: fewer but stronger decision eventsExecution Signals Refinement Inputs One Coherent Cadence -
2
Exercise 5A · Portfolio Level
Design Portfolio Execution Syncs
Use portfolio execution syncs only when execution signals require portfolio-level priority, funding, guardrail, risk, supplier, or cross-value-stream realignment during the PI.
No Portfolio Execution Sync Use when surprises can be handled by Value Streams, Solution Trains, or ARTs.
Merge with Refinement Sync Use one event if future roadmap updates and rare execution escalations need the same people.
Strategic Surprise Market, regulation, or executive priority changes during the PI.
Investment Guardrail Change Budget, staffing, supplier cost, or funding assumptions change materially.
Cross-Value-Stream Trade-off A disruption requires priority or capacity movement across Value Streams.
Executive Decision Window A decision cannot wait for the next refinement or steering rhythm.
Major Risk Escalation Safety, legal, cyber, audit, or reputation risk needs portfolio authority.
Stop / Continue Decision Pause, defer, accelerate, or re-scope a portfolio-level initiative during the PI.
Portfolio Execution Sync Options Option Cadence Purpose Participants Artifact No sync — stable portfolio frame — no update Portfolio Sync once per sprint priority / funding deltas LPM + Business Owners portfolio board Mid-PI Review Sprint 3 / 4 strategic course correction exec + value-stream leads guardrails Initiative Sync weekly if critical critical epic / initiative epic owner + SMEs initiative roadmap Risk / Compliance Sync triggered regulatory or risk event risk + legal + BO risk log Portfolio guardrail: portfolio execution syncs are rare by design. Use them only when fast portfolio-level decisions can change execution.
-
3
Exercise 5B · Value Stream Level
Design Value Stream Execution Syncs
Use value-stream syncs for end-to-end flow problems that cannot be solved by one ART or Solution Train alone: cross-train blockers, capacity drift, shared platforms, supplier disruptions, customer or regulatory escalations, and roadmap deltas.
Value Flow InterruptionSeveral trains are blocked End-to-end Flow is interrupted across domains, suppliers, or Solution Trains.
Capacity RebalancingFixed demand changes Unplanned KTLO, incidents, compliance, or support load shifts capacity across trains.
Cross-Initiative Trade-offShared capacity conflicts Experts, environments, platforms, or integration windows become bottlenecks.
Customer / Regulatory EscalationExternal reality changes A launch, audit, customer, or regulation event needs stream-level action.
Decision Backlog TriageExecution signal becomes choice Turn new signals into decisions, owners, roadmap updates, and sync routes.
Design question Which end-to-end value-flow problems cannot be solved by one Solution Train or ART alone and therefore need a Value Stream-level sync? -
4
Exercise 5C · Solution Train Level
Design Solution Train Execution Syncs
Decide when multiple ARTs need fast cross-ART realignment during execution and whether one combined Solution Train Sync or focused role/topic syncs provide the lowest useful overhead.
Combined ST SyncCross-ART decisions Use when ART leads need one shared decision event and one solution roadmap update.
RTE / STE SyncFlow and impediments Coordinate ART impediments, dependencies, blockers, and escalation needs.
PM / PO SyncScope and objective trade-offs Adjust feature scope, objectives, options, and impact on ART boards.
Architect SyncTechnical direction Manage interfaces, architectural runway, system design, and implementation trade-offs.
Problem-Space SyncUrgent issue solving Bring only affected people when a cross-ART decision cannot wait.
Commitment reminder Solution Train syncs realign execution and update inputs; they do not replace ART-level accountability for committed PI objectives. -
5
Exercise 5D · ART / Solution Area Level
Design ART and Solution Area Execution Syncs
Design lower-level syncs that feed real execution signals upward and receive decisions back down. Keep, merge, split, or add syncs based on response time, people, artifact, and decision type.
ART Execution SyncUpdate the ART board Use to react during PI execution and change owners, risks, dependencies, or plan board entries.
Merge Refinement + ExecutionOne sync can work Use when future work and current issues can be handled by the same people and artifact owner.
Separate Execution SyncFast current-PI realignment Use when current commitments need urgent decisions and different participants.
Solution Area SyncClose to the work Affected teams inspect the problem and validate options before escalation.
Closed-Loop SyncPre-event, focused breakout, post-event Keep going until the decision is usable and the artifact is updated.
Change-Rate TriggerCadence follows volatility Daily, weekly, per sprint, or on demand depending on how fast conditions change.
ART-level rule: split execution and refinement syncs only when refinement needs different depth, people, or cadence.
-
6
Exercise 5E · Merge Logic
Merge What Can Share the Same People, Artifact, and Decision Rhythm
Take the Exercise 4 refinement syncs and Exercise 5 execution syncs. Mark every sync as refinement-only, execution-only, or both. Merge only when focus and response time do not suffer.
Merge Decision Canvas Sync R E BOTH Merge / separate because Artifact owner Portfolio Sync □ □ □ strategy vs execution signal? Value Stream Sync □ □ □ roadmap refinement + flow? Solution Train Sync □ □ □ cross-ART roadmap + blockers? ART Sync □ □ □ current PI execution + next PI input? Architecture Sync □ □ □ runway refinement + incident response? Community Sync □ □ □ shared capability + delivery evidence? R · next-PI refinement E · current PI execution BOTH · dual-purpose sync ? · test before merging -
7
Execution + Refinement Cadence Canvas
Publish the Integrated Cadence Map
Place execution syncs in the current PI and overlay refinement syncs for the next PI. Draw arrows where a decision or artifact update must travel.
Portfolio · Syncs R/E/BOTHValue Stream · Flow + roadmapSolution Train · cross-ART decisionsART · execution + next PI inputsSolution Area / Team · validation close to workArtifacts · boards + roadmaps + logsART Board Current PI execution changes, owners, risks, and dependencies.
Value Stream Roadmap Stream-level roadmap deltas, shared initiatives, guardrails, and confidence.
Decision Log What changed, who decided, and which artifact was updated.
Next PI Inputs Refinement signals that must be considered before the next PI Planning.
Aha question: which syncs are accidentally duplicated because refinement and execution were designed separately?
Roadmap View
Prepared artifacts and execution signals become layers in the shared roadmap
The roadmap is not a management wishlist. It is the living refinement artifact that execution syncs keep honest.
Portfolio intent, outcomes, milestones, strategic choices, and benefit hypotheses.
Architecture, DevOps, cyber, compliance, platform, AI/data, and transformation.
Capacity, KTLO, constraints, local commitments, and dependency signals.
Blockers, risks, demos, customer feedback, quality signals, and capacity drift.
Flow problems, trade-offs, risks, and decision needs.
What changed, who decided, and which artifact was updated.
Operating Rhythm
The full loop: conference, refinement, planning, execution, learning
Debrief 5A–5E
Does the execution cadence create fast realignment?
The cadence is useful only if it lets the right people make the right decisions while keeping artifacts trustworthy.
- Response time is clear: which changes need a day, week, sprint, or PI response?
- Decision power is explicit: who attends, who is on standby, and who can decide?
- Artifact truth is maintained: each sync changes a board, roadmap, risk log, or decision log.
- Merge quality is tested: combined syncs do not lose focus or speed.
- Meeting load is visible and avoidable overhead is removed.
- The cadence has an inspect-and-adapt moment after the first try.
This is not our meeting calendar forever. It is a realignment hypothesis that we test against change rate, decision speed, meeting load, and roadmap reliability.
Facilitation
Keep syncs as decision events, not status theatre with better catering
Ask what can change in the board, roadmap, risk log, decision log, or escalation path. If nothing can change, remove or merge it.
Check whether decision rights can move closer to the work or whether a standby path is enough.
Reduce meeting load by merging compatible rhythms and using topic-specific windows only when needed.
Separate the purpose first. Then decide whether the same people and artifacts can support both.
Shorten the response loop or define a trigger. Cadence should reflect the change rate of the work system.
Require an artifact update before closing the sync. Spoken alignment without an updated source of truth decays fast.
Source Foundation
This page distills slides 86–106 of 05 Value_Stream_Conference.pptx. Supporting public references are used only to strengthen the sync discipline around ART events, portfolio decision cadence, and Kanban flow metrics.