Slide‑free, decision‑first reviews
Senior leaders are favoring slide‑free, narrative‑first reviews that open with a one‑sentence headline and a clear decision ask — pre‑reads 48 hours ahead plus RAPID‑style decision roles are being recommended to keep meetings for alignment, not history. The shift is being framed as a core signal of executive presence at Apple and peers. (forbes.com, koreaherald.com)
Amazon’s six‑page narrative practice requires a written memo and a silent read of roughly 20–30 minutes at the start of a decision meeting, a pattern now cited as a model for shifting sync time to decisions rather than status. (visme.co, azeusconvene.com). Bain’s RAPID framework—Recommend, Agree, Perform, Input, Decide—formalizes decision rights and is widely recommended for leadership reviews to speed approvals and assignment of accountability. (bain.com). A compact decision packet template recommended in recent meeting guides stacks a one‑line decision ask, a one‑page executive summary (≤300 words), a 3–6 page appendix of metrics and trade‑offs, and an explicit “decision date” field to make trade‑offs and timelines visible. (speakwithskill.com, mutedeck.com). Operational rules used by companies adopting pre‑reads include distributing materials 24–48 hours before meetings, requiring a short “acknowledged” reply, and keeping the core live meeting focused on Q&A and the final decision window. (basehq.com, ideaplan.io, workmate.com). When running the live review, teams copy the Amazon cadence or a shortened variant: allow 20–30 minutes for silent reading of a full memo or a 3–5 minute silent skim of a one‑page pre‑read, then timebox discussion items with visible countdowns to lock decisions into the meeting timeline. (azeusconvene.com, mutedeck.com, focustimers.io). Embed a one‑row RAPID table in the front page of the packet that names the single Decider (D), the Recommender (R), and the Agreers (A) with explicit due dates for input; Bain and implementation guides advise naming a single D to avoid escalation loops. (bain.com, umbrex.com). Engineering review appendices that signal director‑level thinking include explicit rollout and rollback criteria, baseline SLOs and targets, a phased rollout timeline with dates, and named owners for each phase so post‑decision execution converts immediately into tracked work. (speakwithskill.com, fitgap.com).
