Every operation has a team like this somewhere on the floor.
Good people. A supervisor who shows up, cares, and works hard. Numbers that aren’t failing, they’re just… fine. Nothing shows up in a performance review. Nothing gets flagged in a staff meeting. By every visible measure, the team is doing okay.
And if you sat with that team long enough, you’d feel something underneath the “okay.” A ceiling. A sense that the people on that roster are individually capable of more than the team is collectively producing.
That gap — between what a team is and what it could be — is one of the most expensive problems in industrial leadership, and one of the least understood. Most senior leaders can feel it. Almost none of them can name it.
Two Different Rooms, One Diagnosis
Patrick Lencioni is one of the most respected organizational consultants in the business world, and his book The Five Dysfunctions of a Team is close to required reading in leadership circles well beyond manufacturing. His model was built inside corporate consulting rooms with executive teams.
That’s about as far from a cockpit or a shop floor as you can get. And yet, walk his five-layer model against what actually breaks down on a frontline team, and it lands with uncomfortable precision.
Two completely different bodies of work, built from two completely different rooms, arriving at the exact same failure points. That’s not a coincidence. When two independent paths of study land on the same diagnosis, it stops being an opinion. It starts looking like a law of how teams actually function or fail to.
The Pyramid Underneath Every Team
Lencioni’s model is a pyramid, five layers tall. The part that matters most isn’t any single layer — it’s the relationship between them. Each layer is the foundation for the one above it. You cannot skip a layer, and if the bottom is cracked, everything stacked on top of it is unstable no matter how solid it looks from a distance.
Trust is the foundation. Not the shallow version — believing someone will show up on time — but the kind of trust where a team member can admit a mistake, a weakness, or an honest “I don’t know” in front of the group without fear of it being used against them later. Most frontline teams don’t have this layer built. Not because anyone on the team is a bad actor, but because nobody ever built the conditions for it.
Fear of conflict sits on top of trust. Without trust, teams don’t debate — they nod. Meetings feel calm, even agreeable, and leaders mistake that calm for health. It isn’t health. It’s avoidance wearing a friendly face. A team that fears conflict isn’t a peaceful team. It’s a team quietly stockpiling problems nobody is willing to name out loud.
Lack of commitment is next. Without real debate, you don’t get real buy-in — you get a room full of nodding heads who walk out the door and go straight back to cruise control. Real commitment requires something concrete to commit to, anchored in something people actually care about. Abstract direction produces polite nodding. Specific, meaningful direction produces commitment.
Avoidance of accountability follows. Without genuine commitment, standards have no substance. It’s difficult to hold a peer accountable to something they never actually bought into, and harder still to hold someone else accountable to a standard you’re not bought into yourself. A team without real accountability usually isn’t full of people who don’t care. It’s a team that was never rallied around anything compelling enough to give accountability something to stand on.
Inattention to results sits at the top. When the first four layers aren’t solid, individuals naturally start placing their own priorities over the team’s shared outcome. At the extreme, that looks like ego and politicking. More often, it’s quieter — a kind of subtle chaos that shows up when collective clarity is missing, and each person fills that void with whatever matters most to them individually.
Trust. Conflict. Commitment. Accountability. Results. Five layers, building on each other from the bottom up.
The Mistake Almost Every Organization Makes
Here’s what happens next in most operations, and it’s the mistake that keeps teams capped for years without anyone understanding why.
When results stall, the instinct is to focus on results. Add another KPI. Tighten the metrics. Install another accountability meeting. It’s an understandable instinct — results are the thing you can measure, and results are what leaders are ultimately responsible for producing.
But if a team is actually stuck two or three layers below the top, adding pressure at the top doesn’t fix anything. It makes things worse. More pressure without safety doesn’t produce more honesty — it produces more hiding. People get better at looking accountable instead of actually being it. The numbers might even move for a quarter or two. But nothing structural has changed. The team has just learned to perform under short-lived scrutiny instead of building real capability underneath it.
That’s the diagnostic mistake. It treats a foundation problem like a top-layer problem, and it’s why the same team can cycle through the same performance conversation year after year without anyone ever finding the actual crack.
A Three-Question Gut Check
Before investing another dollar in a results-focused fix, run your own team through three questions. Not a formal assessment, just something to sit with honestly.
- When was the last time someone on your team admitted a mistake before they got caught?
- Do your team’s meetings actually surface disagreement, or mostly polite nodding?
- When was the last time your frontline leaders or team members held each other accountable, without you or someone above them having to step in?
Wherever the hesitation shows up when you answer those honestly, that’s likely where the real work has to start — not at the top of the pyramid, at whatever layer is actually cracked underneath it.
The Roster Was Rarely the Issue
It’s worth being precise here. A capped team almost never traces back to who’s sitting on the roster. It’s rarely that a supervisor inherited the wrong people, or that a particular group simply doesn’t have what it takes.
What’s usually missing is something nobody deliberately built: a system that establishes leadership before it demands results. Most organizations never built that system — not because leadership doesn’t care, but because nobody ever named the pyramid, showed a leader where their team was actually stuck, or handed them a structure built to address it layer by layer.
Name the gap correctly, and it stops being a mystery. It becomes something you can actually build toward.
What Changes When the Foundation Holds
Picture the same team, eight months later.
The crew brief opens with someone naming a real problem before it becomes unavoidable, not defending against one that already landed. The one-on-one surfaces genuine disagreement instead of a polite nod, and the plan that comes out of it survives contact with the floor, because everyone in the room actually believed it before they left. Standards hold without a supervisor policing every instance, because the team bought into what they’re protecting, not just what they were told to do.
None of that reads as a dramatic turnaround from the outside. But it shows up as fewer fires nobody saw coming, less rework nobody can trace to a single cause, and a floor that runs the same way whether the supervisor is standing on it or stepped away for the afternoon.
That’s not a different set of people. It’s the same team operating on a foundation somebody finally built underneath them.
Where to Start
If you’re recognizing your own team somewhere in this pyramid, start with The Leader’s Preflight Checklist at operationlead.com/checklist. It’s free, and every tool in it has a home in the layer it was built to strengthen — routines that build trust, a rehearsed approach to the conversation that gets avoided, a way to make the mission concrete enough to commit to, and a standard that holds without becoming personal.
If you’re a senior leader who wants to do more than diagnose the ceiling — who wants to actually rebuild what’s underneath it, across an entire organization — you can learn about our system and process at operationlead.com.
Naming the pyramid is diagnosis. Awareness is the first step. Only then you can move towards repair.
Let’s Lead,
Craig
