Why Eager Beginners and Capable Drifters Need Completely Different Management Approaches
In most service businesses, coaching problems rarely show up as abstract talent questions. They show up on the service board, in escalations, in missed documentation, in shaky client calls, in uneven project handoffs, and in the quiet frustration of managers who know a team member could be better but are not sure what kind of help that person actually needs.
One technician is eager, loyal, responsive, and hardworking, but keeps making avoidable mistakes. Another can solve complex issues faster than anyone else on the team, yet drifts, resists process, dismisses feedback, or only performs when the work interests them.
Both people need management. Both people need development. But they do not need the same kind of coaching.
Coaching Only Works When the Employee Is Willing to Engage
That distinction matters because coaching only works when the employee is willing to engage with it.
Coaching is a partnership built around questions that help people discover their own answers, develop critical thinking, and take ownership of results. It also makes an important point that many leaders learn the hard way: you can require someone to attend a meeting, but you cannot force them to think critically, try new techniques, or persevere through failure.
In other words, coaching is not just a manager activity. It is a shared commitment. That insight gives us a useful starting point for managing two very common profiles.
Two Common Profiles That Need Different Approaches
The first is the high-will, low-skill team member. This person wants to win. They care. They usually respond well to feedback, often show loyalty, and tend to take responsibility even when they are still learning. Their main problem is not attitude. It is capability, consistency, exposure, or judgment.
The second is the high-skill, low-will team member. This person often has the technical brain, experience, and raw capability to perform at a high level, but their motivation is unreliable. They may be bored, cynical, poorly aligned to the role, resistant to accountability, or simply unwilling to do the unglamorous parts of the job well. Their problem is not mostly skill. It is energy, ownership, purpose, or fit.
The Mistake Most Managers Make
Leaders often make the same mistake with both groups: they coach each one as though the issue were identical.
They give more encouragement to the high-will, low-skill employee when what is really needed is structure, repetition, and supervised practice. Or they give more training to the high-skill, low-will employee when what is really needed is clarity, consequences, shared goals, and an honest conversation about whether the role still fits.
The result is predictable. The willing beginner feels supported but does not get better fast enough. The capable drifter gets more tools but stays disengaged.
Separate Willingness Problems From Capability Problems
A better way to manage this is to separate willingness problems from capability problems before you decide on the intervention…prepare for coaching by identifying the actual performance issues, skill gaps, or development goals involved, then begin sessions by asking the employee to take the lead, surface their own agenda, and help define a shared goal for the partnership.
That advice is especially relevant in service businesses, because operational noise makes it easy to treat every problem as urgent and visible rather than causal and diagnostic.
Coaching the High-Will, Low-Skill Employee
For the high-will, low-skill employee, the right coaching posture is developmental and structured.
This is the junior technician who is hungry but green, the project coordinator who wants to do well but lacks judgment under pressure, or the account manager who cares about clients but does not yet know how to navigate difficult commercial conversations.
What they need is not vague encouragement. They need a staircase. They need clearer expectations, narrower performance targets, shorter feedback loops, and repeated practice in the real environment where the work happens.
Think about the performance of your players in terms of interest, practice, purpose, and hope. High-will, low-skill employees already tend to have hope and at least some level of interest. What they often lack is disciplined practice aimed at weakness.
Growth is not just a matter of passion. It also requires challenge-exceeding-skill practice, repeated over time, in service of real improvement.
In practical terms, that means you as the manager should not merely say, “Keep at it.” Rather, define what better looks like this week. Better ticket notes. Better time entries. Better root-cause documentation. Better client handoff summaries. Better follow-up discipline. Better escalation judgment.
Build Systems Around Willing Learners
Habit formation also plays a role here. Improvement is usually the product of systems, not bursts of motivation. People do not rise to the level of goals as much as they fall to the level of their systems.
In practical management terms, the high-will, low-skill employee improves faster when you install a system around them: standard operating checklists, templated note structures, shadowing routines, scheduled quality review, weekly skills targets, and measured stretch assignments.
Their will is an asset, but it only compounds when converted into repeatable habits.
Coaching the High-Skill, Low-Will Employee
The high-skill, low-will employee requires a different approach. This person does not need a staircase as much as a mirror.
They may already know how to do the job. What they need is to confront the gap between their capability and their contribution.
This is where many managers get tentative, because high-skill people can be intimidating. They are often the ones who rescue escalations, carry historical knowledge, or solve the problems others cannot.
Your strategy for giving effective feedback is clear: talk about behaviors rather than motivations, elicit the employee’s perspective, probe for the root cause of the performance gap, and close by defining next steps and future expectations.
“Low Will” Is a Symptom, Not a Diagnosis
That matters because “low will” is not a diagnosis. It is a visible symptom.
Sometimes the root cause is boredom. Sometimes it is burnout. Sometimes it is misalignment between strengths and role demands. Sometimes it is a lack of challenge. Sometimes it is a silent conflict of values. Sometimes it is entitlement. And sometimes it is simply that the employee has learned the organization tolerates selective effort.
If you never identify which of those is true, you will end up treating disengagement as though it were a training gap.
Reconnect Skill to Purpose
Research on sustained performance helps again here, but in a different way. Sustained effort depends not only on interest but also on purpose. People remain engaged longer when they experience their work as personally meaningful and connected to the well-being of others.
That is a useful lens because some high-skill, low-will employees are not lazy so much as disconnected. They no longer see their work as meaningful.
They are solving tickets, not protecting client operations. They are patching devices, not preserving uptime and trust. They are documenting changes, not reducing future failure for teammates and clients.
A manager who can reconnect skill to purpose may recover part of the will problem.
Some Will Problems Are Discipline Problems
But, not all will problems are purpose problems. Some are discipline problems.
Behavior is heavily influenced by systems and environment, not just by intention. Desire initiates action, but feelings of success and repeatability sustain it.
In practical terms, if your most capable technician gets rewarded for heroics and never for process discipline, you will get more heroics and less discipline. If documentation is optional until something breaks, the team learns that knowledge hoarding has no real cost. If standards are unevenly enforced for “top performers,” then low-will behavior becomes rational.
This means that coaching the high-skill, low-will employee is not just about conversation. It is about redesigning reinforcement – what gets praised, measured, tolerated, and repeated.
Two Different Systems for Two Different Problems
This leads to a more useful practical distinction. High-will, low-skill employees need confidence-building systems. High-skill, low-will employees need accountability-building systems.
The first group needs support without ambiguity. The second needs clarity without indulgence.
For the first group, managers should slow the work down enough for learning to occur. That means smaller skill targets, observable behaviors, immediate feedback, and visible wins.
The coaching conversation should sound like this: here is the capability gap, here is why it matters to the client and the team, here is the exact behavior to practice, here is how we will review it, and here is what success looks like in the next two weeks. The tone should be firm but optimistic. The employee’s willingness is not the thing to test. It is the thing to harness.
For the second group, managers should make contribution visible and choice explicit.
The conversation should sound more like this: you clearly have the ability to perform at a high level, but these repeated behaviors are below the standard, here is the impact on the team and clients, help me understand the cause, and let’s decide whether you are willing to recommit to the role at the level it requires.
That last part matters. Coaching works when the employee genuinely wants to improve. If that willingness is absent, the manager may no longer be coaching. They may be managing performance, redesigning role fit, or preparing for a talent decision.
Be More Diagnostic, Not Softer or Harsher
What service companies need, then, is not a softer coaching culture or a harsher one. They need a more diagnostic one.
The manager’s first job is to determine whether the employee’s biggest gap is capability or commitment. The second job is to match the intervention to that diagnosis. The third job is to build the system around it.
A good service manager knows that not every ticket belongs in the same queue. A password reset, a firewall outage, and a recurring backup failure may all be “tickets,” but they do not belong to the same response playbook.
Talent works the same way. A willing learner and a reluctant expert may both be “performance issues,” but they do not belong to the same coaching playbook.
If you coach them the same way, you will frustrate both. If you coach them differently, you give each one a fairer chance to become what they are capable of becoming.
And in a service business, where performance is cumulative and operational trust compounds slowly, that difference shows up everywhere: in client confidence, documentation quality, escalation load, leadership bench strength, and ultimately margin.
That is why the smartest managers stop asking, “How do I coach this person?” and start asking, “What is this person missing most right now: skill, or will?”
The answer to that question changes everything.
Five Frameworks for Coaching Different Profiles
The Skill-or-Will Diagnostic. Before coaching, determine whether the employee’s primary gap is capability or commitment. This prevents mismatched interventions and wasted effort.
Confidence-Building Systems for High-Will, Low-Skill Employees. Use structure, repetition, short feedback loops, and clear behavioral targets to convert motivation into capability.
Accountability-Building Systems for High-Skill, Low-Will Employees. Use behavioral clarity, root-cause conversations, visible standards, and consequence-aware management rather than defaulting to more training.
Purpose Recovery for Skilled but Disengaged Employees. Reconnect technical work to mission, client impact, and team value so motivation is linked to meaning, not just task execution.
The Coaching vs. Performance Management Boundary. Coaching is a partnership, not a loophole for avoiding hard decisions. When willingness is missing, managers may need to shift from development to performance accountability.