The Invisible Reason Your Best Customers Quietly Go Somewhere Else
- Philip Edgell
- Jul 3
- 8 min read
TL;DR:
The Friction Problem: Most organizations design their processes for internal convenience, leaving their customers to navigate the consequences.
The Yes Test: Before you finalize any customer-facing process, ask one question: does this make it easier or harder for the customer to say yes?
Outside-In Design: Great customer organizations do not design processes and then add a customer experience layer. They start with the customer's experience and build backward.
Friction is a Tax on Growth: Internal friction carries the same cost as external friction. The faster you want to grow, the more aggressively you need to root it out.

The Reservation That Wasn't
I recently coordinated a dinner for a leadership retreat, a straightforward booking with a well-known restaurant in the city.
Simple enough. Except it wasn't.
OpenTable wouldn't take reservations for more than six people, so I called the restaurant directly. The person who answered was polite but not helpful. They needed to check with their manager.
So I waited.
When they came back on the line, they said I needed to call someone else and offered to give me the number. They didn't offer to transfer me. They didn't offer to take my details and have that person call me back. They gave me the number and wished me well.
I called the number. It went to voicemail. I left a message asking if they had space.
When the reservation person eventually called back, the news kept coming. Fixed menu only. One seating time. Automatic gratuity. Strict time allotment at the table. No orders taken until every guest had arrived. It felt like the fine print at the end of a TV prescription drug commercial.
Every person in that value chain likely felt they had done their job and followed the agreed policy.
Nobody had thought about the cumulative experience they were creating. The customer and I decided to take my business elsewhere. Too much friction.
A different context, same experience.
As part of these sessions, we also book meeting space for day-long retreats that require catering, hotel rooms, and technology. Though I was booking everything at the same location, I had to coordinate with the hotel, conference centre, technology outsourcing partner, and catering group to pull my own booking together.
To add friction to an already frustrating experience, the quote arrived as a non-summarised PDF pulled directly from an internal planning tool. It needed to be printed, initialled on each page, signed, scanned back to PDF, and returned. A separate non-digital contract from the technology supplier. Payment details in a Word document.
Friction at every turn. I want to give you my money. Make it easy for me.
Who Is Getting This Right
In my journey through all of this, I met Kristie at Moxies in downtown Vancouver.
I told her I wanted a dinner experience for a group of executives and shared our date, number of guests, and approximate timing. She confirmed she had space and simply asked: "Would a per-head budget of $x be appropriate?"
That was it.
We had an exceptional chef's table dinner with wine pairings that the group still talks about today.
At every opportunity, I host events with Kristie because she makes it easy for me to say yes.
One question. No friction. Done.
The Process Designed for Everyone Except the Customer
Here is what I know about business.
Very few companies plan a strategy rooted in making it as difficult as possible for customers to spend their money with them. Every business I work with is trying to grow, doing more with existing customers and acquiring new ones.
But when it comes to designing processes and structures, internal myopia takes over. The customer experience becomes the sum of those decisions. Individuals and teams design around how they are measured for their contribution to the value chain, without considering or experiencing the full chain from the customer's perspective.
This is inside-out design. The organization starts with its own needs and asks the customer to navigate whatever remains. It is the default mode of almost every organization I work with, not because they don't care about their customers, but because internal processes are visible and manageable and the customer's experience of those processes is neither.
The alternative is outside-in design. You start with a single question: how do we make it easy for a customer to say yes to us right now? And then you build backward from the answer.

