You Didn't Have Bad People. You Had Bad Conditions.

The Instinct That Gets It Wrong

When a team underperforms, most managers go straight to personnel. The wrong people. Not enough talent. Should have hired better. And sometimes that's true. Sometimes you do have the wrong person in the wrong seat.

But in my experience, that's the exception, not the default explanation. More often, when a team is struggling, what actually happened is that someone handed a group of capable people a broken set of conditions and then graded them on the results.

I've been on both sides of this. I've been the manager who inherited a failing team and eventually figured out the team wasn't the problem. And I've made the other mistake too, kept looking at the people when I should have been looking at the environment I built for them.

The problem with blaming people is that it lets you stop looking for the real cause.

What "Set Up to Fail" Actually Looks Like

It's not always obvious. It rarely looks like negligence. More often it looks like:

A team using software that was the right choice four years ago and hasn't been updated since. A rep trying to manage a complex customer workflow across three systems that don't talk to each other, copy-pasting information manually because nobody ever built the integration, logging calls in one place, tracking outcomes in another, updating a spreadsheet that three people maintain and nobody trusts. Then a manager looks at the output numbers and wonders why productivity is low.

Or a team with no clear escalation path. Someone hits a wall on a deal, a customer issue, a technical problem, and there's no defined process for getting help. They make a judgment call, sometimes it works, sometimes it blows up, and when it blows up the manager says they should have handled it better.

Or a new hire who gets two weeks of onboarding that was designed for a product that no longer exists, then gets dropped into the queue and graded on the same metrics as someone with two years of institutional knowledge.

None of this is malicious. Most managers who create these conditions aren't bad managers. They're busy. They inherited the dysfunction themselves. They've been meaning to fix it. But the team pays the price in the meantime, and then the team gets blamed for the bill.

The Question Nobody Asks

Here's the question I've started asking when a team isn't performing: what would better conditions have made possible here?

Not as a rhetorical device. As a real diagnostic. Walk through it seriously.

If this team had tools that actually fit the workflow, how much time would come back in every person's day? If there was a clear escalation path, how many of those blown-up judgment calls get handled correctly instead? If onboarding reflected the actual product, how much faster would the new hire ramp to full productivity?

Sometimes when you run through that exercise, the numbers are uncomfortable. You realize you've been holding people accountable for output that the environment was physically preventing them from delivering. That's not a people problem. That's a leadership problem.

I ran a team once where call handle times were consistently above target. The standing interpretation was that the reps weren't efficient enough, weren't following the process, needed more coaching. We coached. Handle times didn't move. Then someone finally looked at the actual workflow and found that reps were spending four minutes of every call navigating a lookup process that, with one system change, could have been automated down to about thirty seconds. Four minutes per call, across fifty reps, across hundreds of calls per day. The people weren't the problem. The process was the problem. Nobody had asked what better conditions would have made possible.

Why Managers Default to Blaming People

There are a few reasons this happens, and they're worth naming because if you recognize the pattern in yourself, you can interrupt it.

First, it's faster. Deciding someone isn't performing and managing them out, or putting them on a PIP, feels like action. Auditing your tools, rebuilding a process, redesigning onboarding, all of that takes time and requires admitting that some of the failure is yours.

Second, it protects the ego. If the problem is the person, then by implication the manager's decisions were sound. If the problem is the conditions, then the manager built or tolerated the conditions that caused the failure. That's a harder thing to sit with.

Third, the feedback loops are slow. When you change a person, the result is visible quickly. When you change a process or a tool, the improvement takes time to show up in the data, and by then you've moved on to the next fire.

None of those are good reasons. They're just the reasons it happens.

What to Actually Do About It

If you manage a team that's underperforming, or if you're inheriting one, here's where to start.

Before you make any personnel decisions, do a conditions audit. Sit down with two or three of your people, not in a one-on-one about their performance, but in a working session about the work itself. Ask them what slows them down. Ask them what they're doing manually that could be automated. Ask them where they go when they hit a wall and aren't sure what to do. Ask them what they wish they'd been told in week one that nobody told them until month three.

You will hear things that surprise you. That's the point.

Then look at what those answers are costing. Not in abstract terms. In real numbers. Time per task, calls per day, ramp time for new hires, escalation rate, whatever the relevant metrics are for your team. Quantify the drag. When you can see the cost of the broken condition in actual numbers, it's a lot harder to keep blaming the people.

Then fix the highest-leverage thing first. Not everything at once. Pick the one change that would have the biggest impact on the most people and do that. Then measure. Then do the next one.

This is not a one-time exercise. The conditions that fit your team today won't fit the team you'll have in eighteen months, especially if you're growing. Building the habit of asking "what would better conditions make possible" on a regular basis is what keeps you from accumulating debt you eventually blame on the wrong people.

The Thing About Talent

Here's the part that makes some managers uncomfortable: when you actually fix the conditions, you often find out that you had better talent than you thought.

People who were struggling start performing. People who seemed checked out re-engage because the friction is gone and the work is actually possible now. People who felt like they were constantly failing start feeling like they can win.

That's not a coincidence. Most people want to do good work. Most people came to the job intending to perform. When the environment doesn't let them, they adapt in ways that look like underperformance, they take shortcuts, they stop trying to improve, they do the minimum that the broken process allows.

Fix the process and you get the person who wanted to be there in the first place.

Now, sometimes you do all of this and someone still isn't working out. That happens. There are genuinely wrong-fit situations, and no amount of better tooling fixes a fundamental mismatch between a person and a role. But that conversation is a lot more honest, and a lot more defensible, when you can say you actually gave them the conditions to succeed and they still didn't. That's a very different conversation than deciding someone failed in a broken environment.

The team you want might already be working for you. You might just need to stop blaming them and start building better conditions for them to actually show you what they can do.