Why creating a RACI matrix is not a good idea
summary
A RACI matrix implementation that starts as a lightweight framework becomes a rigid 25+‑role manual after months of meetings, causing more confusion, slower decisions, and killed self‑organization rather than clarity. A corporate experiment shows removing white road markings reduced vehicle speed by 133% and improved safety, supporting the claim that less prescriptive rules increase collaboration. The practical alternative is a competency matrix and forming M‑shaped, multi‑learning product teams with shared responsibility instead of exhaustive RACI charts.
AI-written summary · about
chapters (9)
- 0:00RACI matrix problem
- 1:55Why RACI was introduced
- 4:05First matrix assumptions
- 6:13Problems with RACI matrix
- 8:48RACI update failures
- 10:35London road experiment lessons
- 12:43Flaws in RACI assumptions
- 14:54Alternatives to RACI
- 16:41Q&A
related talks
01h 07mGovern with Agility
45mPortofolio Kanban, The Art of Being Loosely Coupled and Highly Aligned
48mAgile is a cult
21mScaled Agile DevOps
44mStop wasting your time with Retrospectives
24mWhy I Stopped Coaching Agility and So Should You!
26mProduct Ownership and Shared Understanding
48mBetter leaders. Better organizations
