Why Good Strategy Needs a Real Customer

A manager sits in a planning discussion.

The team is talking about the customer.

Customers want simplicity. Customers want value. Customers want better service. Customers want more digital options. Customers want speed, reliability and convenience.

The statements sound reasonable. No one strongly disagrees. Everyone can recognise some truth in them.

But then the manager asks a few simple questions.

Which customer?

In what situation?

What problem are they trying to solve?

What are they choosing between?

What would make them feel this was designed for them?

The room becomes quieter.

The team has been talking about customers, but not necessarily about a real customer.

That is the hidden tension in many strategy conversations. Customer language can sound specific while still being too vague to guide choices.

A strategy can sound logical inside the organisation and still be weak if it is not grounded in a real customer, with a real problem, in a real context.

“The customer” can be too vague

Many teams believe they are customer-focused because they talk about customers often.

They use customer language in planning documents, presentations and meetings.

That is a good starting point, but it is not enough.

“The customer” can become a vague idea. It can become an average customer, an internal picture of the customer, or a broad category that no one has truly tested.

When that happens, the team may design around assumptions.

They may assume customers want more features when they actually want less friction. They may assume customers want speed when they actually want confidence. They may assume customers want choice when they actually want guidance.

The problem is not that the team does not care.

The problem is that caring about customers in general is not the same as understanding a specific customer.

A vague customer creates vague strategy.

Why generic customers create generic strategy

Real customers are specific.

They have different situations, constraints, motivations, worries and definitions of value. They are trying to make progress in a particular situation.

A first-time manager looking for feedback advice is not the same as a senior leader managing organisational change. A small business owner choosing software is not the same as an enterprise procurement team. A runner training for a first 10K is not the same as a marathon runner chasing a personal best.

Even when two customers buy the same product, they may be buying it for different reasons.

One may value speed. Another may value reassurance. Another may value simplicity. Another may want to avoid making the wrong decision.

If a team only designs for “customers,” the offer can become too general. The message becomes broad. The experience becomes acceptable, but not distinctive.

That is why customer clarity matters to strategy.

Strategy is not only about what the organisation wants to offer. It is also about who the offer is for, what problem it solves, and why that customer would choose it over something else.

Without a real customer, the strategy may remain internally tidy but externally weak.

The practical lesson

The practical lesson is simple:

Good strategy needs a real customer because choices only become sharp when you know who you are designing for.

Once the customer becomes specific, decisions become clearer.

It becomes easier to decide what to offer, what to simplify, what to stop and what kind of value to emphasise.

A manager can begin with a few practical questions:

• Who is the specific customer we are designing for?

• What situation are they in?

• What problem are they trying to solve?

• What do they value beyond the obvious functional need?

• What would make them feel understood?

• What would make the experience easier, safer or more useful?

• Who are we not designing for?

These questions move the conversation from customer language to customer reality.

They also help managers avoid solving the organisation’s problem instead of the customer’s problem.

The organisation may want to sell an existing product, simplify an internal process or use a familiar solution. Those goals may matter. But if the customer does not experience the result as useful, the strategy will struggle.

Customer clarity does not mean the team gives every customer everything they want.

It means the team understands who matters most for this strategy, what they truly value, and what choices are needed to serve them well.

Designing for someone, not everyone

Trying to serve everyone can feel safe.

It keeps options open and makes the strategy sound more ambitious.

But broad appeal can quietly weaken relevance.

When a product, service or experience is designed for everyone, it often becomes less meaningful for the people who matter most.

Designing for someone is different.

It asks the team to become precise. It asks them to understand the customer’s context. It asks them to make choices that may not suit every possible buyer, but will matter more to the customer they have chosen to serve.

That is not a weakness.

That is strategy.

A clear customer gives the team something practical to test against.

Would this customer understand the offer?

Would this solve their actual problem?

Would this reduce the friction they experience?

Would this feel relevant compared with their alternatives?

Would they recognise that this was designed with them in mind?

Those questions make strategy more grounded.

They also make it more human.

The real work

The real work of customer strategy is moving from “the customer” to a real person, real problem and real context.

That means not hiding behind broad customer language. It means asking better questions before designing the answer, and listening closely enough that the customer becomes more than a segment, market or assumption.

This is also one of the core reflection questions behind 100 Questions Every Manager Should Ask: Who are we really designing for?

It is a simple question, but it marks an important shift. The manager is no longer only asking what the organisation can offer. They are asking who the offer is meant to serve and what would make it genuinely useful to them.

Good strategy needs a real customer because real value is created for someone specific.

Not an average.

Not an abstraction.

Not a convenient internal assumption.

A real customer.

One question for reflection:

When your team says “the customer,” who exactly do you mean?

If this reflection was useful, join the Riverstone mailing list for practical leadership reflections and updates as the Riverstone resource library develops.