Skip to content

Commit

Permalink
rephrase parts of Empowered Teams
Browse files Browse the repository at this point in the history
  • Loading branch information
sebastianheuer committed Mar 15, 2023
1 parent c782d40 commit 2e3c550
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion book/core-principles/empowered-teams.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,9 @@ To take pride and joy in the things we finish, we need to be able to shape our w

According to Cagan, Empowered Product Teams build solutions that are _valuable_ (customers benefit from them), _viable_ (they meet the needs of the business), _usable_ (customers understand and enjoy using them) and _feasible_ (technical effort and long-term maintenance are in relation to the value). The teams shape and own the solution they build for a given problem and can therefore also be held accountable for their results.[^1]

This kind of empowerment can help to create the perfect environment for intrinsically motivated people, because it will give us a clear _purpose_, _autonomy_ and the means to achieve _mastery_[^2]
This is in line with the views of Daniel H. Pink[^2]: we as a company cannot “create” motivation. People are motivated. Instead, we can only eliminate demotivators by creating an environment that gives clear purpose, autonomy and the means to achieve mastery.

This inherently creates an environment that is incompatible to people not finding value in purpose, autonomy or mastery.

[^1]: Marty Cagan with Chris Jones, [_EMPOWERED: Ordinary People, Extraordinary Products_](https://www.svpg.com/books/empowered-ordinary-people-extraordinary-products/), Wiley, 2021, 9-10.
[^2]: Daniel H. Pink, [_Drive: The Surprising Truth About What Motivates Us_](https://www.danpink.com/books/drive/), Riverhead Books, 2009, 85-146.

0 comments on commit 2e3c550

Please sign in to comment.