The 5-Pillar Service Operations Health Check
A self-assessment for founders, COOs, and service leaders
Most service operations don’t fail dramatically. They fail quietly through accumulated drift, postponed decisions, technology that no longer fits, and processes that were designed for a smaller business and never updated. By the time the failure shows up in customer complaints, attrition, or board reports, it’s usually been visible for months to anyone who knew where to look.
This is a self-assessment built around five pillars that, in my experience, account for almost every meaningful service operations problem I’ve seen. There’s no scoring tool, no email gate, and no booking calendar at the end. Read through it, sit with the questions honestly, and you’ll know within twenty minutes where your operation is genuinely strong, where it’s drifting, and where it’s quietly storing up trouble.
A simple way to use it: rate yourself on each statement from 1 (strongly disagree) to 5 (strongly agree). The number itself doesn’t matter but pay attention to the questions you’d rate 1 or 2. Those are the conversations worth having with your team this quarter.
Pillar 1: Design
How well your service operation has been designed, rather than accumulated.
Most service operations weren’t designed. They grew. A channel was added because a competitor had one. A self-service tool was bought because someone wanted to cut costs. A process was created to handle a specific problem and never retired. The result, in many businesses, is a tangle of channels and tools that nobody chose deliberately and nobody is willing to take ownership of simplifying.
Honest answers to these three questions tell you whether you have a designed operation or an accumulated one:
Our service channels are intentional, not just added over time.
We’ve balanced tech and people to create consistent, reliable customer journeys.
Our self-service is useful to our people and customers, and not just there to reduce costs.
The tell-tale sign of weak design isn’t usually customer complaints, it’s internal confusion. If your team can’t articulate why each channel exists, why each tool is in the stack, or what your self-service is for, the design has failed. The fix isn’t more tools. It’s pulling everything down to first principles and asking, channel by channel, “would we add this today if we didn’t already have it?”
Pillar 2: Direction
Whether your service operation knows where it’s going and why.
Service teams need direction in the same way any team does, but service direction is often weaker than it looks. There’s usually a strategy slide somewhere. There’s usually a set of KPIs. What’s often missing is the connective tissue, the link between what the business is trying to achieve and what the service team does on a Tuesday morning.
Our operating model is clearly defined and understood across teams.
We have clear priorities, and they’re reflected in how we work and make decisions.
Everyone understands how their role impacts the customer, not just frontline teams.
The third question is the one most businesses fail. Frontline teams almost always understand their impact on customers; it’s the function of their job. The disconnect tends to be in the supporting functions - marketing, product, billing, technology - whose decisions reach customers indirectly and whose teams often have no feedback loop telling them how those decisions land. If your billing team doesn’t know what kind of week the service team is having, your direction is fragmented even if your strategy is clear.
Pillar 3: Enablement
How well your team is set up to do good work.
A service team’s performance is determined by the conditions you create for them. Brilliant people will fail in poorly-designed systems. Average people will perform well in good ones. Most operational performance problems are enablement problems wearing different costumes.
Our team is supported with training, coaching, and feedback loops that drive performance.
Internal knowledge is actively managed so it’s accurate, accessible, shared, and actually used.
We don’t have bottlenecks, our systems and ways of working are resilient and scalable.
Knowledge management is the question worth lingering on. Almost every business I’ve worked with thinks their internal knowledge base is “fine.” Almost none of them are right. The test is simple: when an advisor needs an answer, where do they actually look? If the answer is “they ask the person sitting next to them,” your knowledge base isn’t doing its job, regardless of what’s in it. That’s not a content problem; it’s a usability problem dressed up as a content one.
Pillar 4: Efficiency
Whether your operation is getting better or just getting busier.
Growth tends to mask efficiency problems. When demand is rising, the workload is rising too, and it’s hard to tell whether the team is genuinely getting better or just running faster on the same treadmill. The efficiency pillar separates the two.
We improve processes continuously, not just when something breaks.
Change happens fast enough to stay ahead, not just keep up.
Our use of automation and AI is saving time and improving both service and team performance.
The third question now matters in ways it didn’t five years ago. Most businesses I speak to have invested in AI tools: chatbots; agent assistants; summarisation (automated notes); deflection. Most of them are honest enough to admit they’re not sure whether the investment is paying back. The mistake is usually treating AI as a deflection strategy rather than a performance one. AI used to push customers away from human contact tends to perform worse than AI used to make humans better at their jobs. If your AI strategy is mostly about reducing volume rather than improving quality, the results will eventually disappoint everyone.
Pillar 5: Intelligence
Whether you’re learning from what’s actually happening or running on instinct.
The best service operations I’ve worked with share one trait: they treat every customer interaction as a source of information about the business, not just an event to be resolved. The worst ones treat data as a reporting requirement.
We know what’s working and what’s broken and we have the skills and resources to fix things.
We regularly analyse root causes, not just symptoms.
We trust our data, and we always use it to inform decisions.
The most common failure mode here isn’t an absence of data. It’s an abundance of it that nobody trusts. Dashboards proliferate, definitions drift, the same metric means different things in different reports, and the team eventually stops using any of it because it’s all slightly wrong. If your weekly service review is a discussion about whether the numbers are right rather than what the numbers tell us, your intelligence pillar is weaker than you think and rebuilding the data foundation is almost always more valuable than buying another reporting tool.
What to do with what you’ve found
If you’ve worked through the fifteen questions honestly, you’ll have a sense of your strongest pillar and your weakest. The temptation will be to tackle the weakest one first. Resist it.
The pillar that matters most isn’t the lowest-scoring one, it’s the one most directly blocking what your business is trying to do over the next twelve months. A start-up scaling rapidly almost always needs to fix Design before anything else, because accumulated mess gets exponentially harder to untangle as it grows. A mid-market business going through transformation usually needs to fix Direction first, because nothing else holds without it. A business under cost pressure needs to fix Efficiency. A business losing customers it shouldn’t be losing needs to fix Intelligence.
The right next move depends on context. But the wrong move is almost always the same one: doing nothing because the picture feels too complicated.
If any of this felt uncomfortably familiar or if you’d like to talk through what your answers might mean for your business specifically - I’m easy to find. mark@soothconsulting.xyz.