What HR Gets Wrong About "Performance Issues" That Are Actually Executive Function Gaps

There's a moment almost every HR professional has lived through. A manager comes to you frustrated about an employee who is clearly talented — smart, capable, well-liked — but keeps missing deadlines, forgetting steps, or seeming disorganized in ways that don't match their potential. The conversation usually starts the same way: "I don't get it. They're so smart. Why can't they just get it together?"

So HR does what HR is trained to do.

A performance improvement plan gets drafted. Expectations get restated, maybe in writing this time, maybe with a little more urgency. Everyone agrees the employee needs to "take more ownership" or "be more proactive." And then, a few months later, the same pattern shows up again, sometimes with the same employee, sometimes with a completely different one who looks nothing like them on paper.

Here's what's usually missing from that conversation: not every performance problem is a motivation problem. A lot of what gets labeled as poor performance is actually an executive function gap — and those two things require completely different fixes.

Motivation and capacity are not the same thing

Executive function is the mental infrastructure behind getting things done: planning a project, holding multiple priorities at once, starting a task that isn't urgent yet, switching gears when something changes, managing the emotional noise that comes with a heavy workload. When that infrastructure is under strain, you get exactly the symptoms HR sees in a performance review — missed deadlines, dropped details, follow-through that doesn't match the person's obvious intelligence or effort.

The problem is that a PIP is built to fix a will problem. It assumes the employee knows what to do and simply isn't choosing to do it. But if the real issue is capacity, not choice, a PIP doesn't just fail to help — it can make things worse. Now the employee is trying to execute under the exact conditions (stress, scrutiny, added pressure) that make executive function struggles more pronounced, not less.

Why this keeps slipping past HR

Most performance frameworks were built around behavior and attitude, not cognition. HR is trained to spot disengagement, entitlement, and poor communication. They're rarely trained to ask a different kind of question: is this person struggling with how their brain organizes and executes work, independent of how much they care about the job?

That question matters because the employees this happens to are often your highest performers on paper. They interview well, and they can describe exactly what they should be doing. That's actually part of what confuses everyone; if they can explain the plan so clearly, why can't they follow it? That gap between insight and execution is one of the clearest signs of an executive function issue, not an effort issue.

What this looks like in practice

A few patterns worth training managers to notice, before a formal performance process starts:

• The employee can tell you exactly what they should have done, right after they didn't do it

• The struggle shows up consistently across very different projects and managers, not just one relationship

• Performance dips sharply during high-complexity, high-pressure stretches, and improves when things calm down

• Small logistical pieces (scheduling, follow-up emails, task sequencing) fall apart even though the big-picture thinking is strong

None of that means the employee gets a pass on accountability. It means the intervention needs to match the actual problem. Coaching around executive function looks different from coaching around motivation, and building that distinction into how HR evaluates "performance issues" changes both the outcome for the employee and the liability exposure for the company.

If your org is still treating every performance concern as a character or effort issue, you're probably losing good people to a problem that was fixable from the start.

How many performance improvement plans has your organization run in the last year, and how many of them actually worked?

If the honest answer is "not many," the process might be solving the wrong problem. Let’s talk about what a more accurate one could look like.