Organizational Design Forum Report Out
summary
Satirical report enumerates concrete anti patterns and real examples from retail tech teams and a Portland workshop: it lists keeping functional silos and expensive ticket systems, imposing lengthy capex approvals, hiring hyper‑specialists instead of T‑shapes, rewarding hero culture and late‑night support, avoiding collaboration tools and change agents, and optimizing for local cost over customer outcomes. Slides auto‑advance in an ignite style and each anti pattern is illustrated with what went wrong and why those practices increased failures rather than fixed them.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:36Remain functionally siloed
- 1:53Limit communication & collaboration
- 2:10Focus on Local Optimization, Cost Focused
- 2:43Hire for all Hyper-specialized roles
- 3:16Create a lengthy approvals process!
- 3:49Let HR structure dictate how you collaborate
- 4:06Give Leadership Opposing Incentives
- 4:58Rely on cascade messaging to change your culture
- 5:31Focus only on how long the journey is
- 6:04Limit risk by avoiding change agents
related talks
33mDevops' Seven Deadly Diseases
55mFunny Stories and Anti-Patterns from the DevOps Landscape
33mReduce Small-Team Culture Shock with Agile
06mIgnite: How DevOps Anti-patterns Ruin Holidays
40mHow to fail a software project fast and efficiently?
13mTen Ways to Doom Your DevSecOps
33mWhat are the common Anti Patterns of SRE?
22m7 Deadly Traps of SRE