-
We Are Spark
-
Insights
-
Brand Strategy
-
Where the Brand Promise Meets the Customer
Hi! Click one of our member below to chat on WhatsApp
A customer reads that a service is simple. They complete the online form, receive a confirmation and wait. When they call for an update, they are asked to explain the request again. The customer has to repeat work because the service team cannot see what has already been submitted.
Brand decisions reach further than the words used in a campaign. They influence what people expect when they contact an organisation, apply for a service or need help. Those expectations become a practical responsibility for the people designing the service and the teams delivering it.
For a brand leader, the useful question is where the promise becomes something a customer can recognise. That means looking at the ordinary details of an interaction, including the ones that rarely appear in a brand presentation.
A positioning statement gives an organisation a direction. Service teams still need to understand what that direction means in their work. If the promise is clarity, a customer should be able to understand the requirements, know what happens next and find an explanation when something changes.
Consider an application that requires additional documents. A message saying that the submission is incomplete leaves the customer to investigate. A message naming the missing document, explaining why it is needed and showing how to submit it gives the customer a way forward. The brand guidance needs to help the team write the more useful response.
This is where brand guidance can become more practical. Examples of real communications help teams apply a principle to a situation. They also reveal whether the principle is sufficiently clear to guide a decision.
A customer may encounter a campaign, a website, an automated message and a service representative within the same afternoon. Inside the organisation, those moments can belong to different teams. The customer still expects the information to agree.
Start with a specific task and follow it through. Ask what the customer knows at each point, what they are being asked to do and whether the next team can see what has already happened. Include the point where the usual process fails. A delayed delivery or rejected application can expose gaps that a straightforward transaction does not reveal.
The aim is to identify the decisions that affect the customer's understanding. Sometimes the language needs work. Sometimes the service policy is unclear, or the person answering the enquiry cannot access the relevant information. Treating every issue as a design correction would leave those causes unresolved.
A brand system should help the people writing and delivering communications make sound choices. A service email needs a different structure from an investor presentation, although both should feel as though they come from the same organisation.
Useful guidance shows that range. It explains how to handle a difficult message, describe a requirement or present a complex subject without losing the organisation's voice. It gives teams approved examples and makes clear which details they can adapt.
The people using the guidance should have a part in testing it. Ask someone who handles customer enquiries to work through a draft response. Their questions may reveal an ambiguity that a design review would miss. Ask the content owner whether the information can stay current once the new template is in use.
A review may identify a problem between functions. Marketing owns the promise, the digital team owns the form and operations owns the response. An improvement needs someone able to bring those responsibilities together.
Record the issue in terms of the customer's task. For example, a customer cannot tell whether an application is waiting for review or waiting for information. That description gives the teams a specific problem to solve together.
Agree how the change will be checked. Can a person using the service explain the status in their own words? Can the service team answer the next question without sending them elsewhere? These are specific tests that connect the brand intention with the experience.
There is no need to redesign every interaction at once. Choose a moment where the promise matters and where the organisation can make a concrete improvement. An acknowledgement email, a service request or the explanation of a decision can provide a manageable starting point.
Bring the relevant teams into the review, make the change and examine what happens when people use it. The learning can then inform other parts of the service. Over time, the brand becomes easier to recognise because its promises are reflected in the way the organisation responds.