Is your team actually a team?

Five cracks show up in every team that struggles. They stack, one on top of the other. And the first one is invisible from the outside.

A two-minute read

Part 1 · The story in 60 seconds

The best team on paper. Last place in reality.

01

DecisionTech has the best product, the most funding, and the most experienced executive team in Silicon Valley. It's losing anyway.

02

The board hires Kathryn, a 57-year-old CEO with no tech background. The executives are baffled by the pick.

03

She spends her first weeks just watching. Her diagnosis: the product is fine. The executives aren't a team.

04

She takes them offsite and names what everyone feels: silence in meetings, debates in hallways, no one accountable to anyone but her.

05

One by one, the team works down five stacked dysfunctions. It gets worse before it gets better. Two executives can't make the turn and leave.

06

The team that remains is smaller, louder in meetings, slower to agree, and it starts winning. Trust was the product problem all along.

Part 2 · The two teams

The polite team vs. the honest team

Tap each one. Both look functional from the outside.

“We keep it professional.”

Harmony as a performance.

  • Meetings end on time, on script, with nods all around.
  • The real debate happens afterward, in twos, by text.
  • Commitments stay vague, so nobody can be called out for missing them.

How it ends: mediocre decisions everyone privately doubted, missed goals nobody owns, and your best people leaving for somewhere they can say things out loud.

Part 3 · The pyramid

The five cracks, bottom floor first

Each crack makes the one above it worse. Fixing the top without the bottom never holds. Tap each one open.

Part 4 · The 60-second mirror

Where's the crack in your team?

Five questions, one per floor. Answer about your closest team, as it behaved this month. Nobody sees this but you.

1. In meetings, do people hold back what they really think?

2. Do decisions get quietly relitigated after the meeting ends?

3. When someone misses a commitment, does everyone wait for the boss to say it?

4. If you asked your team to describe itself in one word, would it be “polite”?

5. Honestly: do your people care more about their function's win than the team's?

Answered 0 of 5

Your score changes week to week. Re-take it after the next tense meeting.

Part 5 · Use it this week

Three moves. All small. All this week.

01
Go first.

Admit a real mistake to your team this week, plainly. Vulnerability from the leader is permission for everyone else. This is the bottom floor of the pyramid, and it can't be delegated.

02
Mine one disagreement.

In your next meeting, listen for the hedge. “Maybe it's just me, but…” Stop the room and pull the thread until the real issue is on the table. Then thank the person, publicly.

03
Write the decision down.

End each meeting with one sentence: what we decided, who owns it, when it's due, and who tells whom. Thirty seconds that removes both ambiguity and the excuse.

If the mirror raised a question worth sitting with, that's the page doing its job. Take one of the three moves into this week.

Rucker Solutions · ruckersolutions.com · Apex, NC

The Leadership Shelf is a Rucker Solutions series on the leadership books we use most. Rucker Solutions is a systems and AI consulting practice in Apex, NC.
No. 03 is based on The Five Dysfunctions of a Team (2002) by Patrick M. Lencioni. This is our own summary. The book is worth your two hours.
Not affiliated with or endorsed by the author or The Table Group. © 2026 Rucker Solutions LLC.