Five Org Design Things N° 10
Pattern languages and org analysis; RTO is bad, even if offices are good; old maps made 3D; diverging values worldwide; exit interviews
How can we get more of what we want, and less of what we don't want, from where we work? How do we do that with intention? How do we allow for emergence?
46 PostsPattern languages and org analysis; RTO is bad, even if offices are good; old maps made 3D; diverging values worldwide; exit interviews
Organizational health essential for firm performance; Avinsa; the heat death of Google; team performance research; platform teams @ PepsiCo
Hundreds of thousands of hours are getting wasted on bad decision-rights. It’s got to stop. (Contains at least two good ways to fix this problem.)
A tool that helps managers and individual contributors design systems that get better performance out of dual-reporting roles.
Turns out it's about learning, all the way down: How basic technologies shift strategy; Microsoft's org structure research; X-Teams; building Service Design capability; democracy at work
Why Netflix's approach to complexity – going all the way back to 2001 – creates better results.
Collaboration edition! Yumemi’s org design; Collaboration is dead; Elbows of data; How to make good documents; How to run good workshops
Platform teams are an alternative to matrix orgs and siloed, repetitive SBUs.
TLDR: Activist investors want lean SBUs, and they don't love that matrix
A few standout practices: Opacity; Outsourcing for stronger internal networks; Deep technical reviews of ongoing programs.
The 95th percentile isn’t that impressive; how DRIs worked at Apple; Effective leaders decide about deciding; Rooting out bias in decisions; AI and interest rates
Last year I was on a podcast with my friends at Zappi, and we got to talking about matrix orgs – there's an old bug inside the system, and it'll never go away.