From Diagnosis to Action: How to Actually Apply Lencioni's Five Dysfunctions

You've probably heard about Patrick Lencioni's The Five Dysfunctions of a Team. The fable, the model, the pyramid—all compelling. But knowing the theory and knowing what to do Monday morning are two very different things.

The real power of Lencioni's work isn't in understanding dysfunction. It's in fixing it. And that requires a step-by-step action plan you can run yourself, starting this week, without waiting for a consultant or a three-day offsite.

The Five Dysfunctions: The Order Matters

Lencioni discovered something critical: team failure isn't random. It follows a predictable chain:

• Absence of Trust → team members hide vulnerability
• Fear of Conflict → real disagreement gets buried
• Lack of Commitment → agreements are surface-level
• Avoidance of Accountability → no one challenges anyone
• Inattention to Results → individual agendas override team goals

Each dysfunction feeds the next. You can't skip steps. You can't start at accountability and hope trust follows. The order is everything.

Your 30-Day Action Plan: Week by Week

Week 1: Observe and Name

The Goal: Get honest about where your team actually is.

Kathryn Petersen, the CEO in Lencioni's fable, doesn't arrive with solutions. She arrives with observation. She watches. She listens. She notes what people say and—more importantly—what they don't say.

Your Actions:

• Attend your next three team meetings without leading them. Just observe. Note three moments where someone avoided saying something difficult. Note where the group pretended agreement without actually agreeing.
• Write one honest sentence to yourself: "If my team has the talent and resources it needs but isn't delivering results, what conversation isn't happening yet?"
• Have three 15-minute one-on-ones. Ask each person: "What's the one thing you see us not saying out loud as a team?" Don't defend. Just listen and write down patterns.

Why This Matters: Most leaders jump straight to solutions without diagnosing correctly. A talented team that isn't producing is almost never a talent problem. It's a trust problem hiding under professional courtesy.

Week 2: Introduce the Model

The Goal: Make the invisible visible. Name the dysfunction in the room.

This is the moment Kathryn holds a meeting and walks her executive team through the exact five dysfunctions. Not as criticism. As a mirror.

Your Actions:

• Schedule a 90-minute team meeting. Bring the five-dysfunction model on one slide or printed page. Walk through each one with real examples from your team's behavior (without naming individuals).
• Ask this question directly: "If I had to pick one dysfunction that's holding us back most, which would it be?" Let them answer. Don't correct them. Listen for consensus.
• Make this statement: "Starting today, we're going to work on this differently. We're going to say hard things out loud. And I'm going to go first."

Why This Matters: Naming dysfunction breaks the silence that protects it. The moment your team hears "We have a trust problem" or "We avoid real conflict," they're no longer pretending everything is fine. That's where real change starts.

Week 3: The Leader Goes First (Vulnerability)

The Goal: Model the trust-building behavior you want to see.

This is non-negotiable. A leader asking for vulnerability without offering it first is just politics.

Your Actions:

• In your next all-hands or team meeting, admit something real. A mistake you made. A limitation you have. Something you don't know how to do. Be specific. Not "I'm a work in progress" (everyone says that). Try: "I realized this week that I interrupted Maria twice when she was making a point, and I made an assumption about her idea without hearing it fully. That's on me."
• Tell your team why you're doing this: "I want us to be a team where it's safe to be wrong, to ask for help, to say 'I don't know.' That only happens if I go first."
• Invite them into a weekly practice: "Every Friday, I'm going to share one thing I did poorly this week. I'm inviting you to do the same—not in front of everyone if you don't want, but at least with me or the person you work closest with."

Why This Matters: Trust isn't built by being competent. It's built by being vulnerable. The moment your team sees you admit a real mistake without spinning it or defending it, the air in the room changes. Other people suddenly feel permission to be human too.

Week 4: Create Structured Conflict

The Goal: Make disagreement safe and productive.

Most teams confuse harmony with health. A team that never disagrees isn't peaceful—it's checked out.

Your Actions:

• In your next strategic meeting, deliberately introduce a decision that matters. Then explicitly ask: "What's wrong with this idea? Where could we be missing something?"
• Set a rule: "No decision leaves this room without someone playing devil's advocate. If nobody's pushing back, I'm not convinced we've thought it through."
• Reward the person who disagrees first. When someone says "I see a problem with that," respond with "Thank you. I want to hear more." Not "I already considered that." Literally make disagreement the fastest path to being heard.
• Create a low-stakes conflict practice: In your next team meeting, ask a question with no right answer. "What should be our team's top priority next quarter?" Let three different answers sit on the table. Don't resolve them immediately. Let the team sit in disagreement for five minutes and then work through it together.

Why This Matters: Without conflict, commitment is fake. When your team argues, disagrees, and then comes to a real decision together, they own it. When they sit in silence and nod, they're already halfway out the door mentally.

Week 5+: Lock In Accountability

The Goal: Make expectations clear and challenge each other when they're not met.

Your Actions:

• At the end of every meeting, explicitly state what was decided and who's responsible. Use exact language: "Sarah, you're committing to X by Friday. Tom, you're handling Y. We're checking in Monday at 10." Write it down. No vagueness.
• Build a five-minute check-in into your weekly rhythm. "Last week Sarah said she'd do X. She did. Tom said he'd do Y. He didn't, and here's why. What do we do about it?" Make accountability public, not punitive.
• When someone misses a commitment, name it immediately and together. "We said this would happen and it didn't. What got in the way? What do we need to adjust?" Not "You failed." That's blame. This is diagnosis.
• Celebrate when accountability works. "This quarter, when we said we'd do something, we did it. That's new for us, and I want to acknowledge that."

Why This Matters: Teams with accountability win because they correct course in real time instead of pretending everything's fine until it blows up. The moment your team knows that commitments actually matter—and that there's a conversation afterward if they're not met—behavior changes.

The Results Focus: Why This Matters

Once trust, conflict, commitment, and accountability are in place, results follow. Not because people are trying harder. Because the entire system now supports winning instead of protecting reputations.

Start with week one. Observe first. Name second. Everything else flows from there.

The framework works. Thousands of teams have proven it. But it only works if you actually apply it—not read about it, but practice it, week after week, even when it feels awkward.

That awkwardness is the sound of a team learning to be real with each other. Stay in it.

Download BOOKOS and listen to the full audio summary: https://bookosapp.com