Empowered Teams Work. They Really Do
<p>What does it mean to be an empowered team?</p>
<p>An empowered team owns a <em>well-defined</em> slice of product, whatever that may be in the context of their wider organization, and is ultimately responsible for its success or failure. They have the final say over what they create and how they create it.</p>
<p>Chaos! Mass Bedlam! How could this possibly work? What next, the guillotine?</p>
<p>Hold on, you counter-revolutionaries, hear me out.</p>
<p>Empowered teams aren’t little Ayn Randian islands, proudly isolated from the rest of humanity. There is a thing that an empowered team <em>doesn’t</em> have control over, and it makes all the difference.</p>
<p>And this is <em>their context</em>. A team must work within the confines of what success means within the context in which they work. Most software organizations (though not all) are motivated by the bottom line, so a team in this context has a very real constraint placed upon it: contribute to the money-making or fail.</p>
<p><a href="https://betterprogramming.pub/empowered-teams-work-they-really-do-788f10741203">Read More</a></p>