

Sooner or later you'll have a tech who misses the number. You sit down with them, they nod, they say they get it and they'll do better, and then a month goes by and they miss it again. This is usually where the second guessing starts. Maybe the target is too aggressive. Maybe you hired the wrong profile. Maybe you set it too high to begin with and this is partly on you. So you bring the bar down a notch to be fair, and when that doesn't work either, a few months later you bring it down again.
I've done this myself, so I'm not pointing a finger.
Most owners who do it are trying to be decent about it. But I've watched it play out enough times now that I want to tell you where the damage actually lands, because it's not where you'd expect.
First, the question you're really asking is whether the bar is too high, and that deserves a real answer instead of a feeling. Look at the other people in the same role. If they're hitting the number, the number is fine and you've got one person who isn't. If nobody in the role is hitting it, then yes, take a hard look at the bar, but you do that for the whole role at once, not for one guy who's behind.
Now picture your best tech watching you lower it. They know what the target is. They've been working to clear it, in some cases staying late on a Thursday to get a queue down or taking the ugly tickets nobody else wanted, and now the standard moves for someone who didn't do any of that. What they hear is that the number was a suggestion. A few of them get a little bitter about it, a few quietly stop pushing since the extra effort clearly wasn't what you were paying for, and the really good ones start answering recruiter calls they used to ignore. You won't see any of that on a dashboard. You'll see it when one of them gives notice and you honestly can't figure out why.
It doesn't help the struggling tech much either. They end up with a standard that doesn't match the job, no real sense of where they stand next to everyone else, and a bigger hole to climb out of the next time a raise or a promotion comes up. Being straight with somebody is kinder than being flexible with them, even if it doesn't feel that way sitting across the table.
Keep the number where it is and manage to it.
That starts with showing the tech exactly where they are against the target, using what's in your PSA and not how you feel about them. Say your target is a certain number of tickets resolved per day with a first contact resolution rate over a set percentage, and they're sitting well under both. Put those two figures in front of them and agree on a window to close the gap, thirty days is plenty for most roles. Pick the one or two behaviors that will move those figures (maybe they're escalating too fast, maybe they're skipping documentation so the same issue keeps coming back) and coach on those instead of talking about effort in general. Meet every week with the numbers on the table, and write down what you both said and what you both agreed to. Yes, that's a lot of work. It's less work than living with a standard nobody believes in.
When the window closes, one of two things happened. They got there, and now you've got a better tech and a team that watched you hold the line. Or they didn't, and you have a fair, documented reason to have the harder conversation. I know that second one is uncomfortable to say out loud, but it comes down to get them there or get them out. Leaving someone under the bar for six months with no end date isn't fair to them, because they deserve a straight answer, and it isn't fair to the people covering the difference.
I don't think the number is sacred, by the way. Bars can be wrong. The role might have changed since you set it, or you might have picked the target out of thin air without any data behind it, or the whole team could be missing it for reasons that have nothing to do with effort. If that's the situation, change the bar, but change it for the role, on a schedule, with the data in front of you. Never change it in the middle of a plan for one person who happens to be missing it right now. If you hold to that, you'll avoid most of the mess.
A lot of owners put this off, and I get it. The conversation is awkward, replacing a tech costs real money and takes months, and sometimes the person who's missing their number is the one everybody in the office likes best. None of that changes what it costs you to wait, and the cost mostly lands on the people who've been doing it right all along. One practical thing: if a plan like this could end in a termination, talk to your HR person or an employment attorney before the final step so your paperwork and your process hold up.
This pairs with my post on 30-60-90 day expectations. That one is about defining what good looks like in each role, and this one is about what you do when someone doesn't clear it. Put the bar for each role, the review process for a miss and the thirty day plan in your field guide before you need them, so that when it happens you're following a process and not reacting in the moment. That's the kind of thing we help MSP owners put together at www.builttorunmsp.com.
Frequently Asked Questions
Should I lower performance standards for a technician who keeps missing their targets?
Usually not. If the other people in the same role are hitting the target, the target isn't the problem, and lowering it for one person tells your top performers that meeting the standard was optional. Manage that individual to the existing number with a short, specific coaching plan.
How do I manage an underperforming technician at my MSP?
Show them where they stand against the target using real data from your PSA, agree on a short window such as thirty days, and pick the one or two behaviors that will close the gap. Check in weekly, write down what you agreed to each time, and be ready for either outcome when the window ends.
When is it okay to change a performance bar?
When the bar itself is wrong, for example the role has changed, the number was set without data, or the whole team is missing it. Change it for the entire role on a regular review schedule, not in the middle of a plan for one person.
What happens to the rest of the team when a standard keeps getting lowered?
The people hitting the target notice. Some get resentful, some ease off because the extra effort wasn't required, and your best ones may start looking for a place that holds a consistent standard.
Bruce McCully
Bruce McCully built his first company, an MSP, from zero to $8.5 million in recurring revenue. A significant part of that came from cybersecurity incident response. Going into hospitals at 2am and recovering them from ransomware attacks. He didn't learn what happens when a business is unprepared by reading a case study. He was in the room when it happened. Then he founded Galactic Advisors. He scaled it to eight figures in recurring revenue, then stepped down as CEO to focus on MSP Advancement full time. Not because he lost interest. Because the systems he built meant the company no longer needed him to operate it day to day. He remains Chairman of the Board and majority owner. And now he's doing the only thing he wanted to do all along: helping MSPs level up.