Decision Paths

Make Decision Rights Visible Before Work Escalates

Decision Playback — full-sequence snapshots on a timeline, with Expected vs Actual overlay to spot skipped gates and unclear authority.

01Who raised

Product opened SSO GA date as a Launch decision after enterprise pipeline pressure.

02Who advised

Engineering flagged Weeks 4–8 load; Security requested threat model before any GA commit.

03Final authority

Expected: Product + Security co-own. Actual: Sales date stood without Security gate.

04Teams informed

Legal and Customer Success learned the date from Slack — not from the decision log.

05Work impact

Engineering reordered sprint mid-cycle; Customer Success still has no migration owner.

Expected path

Product proposes → Security reviews threat model → Engineering confirms build window → Sales aligns pilot list → CS prepared for cutover.

Actual playback

Sales committed Week 3 pilots → Security queued behind incident → Engineering learned date from Slack → CS zone stayed empty.

Overlay highlights where Actual skipped Expected gates — Save Decision Pattern stores scope and exceptions for the next review.

Change simulator