Your Technician Can't Hit a Number They Never See. Here's the Five-Minute Weekly Habit That Fixes It.
October 30, 2026

Your Technician Can't Hit a Number They Never See. Here's the Five-Minute Weekly Habit That Fixes It.

Let me ask you something and I want you to be honest with yourself on this one. If you walked up to your best tech right now and asked what their utilization is for this week, could they tell you? Not last quarter, not what it was in the report you sent out, but right now, as of Wednesday afternoon.

Most of them can't. And that's not on them.

In our experience working with MSPs, almost everybody has the number. We typically look at hours utilized per week, and it's sitting in the PSA the whole time. Somebody pulls it on Friday or the first of the month, the service manager looks it over, maybe a conversation happens with a tech, maybe not. The tech never sees it. Half the time if you ask them what the target is they'll take a guess, and the guess is usually wrong.

Think about what that does to you. Say your target is 30 billable hours a week and one of your techs has been sitting at 22. You find out in the monthly report, which means you find out about three weeks after it mattered. So you call them in, and the conversation starts with "we noticed your utilization has been low," and now they're defensive because it feels like a gotcha. They've got a list of reasons, some of them even good ones, and the whole discussion is about something that already happened. Nobody can do anything about last month.

Now flip it. That same tech opens their own number on Wednesday and sees 9 hours with two days left in the week. They know they're behind, they know by how much, and they fix it by Friday. No meeting, no gotcha, you never even had to say a word.

The whole idea fits in one line. People change what they can see.

So here's what I'd do, and it takes about five minutes. Same time every week, the tech opens their own numbers, compares them to the target, and writes down one line on what they're going to do differently. That's it. It's not a meeting and the manager isn't reading the numbers out loud to them. The person who owns the number is the person looking at it. If you read my post on metric ownership you know where I'm going with this, because if nobody on your team can name the number they own, you've got a queue and not a team.

They also need to know why that number is the number. Not just "30 hours," but one sentence on what it means. Something like, we need 30 billable hours from each tech because that's what pays for the desk, the tools and your raise. A target with no reason attached feels like something somebody made up to hassle them. (I'm using 30 as an example here, put in your real figure.)

Now I'd be lying if I told you utilization is perfect on its own, because it isn't. Techs can pad time, they can start dodging the work that doesn't bill like documentation or helping the new guy, and if you push the target too high you'll burn out your best people. So pair it with one quality number, like reopen rate or CSAT or first contact resolution, and be clear about which non-billable work counts toward what you expect. Utilization tells you if somebody is busy. It doesn't tell you if they're good.

What changes for you as the manager is pretty big. Your weekly one on one stops being "here's what the numbers say" and turns into "what did you notice in yours?" The conversations get shorter and they get better, and your time goes to the people whose numbers don't move even after they've seen them. That's where the stuff in my post on holding the number comes in. If a tech has looked at their number every week for thirty days and still isn't getting there, you know it's not an awareness problem anymore, and you've got your plan.

 

There's a side benefit too. When everybody's looking at the same measuring stick, your top performers like it because they can see the standard is real, and a miss has a harder time hiding.

Put all of this in your field guide for each role. The scorecard, the target, the weekly five-minute habit, and show every new hire their number on day one so they don't find out what it is at day 90. It plugs right into the 30-60-90 evaluation too. If you want help building that out, it's what we do at www.builttorunmsp.com.

 

Frequently Asked Questions

How often should an MSP technician review their own performance scorecard?

Weekly at a minimum, and ideally with a quick mid-week look so they can still change the outcome of the current week. A monthly review is too late to affect the numbers it's reporting.

What should an MSP technician scorecard include?

Start with billable utilization, meaning hours utilized per week against a clear target, and pair it with at least one quality measure such as reopen rate, CSAT or first contact resolution. Define which non-billable work counts so techs aren't penalized for documentation or mentoring.

How do I improve technician utilization without micromanaging?

Make the number visible to the technician and let them own the weekly review. When people can see their own numbers and know the target and the reason behind it, most adjust without being told, and your coaching time goes to the few who don't.

Why isn't utilization alone enough to measure a technician?

It measures how busy someone is and not how good their work is. Used by itself it can encourage padded time or avoidance of unbilled work, so it should always be paired with a quality metric.

About the author
Adam Kuester

Adam Kuester

Adam Kuester has a PhD in genetics and a career built inside managed services, an unusual combination that shapes how he works. He spent time designing operations at an MSP before joining Bruce McCully to build Galactic Advisors, where he's served as VP of Special Projects. His focus has been operational: finding gaps, building systems, and turning expertise into tools MSP owners can use across a partner base of nearly 1,000 companies. Built to Run MSP is that same work in a different form, practical frameworks for MSP owners who are good at winning business and want to get equally good at running it.