Customer research for branding: turning observation into useful decisions

Customers often describe what they want in familiar terms: quality, convenience, a business they can trust. Those are useful starting points, but they leave plenty to understand.

What makes a service feel reliable before someone has used it? What information helps them choose? Where do they hesitate?

For me, customer research is most useful when it helps connect those questions to a decision the business needs to make. It gives the team a better basis for deciding what to change.

Consider a hypothetical service business that receives enquiries, sends proposals and then hears very little. The team suspects its identity doesn’t look established enough. The following steps show how research could help explore that concern before the business commits to a redesign.

Define the decision and leave room for discovery

Start with what the business needs to understand: why do interested prospects stop before committing?

I’d keep that question open at first. Asking whether customers would prefer a more premium identity could steer the conversation towards appearance before we understand what influenced their choice.

Write down the current explanation and the evidence behind it. Sales feedback, unanswered proposals and recurring questions can help identify what to investigate.

Leave room for unexpected findings. Observation can change the brief itself, particularly when it reveals a difficulty the team hadn’t considered.

Speak to people who made different choices

For this business, relevant participants might include recent customers, prospects who chose another provider and people who postponed the purchase.

Each can explain a different outcome. Satisfied customers can describe what gave them confidence. People who went elsewhere may reveal information or reassurance they couldn’t find.

Begin with a manageable group whose experiences relate to the question. Review what you’re learning and whose perspective is still missing. A small set of interviews can reveal useful patterns, though it won’t tell you how common they are across the whole market.

Explain the purpose of the conversation, obtain permission before recording and agree how responses will be used and stored.

Reconstruct a real decision

Ask about the last time someone chose this kind of service. A specific experience gives you details to explore:

• What prompted them to start looking?
• Which options did they consider?
• What did they need to know before making contact?
• What happened when the proposal arrived?
• Who else was involved in the decision?
• What helped them proceed, choose differently or wait?

When someone describes a provider as “professional” or “expensive”, ask what led to that impression. Their explanation may be more useful than the description itself.

These conversations also help with understanding the alternatives customers consider. That might include handling the work internally or leaving things as they are.

Watch where understanding breaks down

Ask someone to walk through the website or a sample proposal. Can they explain what is included, what happens next and what they would need to provide?

I’d give them time to work through it before offering an explanation. If we step in too quickly, we can miss the difficulty we’re trying to understand.

For example, a participant might read the proposal twice and ask who prepares the content. Record that question before deciding what it means. The answer could be missing, difficult to find or expressed in unfamiliar language.

Another person might compare the fee with a much smaller service package. Explore whether they understand the difference in scope and whether that difference matters to them.

Look for patterns and possible explanations

Suppose several conversations suggest that prospects cannot judge how much work the project will require from their team. Some worry about gathering content. Others need to coordinate colleagues before committing.

That gives the business another explanation to investigate alongside its concern about looking established.

Keep the reasoning easy to follow. Record what people said or did, what might explain it and what you could change or test in response.

Here, repeated questions about content and approvals might suggest uncertainty about workload. The next step could be a proposal that explains responsibilities and required inputs more clearly.

Include different experiences too. A prospect who understood the scope but couldn’t afford the fee may need a different response.

Turn the learning into a brief

The findings give the team a more specific task: help prospects understand what the project will require from them. The brief should explain responsibilities, required inputs and project stages before asking people to commit.

That could affect proposals, sales conversations, the website or how the service is delivered. Agree who will take responsibility for each change.

For the website, the findings inform decisions about audience needs, content and next steps. If customers are concerned about a genuinely demanding process, the business may also need to make that process easier.

There’s still room for creative judgement. Research can help us question accepted expectations and consider improvements people may not have thought to request.

Test the response before expanding it

Create a revised proposal or a small set of pages. Ask relevant participants to explain the scope, responsibilities and next step in their own words.

I’d start with the smallest useful version. Build enough to answer the question before spending time refining the whole experience.

In this example, the immediate test is whether the explanation becomes clearer. Any effect on sales conversion needs tracking over time, alongside factors such as price, lead quality and timing.

The business may still decide to improve its identity. It can now approach that work with a clearer understanding of what customers need and what the design should help them do.