The Yes Test
Make it easy for your customer to say yes, even if that makes your internal process more complicated.
Read that second part again. Even if it complicates your internal process.
Because that is the uncomfortable truth most organizations avoid. Removing friction from the customer experience almost always creates friction somewhere inside the organization. Someone has to make the call instead of transferring it. Someone has to take the details and follow up rather than asking the customer to call back. Someone has to design flexibility into a system built for uniformity.
That internal friction is real and it has a cost. The question is whether that cost is higher or lower than the cost of losing the customer, or never acquiring them in the first place. The customer who gave up before they even became a customer never appears on any report.
If you are a genuinely customer-centric business, internal friction is the price of admission. Most organizations never attempt that calculation because they are organized for their own convenience, not their customer's.
The Yes Test is a simple discipline I recommend every leadership team apply to every significant customer-facing process. Before you finalize how something works, ask one question:
Does this make it easier or harder for the customer to say yes?
If the honest answer is harder, even slightly harder, that is the design problem to solve. Not the process's operational efficiency. Not the convenience of the team managing it. The ease with which a customer can say yes.
What Outside-In Design Actually Looks Like
Most organizations say they are customer-centric. Very few have designed their processes from the outside in.
The test is not whether you have a customer experience team, a Net Promoter Score, or a service excellence programme. Those are inside-out responses to a customer experience problem, designed and managed internally, applied to the customer as a layer on top of existing processes.
The test is simpler. Map the journey a customer takes when they try to say yes to you. Every step, every handoff, every moment where they have to wait, call back, leave a message, navigate a policy, or do work your organization could be doing for them.
Then ask honestly: who designed this journey and who were they designing it for?
One of the most powerful examples I have seen of outside-in thinking in practice is a category-leading manufacturing business I work with. For a long time, they focused on standard manufacturing metrics guided by just-in-time and on-time production principles.
The shift happened when they redefined their success metric as on-time delivery from the customer's perspective. Not whether the unit left the factory on schedule, but whether the customer's project was installed and completed on time.
The metric shift was subtle. The cultural shift was enormous.
What they realized is that customers judge success by when their project is finished, not when the component was manufactured. By reorienting from a single step in the value chain to the entire value chain from the customer's perspective, they shifted what the organization as a whole paid attention to.
That is outside-in design. Not a programme. Not a department. A fundamental reorientation of what success means and who gets to define it.
The pattern I see most often in organizations that haven't made this shift is not malice or indifference. It is invisibility. The customer's experience is simply not in the room when the process gets designed. The people who design processes are internal. Their frame of reference is internal. And so the process reflects that frame, efficient for the organization, effortful for the customer.
Very few organizations conduct a serious secret shopping exercise. What is it actually like to navigate our company from the outside? That single question, asked honestly and followed seriously, changes everything about what gets fixed and what gets ignored.
The Internal Principle
There is a version of this that lives inside every organization too.
I will be direct about a bias. I don't love the concept of internal customers. I prefer to think of an organization as internally united to serve external stakeholders. But the principle holds regardless of the language.
The same friction that frustrates an external customer frustrates the people inside your organization. The colleague who has to navigate three approval layers to book a meeting room. The team member who needs five sign-offs to make a decision that should take five minutes. The new hire who spends their first week trying to get access to the tools they need to do their job.
None of those processes were designed to be obstructive. They were designed for control, compliance, or consistency, all legitimate internal needs. But the experience of navigating them is the same as calling a restaurant and being told to call someone else.
There is a balance between control and speed of growth. The faster you want to grow, the more balanced your approach to internal controls needs to be. And to grow profitably, leaders need to root out friction, because it is the tax on growth that quickly erodes your margins.
Leadership Takeaways
Your process is your customer experience: Every internal process decision has an external consequence. The customer does not see your org chart or your operational constraints. They experience the sum of your decisions.
Apply the Yes Test to everything: Before any customer-facing process is finalized, ask whether it makes it easier or harder for the customer to say yes. If the answer is harder, that is the design problem to solve.
The lost customer is invisible: The customer who gave up and went elsewhere never appears on your dashboard. They are buried in a won/loss report tagged "lost on price." Friction is rarely the official cause of death. It is almost always the real one.
Outside-in is a discipline, not a department: Customer centricity is not a team or a programme. It is the habit of starting every process design conversation with the question: what does it feel like to be on the other side of this?
Redefine your success metrics from the customer's perspective: What you measure internally shapes what your organisation optimises for. If your metrics end at your process boundary, your thinking will too.
The Practical Step: Map the Yes Journey
Pick one significant customer-facing process in your organization. The way a new client gets onboarded, the way a customer makes a booking, the way a prospect gets a proposal, the way a complaint gets resolved, the way credit approval or invoicing is handled.
Now map every step a customer takes from the moment they decide to say yes to the moment they have actually said it and experienced the result.
For each step, ask three questions:
Who designed this step and who were they designing it for?
Does this step make it easier or harder for the customer to say yes?
If we removed or simplified this step, which internal process would become more complicated, and is that cost lower than the friction we are creating for the customer?
The answers will tell you where your Yes Test failures are. They will also tell you something more important: whether your organization is designed from the inside out or the outside in.
If you are unsure where to start, consider a secret shopping exercise. Engage someone outside your organization to navigate your customer journey from scratch and report honestly on what they find. Most leadership teams are genuinely surprised, not because the friction is hidden, but because nobody has ever looked at the sum of it from the customer's perspective before.
That is the outside-in moment. And it is where the real work begins.





Comments