Many execution reviews start too late. By the time a launch has slipped, the failure may have begun in a quieter room. Someone did not say what they knew. Someone nodded without committing. Someone took a disagreement upward instead of raising it with a peer.

The postmortem then sounds familiar: planning, ownership, follow-through, process. Those may be the right things to examine. Sometimes, though, they describe where the problem surfaced rather than where it began. The harder question is whether people trusted one another enough to speak plainly and early. That shifts the conversation from procedure to fear, avoidance, politeness, and the desire to be liked instead of clear.

This is why Patrick Lencioni's The Five Dysfunctions of a Team has endured. It names a pattern many teams recognize: low trust can make people avoid conflict. Without useful conflict, people may leave a discussion without a real commitment. That weakens accountability and can eventually affect results. The model is useful because the dashboard is late. By the time a metric turns red, the team may have spent weeks avoiding the conversation that would have helped explain it.

Where the miss usually hides

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

Process language feels safer. If a launch slipped because the weekly review was weak, you can fix the weekly review. If it slipped because two people did not trust one another enough to disagree three weeks earlier, the problem gets personal. Then you have to ask whether people hide disagreement until it becomes expensive, whether meetings are for making decisions or performing politeness, and whether the team prefers false peace to useful friction.

That is a more uncomfortable diagnosis, so organizations can keep repairing the visible machinery while leaving the human structure untouched. Artificial harmony is costly. From the outside, it can look mature: polite meetings, few flare-ups, and apparent alignment. Then the real discussion starts after the meeting, in side conversations and private reservations. People comply without committing. What looks like an execution problem may be an honesty problem. Healthy conflict costs something in the moment and can save time later. Avoiding conflict feels cheap at first and can become expensive.

Commitment is not consensus. Teams often confuse the two. Real commitment does not require everyone to get the outcome they preferred. People need a clear decision and a chance to be heard. Once the debate is over, they need enough clarity to act on the decision, even if it was not their first choice.

Many teams never get there. They leave with phrases like roughly aligned or let's refine as we go. Those words can sound collaborative while leaving the decision unclear. That ambiguity travels downstream as flexibility. I am wary of cultures that treat consensus as the only fair outcome. They can leave people less ready to act because nobody has said plainly what the decision is or who owns the next step.

Accountability is hard among peers. Teams can treat accountability as a manager's job. A stronger team also makes room for colleagues to speak directly when standards slip. That can be awkward, so people may escalate upward or soften feedback until it changes nothing. Then the manager becomes the only source of correction. If people can only say the hard thing to someone with formal authority, the team still has work to do on candor and peer accountability.

Process still matters. Clear roles, decision rights, and review rhythms help people work together. But process depends on the quality of the conversations underneath it. A team with little trust can turn any process into bureaucracy. A team that avoids conflict can turn any meeting rhythm into theater. Amy Edmondson's work on psychological safety points to one condition that helps: people are more able to raise concerns and admit mistakes when doing so does not expose them to humiliation. Without that, an operating system can run on incomplete information.

The exception I live

Here is where I have to push beyond the model. I have caught myself avoiding hard conversations with my own co-founders, even though we have built a great deal of trust. We have spent more than a decade together. Time has worn down some of our egos. We know one another's intentions. By the model, candor should feel easy for us. It does not. There can still be a pause before the sentence, and butterflies.

Kim Scott tells a story from the other side. After fifteen years of working with people who trusted and liked her, someone finally told her about the metaphorical spinach in her teeth. Trust gave people a reason to care about the relationship. It did not mean the difficult feedback happened by itself.

That has changed how I think about candor. Trust is a foundation, but it is not the skill. You can believe that feedback and bad news are gifts, and still fail to say the hard thing. Practice helps. The butterflies may simply be part of the moment. I now try to treat candor as a rep to do, not a trait to assume. A team that waits to feel comfortable before being honest may wait a long time. Comfort is not the precondition. It may come after the practice.

Many execution problems do not begin with execution. Some begin with concerns people have not made clear to one another. The answer is not always another review meeting. We need a room where people can speak honestly, early enough for the review meeting to have something true to work with.

Notes and Sources