Episode 39: The high-performance MSP: moving from busy to productive

Adam

You know, if you've ever um if you've ever sat in a car, put the transmission in neutral and just slams your foot down on the gas pedal, you know the exact sound I'm talking about.

Christina

Oh, absolutely. The engine is just screaming.

Adam

Right. The RPMs are redlining, the entire chassis shaking under you. Yeah. But you know, you're still just parked in your driveway. You aren't going anywhere.

Christina

Yeah, it's such a visceral image, and it's really a perfect analogy for what we're talking about today. You're generating a massive amount of heat and noise, and well, burning through your fuel at a crazy pace, but you have zero forward momentum.

Adam

All exertion, no execution.

Christina

Exactly.

Adam

And that image really gets at this paradox that is just completely plaguing businesses right now, especially in the tech and services sector. So for this deep dive, we're unpacking a text document we received titled MarkGermspis Busy.txt.

Christina

Which is a very telling title.

Adam

It really is. And for anyone outside the industry, an MSP uh managed service provider is basically an outsourced IT department, right? They keep other companies' networks and servers running. And the mission for this deep dive today is to unpack a really hard truth from this document.

Christina

That most operational problems come from misdirected effort, not a lack of effort.

Adam

Yes. We're going to discover the three operational habits that separate truly high-performing MSPs from those that are just, as the source puts it, firefighting at scale. And honestly, the best part.

Christina

None of it requires buying new software.

Adam

Exactly. No expensive new tools. Here's where it gets really interesting, though. Because when a team is busy, I mean when everyone is screaming that they're at capacity, the default response is almost always just let's add headcount.

Christina

Right. Just throw more bodies at the problem, hire more engineers.

Adam

But our source argues this is just slapping a band-aid on a fundamental process problem.

Christina

Yeah, because the gap between being busy and being productive is exactly where your profit margins disappear. I mean, if your process is fundamentally broken, adding more people just gives you a larger, more expensive, broken process.

Adam

You just have more people standing around that Revving car in the driveway.

Christina

Precisely. So if we want to find out why a team is so busy but not productive, we have to start by looking at where the time invisibly vanishes before the actual work even begins.

Adam

And we are talking about meetings. The invisible time dream. The ultimate time dream.

Christina

It's so easy to ignore because you know it feels like work. You're staring at a video call, talking about client issues. So your brain logs it as doing work.

Adam

But the text breaks down how meeting bloat is literally measurable. It's not just a feeling. If you multiply the number of attendees by the duration across all your recurring meetings, the actual cost in engineer and leadership time becomes completely staggering.

Christina

Because meetings don't cancel themselves, right? They just accumulate.

Adam

They only accumulate. The text has this perfectly painful example. It talks about a weekly stand-up that, you know, it made perfect sense when it was just four people.

Christina

Yeah, 15 minutes and done.

Adam

Right. But fast forward a bit, and now it has 12 attendees. It produces absolutely no clear output, and people are just multitasking off camera.

Christina

It's basically organizational inertia.

Adam

It's like a monthly subscription you forgot to cancel, but it's draining your team's hours instead of your bank account.

Christina

That is a great way to phrase it.

Adam

But okay, I have to push back on this for a second. Let's say I'm running that 12-person meeting. What if my answer is just, well, it keeps people aligned, or it's a really good chance for a remote team to catch up.

Christina

Yeah.

Adam

Doesn't that have value for team culture?

Christina

It's a common defense. But the source is actually really strict on this. It argues that if your only goal is alignment or socializing, that is not a meeting.

Adam

Wait, really? Then what is it?

Christina

It should be a written update or a shared channel in your chat app. A meeting is for synchronous decision making. You don't hold twelve people hostage just to read them a memo.

Adam

Wow. Okay, so how do you fix it?

Christina

The text outlines a strict meeting audit rule. For every single recurring meeting, you have five options. One, keep it. Two, reduce its frequency.

Adam

Unlike going from weekly to monthly.

Christina

Exactly. Three, reduce attendance, maybe only the leads need to be there. Four, convert it to an async update. Or five, just cancel it.

Adam

And to stop it from coming back, I think the document mentions a checklist.

Christina

Yes, the pre-meeting checklist. Before booking any new meeting, you have to answer three questions. What decision needs to be made, who specifically needs to make it, and this is the kicker. Why can't this happen in writing?

Adam

I love that. Why can't this happen in writing? It forces you to justify the interruption. Okay, so let's say we do the audit, we clear the calendar, the engineers are finally free to actually work on tickets.

Christina

This is where people fall into the next trap.

Adam

Right. Because the natural assumption is that more time spent on tickets equals a healthier business. But the source material warns that how we measure that time is fundamentally flawed.

Christina

Yeah, because leaders love looking at a 95% utilization rate.

Adam

Oh, yeah, it looks fantastic on a dashboard. It signals that, hey, capacity is being used. Nobody's just sitting around.

Christina

Well, what are they actually working on?

Adam

Okay, let's unpack this. It's like running on a treadmill at max speed, but wondering why you haven't left the room. How do we actually separate running in place from moving forward?

Christina

The source introduces this concept of effective utilization, because high utilization with low first-time resolution, that just means a team is repeatedly handling the exact same problems.

