Skip to content
HomeVideosBooks
AllTopicsTrends
BlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K
    Cover of The Five Dysfunctions of a Team

    The Five Dysfunctions of a Team

    Patrick Lencioni · 2002

    team leadership handbook for modern executives, managers, and organizations After her first two weeks observing the problems at DecisionTech, Kathryn Petersen, its new CEO, had more than a few moments when she wondered if she should have taken the job. But Kathryn knew there was little chance she would have turned it down. After all, retirement had made her antsy, and nothing excited her more than a challenge. What she could not have known when she accepted the job, however, was just how dysfunctional her team was, and how team members would challenge her in ways that no one ever had before. For twenty years, The Five Dysfunctions of a Team has been engaging audiences with a page-turning, realistic fable that follows the travails of Kathryn Petersen, DecisionTech’s CEO, as she faces the ultimate leadership crisis. She must unite a team in such disarray that it threatens to derail the entire company. Equal parts leadership fable and business handbook, this definitive source on teamwork by Patrick Lencioni reveals the five behavioral tendencies that go to the heart of why even the best teams struggle. He offers a powerful model and step-by-step guide for overcoming those dysfunctions and getting every one rowing in the same direction. Today, the lessons in The Five Dysfunctions of a Team are more relevant than ever.

    Business & Management
    Open LibraryAmazon
    Stats for nerds
    44recommend
    66mentions
    54people
    2012–2026years
    79% recommend20% neutral2% critical

    Mentions per year

    20122014201620182020202220242026

    What Hacker News says

    1. areactnativedevAug 2026
      Would you have any good such resources for “clicking” or expanding one’s understanding to share?

      From the top of my head and of my Goodreads I have enjoyed The art of Electronics, Understanding Earth, Material World, The world for sale, Beej’s Guide to C, The Five Dysfunctions of a team, Financial Intelligence for Entrepreneurs, The Lean Startup, Fouché by S. Zweig

      https://ciechanow.ski/mechanical-watch/

      thread
    2. jkingsberyJun 2026
      Mostly agree with this article. When I mentor people about managing, some other bits I also usually mention:

      1. 'You’re not “part of the team” anymore.' - You're not part of the software dev team, but if you're doing things right, you're part of a team, just a new one. I encourage manager mentees of mine to read a book "Five Dysfunctions of a Team" which talks about figuring out who your "first team" is. Even in environments where you manage an autonomous team, you likely are working alongside other teams towards some bigger goal. Some of the things that worked being part of a software development team continue to work in the new setting, but you also need a new set of tools.

      2. It's a two-way door. I've bounced back and forth between IC and manager roles. Some of it is just how the job market is (you look for a job, there aren't manager jobs, you go back to being an IC). Sometimes, people do it intentionally because they like being an IC. It's ok to try out being a manager, and realizing you don't like it.

      A lot of what's here isn't specific to managing, and if you advance in your career as an IC, you'll experience similar.

      thread
    3. tpoacherFeb 2026
      > Nobody disagrees with the technical argument

      That's a very strong foundational claim right at the start. And in my experience, a completely false one. Which makes the whole argument that follows it completely unsound.

      Also, the author seems to treat the terms "consensus" and "buy-in" as synonymous. They're not, and this distinction can make a huge difference in terms of healthy teams can operate. Patrick Lencioni covers this well in his classic book, "Five Dysfunctions of a Team".

      thread
    4. sseagullJan 2026
      This is one of the Five Dysfunctions of a Team (fear of conflict, caused by absence of trust).

      Highly recommend the book.

      https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Tea...

      thread
    5. hervalOct 2025
      Big American corporations (and to lesser extent, other countries that try to mimic US corporate culture) operate in a particularly dysfunctional ways. There’s ample literature on it (moral mazes, bullshit jobs and five dysfunctions of a team are particularly good books on the topic). You’re lucky to not have been a victim of that system!
      thread
    6. romanhnMay 2025
      The Five Dysfunctions of a Team by Patrick Lencioni is another classic.
      thread

    Related

    Cover of Overcoming the five dysfunctions of a team
    2018–2019

    Overcoming the five dysfunctions of a team

    Patrick Lencioni
    1 recommend · 2
    Cover of The Advantage
    2014–2023

    The Advantage

    Patrick Lencioni
    6 recommend · 14
    Cover of Influence
    2007–2026

    Influence

    Robert B. Cialdini
    214 recommend · 408
    Cover of Connecting the dots
    2018–2023

    Connecting the dots

    John Chambers
    1 recommend · 2
    Cover of Turn the Ship Around!
    2014–2026

    Turn the Ship Around!

    L. David Marquet
    55 recommend · 94
    Cover of Death by Meeting
    2010–2025

    Death by Meeting

    Patrick Lencioni
    6 recommend · 9
    Cover of The culture code
    2008–2025

    The culture code

    Daniel Coyle
    18 recommend · 29
    Cover of Team Topologies
    2019–2026

    Team Topologies

    Matthew Skelton
    24 recommend · 51