Why Good Employees Underperform: Sorting the Person From the System

"He was excellent for three years. Something has changed in him."

You have said a version of that sentence about one specific person. A plant head, a key account manager, the finance controller who used to catch things before you saw them. The work still arrives. It arrives later, thinner, with the interesting part missing. You have quietly started checking their output again, which you had stopped doing years ago, and both of you know it.

And you already have an explanation. There are only two on offer, and most promoters settle on one of them within a week.

• He has become comfortable. The hunger has gone.
• He is planning to leave, and this is what the last four months look like.

Both explanations put the cause inside the person. That is what makes them expensive. Both lead to the same conversation — a calm, disappointed one about attitude and commitment — and that conversation reliably makes things worse, because if the cause was not inside the person, you have just told a constrained employee that his standing with you has dropped for reasons he cannot control.

The claim here is narrow. Five different constraints produce underperformance that looks identical from your chair. Output down, initiative down, escalations up, energy flat. Only one of the five is about the person, and in someone who was genuinely good before it is the rarest. The other four are installed by the company, usually in the previous eighteen months, usually by growth rather than by anyone's decision.

Sorting matters more than fixing. Acting on the wrong constraint is how a company loses a person it wanted to keep — slowly, over two quarters, with everyone watching.

Why the pages above this one don't help

Search this and you get AIHR, Personio, Glassdoor, Forbes and American Express, all answering a different question: what process to follow once someone has already been classified as an underperformer. Improvement plans, documentation, scripts, escalation to exit. Useful to an HR department handed a case. Useless to you, because you are not at the case stage — you are at the stage where a person you rate is not performing, and the whole question is whether this is a person problem at all.

It sits under a larger pattern — see employees not taking ownership for the five conditions ownership needs. This article is the individual case.

The Constraint Sort

Five constraints. Each has a test you can run without announcing anything. Run them in order — the earlier ones are cheaper to check, the later ones are more likely to be true.

Capability — they cannot do it

The person lacks the skill the job now needs. Not the skill it needed when they were good at it. The one it needs now.

The test: could they do this task with two hours of help from someone who can already do it? If yes, it is not capability. It is a missing input — a template, a method, one worked example — and two hours closes it. Real capability gaps survive the two hours, and the second two hours as well.

This is the only constraint on the list genuinely about the person, and in someone with a track record it is the rarest — they demonstrably had the capability before. When it does appear, it is almost never that the person got worse. It is that the job quietly became a different job: more people, more scale, less doing. A real gap, but one the company created, and it has its own section below.

Clarity — the standard moved and nobody told them

The role grew. The definition of good did not.

The test: ask them what a good quarter looks like in their role. Write down their answer before you give yours, then compare. If the two differ in substance — not wording, substance — you have found your constraint, and you found it in eleven minutes.

Gallup's India performance-management work found the sharpest correlation in this field: among employees clear about the criteria their performance was judged on, 66% were engaged. Among those who were not clear, 1% were. Sixty-six against one. Gallup also found that 56% of employees formally review goals with their manager once a year or less — roughly the frequency at which a fast-growing Indian business changes what it actually wants.

The shape this takes in a promoter-led firm is specific. The KRA sheet was written when the company was doing ₹18 crore. It is now doing ₹55 crore, the customer mix has changed, and the sheet has not. The person is still hitting the sheet. You are judging them against a standard that moved when the business moved and that you have never said out loud in one sitting. From where they sit, the target did not get harder. It became invisible.

Capacity — they are doing three jobs

Good people accumulate work as a punishment for competence. Anything with no obvious owner ends up with the person who does not drop things: the audit, the ERP rollout, the new location's hiring, the client who shouts.

The test: list everything they actually do. Not their JD — the real list, built by asking them to describe last week hour by hour. Most promoters are surprised by it, because they added to the list one item at a time, months apart, each addition reasonable on its own.

The signature of a capacity constraint is that the core job degrades first. The added work has visible deadlines and visible askers. The core job has neither, so it absorbs the shortfall. From your side that reads as "he has gone off his main responsibility", which sounds exactly like complacency and is its precise opposite.

Authority — the job needs decisions they are not allowed to make

This is the most common cause in a growing Indian business and the most consistently misdiagnosed, because from the outside it looks like slowness, indecision or lack of drive.

The test: take the last three things this person escalated to you. For each, ask whether the escalation could have been avoided by a written rule — a discount band, a spend limit, a hiring threshold, a credit-period range. If the answer is yes for two of the three, the person is not underperforming. They are waiting, correctly, inside a system that requires them to wait.

The sales head who owns the number but cannot approve a discount does not own the number. The operations head who cannot spend ₹80,000 without your signature cannot fix an ₹80,000 problem on Tuesday. The second-order effect is worse than the delay: a person who must ask permission on the substance of their job eventually stops proposing things, because each proposal is another chance to be overruled in front of someone.

