A skill will matrix can become unhelpful when managers use it as a fixed label for people rather than a prompt for coaching. Workforce management gets better when we treat the grid as a task-by-task diagnostic that we revisit with the employee.
How the grid is supposed to work
The skill will matrix plots skill on one axis and will on the other for one task at a time. High skill with high will calls for a Delegate approach with real autonomy. High skill with low will calls for an Excite approach that rebuilds connection and clears blocks. Low skill with high will calls for a Guide approach with close direction and encouragement, while low skill with low will calls for a Direct approach with clear steps and tight follow up.
This is not a personality test. Treat its categories as prompts to adapt support to the task, not as diagnoses or a fixed formula for managing a person. Used well, the grid shapes delegation strategy and feeds straight into an employee development plan with one or two agreed actions.
Skill depends on the task. A technician can be expert at routine service and a beginner at fault finding on a new system, and will can be high on Monday and flat by Friday after a tough shift pattern. The rating belongs to the task at hand.
That distinction matters whenever we use the grid.
Treating will as a fixed trait
One damaging error is treating will as character. A manager decides Sam is unmotivated and plots him in low will for everything, then stops looking for reasons. Will is a state, not a trait. It moves with workload and home life and with whether the work still feels worth doing.
Consider a hypothetical example involving Sam. He was keen on breakdown calls until rota changes cut his autonomy and left him covering nights he didn’t choose. His skill hadn’t dropped, but his energy had, because the drivers of engagement had shifted. A manager who labels him as low will misses the point and won’t fix the rota issue that sits behind it.
The fix is a regular conversation. Don’t plot will from memory. Ask what helps and what gets in the way right now, and listen for purpose and control rather than attitude. Revisit the rating each month or when the work changes, because a grid from last quarter can’t tell you how Sam feels this week.
Autonomy and purpose are useful topics to explore, alongside confidence, workload, equipment and unclear expectations. No single explanation will fit everyone. Ask what would help this person with this task, then agree a practical change and review whether it helped.
Rating without evidence
Managers often rate on gut feel. They mark someone low skill after one rough week or high will because the person is cheerful in meetings. Recency bias and halo effect creep in fast when there’s no agreed standard. Without evidence, the grid reflects mood more than reality, and staff can tell.
The answer is to use evidence. Tie skill ratings to a competency framework that spells out what good looks like for that task, then note one or two observed examples that support the call. A skill gap analysis should separate a need for training from a lack of observation, so we don’t penalise someone who can do the work but hasn’t been seen doing it yet.
Motivation guesses need the same care. A late finish doesn’t prove low will and a smile doesn’t prove high will, so keep the two axes apart in your notes. Record what the person did for skill and what they said about blocks for will. That split stops us reading attitude into every slip.
In another hypothetical example, Aisha is quiet on site and new to the team. She says little in toolbox talks, so her manager assumes low skill and keeps her on basic duties. In fact she did similar fault work for two years elsewhere and only lacks confidence in new procedures. Equating volume with ability keeps good people stuck and it can shade into unfair assumptions about age or background if we aren’t careful.
There’s a practical test here. If you can’t name what you saw and when you saw it, don’t plot it yet. Go and watch the work first.
Skipping calibration and keeping ratings private
Even with evidence, ratings drift between managers. One manager’s moderate will is another’s high will, and one team’s high skill would be average elsewhere. Without shared definitions the grid can’t be used to compare teams or plan cover. Calibration sessions help managers agree on those differences without becoming a lengthy exercise.
Bring managers together to discuss a fictional or appropriately anonymised example. Agree what evidence supports a skill judgement and which questions would help explore barriers. Do not create a checklist that treats quietness, absence or limited overtime availability as proof of low will. Record the agreed task criteria and prompts for conversation so the next discussion is fairer.
The other half of this mistake is keeping the grid in a drawer. Staff trust drops when they are plotted in secret and only hear about it at review time. Ratings should be discussed in a regular one-on-one where the employee adds their own view on barriers and support needs, and once that shared view is agreed the next move is to get clear on how to use a skill will matrix step by step for daily decisions.
That chat often surfaces what the grid alone won’t show. Childcare clashes and unclear instructions can both look like low will from a distance. Asking directly gives you a chance to understand the cause and find a practical fix.
Matching the wrong fix to the quadrant
This is where time gets wasted. A low will issue gets sent to training, so a skilled engineer sits through basics she already knows and comes back even flatter. A low skill issue gets a pep talk, so a keen newcomer leaves motivated and still unable to do the job safely. Each quadrant needs its own response. Training builds skill while guided support rebuilds will, and mixing them up helps no one.
High will with low skill needs coaching on the job with clear demos and fast feedback. Low will with high skill needs a different move, with space to talk through blocks and agree changes to scope or rota. Mentoring fits later, once basic competence is steady and the question is growth rather than readiness. Delegation follows the same logic, with tight checks for new skills and looser rein where skill and will are both proven.
Take Marco, who is strong on installs but keeps missing paperwork deadlines. Sending him on a forms course won’t help if the real issue is that he doesn’t see the point and never got a simple template. Give him the template and show how it avoids rework. Review progress in two weeks. That support addresses the specific problem behind his rating.
Plot the task, then match the help to the box. That habit stops us throwing training at motivation dips and chats at skill gaps.
Using the grid as a verdict for pay or discipline
A grid should never decide pay. It is a coaching aid, not a scorecard for salary moves and formal reviews. When ratings feed straight into those calls, staff hide struggles and managers inflate scores to avoid tough talks. Both sides lose the honest view that makes development work.
The same line holds for safety and discipline. A high skill tick on the matrix is not proof someone can run a press or isolate electrics unsupervised. Those calls need formal sign off against set standards with observed proof and records. The grid can prompt a training need, but it can’t grant permission. Keep those two systems apart.
The low skill with low will box gets misused most. It’s easy to write someone off there and move to warnings. Everyone in that box still needs support. Treat every plot as a next step, not a verdict, with a short development plan that names support and a check date. Even a difficult case needs a clear task and close follow up before any formal route is considered.
Suppose Jon misses two call outs after a bereavement. Plotting him low will and pushing straight to a formal warning skips support and stores up resentment. A short plan with adjusted cover and a weekly check gives him room to recover while standards stay clear. Discipline stays as a last resort, not a first response to a low plot.
Labels stick. Once a name sits in a low box for months without review, later decisions get shaded by that old view.
Letting the grid go stale
Skill and will don’t sit still. A new supervisor and a change in shifts can lift one person and knock another in the same month. An annual grid can’t keep up with that pace. A change in engagement is worth exploring without assuming it predicts resignation. An early conversation can identify a practical barrier before it becomes a longer-running problem.
Set a manageable rhythm. Review task ratings each quarter or when goals change, and keep the note to two lines per person with an agreed action. That steady loop matters more than perfect scores. In its 2015 analysis, Gallup estimated that managers account for at least 70% of the variance in employee engagement scores across business units. Getting the conversation right takes more attention than simply keeping a neat chart up to date.
Two apparent performance problems can have very different causes. In a hypothetical comparison, Lena cannot accept additional night cover because of care duties, while Tom is unsure how to improve because he has not received useful feedback. Neither circumstance establishes low willingness. They need different conversations and practical support. The grid should prompt questions, not turn availability or missing guidance into a judgement of character.
Ask what sits behind the mark before you choose support. That question keeps the tool fair and keeps trust intact across the team. Small fixes beat big speeches.
The grid works when we hold it lightly and use it often. Rate the task with evidence and agree the rating face to face, then match help to the box and come back soon. Do that well and the matrix becomes a practical way to support people’s development. That’s what good workforce management looks like in practice.