Guide

Skill problem or motivation problem? How to tell the difference

From the outside, three very different problems produce the same picture: the work is late, the quality is uneven, and people look disengaged. Treating the wrong one is how good teams get training they don't need and pep talks they resent.

The three look-alikes

• Skill — they would if they could, but they can't yet. Effort is visible; results are inconsistent.
• Will — they could, but won't. Capability shows up elsewhere, just not here.
• Means — nobody could, with the tools, time, access or information available. The task is impossible as configured.

Four questions that separate them

• Has anyone here done this well, ever? If yes, it is unlikely to be pure skill. If no one ever has, suspect means or skill.
• Do they do it well when someone senior is watching? If performance jumps under observation, it is not skill — it is will, grip or priority.
• What would happen if I did the task myself, today, with their tools? If you would also fail, it is means.
• What does the person say the obstacle is? People usually name the real obstacle accurately, and are usually not asked.

The fix depends entirely on the answer

• Skill — deliberate practice on the specific failing step, with feedback inside the work, not a generic course.
• Will — find what the current behaviour is protecting. Something is rewarding it, or something about doing it well is costly.
• Means — remove the impossibility. Access, tooling, time, or a smaller scope. Training here is an insult.

Applying the wrong remedy is not neutral — it teaches the team you don't understand the work, which makes the next diagnosis harder.

Check it in ten minutes

The free diagnostic on this site asks these questions systematically across skill, will and means (plus aim, sync, grip and loop), scores them the same way every time, and returns the top three constraints with concrete actions for each.