Dev Culture Hacking and Org Refactoring Transformation tips from Software Pros
summary
Argues organizations should be refactored continuously like code, not big‑bang reorganizations, and offers five concrete patterns: map roles as circles and domains (used mind maps and Confluence to model 36 developers and 98-person org), read the dynamic system (value‑stream/event flow, event storming and post‑its), make targeted tweaks (auto‑approve training then deploy email templates, tags and Outlook rules — initial change backfires then tuning almost maxes the training budget), advice process replaces consensus, and devolve power instead of mere delegation.
AI-written summary · about
chapters (21)
- 0:00Org Refactoring & Culture Hacking Andrew Harmel-Law @al94781 Tech Principal @ ThoughtWorks
- 4:07Who is to blame!?!
- 8:02"Traditional" Re-Orgs & Transformations
- 10:00We can do a better job
- 11:031. Your organisation's structure is best
- 11:28The best people to drive these changes are those closest to the action makers.
- 11:44Our existing maker skills are ideally suited for this work.
- 12:02Refactoring and Hacking
- 13:28I. Map the Human Architecture II. Read the Dynamic System III. Make the Right Change IV. Kill Consensus V. Beyond Delegation
- 21:55Don't overestimate existing understanding of how the org works . It's a map of existing power and influence • Openness builds trust • You don't need to be in charge to do this . You'll learn loads • What you can see you can change
- 33:50Refactor- ing Tips
- 36:18Your next hits... THE TOYOTA WAY
- 46:01CULTURE: "The pattern of basic assumptions that a given group has invented, discovered, or developed in learning to cope with it's problems of external adaptation or internal integration"
- 47:32It's about POWER
- 48:29Devolution Beats Delegation
- 50:15Advice Process++ • Power will be initially held by managers / leaders • Role models will be required . It's a safe way to transfer power (and a gateway drug)
- 51:46Right changes in end-to-end dynamic systems++
- 53:05Circles and Roles++ • Invite co-owners - start with holiday cover • Make / encourage changes • Let hierarchy emerge as, where and when required
- 54:59Refactoring or Hack?
- 56:49What's
- 57:27What questions have you got?
related talks
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
45mRefactoring in Business World... for Developers?
39mDesigning an Organization, Lessons from scaling technical orgs
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
43mSoftware Eats Culture For Breakfast
59m✊ Join the DEV-olution: A Culture of Empowered Developers
58mRefactoring the Architect’s role
33mVersatile Organization Design with the unFIX Model