Why Your Technicians Don’t Care (And What That Costs You)
Walk into most MSPs and you can feel it within ten minutes. The silence. The blank stares when you ask people about their current task list. The way tickets get closed with the digital equivalent of a shrug. Nobody is screaming. Nobody is quitting. The energy in the room says enough.
This is not a burnout problem. Burnout happens when people push too hard for too long without relief. This is different. This is the outcome when competent staff learn that extra effort gets them nothing. No recognition. No consequence. No difference at all. And once an employee crosses that line, you cannot buy them back with a pizza party or a 2 percent raise.
The Recognition Gap Is Wider Than You Think
ScalePad’s 2026 MSP Trends Report surveyed more than 1,100 MSP professionals and found that improving client experience ranked as the top priority for the year. Most MSPs have built entire systems around client satisfaction. Ticket metrics. CSAT scores. Quarterly review rhythms. But the same rigor rarely applies to the people delivering the service.
The disconnect is straightforward. You cannot deliver excellent client experiences with a team that gets managed by exception. Recognition is not a soft skill. It is an operational function, like patching or monitoring. When it is absent, the people who have options leave, and the people who stay are the ones who learned to do the minimum.
Most MSP owners do not set out to build indifferent teams. They get busy. They focus on client fires, vendor negotiations, and quarterly numbers. Meanwhile, the person who stayed late to finish a server migration goes unnoticed. The person who wrote a detailed root cause analysis gets the same response as the person who closed the ticket with “fixed.” Over time, both people learn the same lesson: nobody is paying attention.
What Accountability Actually Looks Like
Most MSP owners think they have accountability because they track ticket closure rates. Ticket volume is a productivity metric, not an accountability metric. Accountability means that when a technician closes a ticket without documenting what was done, someone notices. When a client gets a sloppy update email, it gets corrected. When someone goes above and beyond, it gets seen by the people who make decisions.
The book Rewired MSP puts it simply: if it is not in the PSA, it did not happen. That principle applies to your team the same way it applies to your clients. If good work disappears into a void and bad work disappears into a void too, you have built a system that trains people to coast.
Accountability does not mean surveillance. It means that work is visible, feedback is specific, and there is a difference between how your best performers and your worst performers get treated. If everyone on the team knows that nobody checks the quality of documentation, then documentation quality will decay to whoever cares most on their own. That is not a team. That is a collection of individuals with no shared standard.
The Cost of Not Caring
The staff members who have checked out are not your biggest expense. The opportunity cost is. When your senior tech spends three hours on a problem that should take one because they are running on autopilot, you are paying for two hours of wasted capacity. When a client gets a careless response and quietly starts looking for a new MSP, you will not hear about it until the termination letter arrives.
The hidden cost is worse. When one person coasts and nobody says anything, the rest of the team notices. High performers see someone getting the same paycheck for half the effort, and they either leave or adjust their own output downward. This is how mediocrity spreads. It is not a dramatic mutiny. It is a slow, quiet leveling down of the entire team to the lowest acceptable standard.
Research that Bain & Company originally published and that Harvard Business Review has cited for over a decade shows that acquiring a new customer costs 5 to 25 times more than retaining an existing one. That ratio applies to employees too. The cost of replacing a mid-level technician, recruiting, onboarding, lost productivity during the gap, easily runs 50 to 200 percent of their annual salary. Every person you lose to indifference is a five-figure decision that nobody in leadership consciously made.
What Recognition Actually Is
Recognition is not an annual review. It is not a bonus that shows up in a paycheck and gets spent on groceries. Recognition is specific, timely, and tied to behavior you want to see repeated.
Consider a concrete example. A technician identifies a recurring failure pattern, documents it, and writes the knowledge base article without being told. That gets mentioned in the team meeting. Not “great job, everyone.” Not a generic shout-out. A specific callout: “Sarah found the root cause of the backup failures that have been hitting four clients, wrote the KB article, and updated the monitoring template. That is exactly the kind of ownership we need.”
Why does the specificity matter? Because the person being recognized knows you actually paid attention. And because everyone else on the team now knows what “good” looks like. Recognition is not just about the person receiving it. It is a signal to the entire team about what gets noticed and what gets rewarded.
The Accountability Ladder
If you are building or rebuilding a culture of accountability, the steps are sequential. Skip one and the rest collapse.
Set the standard clearly. If your team does not know what “good” looks like for documentation, communication, and escalation, you cannot hold them to it. Write it down. Make it specific. “Tickets get closed with notes on what was done” is a start. “Notes include what was found, what was done, and what the client should watch for” is a standard.
Make the work visible. If you cannot see the work, you cannot manage it. The PSA should be the record of what actually happened, not a ticket-closing game. If your technicians see that nobody ever looks at the notes on what was done, they will stop writing them.
Give feedback quickly. Annual reviews do not change behavior. Feedback within 48 hours of the work does. If a technician writes a sloppy KB article and nobody says anything for three months, the message is clear: nobody reads them.
Separate the people from the problem. Accountability is not punishment. It is “here is the gap between the standard and what happened, and here is how we close it.” When managers avoid the conversation, the standard becomes optional.
Reward the behavior you want to scale. When someone does something that makes the whole team better, that gets noticed by the people who make decisions. Not just a “nice job.” A promotion conversation. A project lead. A seat at the table when decisions get made.
Why Most Owners Miss It
MSP owners tend to be problem solvers by nature. When something breaks, they fix it. When a client complains, they respond. But this creates a reactive management style where the only things that get attention are the things that are visibly on fire. The quiet technician who never causes problems also never gets noticed, until they are updating their resume.
The 2026 data from ScalePad shows that only 36 percent of MSPs have structured onboarding. That means nearly two-thirds of new hires are figuring out the company’s standards on their own, or not figuring them out at all. If you do not define what good looks like in the first week, people will define it for themselves. And their definition will be shaped by the worst performer on the team, not the best.
The Owner’s Part in This
Here is where most MSP owners deflect. They blame HR. They blame the hiring market. They blame the younger generation for not wanting to work. But the single biggest factor in whether staff members care about their work is whether they feel seen by the person running the company.
If you have never had a one-on-one with your junior technician, that is a choice you made. If you cannot name the specific strengths of each person on your team, you are not leading them. You are just billing for them.
This is not about being soft. This is about building a team that performs at a level where clients stay because the service is excellent, not because the contract has an auto-renewal clause. The difference between those two retention models is whether your people give a damn.
Where This Leaves You
Start with one change this week. Pick the person on your team who does the best work and make sure they know you noticed. Not in a generic “great job” email. Specifically. What they did. Why it matters. What it meant for the team or the client. Then do the same for someone who is coasting and needs a conversation about the gap between their effort and the standard. These two actions, recognition for the top and clarity for the bottom, are the foundation of a team that performs at a level clients can feel. The MSPs that will still be standing in ten years are not the ones with the best tools. They are the ones with the best teams. And best teams get built one specific conversation at a time.
Sources
1 ScalePad, “2026 MSP Trends Report,” 2026.
2 Bain & Company, cited in Harvard Business Review, “The Value of Getting Customer Retention Right,” 2014.
3 Society for Human Resource Management, “Costs of Turnover” research series, 2025.
About Brent Lacy: Brent Lacy has been in the IT industry since 1997. He moved into the managed services world around 2015 and was doing vCIO work before the title even existed. He writes about the operational discipline, trust-based relationships, and strategic thinking that separate MSPs built to last from those built to bill. He is the author of Rewired MSP: Mastery, Scalability and Performance, vCIO Rewired: Virtually Conquering IT Obstacles, and Near Miss: Preventable IT Failures Threatening Your Business Security.
