Deck purpose: Introduce the Decision Latency frameworks and facilitate the capstone War Room simulation. All three program metrics are assessed in this session. Participants need all M01–M07 content completed before attending. Allow 120 minutes minimum: the War Room simulation alone requires 45 minutes plus debrief.
Opening (Slides 1–4)
01Title
M08: Decision Latency: Breaking Deadlocks Without Breaking Trust
Capstone module title and framing
Core question: "Can you break a deadlock without breaking trust?"
Session structure preview: frameworks (45 min) → War Room simulation (45 min) → metric assessment and debrief (30 min)
02Capstone Framing
This Is the Assessment
All three program metrics are measured today: simultaneously, in the War Room simulation
Discovery Audit: Surface 3+ unstated constraints from the Meridian scenario
Jargon-Free Test: Brief the CFO character on the architectural decision in ≤5 acronyms
Consensus Score: All War Room participants rate "feeling heard" at 4/5 or higher
Program completion requires all three at "Ready," not sequentially, but in one integrated scenario
Three metric cards in a row: each with metric name, pass threshold, and "how it is assessed in today's session." Gold border on all three: Capstone integration.
03Problem
Decision Latency: The Silent Project Killer
Decision latency: the time between when a decision is needed and when it is made
The most common cause of project delays, but almost never listed as the root cause in post-mortems
The delay is attributed to subsequent work: "integration took longer," "testing found issues," "the team was under-resourced"
The real root cause: an architectural decision was deferred, and every downstream task was blocked waiting for it
Timeline diagram showing a deferred decision at week 3 and the cascading delay it creates across 6 downstream workstreams: each stream blocked until the decision is made at week 11.
04Scenario
The Meridian Financial Group Scenario
$8B regional bank, 14-month planning stall, 3 open architectural decisions
Cost of latency: $180,000/week in delayed time-to-market
Four stakeholder types: CTO (skeptical, values stability), VP Engineering (wants velocity), CFO (wants predictability), Compliance Lead (shadow stakeholder, informal veto)
Project sponsor (CDO) believes architecture is ready, but cannot make the decision alone
Today's War Room: produce a documented decision on at least one of the three open decisions within 45 minutes
Frameworks (Slides 5–8)
05Framework
Framework 1: Architecture Decision Record (ADR)
Captures: what was decided, why, what alternatives were considered, what constraints ruled them out, what the compliance path is
An ADR built on unverified assumptions is not an ADR. It is a hope document
The compliance path (what signal would indicate the decision should be revisited) is the section most architects skip
A well-written ADR prevents "who decided that?" from becoming an architectural veto two years later
ADR section map: 8 sections labeled (Status, Context, Decision, Alternatives, Drivers, Consequences, Compliance Path, Sign-Off). Highlight "Compliance Path" as the critical section most often missing.
06Framework
Framework 2: One-Way Door vs. Two-Way Door
One-Way Door: Effectively irreversible within the project lifetime: vendor lock-in, data residency, security architecture foundations, primary cloud commitment. Deserves full ADR rigor and broad stakeholder consultation
Two-Way Door: Reversible at reasonable cost: naming conventions, toolchain choices, internal API versioning. Should move fast, with minimal ceremony
Applying One-Way Door rigor to Two-Way Door decisions is the most common cause of decision latency in high-functioning teams
The architect's job: classify first, then allocate effort proportionally
07Framework
Framework 3: Decision Latency Measurement
For each open decision: name the decision, the owner, the blocker, and the cost of deferring 1 week
The cost of latency calculation: downstream team size × average cost/day × number of blocked days
Making latency visible in financial terms creates urgency without creating pressure. It is not the architect's judgment that the decision is needed; it is the math
The decision inventory is presented at the start of the War Room: the cost of latency is the opening number
08Framework
Framework 4: The War Room
Time-boxed facilitated session to produce a documented decision within a defined window
The facilitator's role: ensure the decision happens, not advocate for a position. Own the process, not the outcome.
A documented bad decision is better than no decision because a documented bad decision can be revised with an ADR amendment
5-phase War Room arc with time allocations: Constraints (10 min) → Options (10 min) → Criteria (10 min) → Vote (5 min) → Document (10 min). Total: 45 min.
War Room Simulation (Slides 9–11)
09Simulation Setup
War Room Roles: Meridian Financial Group
Facilitator (Architect): Own the process; no position on outcome; hard stop at 45 minutes; ADR completed in the room
CTO: Values stability; has seen two migrations fail; will not approve without a compliance path and exit criteria
VP Engineering: Values velocity; tired of waiting; will support any credible option that lets the team start
CFO: Values predictability; needs a 3-year TCO with break-even date; does not trust estimates
Compliance Lead: Shadow stakeholder; informal veto power; will block at go-live if not included now
Brief each participant on their role privately before the simulation begins. Each character has a red line (something they will not accept) and a potential champion condition (what would make them support the decision). See M08_War_Room_Facilitation_Guide.pdf.
10Simulation
Run the War Room: 45 Minutes
Decision to reach: classify Decision 1 (Cloud-Native Rebuild vs. Lift-and-Shift) and produce a completed ADR
Facilitator sets the opening: "We are leaving this room with a documented decision. The cost of another week of latency is $180,000."
Hard stop at 45 minutes: no extensions. If no consensus, document the impasse and the reasons in the ADR.
After the War Room: all participants complete the Consensus Score anonymously before debriefing
11Debrief
Capstone Debrief: All Three Metrics
Discovery Audit: How many unstated constraints were surfaced during the War Room? Were they in the scenario brief?
Jargon-Free Test: How many acronyms did the facilitator use when briefing the CFO character? Was it ≤5?
Consensus Score: What was the average? Which question scored lowest? What would the facilitator do differently?
Program completion determination: all three at "Ready"? If not: what needs more practice before reassessment?
Close (Slide 12)
12Close
What Comes After Program Completion
Apply the War Room framework to the next real deadlocked decision on a current engagement: within 60 days
Use the ADR template for every One-Way Door decision going forward, not just the ones that feel important
Run a Decision Inventory for your highest-stakes current engagement: how many open decisions? At what weekly cost?
Teach the Elevator Vision to your next account sponsor: the measure of mastery is whether they can repeat it