TL;DR
A company I was working with had what looked, from the outside, like a strong team.
They were smart people, experienced, genuinely committed. Their meetings ran well. Decisions got made. And then, almost every time, something would happen in the weeks that followed that required the decision to be reopened. Projects that had been signed off needed revisiting. Directions that seemed settled weren't being acted on. The founder kept looking at execution, at timelines, at how work was being scoped and handed off.
It took a while for both of us to see what was actually happening.
The agreement in the rooms was real. Nobody was being dishonest. But somewhere along the way, disagreeing directly had started to feel more costly than going along and adjusting later. So people said yes in the meeting and then spent the next few days quietly building a counter-case with each other, modifying the work without raising the concern, or waiting to see if the decision would unravel on its own. The real negotiation was always happening somewhere the founder wasn't.
What they were calling alignment was people choosing to say what was easiest, not what was true.
I've been in rooms like that one, on both sides of the table. Working through that pattern with teams made me want to understand it properly. When I came across Patrick Lencioni's framework, the five dysfunctions of a team, built as a pyramid, I had a name for what I'd been watching. The second layer of his pyramid is fear of conflict: the tendency to replace genuine debate with artificial harmony. He argues it's the dysfunction that does the most quiet damage, and everything above it on the pyramid collapses when it's missing. In my experience, he's right. But his framework describes the pattern. What I want to talk about here is what it actually looks like from inside it, and what it costs before you see it.
Lencioni calls it artificial harmony. The team appears aligned because nobody is fighting. But the absence of visible conflict doesn't mean the conflict isn't there. It means the conflict has found somewhere safer to go.
There are two forms of this I see most often.
The first is what I'd call performance disagreement. A team argues, sometimes quite loudly, but always about safe things. Timelines. Tools. Whether the slide deck should open with the data or the story. The underlying questions, direction, priorities, whether the strategy is actually working, never get touched. I've sat in review meetings where people debated the font on a presentation for twenty minutes and said nothing about the brief they all knew was underbaked. The debate feels real. The culture of debate is entirely constructed. The team has located the edges of what's actually up for discussion and learned to stay well within them.
The second is corridor consensus, which is what was happening in the company I described above. Someone says yes in the room, and then the actual decision gets renegotiated in a series of smaller conversations that the decision-maker isn't part of. On paper the team is collaborative. In practice every decision is provisional and you're the last to find out.
In both cases, the room runs smoothly. And that smoothness is the thing you have to stop reading as a positive signal.
Here's what I think Lencioni gets right that gets lost when people talk about this framework at a surface level.
Fear of conflict doesn't just produce bad meetings. It produces everything above it on the pyramid too.
When a team avoids real debate, decisions get made without genuine buy-in. People agree because they're supposed to, not because they believe it. And when people don't believe in a decision, they don't hold each other accountable for executing it. Accountability requires a shared standard. A shared standard requires having actually argued out what that standard is. Skip conflict, skip commitment. Skip commitment, and accountability becomes a matter of individual personality rather than team expectation. And when accountability erodes, people retreat to what they can control and protect individually. Collective results stop mattering as much as personal comfort.
The smooth meeting is never just one smooth meeting. It's the first step in that sequence.
Your team watches how you handle disagreement more closely than almost anything else you do.
I learned this the hard way. There was a strategy conversation at Pangolin a couple of years ago where someone pushed back on a direction I'd already committed to internally. Their point was reasonable. But I'd already done the work in my head, already moved forward in my thinking, and what I felt in that moment wasn't curiosity. It was impatience. I didn't shut them down. I asked a question, heard the answer, and then moved the conversation forward in a way that made it clear the direction wasn't changing.
They raised it once more, a few weeks later, in a different context. After that, they stopped.
The signal that someone has stopped challenging you doesn't come with an announcement. It comes as a gradual smoothing out of your conversations, a slight shift in how they frame things, a reduction in the moments where you feel any friction. It can feel, for a while, like things are getting easier. What it actually means is that someone has made a calculation and decided that being direct with you costs more than it's worth.
The culture you build is almost entirely shaped by your own relationship with being challenged. Not by what you say you want. By what people experience when they actually try it.
In Edition 2, I wrote about Work Shouldn't Feel Like an Audition — the idea that people do their best work when they're not performing for an audience. A team afraid of conflict is always performing. They've learned what you want to see in a room, and they're showing you that.
If genuine challenge only happens when someone is individually brave enough to initiate it, you are relying on personal courage to do the work that culture should be doing. And courage doesn't scale.
At Pangolin, we've been building something that helps with this. In certain reviews and creative presentations, we now assign someone, it rotates, usually whoever has the least ownership over the work being reviewed, the specific job of arguing against the approach. Not to be difficult. To make sure we haven't missed something we'd want to know about before committing further.
The role gets introduced at the start of the session, briefly: this person's job today is to find what's wrong, or what we haven't considered. Everyone knows it's coming. That framing matters because it separates the challenge from the challenger. The person isn't being critical. They're doing a job the team agreed was worth doing.
The first two or three times we ran it this way, it was stilted. The designated person would raise something mild, something obviously safe. It felt more like a formality than a genuine stress test. What changed it was when someone in the role pointed out an assumption in our brief that none of us had named, but that everyone immediately recognised as real. That shifted the room. People started taking the role seriously because they'd seen it actually work.
What made it land was that we responded to that challenge by changing the approach. Not dramatically. But visibly. The person who raised it saw the consequence of having raised it. And that's what made the next person willing to actually push.
The practice may not translate directly to every team. But the underlying principle holds: if you want challenge to be normal, you have to build it into the structure of the work, not leave it to whoever happens to be feeling confident that day.
There's a version of building a moat that's about protecting something you already have. But the more durable version is building something that gets stronger with use.
A team that has genuinely learned to fight well, to challenge each other openly, to argue about the right things, to disagree without it becoming personal, gets better at it over time. The first hard conversation is the hardest. The second is easier. The standard of what's worth raising gradually rises, and so does the quality of what gets caught before it becomes a problem.
In practical terms, that looks like this: in the company I described at the start, decisions being reopened two weeks later was the norm. At Pangolin, since we started building challenge into our process deliberately, we've had moments where a concern raised in a session changed a direction before it became expensive to change. The brief got sharper. The reversal happened early, not late. That's the difference between a team that fights well and one that doesn't.
That's not something you can replicate quickly from the outside. You can hire smart people. You can introduce the right processes. But a culture of genuine challenge takes years to build and is almost invisible until you see what it produces.
When did someone last push back on you in a room full of people? Something that actually mattered. Something that made you pause before you responded.
If you're struggling to answer that, it's worth sitting with why.
I'd love to know what this brings up for you. The best conversations from The Moat always happen in the thread. Hit reply or drop a comment.
See you next month. Avani
