Most of the weak performers I have managed over the years were not weak when they started. They got there. And in more cases than I am comfortable admitting, I helped move them along.

That is an uncomfortable thing for a manager to say out loud, because the story we prefer is cleaner. The story we prefer is that some people are strong and some people are weak, and our job is to sort them, reward the first group, and manage the second group out. What that story leaves out is the part we play in deciding who lands in which group, and how our own behavior after we decide quietly makes the sorting come true.

Two professors at IMD, Jean-François Manzoni and Jean-Louis Barsoux, gave this pattern a name in a 1998 Harvard Business Review article called “The Set-Up-to-Fail Syndrome.” Their research with hundreds of executives pointed at a conclusion most of us would rather not sit with: bosses themselves, accidentally and with the best intentions, are often the ones who cause a capable employee’s sub-par performance. Not by being cruel. By being logical.

How a good manager builds a poor performer

The cycle almost never starts with a villain. It starts with something small and real. A missed deadline. A report that came back thinner than you expected. A meeting where someone fumbled a question in front of your boss. Nothing that would end a career on its own. But it plants a seed, and the seed is a quiet downgrade in how you rate that person.

Once that downgrade happens, everything you do next is reasonable on its own terms and disastrous in aggregate. You start checking their work more closely, because you are not sure it will be right. You ask for more frequent updates, because you want to catch problems early. You give them the smaller, safer assignments, because the big visible ones feel too risky in their hands. Each of these is a defensible management decision. Together they send one unmistakable message to the person on the receiving end: I do not trust you.

And here is the part that makes it a syndrome rather than a bad week. The employee reads that message and responds exactly the way a reasonable person would. They get cautious. They stop volunteering ideas, because ideas from someone under suspicion get picked apart. They run more decisions past you, which you experience as neediness and further proof they cannot operate on their own. They disengage a little, protect themselves a little, and their performance narrows to the small safe box you have built around them. You watch that happen and think: I was right. Manzoni and Barsoux describe the closing of that loop precisely. The employee lives down to the low expectations, and the manager reads the result as confirmation of the original judgment.

The frustrating truth is that this whole machine runs on good intentions and sound-looking logic. Nobody in it is acting in bad faith. That is why it is so hard to see from the inside.

What it looked like when I was the one doing it

I ran network operations for a large telecom for a chunk of my career, and one of the sharper lessons I learned there had nothing to do with networks. It was about an engineer I had written off too early.

He came onto my team after a reorganization, and within his first month he mishandled a change during a maintenance window. Not a catastrophe, but it created cleanup work and it happened in front of people I answered to. From that night forward, I managed him differently, and I did not notice I was doing it. I reviewed his change plans line by line when I skimmed everyone else’s. I kept him off the high-visibility cutover work. When he proposed an approach in a planning meeting, I would “just double-check” it in a way I never did for the engineers I trusted.

He got quieter over the following months. He stopped bringing me ideas. He asked permission for things he was entirely capable of deciding himself, which irritated me, because I read it as a lack of initiative rather than as the exact behavior my own scrutiny had trained into him. I had a story in my head that he was a mediocre engineer, and every week supplied me with evidence, because I had arranged the conditions that produced the evidence.

What broke the pattern was luck, not wisdom. He got pulled onto a cross-team project I was not running, under a manager who had no history with him and no downgraded opinion to protect. Six weeks later that manager mentioned, offhand, how sharp this engineer was and how much good thinking he brought to the design. I remember the specific discomfort of that moment, because there were only two explanations. Either the other manager was wrong, or I was. It was me. The engineer had not changed. The person managing him had.

The tell: you are running two different playbooks

The reason this is so hard to catch is that it never feels like bias. It feels like calibration. You genuinely believe you are giving each person the level of oversight their track record has earned. What you cannot see from inside your own head is that you are running two entirely different management playbooks, one for the people you have decided are strong and one for the people you have decided are weak, and the second playbook is manufacturing the very results that justify it.

There is a well-documented flip side to this, which is the encouraging part. J. Sterling Livingston laid it out in another HBR classic, “Pygmalion in Management,” drawing on studies across military, industrial, and business settings: people tend to rise or fall to the level their manager believes them capable of reaching. High expectations, communicated through how you actually behave rather than through a pep talk, pull performance up. Low expectations push it down. Your read on someone is not a passive observation. It is an input to their results.

The behaviors that carry the low read are the same ones employees flag as intolerable. In a Monster survey reported by HR Dive, nearly three out of four workers named micromanagement the single biggest red flag about a workplace, and 46% said they would quit a job over it. The tighter you grip the person you have already downgraded, the faster you push them toward the exit, and then you tell yourself the departure proves your judgment. It does not. It closes the loop.

A few honest questions surface the pattern faster than any personality assessment:

• Is there someone on my team whose ideas I instinctively double-check before I take them seriously?
• Who do I give the safe, low-visibility work to, and is that still based on evidence or on a first impression I never revisited?
• When this person succeeds, do I credit them, or do I explain it away as luck or an easy task?

That last one is the sharpest. When you catch yourself discounting a person’s wins while banking their misses as proof, you are not evaluating them anymore. You are defending a verdict.

Reversing it is harder than never starting it

Prevention is cheap. When someone new joins your team, or someone stumbles once, resist the downgrade. Give a specific piece of feedback about the specific miss, then keep the reins where they were. One bad maintenance window is data about one night, not a verdict on a career.

Once the cycle is running, though, you cannot fix it silently by just being nicer, because the employee has learned not to trust the warmth. Manzoni and Barsoux are clear that reversal requires an actual conversation, and it is an awkward one, because it means naming the dynamic out loud. Something close to: “I think I have been managing you more tightly than the situation calls for, and I suspect that has made it harder for you to do your best work. I want to reset that. Here is what I am going to stop doing, and here is what I would like to see us do differently.”

That conversation costs you something. You have to admit, at least partly, that the problem was not entirely them. Most managers would rather manage the person out than say that sentence, which is exactly why the syndrome is so common and so expensive. It quietly burns capable people, and it teaches everyone else on the team a lesson you did not mean to teach: that one bad week here can put you in a box you will never climb out of. That lesson does more damage to your credibility than the original mistake ever did. This is the same mechanism I have written about in how your team mirrors your worst habits, and it is a big part of why good people leave managers they could have thrived under.

The engineer I nearly wrote off ended up leading design work on projects I would not have trusted him with a year earlier. Nothing about his ability changed in that year. What changed was that someone expected more of him, and I got a second chance to be that someone. Most managers do not get the luck I got, the outside manager who accidentally showed me my own blind spot. You have to go looking for it on purpose. Start by picking the one person on your team you have quietly filed under “weak,” and ask yourself honestly whether you are describing them or describing what you have built.