Someone on the team isn't meeting expectations. The reflexive read is usually about effort - they need to care more, try harder, focus better. That diagnosis is sometimes right and, more often than most managers assume, wrong - and treating an effort problem with a motivational push, when the real cause is something else entirely, doesn't just fail to fix it. It usually makes the person feel worse about a problem that was never actually about their effort.
Four causes, one identical symptom
A missed deadline, a piece of work that needed rework, a commitment that didn't happen - the visible symptom looks the same regardless of cause. The actual cause is usually one (or more) of four things:
Capability. The person doesn't yet have the skill or knowledge the task requires. This isn't a character issue - it's a training and development issue, and it's common when someone is newly promoted, newly assigned to unfamiliar work, or has been quietly stretched past what they've actually been taught.
Capacity. The person has the skill but not the bandwidth - too much on their plate, competing deadlines, or a workload that was never realistically sized for one person. This looks identical to low effort from the outside; the difference is that a capacity problem doesn't improve no matter how motivated the person is, because there simply isn't enough time.
Clarity. The expectation itself was never actually clear - what "done" looks like, what quality bar applies, who owns which piece, or by when. A surprising share of "performance problems" are really unstated-expectations problems: the person did what they believed was being asked, and it wasn't what was actually needed.
Motivation. The person has the skill, the time, and a clear picture of what's expected, and still isn't doing it. This is the one situation where a motivational conversation - about engagement, priorities, or genuine disengagement - is actually the right tool. It's also, in practice, the least common of the four, despite being the default assumption.
How to actually tell them apart
Ask, directly and specifically, before assuming: "Walk me through what happened." The answer usually reveals which of the four is actually operating - someone describing a skill they've never been shown ("I wasn't sure how to structure that kind of analysis") points to capability; someone describing an overloaded week points to capacity; someone describing a task they approached differently than intended points to clarity; and someone who can't point to any external cause and simply didn't prioritize it points, more plausibly, to motivation.
A second, useful check: has this person succeeded at similar work before, under similar conditions? If yes, capability is unlikely to be the cause - something has changed instead, which usually means capacity, clarity, or a new motivation issue worth understanding.
Why the diagnosis matters more than the conversation itself
Each cause has a genuinely different fix. A capability gap needs training, pairing, or a smaller scope while the skill develops - not a stern conversation about trying harder. A capacity problem needs a real, honest conversation about tradeoffs (what gets deprioritized) - not encouragement to work more efficiently within an already-impossible load. A clarity problem needs the standard made explicit and, often, written down - not a consequence for missing a target that was never actually stated. Only a genuine motivation problem calls for the kind of direct conversation about engagement and consequences that "holding someone accountable" usually conjures.
Applying the motivation fix to a capability, capacity, or clarity problem doesn't just fail - it teaches the person that raising the real, structural cause won't change anything, which makes them less likely to surface it honestly next time.