Why your team stopped performing (and why it's probably not the team)

If you're typing "why is my team underperforming" into a search bar at 11pm, I can save you some time. In eighteen years of coaching, across more than a thousand clients, I have almost never seen a good team suddenly turn bad. What I see, over and over, is a team responding rationally to conditions the founder can't see because the founder is standing inside them. Same people. Same skills. Same intentions. Different conditions. So before you start performance-managing anyone, look upstream. That's where the answer usually lives.

Why is my team underperforming? Ask what changed first

A team that used to perform and stopped is giving you information. Something changed. It's almost never that six people simultaneously lost their work ethic. That story is comforting, because it puts the problem outside you, but it doesn't survive contact with a simple question: what's more likely, that the humans changed, or that the environment did?

The usual suspects, in rough order of how often I see them:

The company grew and the old way of communicating didn't. At eight people, everyone hears everything. At twenty-five, information travels through you, and you've become a bottleneck without noticing. People aren't slow because they're lazy. They're slow because they're waiting. Waiting for your sign-off, your context, your answer to the Slack message you haven't opened.

The goal got fuzzy. In the early days the goal was survival, and survival is wonderfully clarifying. Then you raised, or hit profitability, or landed the big client, and the single sharp goal dissolved into seven medium-sized ones. A team without a clear North Star doesn't stop working. It works hard in six directions at once, which from the outside looks exactly like underperformance.

Fear got into the room. This is the big one, and it deserves its own section.

Fear looks like laziness from the outside

There's a frame I use with every client, from The Location of Leadership: above and below the line. At any moment, each person on your team is in one of two states. Above the line means open, curious, willing to learn and to be wrong. Below the line means closed, defensive, protecting themselves. Everyday example: your designer ships something rough. Above the line, she flags it herself and asks for input. Below the line, she buries it, hopes nobody looks closely, and spends her energy managing how things appear instead of making things better. Same person. Same talent. Completely different output.

And what pushes people below the line is fear. Clients don't like that word. They call it stress, overwhelm, "a lot going on". It's fear. Fear of your reaction to bad news. Fear of being the one who broke the thing. Fear of asking a question that makes them look junior.

The research here is solid and worth your ten minutes. Google's Project Aristotle studied 180 of its own teams to find out what separated the best from the rest, and the answer wasn't talent, seniority or workload. It was psychological safety, the shared belief that you won't be punished or humiliated for speaking up with questions, mistakes and ideas. Amy Edmondson's work at Harvard, summarised well here, found the same thing in hospitals: the best teams weren't making fewer mistakes, they were reporting more of them, and fixing them faster.

Now the uncomfortable part. In a company of 15 to 60 people, the biggest single input into whether people feel safe is you. How you react when someone brings you a problem. Whether the last person who admitted a mistake got curiosity or a public autopsy. Whether your Monday mood sets the temperature for the whole floor. Culture is what people do when you're not in the room, and what they do when you're not in the room is shaped almost entirely by what happened the last few times you were.

The mirror questions

Before you diagnose the team, sit with these honestly. Not the answers you'd give on a podcast. The real ones.

When did someone last bring you genuinely bad news, early? If you can't remember, that's not because nothing is going wrong. It's because the bad news is being managed around you. Teams go quiet before they go bad.

How much feedback are you actually giving? I ask founders this constantly and the honest answer is nearly always "not enough". Not performance reviews. Real, regular, specific feedback, weighted heavily to the positive: what they're doing well and why it matters. People who only hear from you when something breaks learn to keep their heads down. If your feedback muscle is weak, The Effective Feedback Protocol in the full library gives you the structure.

Are you still making decisions that stopped being yours months ago? Count the decisions that waited on you this week. Every one of them taught your team that thinking is your job and executing is theirs. Then you wonder why nobody takes ownership.

Is there one person poisoning the well? Researchers call it the bad apple theory, and it's real: one consistently negative, checked-out or toxic team member drags the performance of everyone around them, fast. If there's a name in your head right now, you already know. That one genuinely is a team problem, but tolerating it for six months was a you problem.

What this looked like for one founder

A composite from my coaching room, details changed. A founder running a 30-person company came to me convinced he had a B-team. "They used to be hungry. Now everything takes three follow-ups." He'd drafted a plan to replace two of his leads.

We didn't touch the plan. Instead we looked at his last month. He'd torn strips off an engineer in a stand-up over a missed deadline. He was the approver on every piece of client work. And the company's goal had shifted from "win the big contract" to something he described, without irony, as "sustainable diversified growth". His team wasn't hungry for that because nobody can be hungry for that.

Three changes. He apologised to the engineer in front of the same people who'd watched the spray, which cost him more than it sounds and bought back more than he expected. He handed full sign-off on client work to his two leads, the same two he'd been about to replace. And he gave the company one goal for the quarter, one, written where everyone could see it.

It took about six weeks to feel different, because trust comes back slower than it leaves. But the "B-team" turned out to be an A-team that had spent a year learning that initiative got you burned and waiting was safe. Nothing was wrong with the people. Something was wrong with the room.

What to do this week

Not a transformation program. Four moves you can start Monday.

Name one goal. If the team can't tell you the single most important thing this quarter, that's the first fix, and it costs nothing but the discomfort of choosing.

Go find bad news. Ask each of your direct reports: "What's the thing you've been hesitating to tell me?" Then, and this is the whole exercise, respond with curiosity instead of a verdict. You're not gathering information. You're teaching them that bad news is safe here. One good reaction is worth more than a values poster.

Give five pieces of real feedback. Specific, mostly positive, tied to why it mattered. "The way you handled that client call kept the account" beats "good job" by a mile.

Take yourself out of one loop. Pick one category of decision you're still approving and hand it over, fully, with the context needed to make the call without you. This is the start of a much bigger shift, from being the best player on the field to building a team of CoFounders, people who think and act like owners. That whole journey is mapped in The Founder-to-Leader Transition: How to Build a Team That Runs Without You, and the operating system behind it is in The Coaching Standard: How to Turn Your Team Into CoFounders.

The reframe that changes everything

"Why is my team underperforming" is a fine question to start with, but the better question is the one underneath it: what conditions am I creating, and what would this team do in better ones? The first question leads to performance plans and quiet resentment. The second leads to a team that runs harder when you're not watching, because the thing driving them was never your supervision.

The founders who make this shift don't end up with a fixed team. They end up with a different company. And it starts with one honest look in the mirror, ideally with someone in your corner who'll tell you the truth about what they see.

If you want that conversation, Book a Discovery Call.