Skip to the main content.

5 min read

Stop Building Faster Horses

Henry Ford is often credited with saying, “If I had asked my customers what they wanted, they would have said a faster horse.”

Whether he actually said it is debatable. But the point? Pretty brilliant.

Imagine asking someone in the early 1900s what they needed to make their lives easier. They might have asked for a stronger horse, a more comfortable saddle, or perhaps a wagon that didn’t threaten to rearrange their spine every time they hit a bump.

All reasonable requests.

But what they really needed was a better way to get from point A to point B.

And that’s the difference between listening to what customers want and understanding what customers need.

It’s also where a lot of organizations get strategy wrong.

The Customer Isn’t Always Right. (There, I Said It.)

We’ve all heard the phrase, “The customer is always right.”

Well, sometimes the customer is frustrated, tired, overwhelmed, or trying to solve a problem with the only solution they know exists.

That doesn’t make them wrong. It makes them human.

In a recent episode of The Leadership Line, Scott and Tammy explored what it really means to be customer-centric. One of the ideas that stood out to me was the importance of understanding what customers truly need, not simply fulfilling every request they make.

They also discussed something that can be surprisingly difficult for organizations: making it easy for customers to work with you.

And that got me thinking about strategic planning.

When organizations set their direction, they often begin by asking customers, “What do you want us to do differently?”

That’s a good question. But it’s not enough.

Because if we build our entire strategy around what customers tell us they want, we may end up investing a tremendous amount of time, money, and energy into building a really impressive faster horse.

Sometimes the Request Isn’t the Problem

Let’s start with healthcare, because it’s an industry where this distinction can have a tremendous impact.

Imagine a patient tells a clinic, “I want more appointment times.”

The immediate response might be to extend clinic hours, add providers, or open weekend appointments.

Maybe that’s exactly what’s needed.

But what if we ask a few more questions?

What if we discover that the patient isn’t struggling with appointment availability at all? They’re struggling because they can’t get through on the phone, don’t understand how to schedule online, or have to miss three hours of work for a 15-minute visit.

Suddenly, the conversation changes.

The want is more appointments.

The need is timely, convenient access to care that fits into their life.

And those are two very different strategic problems to solve.

Here’s another example.

A hospitalized patient says, “I want my nurse to come into my room more often.”

We could respond by increasing the frequency of rounding. Create a schedule. Develop a checklist. Add another box to document in the electronic health record. (Because clearly, healthcare needs more boxes to check.)

But what if the underlying need is reassurance? The patient doesn’t know what’s happening next, worries about being forgotten, or doesn’t feel confident that someone will respond when they need help.

More rounding might help. But purposeful communication, setting expectations, and building trust might create far more value.

If we don’t understand the need, we risk measuring our success by how well we delivered something that never really solved the problem.

It’s Not Just Healthcare

Think about a manufacturing customer who asks a supplier to deliver products more frequently.

The supplier might immediately start exploring additional deliveries, transportation costs, and staffing.

But dig a little deeper and you might discover that the customer doesn’t actually need more deliveries.

They need confidence that the right materials will be available when production needs them.

The real opportunity might be improved forecasting, inventory visibility, or more reliable lead times.

Or consider a bank customer who says, “I want a branch closer to my house.”

Are they asking for another building? Or do they want banking services that are accessible, convenient, and easy to navigate?

A new branch is one possible solution. A better digital experience, simpler processes, or more responsive support might address the underlying need more effectively.

The common thread?

Customers are often very good at describing their frustrations. They aren’t always in the best position to design the solution.

And they shouldn’t have to be.

That’s our job.

Listening Is More Than Collecting Feedback

Most organizations have no shortage of ways to collect customer feedback.

Surveys. Focus groups. Comment cards. Online reviews. Complaint logs. Advisory councils.

We collect a lot of information.

But collecting feedback and understanding customers are not the same thing.

True customer-centricity requires us to listen beyond the request and get curious about what’s driving it.

When a customer tells us what they want, we should be asking:

  • What problem are they trying to solve?
  • What is making their current experience difficult?
  • What outcome matters most to them?
  • What might they not know to ask for?
  • How could we deliver that outcome in a way that creates meaningful value?

And importantly, we need to pay attention to what customers do, not just what they say.

If customers consistently abandon an online process halfway through, that tells us something.

If patients repeatedly call a clinic to confirm information they’ve already been given, that tells us something.

If employees routinely create workarounds to deliver what customers need, that tells us something, too.

Those behaviors are clues.

Sometimes the most valuable customer insight isn’t found in a survey response. It’s found in the frustration, workaround, or experience we’ve become so accustomed to that we no longer notice it.

So What Does This Have to Do with Strategy?

Everything.

A customer-centric strategy doesn’t start with a list of things customers have requested.

It starts with a clear understanding of the customers we serve, the outcomes they’re trying to achieve, and the value our organization is uniquely positioned to provide.

From there, we can make intentional decisions about where to focus our resources.

This is especially important because organizations cannot be everything to everyone.

And trying to be everything to everyone is a pretty effective way to exhaust your people, dilute your resources, and accomplish very little.

When we understand what customers truly value, we can make better choices about what to improve, what to innovate, what to stop doing, and where to invest.

We can also recognize that customer-centricity doesn’t mean giving customers everything they ask for.

Sometimes it means saying no to a request because there’s a safer, more effective, or more sustainable way to meet the underlying need.

That’s not ignoring the customer.

That’s understanding the customer well enough to create something better.

Of course, organizations have needs, too. A strategy must create value for customers while remaining operationally and financially sustainable. A solution that delights one customer but makes the organization unable to serve the next hundred isn’t much of a strategy.

The sweet spot is where customer needs, organizational capabilities, and sustainable value come together.

Don’t Just Ask. Get Curious.

The next time you’re reviewing customer feedback, developing a strategic plan, or considering a new initiative, I’d encourage you to challenge your team with one simple question:

“Are we solving the problem our customers have, or are we delivering the solution they asked for?”

There’s a difference.

And finding that difference requires curiosity, empathy, a willingness to challenge assumptions, and sometimes the courage to rethink what we’ve always done.

It means getting closer to our customers, understanding their experiences, and designing systems that make their lives easier.

It means recognizing that being customer-centric isn’t a department, a slogan, or a line in a strategic plan.

It’s a way of thinking.

Scott and Tammy explore several of these ideas in their recent episode of The Leadership Line, “What Does It Mean to Be Customer-Centric?” It’s worth a listen, especially if you’re thinking about how your organization balances customer expectations with operational realities.

And as you think about your own strategy, remember:

Your customers might be asking for faster horses.

Your job is to understand where they’re trying to go.

And then figure out the best way to get them there.

Preferably without adding another checklist.