Got a question about how to diagnose a performance issue, run a coaching conversation, or use the escalation ladder? Ask the training bot — it answers directly from this guide so you don't have to search through the whole document.
Diagnose why it's not getting done. Fix the right thing. Help your people succeed — or know when it's time to move on.
Before you fix anything, you need to figure out why someone isn't doing what you need them to do. This is the starting point for everything else.
Work through these in order, top to bottom. Don't skip ahead. The most common problems are at the top, and you'll waste time fixing the wrong thing if you jump to motivation before checking if they even understood the task.
You asked someone to send a follow-up email to a client. It didn't happen.
Check WHAT first: Did you say which client? What the email should say? Where to find the info? → If any of that was vague, it's a WHAT problem.
Check HOW: Have they ever written a client follow-up before? Do they know the tone you expect? → If not, it's a HOW problem. They need training, not a lecture.
Check WHEN: Did you say "by end of day" or just "when you get a chance"? → If there was no deadline, it's a WHEN problem.
Check WHY: Everything above was clear and they still didn't do it? Maybe they don't see why it matters. → Incentive problem.
Check BLOCKERS: Did they not have the client's email? Were they locked out of the CRM? → External obstacle.
Work the list top to bottom. Don't assume motivation is the problem.
Most managers jump straight to "they're not motivated" or "they don't care." In reality, the vast majority of performance issues come from the top of the list — unclear expectations or missing training. Start there.
You diagnosed it — they didn't know what you actually wanted. Here's how to communicate expectations so clearly there's zero room for confusion.
The less experienced someone is, the more specific your instructions need to be. What feels obvious to you is not obvious to them. Break the task down into concrete, observable actions — things you could literally watch them do.
Don't tell someone to "be more professional." Tell them exactly what that looks like: "When a client calls, answer within 3 rings, introduce yourself by first and last name, and recap their issue back to them before responding."
Verbal instructions evaporate. People forget. They remember differently. They fill in the blanks with assumptions. Every expectation that matters needs to be documented — in a message, an email, a shared doc, anywhere they can go back and reference it.
The habit: After any conversation where you assign something, follow up in writing. Even a quick message that says "just to confirm, here's what we agreed on" eliminates 80% of miscommunication.
Asking "does that make sense?" is useless. People say yes whether it makes sense or not. Instead, ask them to repeat back what they're going to do, in their own words. If their version matches yours, you're good. If it doesn't, you just caught a problem before it became one.
The phrase to use: "Walk me through what you're going to do first." This isn't a test — it's a safety net for both of you.
"Hey, can you follow up with that client?"
"Clean up the report before Friday."
"Be better about responding to people."
"Handle the onboarding stuff."
"Send John at Acme a follow-up email with the proposal PDF from the shared drive. By 3pm today."
"Fix typos on slides 4–8 and check revenue numbers against the spreadsheet. Send me the updated doc by Thursday noon."
"Reply to every client email within 4 hours. If you need more time, send a quick 'working on it' reply."
You don't give the same level of detail to a 5-year veteran and someone in their first month.
If someone keeps missing the mark, you're probably giving them instructions one level too broad for where they actually are. Go more specific, not more frustrated.
"Hey Sarah — I need a one-page summary of last month's client feedback. Pull the data from the survey results in the shared Google Drive folder called 'Q1 Feedback.' Use last month's template as a guide — same folder. Focus on the top 3 complaints and include one suggested fix for each. Send me the draft as a Google Doc by Wednesday at 5pm. Walk me through your approach real quick so I know we're on the same page."
This covers: what to do, where to find what they need, what format, what to focus on, when it's due, and a confirmation step. Nothing left to guess.
Clarity is kindness. Vague instructions set people up to fail.
If someone didn't do what you needed, the first question is always: "Did I actually make it clear?" Be honest with yourself. If there was any ambiguity, own it — and it's the easiest thing to fix going forward.
They understood the task. They just don't know how to do it yet. This isn't a discipline issue — it's a training issue. Here's the method.
This is the sequence. Every time you train someone on anything — a new task, a soft skill, a process — follow these three phases in order.
One of the biggest training mistakes: trying to teach the whole job at once. Instead, break skills into the smallest teachable pieces, then stack them.
If you can't describe it as a specific, observable action — it's not teachable yet.
"Be a better communicator" is not teachable. "When a client asks a question, pause for 2 seconds before answering, then repeat their question back before giving your response" — that's teachable. That's something you can demonstrate, watch them do, and give feedback on.
Every vague concept needs to be translated into concrete behaviors before you can train on it. This applies to "soft skills" just as much as technical ones.
Take the skill → list every sub-step involved → identify which sub-steps they can already do → train only on the ones they can't. Don't waste time re-teaching what they already know.
Example: "Handle a client complaint" breaks into: (1) listen without interrupting, (2) acknowledge their frustration, (3) restate the problem, (4) offer a specific next step, (5) follow up within 24 hours. Maybe they're fine at 1 and 2 but fall apart at 4. Train on step 4. Don't redo the whole thing.
You assumed they knew something they didn't. Always ask: "Have you done this specific thing before?" Not "are you familiar with" — that gets a yes every time.
You sent them a doc and expected them to figure it out. Documentation supports training — it doesn't replace it. They need to see it done live.
You showed them once and walked away. Without the duplication phase, you have no idea if they actually absorbed it. Observation is where you catch gaps.
You dumped 10 new things on them in one session. They retained maybe 2. Train one skill at a time, make sure it sticks, then move to the next one.
Document: Create a one-page checklist — call structure (greeting, agenda review, updates, next steps, close), what to have open on screen, how to log notes after. Put it in a shared folder.
Demonstrate: Run a real check-in call while they listen. After, walk through what you did and why — "I opened with the agenda because it keeps the call on track and shows respect for their time."
Duplicate: They run the next call while you listen in silently. Afterwards, give specific feedback — "Your greeting was great. On next steps, you were a little vague — try saying the exact date and deliverable instead of 'we'll get back to you soon.'" Repeat until they're solid.
If they can't do it, you haven't trained it — you've only explained it.
Telling someone how to do something is not training. Training is document → demonstrate → duplicate. All three. In order. Until they can do it on their own at the level you need. If you skipped a phase, go back and do it before getting frustrated.
They knew what to do. They know how to do it. But there was no deadline — so it sat on their list and never got done. Here's how to fix that permanently.
"Can you get that proposal done?"
"Sometime this week would be great."
"Whenever you have time."
"ASAP" — which means something different to everyone.
"I need the proposal by Wednesday at 5pm."
"Get me a draft by Tuesday noon, final by Thursday 3pm."
"Before your end of day today — what time do you plan to have it done by?"
"I need this in the next 2 hours. Can you do that, or do we need to move something else?"
This is a small habit that prevents huge problems. Before setting deadlines, ask them to estimate the time. Here's exactly how it goes:
What just happened: You got their buy-in on the timeline. You set a specific deadline. And you gave them a window to flag problems early instead of missing the deadline silently. All in 30 seconds.
It's going to happen. Here's how to handle it without becoming a micromanager or letting it slide.
Don't open with frustration. Open with curiosity. "Hey, the report was due at 5pm yesterday. What happened?" Then listen. The answer will usually point you back to one of the other 4 categories in the diagnostic:
"I didn't realize it was due yesterday" → It was actually a WHAT problem, not a WHEN problem. Go back to Step 2.
"I got stuck on the formatting" → It's a HOW problem. Go back to Step 3.
"Something else came up" → Either a prioritization issue (help them rank tasks) or a BLOCKER (Step 6).
"I just didn't get to it" → If the first 4 check out, it might be a motivation issue. That's Step 5.
"Marcus, I need you to update the pricing spreadsheet with this month's numbers. How long do you think it'll take?"
"Cool — so let's say by tomorrow at noon. Send me the updated file in Slack when it's done. If you run into any issues with the data, shoot me a message today before end of day so we're not scrambling tomorrow. Sound good?"
Deadline: specific. Check-in point: built in. Escalation path: clear. Confirmation: locked in.
No deadline = no priority. No priority = it doesn't get done.
Every single task you assign needs a specific day and time attached to it. If you find yourself saying "when you get a chance" — stop. Pick a time. You're not being demanding, you're being clear. Your team will actually prefer it because they'll stop guessing what's urgent.
They know what to do, how to do it, and when it's due. They're still not doing it — or not doing it well. The incentive is broken. Here's how to fix motivation without resorting to threats or pep talks.
Forget "motivating your team" in the abstract. Focus on one thing: reinforcing the specific behaviors you want to see more of. When someone does something right, make sure something good happens as a result. When they don't, make sure they feel the absence. That's the entire system.
But not all reinforcement is equal. There are 3 ways to make any reward hit harder:
The ideal recognition hits all three: it's unexpected, it comes fast, and it happens in front of others. That's the combination that makes people think "I want to do that again."
Not everyone is motivated by the same thing. Some people light up from public praise. Others cringe at it and would rather get a quiet bonus. Some want more responsibility. Others want more flexibility. You have to figure out what works for each individual.
This is a real conversation you should have with each person on your team. Keep it casual:
"Hey, I want to make sure I'm recognizing good work in a way that actually matters to you. When you've done something well at a job, what kind of recognition felt the best? Money? Public shout-out? More independence? What actually makes you want to keep going?"
Then write down what they say and actually use it. Most managers never ask this. The ones who do have a cheat code for motivation.
Common reinforcers: money/bonuses, public recognition, praise from their specific manager, more autonomy, more interesting projects, flexible schedule, title/promotion, learning opportunities. Don't assume — ask.
Only giving feedback when something goes wrong.
Saving all recognition for annual reviews.
Generic praise: "Good job, team."
Rewarding everyone the same regardless of performance.
Letting great work go completely unnoticed.
Catching someone doing something right and naming the specific behavior: "The way you handled that client pushback on the call — you stayed calm and offered a clear alternative. That's exactly what I need."
Recognizing effort within hours, not weeks.
Shouting out wins in team meetings or group chats.
Tying rewards to specific outcomes and behaviors.
When you need to realign someone's behavior — not just praise it — use this framework. It's direct, balanced, and gives them a clear picture of what to change.
"Hey David, wanted to give you some quick feedback."
Start: "Start sending a recap email after every client call. Even 2–3 bullet points. It keeps everyone aligned and the client feels taken care of."
Stop: "Stop waiting until Friday to flag problems with projects. If something's going sideways, I need to hear about it the same day so we can course-correct."
Keep: "Keep doing what you're doing on the proposal presentations. The last two were excellent — clean, clear, clients loved them. That's the standard."
You've confirmed they know WHAT, HOW, and WHEN — and there are no blockers. They're still not performing. Here's the honest conversation:
"I want to make sure we're on the same page. You know what the task is, you know how to do it, and you know when it's due. But it's consistently not getting done at the level I need. Help me understand what's going on."
Then listen. Really listen. The answer will be one of a few things:
They're burned out: They need support, a temporary load reduction, or a conversation about priorities. This is fixable.
They don't see how it connects to anything: They need context. Explain why this task matters to the team, the client, or the company. People work harder when they understand the impact.
The role is wrong for them: Sometimes a person is in the wrong seat. They're capable but disengaged because the work doesn't fit their strengths. Consider reassignment before giving up on them.
They've checked out: If none of the above applies and the effort just isn't there, that's a different conversation — one that involves clear expectations, a defined timeline for improvement, and consequences if nothing changes. That's the escalation ladder (covered separately).
People don't do things for your reasons. They do things for their reasons.
Your job is to find out what drives each person and connect the work to that. Reinforcement beats inspiration every time. Praise specific behaviors. Do it fast. Do it in front of others. And actually ask people what motivates them — then use it.
They want to do it. They know how. They have a deadline. But something external is in their way — and they can't remove it themselves. That's your job.
Most blockers fall into one of four categories. Knowing which type you're dealing with tells you exactly where to direct your energy.
Most people won't come to you and say "I have a blocker." They'll quietly try to work around it, get frustrated, and fall behind. You have to go looking for blockers proactively. Here's how:
When you've identified a blocker, here's how to handle it:
What happened: You identified the blocker (people dependency), took ownership of removing it, set a new deadline, and told them to flag future blockers immediately. Total time: 2 minutes. Impact: massive.
Your #1 job as a manager is to remove obstacles so your people can do their best work.
You're not there to hover. You're not there to do the work yourself. You're there to make sure the path is clear. Think of yourself as a blocker-removal machine. Every time you remove one, the whole team accelerates.
If you're spending most of your time doing tasks instead of clearing the way for others — you're in the wrong lane.
The biggest problem with blockers isn't that they're hard to fix — it's that you don't hear about them until it's too late. Here's how to change that:
Never punish someone for flagging a blocker. If someone tells you they're stuck and your response is frustration, they'll never tell you again. They'll just quietly fall behind. Instead, thank them for raising it early — "Good, I'm glad you told me now instead of Friday."
Make it a standing question. In every check-in, every standup, every 1-on-1 — ask: "Any blockers?" Make it so routine that it becomes the culture. It's not complaining. It's reporting.
Follow through fast. When someone flags a blocker, move on it quickly. If you say "I'll handle it" and nothing happens, you've taught them that raising blockers is pointless. The speed at which you remove blockers determines how often your team tells you about them.
You notice your sales rep's call numbers dropped this week. Instead of assuming it's a motivation issue, you ask: "Hey, I noticed your calls are down. Is anything getting in your way?"
They tell you the CRM has been running slow all week — it takes 30 seconds to load between each record, which adds up to over an hour of lost time per day.
You flag it to IT that afternoon. It gets fixed the next day. Calls bounce back immediately.
If you hadn't asked, you might have assumed they were slacking. The real answer was a 30-second loading screen.
If they want to do it and they can do it, but it's still not getting done — the environment is broken, not the person.
Blockers are the only category that is 100% your responsibility to fix. Your people can't fire a vendor, buy new software, or override another department. You can. Ask about blockers constantly, take ownership when you find them, and move fast. The speed at which you clear obstacles is the speed at which your team performs.
You now have the full diagnostic and the fix for every category. When something isn't getting done, work through these in order:
And if none of those are the issue → remove the BLOCKER.
Diagnose first. Fix the right thing. Don't skip steps.
Everything is trainable — but not everything is worth training. This is how you determine whether someone can't do the job or won't do the job. And why that distinction changes how fast you escalate.
You don't get to call it a will issue until you've eliminated everything else. This is a process of elimination — not a gut feeling. Run through this checklist honestly. If you can check every box, what's left is will.
If you can't check every box — it's not a will issue yet. Go back and fix the gap. But if all six are checked and the work still isn't getting done? You're looking at a will issue. They can do it. They've been taught. They've been coached. They're choosing not to.
Will issues have a specific pattern. Here are the behavioral signals that separate "can't" from "won't":
They do the work perfectly when they know they're being watched or when there's an immediate consequence — but the quality or consistency drops the moment oversight decreases. Their true standard is the one they hold when no one is looking.
They say "got it" every time. They nod in the coaching session. They agree to the expectation. Then nothing changes. The words are right but the behavior doesn't move. Repeatedly.
They've already proven they CAN do it — you've seen them do it well. But they don't do it consistently. The skill exists. The application is spotty. That gap between capability and output is will.
Every time you follow up, there's a new reason. The reasons change but the result stays the same. When someone is genuinely blocked, the reason is consistent. When they don't want to do it, the excuses shift because the real reason is never the one they're giving you.
They do just enough to not get in trouble, but never enough to actually excel. They're technically compliant but practically disengaged. The bare minimum is their ceiling, not their floor.
When you coach them, there's pushback — subtle or overt. They argue the process, question why it matters, or get defensive. Someone with a skill gap is usually grateful for coaching. Someone with a will issue treats coaching as an inconvenience.
Same symptom (the work isn't getting done), completely different cause:
They ask questions. They're trying to figure it out.
They're visibly frustrated with themselves when they miss.
Performance improves after coaching, even if slowly.
They accept feedback and try to apply it.
The miss is consistent — they fail at the same thing the same way, because they haven't learned it yet.
They do the work even when no one is watching — it's just not at the right level.
Response: More training. More patience. Run Document → Demonstrate → Duplicate again. Break the skill into smaller pieces. This person is worth investing in.
They don't ask questions. They already know how — they just don't care enough.
They're indifferent when they miss. No visible concern.
Performance doesn't change after coaching, or it spikes briefly then drops again.
They deflect feedback with excuses, justifications, or passive agreement with no action.
The miss is inconsistent — they do it right sometimes (proving they can), but not always.
They perform differently when being observed vs. when they're not.
Response: Direct conversation. Shorter runway. The escalation ladder moves faster because more training won't fix a motivation problem.
Once you've run the elimination checklist and you're seeing the will-issue signals, it's time for the direct conversation. This is not a coaching session — it's a clarity session. You're putting the truth on the table.
Then listen. Their answer will tell you everything. It will fall into one of three categories:
1. They reveal a hidden blocker or gap you missed. This is great — it means it wasn't a will issue after all. Fix the real problem and give them another shot. Go back to the diagnostic.
2. They're honest and tell you something real. Maybe they're burned out. Maybe they don't understand why it matters. Maybe the role isn't right for them. This is someone you can potentially still save — but only with a real plan and a tight timeline. Proceed through the escalation ladder normally.
3. They give you nothing — or give you the same empty agreement. "I know, I'll do better." No specifics. No explanation. No ownership. Just words to end the conversation. This is the strongest confirmation of a will issue. The behavior won't change because they haven't decided to change it.
In the normal escalation ladder, you go: Coaching → Re-Coaching → Written Warning → PIP → Termination. That full runway is designed for people who are trying and falling short. But a confirmed will issue compresses the timeline — because more coaching won't teach someone to care.
"Everything is trainable. It's just not everything's worth training."
You can train skills. You can train knowledge. You can even train soft skills by breaking them into specific, observable behaviors. But you cannot train someone to want to do the work. If the desire isn't there, no amount of coaching closes that gap — it just delays the inevitable and drains your team's energy in the process.
They did it right — consistently — and then stopped. This isn't a learning curve. They made a choice. When someone downgrades their own performance after proving they're capable, there's nothing left to train. Move directly from re-coaching to written warning. Skip the patience you'd give a skill issue.
With skill issues, coaching usually creates at least a short-term improvement. With will issues, the coaching session ends and nothing changes at all. If you've coached and re-coached with zero measurable movement, the normal re-coaching window can be shortened. Don't wait 2 weeks to confirm what's already clear.
If their lack of effort is creating real damage — dropped clients, teammates picking up their slack, missed revenue, broken trust — the cost of a slow escalation is too high. You still follow the steps (coaching, write-up, PIP), but you compress the timeline. Tighten deadlines. Shorten the PIP from 30 days to 2 weeks. The business can't absorb a month of someone who's checked out.
If someone is arguing against the standard, discouraging teammates from following the process, or showing visible contempt for coaching — that's no longer passive. That's active resistance. This poisons the culture around them and can undo the progress of people who ARE trying. Move through the ladder at maximum speed. Still document every step — but don't extend grace periods for someone who's working against you.
Faster doesn't mean skipping steps. It means compressing the time between them. You still document. You still give them a chance. But you don't extend the runway when the signals are clear.
Coaching → wait 1–2 weeks → Re-coaching → wait 1–2 weeks → Written warning → wait → PIP (30 days) → Termination if failed.
Total: 4–8 weeks depending on role.
Coaching → wait 3–5 days → Re-coaching with escalation ladder introduced → wait 3–5 days → Written warning → PIP (2 weeks, even for non-high-volume roles) → Termination if failed.
Total: 2–4 weeks.
The difference: You're not giving less chances — you're giving the same number of chances in a tighter window, because the diagnosis is clear and more time won't change the outcome. Every step is still documented. Every conversation still happens. You just stop extending the benefit of the doubt when it's already been exhausted.
This is the most important section. It's easy to blame motivation when the real problem is your management. Before you label anyone as a will issue, ask yourself these questions honestly:
"Was I actually specific, or did I think I was specific?"
There's a difference between what's clear in your head and what came out of your mouth. If you can't point to a written document that spelled out the expectation, you weren't specific enough.
"Did I actually train them, or did I just tell them?"
Explaining something once is not training. If you didn't do Document → Demonstrate → Duplicate, they may have a skill gap you assumed they didn't have.
"Did I ever ask them what's going on — and really listen?"
Sometimes people look disengaged because something real is happening — burnout, personal issues, feeling stuck in the wrong role. If you've never asked the honest question, you don't have an honest answer.
"Am I frustrated, or am I objective?"
Frustration makes everything look like a will issue. If you're annoyed, give yourself 24 hours before making a judgment. Run the elimination checklist cold.
"Have I tried changing the reinforcement?"
Before deciding they don't want to do it, make sure you've tried different motivators. Maybe public praise doesn't work for them but more autonomy does. Maybe money isn't the driver but development opportunities are. If you haven't experimented with what actually moves them, it may be a reinforcement problem, not a will problem.
A skill issue is a problem you solve. A will issue is a problem you confirm — and then you move decisively.
Never call it a will issue until every other category in the diagnostic has been honestly ruled out. But once it's confirmed — once they know what to do, they've been trained, they have deadlines, blockers are removed, they've been coached, and nothing has changed — stop treating it like a training problem. It's not. More training won't help. More patience won't help. What helps is honesty: a direct conversation, a clear expectation, a tight timeline, and the willingness to follow through.
You've diagnosed the issue. You've fixed the WHAT, trained the HOW, set the WHEN, reinforced the WHY, and removed the BLOCKERS. It's still not working. Here's the structured path from coaching to consequences — fair, documented, and clear every step of the way.
Every time someone misses, run the diagnostic first. If the miss is because you were unclear, they weren't trained, or there was a blocker — that's on you to fix, not on them to be written up for. The escalation ladder is only for when the issue has been properly addressed and the employee still isn't applying the coached skill.
Before you coach, make sure you're coaching the right problem. Ask yourself:
If all of the above check out — they knew what to do, they've been trained, they had a deadline, and nothing was blocking them — now it's a coaching conversation.
Log in the coaching tracker: date, specific skill coached, what you agreed on, and the deadline for improvement. If it's not documented, it didn't happen.
Before escalating, check one more time. Did they understand your coaching? Sometimes the coaching itself was a WHAT problem — you told them to improve but weren't specific enough about what "improved" looks like. Did they have the opportunity to practice? If it's a soft skill and they've only had a few days, they may still be installing the habit.
The first 2–4 weeks after introducing a new skill are about installing habits. It takes repetition before things stick. If someone is clearly trying but inconsistent during this window, re-coach with patience. If they're not trying at all — that's different. Use your judgment, but err on the side of one more coaching cycle during this period, especially for soft skills.
Log in the tracker as Repeat Coaching. Follow up with an email summarizing the conversation and CC the owner. This creates the paper trail.
Only one re-coaching per issue before escalation. You don't coach the same thing three times at this level. If it's been coached and re-coached and it's still happening — it moves to a written warning.
Before you write someone up, do one last honest gut-check. Go through the diagnostic one more time:
If you can honestly say yes to all of the above — proceed with the write-up.
Employee must acknowledge the write-up in writing. Signature, email reply, or documented acknowledgment. Log in the tracker with the write-up attached.
Being on a PIP does not mean you stop diagnosing. You still check for blockers. You still make expectations specific. You still train if a new gap surfaces. The PIP doesn't excuse you from running the process correctly — it's your responsibility to ensure the process is still being done right even while they're on the plan.
If PIP targets are not met → termination. This is the final structured chance. Be clear about that from day one of the PIP — not as a threat, but as honesty. They deserve to know exactly where they stand.
If you've followed every step — diagnosed properly, coached, re-coached, written up, and given a PIP — and they still haven't met the standard, this is the outcome. It's not a surprise to anyone because you've been transparent the entire way.
If you followed this system, you can walk into that meeting knowing you did everything right. You diagnosed the real issue, you trained them, you gave them clear expectations, you removed obstacles, you coached them multiple times, and you gave them a structured final chance. That's not failure — that's integrity.
Not every role moves at the same speed. Roles with higher task volume escalate faster because there are more opportunities to practice and demonstrate improvement.
The goal of this system is never to fire someone. The goal is to give them every possible chance to succeed — and to make it painfully clear what "succeed" looks like at every step.
If you run the diagnostic honestly, train properly, set clear expectations, remove blockers, reinforce good behavior, and then escalate with transparency and documentation — you've done your job. The outcome is up to them.
Most people will never make it past Step 1 or 2 of this ladder, because most problems are diagnosed and fixed before they ever need to escalate. That's the whole point.