In this essay 16 sections
A brand is what people expect you to do because of what they have seen you do before. Design helps them recognise the name. Marketing introduces the offer. The work decides whether either deserves to be remembered.
I want a business to be known for something useful. That requires more than being visible. A customer needs to understand what is being offered, receive what was agreed and know where to go when something needs attention. Those experiences accumulate. So do their opposites.
This is why I am interested in the ordinary parts of business that rarely appear in a brand presentation: whether a question gets answered, whether materials arrive when the team needs them, whether a product suits the person buying it, and whether someone takes responsibility after the transaction. These details determine what the name comes to mean.
I am not arguing against promotion. I promote my work and my businesses. I think capable people should explain what they are building. But promotion creates an expectation that somebody eventually has to meet. The stronger the claim, the more important the work behind it becomes.
Evidence survives the announcement.
On 5 September 2026, I posted about walking past fencing I had imported more than a decade earlier. I had personally poured the concrete into its feet. Seeing it still there made a straightforward point about taking the work seriously.
That observation is limited. One piece of fencing does not establish the quality of every product or project connected with me. It does give me a concrete example of work remaining visible long after the original transaction. I find that more interesting than a description of quality with nothing attached to it.
A business should want evidence that can exist independently of its current advertising. A finished product, a clear record of what was supplied, an answer that helped a customer make a decision: each gives someone a reason to remember the business beyond the fact that it appeared in front of them.
The useful question is what remains when the presentation is over. If the customer has only a slogan, there is very little to inspect. If they have an experience they can describe, the name begins to carry information. They can explain why they would use the business again, or why they would not.
This should influence what a founder pays attention to. The launch matters, but it is not the only event. How something behaves after delivery, how questions are handled and whether the original description remains fair are all part of the record. A reputation develops over that longer period.
Recognition is only the beginning.
There are several different things people call a strong brand. They might mean that the name is familiar, that the design is distinctive, that customers associate it with a particular product, or that people trust it. Those are related, but they are not interchangeable.
Familiarity can help someone notice an offer. It does not tell you what they expect from it. A person can recognise a company immediately and still avoid buying from it. Another company may be known by fewer people but have a very clear place in the lives of the customers it serves.
I would separate the questions. Do people know we exist? Do they understand what we do? Do they think the offer is relevant to them? What evidence would give them confidence to proceed? What actually happens when they do? A campaign might help with the first questions while an operating problem undermines the last.
That distinction prevents a lot of confused spending. If customers cannot find the business, greater visibility may be useful. If they find it but cannot understand the offer, clarity is the job. If they understand it and keep encountering the same delivery problem, a new identity will leave the important issue untouched.
A name becomes valuable when recognition carries a useful expectation. The aim is not simply to make people say that they have heard of you. It is to make the right people understand why dealing with you could solve a problem they actually have.
Make the promise specific enough to examine.
Words such as quality, service and value are easy to agree with because they can mean different things to different people. A business needs to explain what they mean in the particular offer. Otherwise, it leaves the customer to fill in the gaps, then acts surprised when the result is judged against a different expectation.
For a product, that might involve dimensions, materials, inclusions, limitations and the intended use. For a service, it might involve the work included, how the process runs, who the customer deals with and what remains the customer’s responsibility. The right detail depends on what is being sold.
Consider a hypothetical supplier advertising fast delivery. A customer may understand that to mean dispatch today, arrival tomorrow or simply a shorter lead time than the alternatives. Those are different promises. The supplier should explain the available stock, the dispatch process and what is known about the delivery timing before the customer relies on an assumption.
That explanation does not have to be long. It has to remove the uncertainty that matters to the decision. A concise answer to the right question is better than a page of reassuring adjectives. If a detail can change the customer’s choice, hiding it behind attractive language creates a problem for later.
Specificity also helps the team. People cannot deliver a standard consistently if nobody can describe it. A clear promise gives sales, operations and service something in common. They may perform different jobs, but they should recognise the same result at the end.
Establish fit before increasing persuasion.
On 7 September 2026, I wrote that a home has to function in everyday life. I mentioned layout, storage and the journey to work, and said I wanted Williams Corporation to explain the trade-offs honestly. No individual home suits everybody.
That is a useful discipline for any business. The offer needs a customer for whom its strengths matter and its limitations are acceptable. A successful sales conversation should help establish that fit. It should not depend on treating every objection as something to overcome.
Imagine someone considering a compact home. They may value the location and lower amount of space to look after, but need to check whether their furniture, work routine and possessions fit. Showing how the rooms work is useful. Insisting that the home is perfect for everyone is not.
The same principle applies to a service package. One customer may want a defined, repeatable service with a clear price. Another may need extensive custom work. Neither customer is wrong. The business needs to know which promise it can deliver and make the boundary clear.
A poor fit can create a dispute without either side initially intending to mislead the other. The seller hears enthusiasm. The customer hears flexibility. Important differences remain unspoken until delivery makes them impossible to ignore. A better conversation brings those differences forward while there is still a useful choice to make.
I would rather a customer understand an honest limitation than discover an impressive claim was doing more work than the product. There is a longer discussion of the housing side of this in Density Has to Work at the Front Door.
The customer experience starts before the customer sees it.
Another post on 7 September 2026 concerned a crew waiting for materials. My point was that better coordination can allow more work to be completed in the same hours without reducing quality. It is a practical way to think about productivity, rather than simply asking people for more effort.
There is a reputation question inside that observation. Much of what the customer eventually experiences is determined by work they never watch. Information has to travel. Someone has to order the right item, confirm the timing and make sure the next team can use it. A delay becomes visible at the end, even if its cause began much earlier.
The customer does not need to understand every internal handover. They do need the organisation to take ownership of the result. Explaining that another department has not replied may accurately describe the problem, but it does not by itself help the person waiting.
Imagine a supplier’s salesperson confirming an order while the fulfilment team is working from a different specification. Each person might believe they have done their part. The customer receives the mismatch. From outside the business, the division between those responsibilities is largely irrelevant.
This is why a brand standard cannot live only in the marketing team. Every handover that affects the promise belongs in the discussion. The people closest to those handovers often know where information is missing or repeatedly misunderstood. Listening to them is more useful than asking them to compensate indefinitely with personal effort.
Customers remember the unresolved part.
A business can complete most of a job well and still leave someone with a frustrating experience. The remaining issue may be small in the company’s account of the project but important in the customer’s use of the result. An unanswered question can also make it difficult for the customer to know whether the company considers the work finished.
I would be careful with the phrase nearly done. It can describe genuine progress, or it can conceal an obligation nobody has clearly accepted. The distinction is whether the remaining work is named, owned and connected to a next step that the customer understands.
Consider a hypothetical installation that is complete except for an item requiring a return visit. The installer has packed up. The office has sent the invoice. The customer knows something remains, but has no date and no contact who appears responsible. Each internal milestone looks reasonable. The overall experience is unfinished.
A useful close-out would record the outstanding item, the person responsible, what must happen before the visit can occur and when the customer will next receive an update. If a date cannot yet be confirmed, say that and explain the next decision. Do not supply a date merely to end the conversation.
This is not a promise that every problem can be resolved instantly. It is a standard for making the unfinished part visible. People can deal with a clear account of a problem more intelligently than an indefinite assurance that somebody is looking into it.
Use a complaint to locate the gap.
A complaint contains at least two questions. What does this customer need now? What does the experience tell us about the business? The first deserves a practical response. The second deserves enough curiosity to discover whether the same problem is being created elsewhere.
Those questions should not be collapsed into an argument about who is a good person. Someone can be disappointed without every part of their account being correct. A business can believe it acted reasonably and still discover that its explanation was confusing. Start with what was represented, what was understood and what happened.
Suppose a hypothetical customer thought an accessory was included because it appeared prominently in the product photograph. The written offer says it is separate. That may explain the transaction, but it should also prompt a review of how the offer is presented. Are customers given a clear opportunity to understand the distinction before deciding?
The response should be appropriate to the actual circumstances and obligations. I am not suggesting that a business promise the same remedy for every complaint, or that an essay can decide a contractual dispute. I am suggesting that defending one transaction does not answer whether the next customer will encounter the same avoidable confusion.
A useful internal record keeps the facts, the response and any change to the process together. It does not need to turn the customer into an anecdote circulated around the office. The purpose is to resolve the issue and improve the promise, not to give the team another reason to dislike people who raise problems.
Recovery needs an endpoint.
An apology can acknowledge an experience. It cannot, on its own, finish the practical work. When a response requires an action, somebody needs to own that action through to an appropriate endpoint.
I would want the person handling a problem to distinguish acknowledgement, investigation, decision and completion. These are different stages. Telling a customer that their message has been received is useful, but it should not later be counted as evidence that the issue was resolved.
In a hypothetical delivery problem, the first task may be to establish what arrived and what did not. The next may involve confirming the correct replacement or another appropriate response. The final task is to check the agreed action happened. A long email exchange is not a substitute for that sequence.
Updates should contain information the customer can use. What is known? What remains uncertain? Who is acting? When will the next update occur? If the circumstances change, the explanation should change with them. Repeating the original estimate after it has become implausible makes the customer do the work of discovering the truth.
There is a limit to what any one staff member can decide. That is another reason to define a route for decisions rather than leaving them to improvise under pressure. A person should know when to seek help and what information the decision-maker needs. The customer should not have to start the entire account again each time responsibility moves.
A promise must survive a handover.
A customer’s understanding of the offer should not depend on one unusually experienced person being available. If the business needs that person to interpret every previous conversation, the promise is stored in memory rather than in a form the organisation can use.
The handover needs enough information to preserve the decision. What is being supplied? What has been confirmed? Which options were chosen? What did the customer explicitly say mattered? Are there exclusions, dependencies or unanswered questions that the next person needs to understand?
More information is not automatically better. A long record of every message can still leave the important decision buried. The team needs a concise account of the current agreement, with the supporting detail available where required. People should not have to reconstruct a promise from an inbox every time they act.
Changes are particularly important. An earlier version of a specification may remain plausible even after it has been replaced. If two teams can each find a document that looks current, the business has created a predictable source of disagreement. Make the current version clear and make superseded decisions recognisable.
There is also a human part. The person receiving the work should be able to say that something is missing before they are treated as fully responsible for it. A handover is more useful when it confirms understanding than when it merely transfers a file. I discuss the wider question of ownership in The Founder Is Not the Inbox.
One name can cover several different promises.
When a group operates several businesses, a familiar name can make it easier to introduce a new offer. It also makes clarity more important. Customers need to understand which business they are dealing with, what it provides and where responsibility sits.
My ventures directory distinguishes companies, brands, programmes and my relationship to them for that reason. A development business, an education business and a product supplier are not identical services simply because I am connected with each of them.
A shared identity can communicate a common ambition or set of values. It should not obscure the practical differences in the offer. The customer still needs the right information, the right contact and a clear account of the business responsible for their transaction.
Imagine a customer who recognises a group name from one service and approaches another part of the group. That recognition may open the conversation. The second business still has to explain its own process and establish that it can meet the customer’s need. Familiarity is an introduction, not evidence of every capability.
I would be especially cautious about borrowing the strongest claim from one activity and applying it to the entire group. Experience in one area can be relevant elsewhere, but the connection should be explained rather than assumed. A directory becomes more credible when each entry describes the actual relationship instead of treating every logo as the same kind of ownership or responsibility.
Be consistent without refusing to improve.
Consistency is valuable when it makes the customer’s experience dependable. It becomes a weakness when the business uses it to defend a process that no longer works. Keeping a promise and preserving every old method are different responsibilities.
A company may need to change its product, opening hours, service process or the way it communicates. The question is whether people understand what is changing and how existing commitments will be handled. A change can be sensible while its communication is poor.
For a hypothetical recurring service, a new booking process might reduce confusion. Existing customers still need to know where to book, what happens to appointments already arranged and who can help if the new process does not work for them. Launching the system is only one part of making the change real.
The team also needs to understand the reason. If staff hear only that a new rule applies, they may follow it literally in situations it was not designed to handle. Explain the result the change is intended to produce and where judgement remains necessary.
I would judge consistency at the level of the promise: accurate information, clear responsibility and a useful result. The methods should improve as the business learns. A reputation for reliability should not require pretending that the first version of the operating model was the final one.
Good marketing still matters.
The strongest objection to an argument about reputation through work is that good work can remain unknown. A capable business can lose customers to a competitor that explains its offer more clearly. People cannot choose a product they have never heard of, and they cannot inspect every supplier personally before making a decision.
I agree. There is no virtue in making a useful business difficult to discover. Clear design, good photography, direct language and a sensible path to an enquiry can all help someone understand what is available. Presentation is part of the experience, not an embarrassment to be tolerated.
The distinction is between presenting the evidence well and substituting presentation for evidence. Photographs of completed work, accurate descriptions and specific examples give the audience something to consider. A dramatic claim without a clear basis asks them to rely on confidence alone.
A business should also have the courage to say what it does well. Being precise is not the same as being timid. If the team has a useful capability, explain it. If the product solves a particular problem, show how. Strong communication makes the substance easier to understand.
What I would resist is the idea that operational problems must wait until the brand work is finished. The two should inform each other. Customer questions can improve the website. Delivery limitations can make the offer more accurate. Evidence from completed work can make promotion more persuasive without making the claims larger.
Marketing earns its place by helping the right people make a better-informed decision. The business then has to honour the expectation it helped create.
Publish only what you can stand behind.
A website is easy to add to. It is harder to keep every claim current as the business changes. Products move, roles change and projects progress through different stages. A statement that was accurate when it was written can become misleading if nobody revisits it.
The practical answer is to give important claims an owner and a source. Where did the figure come from? What does it include? When was it checked? What would cause it to need updating? These questions are especially useful when several people contribute to the same site or presentation.
Completed work should be distinguished from proposed work. A person’s role should be described accurately. A photograph should not imply that a project is finished if it is a rendering of an intended result. Customers deserve to know what they are looking at without becoming investigators.
If something is wrong, correct it plainly. A correction does not need to become a performance. It needs to leave the audience with a more accurate understanding. Where someone may already have relied on the earlier information, the business should consider how to reach them appropriately rather than assuming a quiet edit solves every consequence.
That applies to personal branding as well. I can hold a strong view without claiming certainty about every supporting detail. I can describe my connection to a business without inflating the role. The point of a personal website should be to make the person easier to understand, not to surround ordinary facts with unnecessary grandeur.
Measure the experience at the edges.
Averages can be useful, but they can also make a frustrating experience disappear. If most enquiries receive a reply quickly while a small group is repeatedly missed, the headline number may look reassuring. The people in that group still experience the business as unresponsive.
I would look at the points where work changes hands or waits for a decision. How many enquiries have no clear next action? Which orders are waiting for information? Which issues have been acknowledged but not resolved? What has passed its promised update date? These are practical questions about obligations, not a demand for an elaborate dashboard.
Choose measures that relate to the promise. Counting messages sent may tell you that the team is active, but not whether the customer received a useful answer. Counting completed tasks may hide that the final result is still waiting on one unresolved item.
Combine the totals with a few actual journeys. Follow an enquiry from the first question to the eventual outcome. Look at what the customer was told along the way. Ask the people doing the work where they had to improvise or chase missing information. The story of that journey can explain something a total cannot.
Keep the review proportionate and respectful. The purpose is to improve delivery, not to create surveillance for its own sake or expose customer details unnecessarily. A useful measure directs attention to a decision someone can make. If the same problem appears on a report indefinitely without changing the work, the report has become decoration.
A practical brand review starts with five promises.
If I were reviewing a business from this perspective, I would start with five promises that matter to its customers. They might concern the product, the price, the process, the timing or the support after delivery. The exact list should come from the offer, not from a generic brand framework.
Write each promise as a sentence a customer could understand. Then identify where they encounter it: a website, a proposal, a conversation, a photograph or an assumption encouraged by the way the offer is presented. Include promises made informally. The customer does not necessarily distinguish between the official statement and what a salesperson said.
For each one, follow the work required to meet it. Name the people or teams involved, the information they need and the points where responsibility moves. Ask what evidence shows that the result was delivered. An internal tick-box may be part of that evidence, but it should correspond to something real.
Next, examine a small number of recent journeys. Choose more than the easiest success. Include an ordinary transaction, an exception and an unresolved issue if one exists. The aim is to understand the range of experience, not to produce a flattering sample.
Decide what needs to change first. Sometimes the claim is too broad. Sometimes the process is unclear. Sometimes the promise is reasonable but the team lacks the information or authority to deliver it. Each problem requires a different response.
Finish with an owner, an action and a review point. The result should be a better explanation or a better experience that someone can observe. Another presentation about being customer-focused would leave the original question unanswered.
Give the name something to mean.
I like the idea of building a name that stands for useful work. It does not require universal approval. People will have different preferences, priorities and views. The goal is to be clear about what is offered and dependable about the commitments that follow.
The work has to survive ordinary conditions: a staff member being away, a customer asking an unexpected question, a delivery changing, a detail requiring another decision. A brand becomes more credible when the organisation can handle those situations without the promise dissolving into a collection of excuses.
That standard is demanding because it is ongoing. One good result does not finish it. Neither does one mistake automatically define the whole business. What matters is the record being built, the way problems are addressed and whether the next customer receives the benefit of what has been learned.
There is room for good design, confident promotion and a distinctive voice in that work. They should make the substance more visible. They cannot supply the substance by themselves.
The name on the sign is the beginning of the introduction. What people can rely on after the introduction is the part worth building.