If you only step back to review your operations once a year, you aren’t protecting your margins — you’re discovering the leak long after it’s drained the tank.
Building a high-performing MSP isn’t about the technology you deploy. It’s about the operating culture you build. Too many owners are flying blind, running on gut feel instead of a system that drives margin and valuation. The fix isn’t another tool. It’s a rhythm of continuous improvement — and the most powerful tool in that rhythm is the quarterly “180.”
Why MSPs should run a quarterly 180
In managed services it’s dangerously easy to live in the weeds. Between fire-fighting tickets and managing client escalations, leadership and the ops team drift in different directions. If it feels like your team is paddling in circles instead of rowing in sync, that’s the signal you need a regular 180.
A 180 is dedicated time to turn away from daily service delivery and look at the bigger picture of operational health. Some industries do this every two weeks; for most MSPs, a quarterly cadence is the sweet spot — enough data to reveal trends, not so frequent it becomes busywork. The agenda is simple and honest:
- Review the wins. Which processes are actually working?
- Name the failures. Where did we drop the ball this quarter?
- Find the bottlenecks. What’s slowing delivery or keeping us from hitting KPIs?
How to run your first 180
A 180 only works in a safe space. It is not a blame game — the focus is process improvement, not individual performance. Four moves make the difference between a useful session and a gripe session:
1. Open with the prime directive
State it out loud: regardless of what we uncover, we believe everyone did the best job they could given what they knew at the time. Borrowed from blameless retrospectives, this is what gives people permission to surface the real problems instead of protecting themselves.
2. Get the right people in the room
Include leadership and the ops team. You need the people in the trenches — dispatch, the service desk, the engineers — to tell you where the leaks actually are. Owners rarely see them from the org chart’s top.
3. Generate insight, not just a problem list
Don’t stop at “tickets are slow.” Ask why. Is it missing documentation? A tool that was never configured correctly? A handoff with no owner? The root cause is where the margin is hiding.
4. Commit to action
Pick one to three specific items to fix in the next 90 days. If you try to fix everything, you’ll fix nothing. A short, owned, dated list is what turns a meeting into a result.
The 180 and your margins are the same conversation
Why does this hit the bottom line? Thin margins are usually efficiency leaks — the slow drip of over-servicing “bespoke” clients and spending technician hours on repeatable work that should have been automated months ago. When you don’t run a regular 180, those leaks become permanent fixtures of your cost base.
Find and close them quarterly and you do two things at once: you protect this year’s margin, and you raise the enterprise value of the business. Investors look for operational excellence — systems that run and improve without the owner sitting in every meeting. A documented 180 cadence is exactly the kind of proof of operational maturity that moves a valuation multiple.
Make it a habit, not a project
Are you ready to stop tossing deliverables between departments and start building a team that scales? Continuous improvement isn’t a one-time initiative — it’s a habit. The accountability flywheel that keeps a team focused on what moves the needle starts spinning with a single honest retrospective.
At Ridgeview Advisors, we teach MSP leadership and operations teams how to build that rhythm of continuous improvement into the way they work — so it sticks after we’re gone. Run your first quarterly 180 this month, and when you’re ready to make operational discipline a capability your team owns, let’s talk.
