Explore transformation tips from software professionals in this conference talk on dev culture hacking and organizational refactoring. Discover how to effectively map human architecture, read dynamic systems, implement the right changes, move beyond consensus, and embrace devolution over delegation. Learn why traditional re-organizations often fall short and how to leverage existing maker skills for driving meaningful change. Gain insights on the importance of understanding organizational culture, power dynamics, and the role of openness in building trust. Delve into practical strategies such as the Advice Process, circles and roles, and the emergence of organic hierarchies. Acquire valuable knowledge on refactoring techniques and culture hacking methods to drive successful transformations in software development organizations.
Dev Culture Hacking and Org Refactoring - Transformation Tips from Software Pros
Overview
Syllabus
Org Refactoring & Culture Hacking Andrew Harmel-Law @al94781 Tech Principal @ ThoughtWorks
Who is to blame!?!
"Traditional" Re-Orgs & Transformations
We can do a better job
1. Your organisation's structure is best
The best people to drive these changes are those closest to the action makers.
Our existing maker skills are ideally suited for this work.
Refactoring and Hacking
I. Map the Human Architecture II. Read the Dynamic System III. Make the Right Change IV. Kill Consensus V. Beyond Delegation
Don'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
Refactor- ing Tips
Your next hits... THE TOYOTA WAY
CULTURE: "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"
It's about POWER
Devolution Beats Delegation
Advice 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)
Right changes in end-to-end dynamic systems++
Circles and Roles++ • Invite co-owners - start with holiday cover • Make / encourage changes • Let hierarchy emerge as, where and when required
Refactoring or Hack?
What's
What questions have you got?
Taught by
Devoxx
