Here's a question we like to ask in workshops: what's the number one thing your customers want from your service?
The company side of the table usually says something like "fast resolution" or "innovative self-service." When we ask the people who actually work the phones and tickets, the answer is different. It's usually something simpler: "They just want someone to pick up the damn phone."
That gap is what we call inside-out thinking. And it's at the root of most customer service problems we encounter.
Inside-out thinking happens when organisations make decisions about customer experience based on their own assumptions, internal politics, and technical preferences. It's not intentional. It usually starts with good intentions. But over time, the customer quietly disappears from the conversation.
We worked with a client recently who had spent months building a feature they were confident customers needed. When we pulled the usage data, it turned out that 0.015% of their customer base was actually using it. Nobody had checked. The team was so deep in internal discussions about technical implementation that they'd forgotten to ask whether anyone wanted it in the first place.
This is a pattern we see again and again. Teams that are genuinely trying to improve their service, but doing it from the inside out. They design processes that make life easier for the company, not the customer. They build solutions for problems they assume exist, rather than problems they've validated.
One of the exercises we run in workshops is deceptively simple. We bring together people from different departments and ask them to describe the customer experience when someone contacts the company.
It gets uncomfortable fast. "The customer calls us." "Actually, they can also use the portal." "Which portal?" "The one with the outdated information." And suddenly, people who've worked at the same company for years realise they have completely different pictures of what the customer goes through.
That's the value of looking at things from the outside in. When you force internal teams to step into the customer's shoes, they start seeing problems they'd never noticed before. Not because they didn't care, but because they'd never been asked to look.
This is what we mean when we talk about customer journey mapping. Not a marketing exercise with post-its and seven expensive consultants. A practical, ongoing process of understanding how customers actually experience your service, and where the friction points are.
Here's where most companies get it wrong. They treat journey mapping as a project. They book a room, run a workshop, produce a nice-looking document, and then it goes on a shelf. Six months later, the customer experience has changed but the map hasn't.
The best service organisations we work with treat it as a continuous process. They involve customers in sprint demos. They bring real customer feedback into planning meetings. When they build something new, they test whether it actually improves the experience before rolling it out further.
One of our experts puts it well: you need to take your customer along for the entire journey, from idea to solution. Not just at the beginning when you're gathering requirements, and not just at the end when you're asking for a satisfaction score. Throughout.
There's another source of insight that most organisations overlook: their own agents. The people who answer the phones and handle the tickets know exactly what frustrates customers. Ask any experienced agent what could be better, and you'll need to clear your schedule, because three hours later they'll still be going.
The challenge is that this knowledge rarely makes it to the people who make decisions. In some organisations the culture doesn't support upward feedback. In others, it's simply never been asked.
We've found that combining both perspectives, what customers tell you directly and what your agents observe every day, gives you the most complete picture. They'll agree on a lot of things. Where they disagree is often where the most interesting insights are hiding.
There's one question we've found that cuts through all the noise. We borrowed it from a conversation with one of our experts, and it's become a staple in our workshops:
Would you want to be a customer of your own company?
It's a simple question. But in our experience, most people need a moment before they can answer. And when the answer isn't an immediate "yes," the conversation shifts. Suddenly, the theoretical becomes personal.
If all of this feels overwhelming, here's where we'd suggest you begin. It doesn't involve a framework, a matrix, or a consulting engagement. It involves a cup of coffee.
Invite a real customer. Sit down with them. And then do the hard part: listen. Don't pitch. Don't defend. Don't explain how things work on your end. Just listen to what their experience is actually like.
You'll learn more in that one conversation than in a month of looking at dashboards. And if you want to go deeper after that, we're here to help you look at your business from the outside in.
