Most execution reviews start too late. By the time a launch has slipped, the real failure has usually already happened in a quieter room: someone did not say what they knew, someone nodded without commitment, someone escalated upward instead of challenging a peer. The postmortem then sounds familiar: planning issue, ownership issue, follow-through issue, process issue. Sometimes those are correct. Often they are not wrong so much as shallow. They describe where the problem surfaced, not where it began. The harder diagnosis is usually this: the team did not trust one another enough to say the true thing early enough. That is no longer procedural. Now the conversation is about fear, avoidance, politeness, and the preference for being liked over being clear.

This is why Patrick Lencioni's Five Dysfunctions of a Team has endured. It names a pattern most teams have lived through: low trust creates fear of conflict, weak conflict creates false commitment, false commitment weakens accountability, and weak accountability eventually shows up as missed results. The model earns its keep for one reason: the dashboard is late. By the time the metric is red, the team has already spent weeks avoiding the real conversation.

Where the miss usually hides

Most companies can recite the model. Fewer notice where they stop short of using it. In my experience the real work hides in three places.

Leaders prefer process language because it feels safer. If the launch slipped because the weekly review was weak, you can fix the weekly review. If it slipped because two executives did not trust each other enough to disagree three weeks earlier, the problem gets personal, and now you are talking about whether people hide disagreement until it is expensive, whether meetings are forums for decision or rituals of politeness, whether the team prefers false peace over useful friction. That is a far more uncomfortable diagnosis, which is why many organizations stay stuck. They keep repairing the visible machinery and leave the human structure untouched. Artificial harmony is one of the costliest lies in a company. From the outside it looks mature: polite meetings, few flare-ups, apparent alignment. Then the real movie starts after the meeting, in side conversations and private reservations and compliance without commitment. What looks like an execution problem is often an honesty problem. Healthy conflict is expensive in the moment and cheap in the aggregate. Avoided conflict feels cheap in the moment and becomes expensive later.

Commitment is not consensus. Teams confuse the two. Real commitment does not require everyone to get their preferred outcome. It requires clarity, people feeling heard, and a decision explicit enough to align behind once the debate is over. Many teams never get there. They leave with "roughly aligned" or "let's refine as we go," which sounds collaborative and is often evasive, and ambiguity travels downstream disguised as flexibility. This is why I distrust over-romanticized consensus cultures. They tend to produce less commitment, not more, because people leave without enough clarity to act or enough ownership to defend the call when it gets hard.

Accountability is hardest among peers. Teams treat accountability as a manager's job. The strongest form is peer accountability, colleagues calling one another out directly when standards slip, and it is where many teams fail, because holding a peer accountable risks tension and awkwardness. So people escalate upward or soften the feedback until it changes nothing, and the manager becomes the only source of correction. If the only person who can say the hard thing is the boss, you do not yet have a strong team. You have a reporting structure.

None of this means process is irrelevant. Clear roles, decision rights, and review rhythms matter. But process amplifies the quality of the team underneath it. It rarely saves a team from fundamental dysfunction for long. A low-trust team turns any process into bureaucracy. A conflict-avoidant team turns any cadence into theater. Amy Edmondson's work on psychological safety says the same thing: a team only voices disagreement and admits mistakes when it is safe to do so, and without that, every operating system you install runs on bad data.

The exception I live

And here is where I have to push past the model, because I live the exception to it. The chain says trust unlocks conflict. I have caught myself not saying hard things to my own co-founders, and we have about as much trust as a leadership team can build. More than a decade together. Egos worn down by the years. Nobody second-guesses intent; whatever is said, we know it is said for the right reason. By the model, candor should be free for us. It is not. The discomfort still shows up, the pause before the sentence, the butterflies. Kim Scott tells the same story from the other side: she walked through fifteen years of her career, surrounded by people who trusted and liked her, before anyone told her about the metaphorical spinach in her teeth. What that taught me is that trust is the floor, not the skill. You can believe feedback is a gift and bad news is a gift, and the belief still will not deliver the hard sentence for you. Practice does. The butterflies are the point. I now treat candor as a rep to be done, not a trait to be assumed. A team that waits to feel comfortable before being honest will wait forever. Comfort is not the precondition. It is the reward.

Many execution problems do not begin as execution problems. They begin as trust problems that have not yet become legible. The work is not to add another review meeting. The work is to make the room honest, by practice, early enough that the review meeting has something true to work with.

Notes and Sources