Adam

They're trapped in a loop.

Christina

Exactly. So the document breaks it down into two buckets. First, you have productive hours. This is your first-time resolutions, proactive work, and actual environment improvement. Right. But then you have waste hours. This is rework, repeat tickets, or, and this is a great metric, things appearing in the queue three or more times without a permanent fix.

Adam

Oh wow. Three strikes and it's classified as waste.

Christina

Yeah. And once you identify that waste in your PSA, your professional services automation software, the fixes are actually really clear.

Adam

Like what? What's an example?

Christina

Well, if the data shows repeat tickets, you clearly need better automation or better documentation.

Adam

What if it's an engineer just bouncing around a lot?

Christina

Context switching. Like if an engineer is jumping between five completely different clients in a single morning, that points directly to a scheduling problem.

Adam

Right, because they have to mentally reboot every time they look at a new network.

Christina

Exactly. And if you see client-level time sinks like one client taking up half your week, that requires a scope conversation with that client.

Adam

So how does a team actually start doing this without getting overwhelmed?

Christina

The text offers a 90-day challenge. You pull a PSA time entry export, find the top five time sinks, and you just ask the team if 20% of this wasted time needed to be cut in the next 90 days, where would we start?

Adam

Just 20%? That feels, I mean, that feels manageable. It gives the engineers agency.

Christina

It totally shifts the mindset from feeling overwhelmed to feeling analytical.

Adam

Okay, so we've fixed the daily schedule by cutting meetings. We've fixed the daily workload by focusing on effective utilization. The machine is humming.

Christina

In theory, yes.

Adam

Right, in theory. But why does the entire system still seem to blow up every single Monday morning? I mean, this happens everywhere. And the source argues that to fix Monday, we actually have to rewind to Friday.

Christina

Monday chaos is just Friday's unfinished business.

Adam

It's the classic scenario. Laptops close on Friday at 5 p.m. Everything feels totally fine. But Monday arrives, and you've got three escalated tickets, an angry client and an on-call engineer who has absolutely zero context.

Christina

And usually an SLA breach, right? A service level agreement violation.

Adam

Yes. And the text's central thesis here is that none of this is just bad luck. That SLA breach risk was completely visible at 4 p.m. on Friday.

Christina

It was sitting right there in the queue.

Adam

Okay, I get this in theory, but let's be real for a second. On Friday at 4 p.m., everyone's brain is just completely fried. The instinct is to shut the laptop and literally run away from the desk. How do you actually get an exhausted team to do more admin work right before the weekend?

Christina

Well, the source acknowledges that friction. The solution is you make it non-negotiable for exactly one month to build the habit. And you assign ownership to one specific individual.

Adam

Ah, so not just a vague team responsibility.

Christina

Right. Because if everyone is responsible, nobody is responsible. And you keep it incredibly brief. After four weeks, the team actually sees the self-evident benefits. Calmer weekends, cleaner Mondays.

Adam

So what does this incredibly brief closeout actually look like?

Christina

It's a 10 to 15 minute Friday closeout checklist, just five steps. Step one, open P1 and P2 tickets.

Adam

Just check in the status.

Christina

Status and next action, yeah. Step two, flag any SLA breach risks in the next 48 hours. Exactly. Step three, verify scheduled weekend changes. You confirm ownership and make sure there's a documented rollback plan.

Adam

In case someone breaks a server on Saturday night.

Christina

Right. Step four is the on-call handoff with context. And step five is just proactive updates for clients with unresolved issues so they don't feel ignored over the weekend.

Adam

I noticed the text draws a really cool connection here to security operations, specifically at enhanced.io.

Christina

Yeah. In security ops, triaging alerts correctly the first time massively reduces downstream rework.

Adam

So it's the exact same principle.

Christina

It is. And the text notes that this internal closeout shouldn't be a meeting. It should be a written summary under 200 words that takes the on-call engineer maybe three minutes to read.

Adam

Giving them instant context instead of making them dig through logs at 2 a.m.

Christina

Exactly.

Adam

It really all comes down to operational discipline. So to summarize the core message of this deep dive for you listening, scaling a business successfully doesn't always mean hiring the most engineers you can find.

Christina

Usually that makes it worse if the process is bad.

Adam

Right. It actually means building the discipline to make every hour count, purging useless meetings, measuring effective utilization, and closing out Friday to protect Monday.

Christina

It's about working smarter, but mechanically smarter.

Adam

So what does this all mean for you right now? The text's final advice is so practical. Just start with the one problem causing the most friction for you this week. Fix that, and the rest will naturally follow. Don't try to boil the ocean.

Christina

But there is a flip side to this that I think is a great lingering thought for everyone. The text warns heavily about just adding headcount to solve chaos. So if you ignore these operational basics and you just keep hiring more and more people to handle the noise, at what point does the sheer weight of undocumented processes and bloated meetings cause the entire operation to just collapse under its own size?

Adam

That is a terrifying thought. You just build a heavier car that's still stuck in neutral right until the engine blows.

Christina

Exactly.

Adam

Well, definitely something to chew on before your next 12 person stand up meeting. Thanks for joining us on this deep dive, and we'll catch you next time.