We have taken this apart in the decision bottleneck, on writing decision rights down, and in why your team waits to be told, on how the waiting habit gets installed.

Consequence — nothing happened last time they went beyond the role

Somewhere in the last eighteen months this person did something excellent that nobody asked for. And somewhere in the same period, they got something wrong.

The test: what happened after their best piece of work last year? If the honest answer is "more work", you have your cause. Then ask what happened after their worst mistake. If that answer is sharper, faster and more personal, you have the full picture: the upside of stretching is more workload, and the downside of a mistake is standing. Against that arithmetic, doing exactly the defined job is not laziness. It is the correct strategy, and a smart person finds it faster than a mediocre one.

Gallup's India study measured this directly. Among employees who strongly disagreed that good performers were rewarded significantly better, 41% were actively disengaged. Among those who strongly agreed, 3% were. Gallup's 2023 work found only 22% of employees strongly agree their review process is fair and transparent, with roughly one in five saying reviews inspire better work.

This sits alongside the accountability gap — consequence that runs in one direction does not produce accountability, it produces caution.

The promotion trap

One version of this is so common in the Indian mid-market that it deserves naming separately, because it manufactures all five constraints at once.

Your best individual contributor is made a manager. Not because anyone assessed them as a manager, and often not because the business needed one. It happened because the pay band for their role had a ceiling, they had reached it, a competitor was circling, and the only mechanism the company had for paying them more was a title with people under it.

So the best salesman becomes sales manager. Six months later he is judged a failure at a job nobody trained him for, against criteria nobody wrote down, with authority nobody actually transferred, while still personally carrying the hardest accounts because he is the only one who can.

Read that against the sort. Capability: real, because managing is a different skill. Clarity: absent, because the standard for the new role was never defined. Capacity: broken, because they kept the old job. Authority: missing, because their reports still escalate past them to you. Consequence: perverse, because their reward for being outstanding was a role they are now failing at publicly.

This is a pay-band problem wearing an org-chart costume. If the only route to a higher salary runs through people management, you will keep converting your best operators into your weakest managers and keep concluding that they changed. The structural fix is a senior individual-contributor track with real money attached — a principal engineer, a key-accounts director with no reports — so that pay and headcount stop being the same lever. That is a compensation design decision, not a performance conversation.

The layer-wide version is in why middle management fails. If the person came in from outside at senior level instead of being promoted, the failure mode differs again — see why executive hires fail.

When it actually is the person

An article claiming the system is always at fault is not worth reading. Sometimes it is the person. Here is how to tell.

• The two-hour test fails twice. Real help, from someone competent, applied properly, and the work still comes back wrong. That is capability, and no amount of clarity fixes it.
• All four system constraints come up clean and the behaviour persists. You state the standard, they state the same standard, their workload is defensible, they have the authority the role needs, and their last good piece of work was recognised. If that is all true across two quarters, stop looking at the system.
• It travels with them. The same pattern showed up in their previous role, under a different manager, on different work. Constraints are local. Person problems move.
• They cannot name a constraint when asked directly. Ask plainly: what is stopping you doing this the way you did it two years ago? Someone inside a system constraint answers instantly and specifically, and is relieved to be asked. Someone who has checked out answers generally, about the market or the industry.

There is also the case you will not enjoy: something outside work — a parent's illness, a marriage, a financial hole — where the honest response is time and privacy rather than diagnosis. Ask once, without a notebook.

When it is the person, say so early and plainly. The failure mode here is not harshness. It is a long, polite, ambiguous decline in which someone is quietly stripped of scope over eighteen months and never told why. Everybody watching learns from that, and what they learn is that performance and consequence are unrelated here.

Running the sort this week

Pick the person you are most worried about. Take forty-five minutes alone first and write down, from memory: what a good quarter looks like in their role in numbers, everything they actually did last month, their last three escalations, and what followed their best piece of work last year. Four of the five tests are now answered from your side, before you have spoken to anyone.

Then thirty minutes with them, framed as a role conversation rather than a performance one, because it is one. Ask the same questions of them. Do not give feedback in that meeting — the moment you do, the information stops. The constraint is almost always visible in the gap between the two sets of answers.

Where to start

Do not have the attitude conversation this week. It is the one action that is hard to reverse, and the one you are most tempted to take.

Run the sort first. If it returns clarity, authority, capacity or consequence, you have a design problem with a name, and the person you were about to write off is the same person who was excellent three years ago.

If you want to see where this pattern sits across the whole company rather than one person — a constraint that caught your best operator has almost certainly caught others more quietly — the Business Pulse diagnostic maps where decisions and standards actually live in your organisation, as against where the org chart says they do.