Search for books, people and lists
Read This Twice
HomePeopleBooksSonaLibrariesSign in
The Five Dysfunctions of a Team book cover

The Five Dysfunctions of a Team

Pike Logan Series

A Leadership Fable

Patrick Lencioni

Learn the secrets of team leadership with this gripping fable from a bestselling author. Follow Kathryn Petersen, CEO of Decision Tech, as she must unite her struggling team or risk bringing down the entire company. Patrick Lencioni breaks down the five dysfunctions that plague even the best teams, providing actionable steps to create a cohesive and effective team. With his trademark storytelling and insightful model, you'll walk away inspired to become an exceptional team leader.
Publish Date
1900-01-01T00:00:00.000Z
1900-01-01T00:00:00.000Z
first published in 2002
Goodreads Rating
4.1
ISBN
0352713295663
Recommendations
3
Recommendations
2019-04-11T17:55:13.000Z
22/ The Five Dysfunctions of a Team. @patricklencioni in an engaging narrative illustrates problems that can debilitate a team’s performance. Solutions will necessarily be situation-specific, but he gives helpful approaches. Thanks to @LilaGraceRose for recommending Lencioni.      source
2021-04-08T01:45:07.000Z
The Five Dysfunctions of a Team by Patrick Lencioni. A classic book that talks about how to recognize and resolve dysfunctional team relationships. You can get most of the value from the framework at the end, but the case study helps to remember it.      source
2014-10-23T00:00:00.000Z
There's another great element of high performing teams that I really like. Which is this pyramid that was created by Patrick Lencioni, and he wrote this book, “The Five Dysfunctions of a Team.” And the reason this is interesting is he talks about the breakdowns of the team. A lot of teams break down because they have no trust and even if you had trust, why do you need trust? If you have trust, you can actually have debates and conflict and get to the right answer. If you don't have conflicts and debate, it's the blind leading the blind. How do you actually know you got to the right answer before you commit to something? So people are not actually wanting to commit, they're afraid of committing.      source