How's this work Pros: High autonomy within tribes / squads
{"Image DocumentName": "How\u2019s this work? Pros: High autonomy within tribes / squads", "Image ImageDescription": "Clear missions within tribes / squads. Healthy tension between delivery and people management. Easy to spin up new parts of the org, model seems to continue to scale well. Initial signs that model can support fast restructuring. Teams do retain a high degree of control over how they work day to day, and even a substantial degree over what they work on, though this differs widely. Both tribes and squads have clear missions that people general understand. At the tribe level, I think it\u2019s also relatively easy to see how all the missions roll up together to form a whole. On the best of days, there really can be a benefit to having managers whose primary concern is the happiness and growth of the members of their chapter. We don\u2019t just tromp on someone\u2019s needs in a rush to get something done, in part because there is a layer of the org dedicated to reminding us not to do that. Agile coaches often join Chapter Leads in this role. The scaling aspect just works. We recently spun up two new tribes, mine included, and it was rather amazing how simple it was, everyone just sort of new the drill. We\u2019ve also got some sign that, as our scaling has slowed down a little bit recently, and we\u2019re more likely to want to spin up a new tribe or a new squad by breaking it off from an existing part of the org, the model seems to support this well too.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}