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

When a team underperforms, check the work conditions before deciding the people are the problem. Look at the tools, process, training, priorities, and access to help. Then ask whether the team had a fair chance to meet the standard you set.

Sometimes the role is a poor fit, or someone is not doing the job. That happens. But if several people struggle in the same way, or a new hire falls behind despite trying, inspect the system around the work before making a personnel decision.

What bad conditions look like

Bad conditions rarely announce themselves. They often look like ordinary friction that has been accepted for so long that nobody questions it.

A team might copy the same customer information into three systems because the systems do not connect. A representative might pause a customer call to search for an answer in an outdated manual. A new hire might receive training written for an older product, then get measured against colleagues who know the current one. A manager might hold people accountable for a deadline without making clear which of their other priorities should move.

These are hypothetical examples, but the pattern is familiar: the job asks people to produce a result while making that result harder to reach.

That does not excuse every missed commitment. It changes the questions a manager should ask before deciding what the miss means.

Look for a team pattern

Start with the shape of the problem. Is one person struggling while others doing similar work meet the standard? Or are several people missing the same target, repeating the same mistake, or raising the same obstacle?

A problem across the team is a reason to inspect the conditions. A problem limited to one person may call for closer coaching, clearer expectations, or a conversation about fit. Neither pattern proves the cause on its own. It tells you where to look first.

Compare the work people are actually doing. Check whether they have the same tools, training, time, access to decisions, and definition of done. A target can look consistent on a dashboard while the work behind it is not.

Run a conditions audit

Before making a major performance decision, talk with a few people who do the work. Make the conversation about the job, not a disguised performance review.

Ask where work gets stuck and which steps take longer than they should. Find out what people have to redo, copy, or chase, and whether they know who can help. Ask what they needed to know earlier, and which priority should move when urgent work appears.

Listen for specific examples. "The process is broken" gives you a direction. "I wait two days for an approval, then rush the task that was due yesterday" gives you something to check.

Then compare what people say with the work itself. Observe a task from beginning to end. Look for handoffs, repeat entry, waiting, unclear decisions, or rules that conflict. Ask whether the expected result can be produced with the time and resources available.

Measure the cost before you pick a fix

Once you find a possible obstacle, estimate what it costs. Use a measure that fits the work: minutes spent per task, rework, delayed cases, missed handoffs, errors, or time for a new hire to work independently.

For example, suppose a team says it re-enters customer details in two systems. Before promising a software fix, sample several cases. Confirm how often the duplicate entry happens, how long it takes, and whether it causes errors. The evidence may support an integration, a simpler process, or a decision to stop collecting information nobody uses.

That small check beats launching a broad project based on a hunch.

Fix one condition that affects several people, then watch the measure you chose. If the team has more capacity but the result does not improve, revisit the diagnosis. The obstacle may be somewhere else, or the team may need a clearer standard or more practice.

Why managers blame people first

A personnel decision feels immediate. Rebuilding a process, replacing a tool, or improving onboarding takes more time. It can also reveal that the manager set an unrealistic expectation or let a bad workflow continue.

That discomfort is real. It is still part of the job.

The reverse mistake is excusing every miss as a system problem. Once you have checked the tools, process, training, time, and support, you still need to talk directly with the person about the gap. Explain the expected result, the evidence you see, and what must change. Agree on a follow-up date.

Fair accountability needs both parts: a reasonable chance to succeed and a clear conversation when the person does not meet the standard.

Give the conditions a fair test

After removing an obstacle, make the change visible. Tell the team what changed and what result you expect to see. Give people enough time to use the new process, then check the measure again.

If the work improves, keep the change and look for other friction. If it does not, do not keep defending the fix because it took effort. Recheck your assumptions and ask the people doing the work what still gets in the way.

Good managers are responsible for the conditions they create or tolerate. They are also responsible for addressing performance that remains below standard after those conditions are made clear and workable.

Before you label someone a bad fit, ask whether the work gave them a fair chance. If the answer is no, fix that first. If the answer is yes and the gap remains, have the conversation.