Are We Solving Our Problem or the Customer’s Problem?

A team receives a customer request.

The request sounds familiar. The customer wants something improved, simplified, priced, redesigned or delivered differently. The team understands the topic quickly because they have seen similar situations before.

So the conversation moves fast.

We could use the existing product. We could adjust the process. We could respond with the standard proposal. We could simplify the internal workflow. We could position what we already have in a slightly different way.

Everyone is trying to be helpful.

The team sounds customer-focused. They are discussing the customer, responding to the request and trying to move quickly.

• But then the manager pauses and asks:

• What problem is the customer actually trying to solve?

• What is sitting underneath the request?

• Would the customer describe the problem this way?

• Are we making this easier for them, or easier for us?

The room becomes quieter.

The team may not be ignoring the customer. But it may have moved too quickly from customer request to internal solution.

That is the hidden tension in customer strategy.

A team can be sincere about helping customers, while still designing from the inside out.

The familiar answer can arrive too quickly

Familiar answers are useful.

They help teams move quickly, reuse capability, avoid unnecessary reinvention and respond consistently.

The problem is not familiarity.

The problem is when familiarity becomes assumption.

A customer raises an issue, and the team quickly recognises a pattern. The request sounds like something they have solved before. The organisation already has an answer. The process is known. The template is ready. The product exists.

So the team starts shaping the customer’s problem around the answer it already has.

This can happen quietly.

The team may ask, “What can we offer?” before asking, “What is the customer really trying to solve?”

It may ask, “How do we fit this into our process?” before asking, “What friction is the customer experiencing?”

It may ask, “How do we make this efficient for us?” before asking, “What would make this useful for them?”

When an organisation has a familiar hammer, many customer problems can start to look like nails.

Why inside-out solutions feel sensible

Inside-out solutions do not usually feel careless.

They often feel responsible.

The organisation has constraints: systems, processes, products, risk limits, budgets and timelines. Managers cannot ignore those realities.

There is also pressure to move quickly. A customer is waiting. A stakeholder wants progress. A team has limited time. Starting from an existing answer can feel efficient.

That is why this issue is hard to notice.

The team may believe it is being practical, reducing complexity and responding to the customer.

But practical does not always mean customer-useful.

A solution can be technically correct and still miss the problem. It can meet the stated request but ignore the deeper need. It can improve an internal process while creating new friction for the customer. It can solve the organisation’s problem of having something to sell, while leaving the customer’s real problem only partly addressed.

The deeper risk is that the team believes it has been customer-focused because the customer was mentioned throughout the discussion.

The practical lesson

The practical lesson is this:

Customer strategy should begin with the customer’s problem, not the organisation’s preferred solution.

That does not mean the organisation ignores its own constraints. It means the sequence matters.

First understand the problem.

Then decide what the organisation can credibly and responsibly do about it.

A manager can slow the conversation with a few practical questions:

• What is the customer actually trying to solve?

• Why are they asking for this now?

• What pressure, risk or frustration might sit underneath the request?

• What would the customer define as useful?

• Where might our process be creating friction?

• Are we offering this because it fits the customer, or because it fits us?

• What would change if we listened longer before proposing?

These questions help the team test whether it is solving the right problem.

They also help managers avoid becoming trapped by the first available answer. Sometimes the existing solution is right. Sometimes it only needs adjusting. Sometimes the real issue sits somewhere else entirely.

The value of the questions is that they create enough pause to find out.

Listening before solutioning

Listening before solutioning is not the same as delaying action.

It is a way to improve the action.

In customer work, the stated request is not always the full problem. A customer may ask for a feature, but the deeper issue may be confidence. They may ask for a faster process, but the real pain may be uncertainty. They may ask for a lower price, but the underlying concern may be risk, trust or proof of value.

If the team only responds to the surface request, it may miss what matters most.

This is why managers need to listen for context.

What happened before the request?

What decision is the customer trying to make?

What are they worried about?

What alternative are they comparing against?

What would make them feel that the solution worked?

The more clearly the team understands the context, the better the solution can become.

Not always bigger.

Not always more complex.

Often, simply more relevant.

The real work

The real work is not only having a solution.

It is making sure the solution belongs to the customer’s problem.

That means resisting the rush to fit every customer issue into the organisation’s existing answer. It means asking whether the team is solving for customer usefulness or internal convenience. It means being willing to listen longer before proposing, especially when the answer seems obvious.

This is also one of the core reflection questions behind 100 Questions Every Manager Should Ask: Where might we be solving our problem rather than the customer’s problem?

It is a simple question, but it marks an important shift. The manager is no longer only asking what the organisation can provide. They are asking whether what the organisation provides is genuinely useful for the customer’s situation.

A familiar answer can be valuable.

But it should still earn its place.

One question for reflection:

Where might we be reaching for a familiar answer before fully understanding the customer’s question?

Continue Your Leadership Journey

If this article was useful, explore the practical resources designed to help you become a more confident and thoughtful manager.

📘 100 Questions Every Manager Should Ask

A practical reflection companion with 100 questions for real management situations.

🎓 Riverstone Mini Courses

Short practical video courses with workbooks and tools you can apply immediately.

Stay Connected

Receive new articles and practical leadership ideas as Riverstone grows.