The symbol is not the experience
A network can repeat the same colour across every frontage and still deliver experiences that have little in common. Customers recognise the symbol, yet no longer know what to expect when they walk through the door. For me, that is where the real question begins: what are we actually making consistent? The appearance, the promise, or the ability to fulfil that promise?
I believe expansion should begin with that distinction. I am not arguing that every branch should invent its own version of the brand. I am arguing that leadership must be able to explain which commitments are shared, which choices belong locally and who resolves a situation that the manual does not yet cover. Without that clarity, a network becomes dependent on personal interpretation, however extensive its documentation may be.
Define the promise through observable behaviour
Imagine a fictional network that promises to resolve service enquiries quickly. One branch mainly serves people passing through; another depends on close relationships and longer visits. Requiring both teams to use precisely the same conversation may create artificial uniformity. Requiring that no customer leaves without understanding the next step protects a concrete part of the promise.
That difference does not make procedures unnecessary. It gives them a purpose. A useful procedure explains the action, the reason for it and the evidence that shows whether it has been completed. Once the form becomes the objective, a team can fill in every field and still leave the customer without an answer. Head office sees a completed record; the person receives an experience that does not match what was promised.
A standard should explain more than the action
I would begin by writing the promise in observable terms. Rather than demanding excellence as an abstract virtue, I would define what should happen when there is a question, a failure or a handover between teams. Who welcomes the customer? Who follows up? How is the outcome confirmed? The answer need not be lengthy. It needs to help different people recognise the same commitment.
This is the difference between a rule that supports judgement and a rule that replaces it. People need enough guidance to act with confidence, but not so much rigid instruction that they stop noticing the situation in front of them. Consistency is not the disappearance of judgement. It is the presence of a shared standard within which judgement can be used responsibly.
Put the right decisions in the right place
Some decisions can remain close to the customer: the organisation of the interaction, the choice of examples used in an explanation and the way validated information is presented. Other decisions change the network’s commitments and require someone with the authority and competence to take responsibility for them. Granting autonomy without distinguishing between these areas simply transfers ambiguity to the people on the frontline.
A person should not discover the limits of their responsibility only after being criticised. If leadership wants initiative, it must explain where initiative is welcome. If prior consultation is required in a particular situation, there must be a channel that responds. A system that demands approval for everything and takes too long to decide teaches teams to wait, even when faced with a straightforward problem.
Allow local testing without losing the common promise
In the fictional network, one branch might test a different order for explaining the service. Before the test begins, it should identify what is changing and what remains fixed: the conditions, the essential information, respectful treatment and the recording of the enquiry. Local experience can then teach the wider organisation something, rather than creating an invisible custom that is discovered only when it causes conflict.
A local variation should have a clear purpose and a defined way of being reviewed. It should not become permanent simply because nobody has challenged it, nor disappear merely because it looks unfamiliar to the centre. The question is whether it protects the promise, improves understanding and can be adopted without weakening the wider standard.
Treat exceptions as information
An exception may be a legitimate need, an error in application or a rule that has lost its usefulness. Classifying every departure as indiscipline closes the possibility of learning. Accepting every departure as a local preference dissolves the common commitment. Leadership must examine the specific situation and make its conclusion explicit.
That examination should include the person who carries out the work. A manual can seem clear to its author and ambiguous to someone working under pressure. Listening to that difference does not mean giving the decision to whoever complains most forcefully. It means gathering the information needed to decide well. The rule still has an owner; it also gains contact with reality.
Make decisions traceable
If an exception is accepted, it is worth stating whether it applies only to that case, begins a controlled test or changes the network standard. These are different decisions. A one-off authorisation should not circulate as a general rule through forwarded messages. The valid version must be easy to find, while the previous version should remain clearly identified as historical.
This is not administrative fussiness. It is part of protecting trust. Teams need to know which instruction governs their work, customers need a dependable experience and leaders need to understand why a practice changed. When decisions cannot be traced, the organisation starts to rely on memory, hierarchy and assumption. None of those provides a stable foundation for growth.
Judge how results are produced
The assessment of a branch can look at outcomes, but it also needs to understand how those outcomes were achieved. A good result produced through the extraordinary effort of one individual may conceal a serious weakness. If that person is absent, can the branch continue? If the question changes slightly, does the team understand the principle or does it have to guess?
I would make room for the examination of real situations. A resolved enquiry, a failed handover and a recent exception can reveal more than a general presentation about quality. The purpose is to understand the journey: the information available, the decision made, the intervention required and the response delivered. This can be done without exposing customers or turning the review into a public search for someone to blame.
The centre must carry its share of the discipline
It is also necessary to examine the work imposed by the network’s centre. Duplicate requests, contradictory instructions and changes introduced without preparation make it harder for branches to achieve the consistency that leadership demands. Discipline must travel in both directions. Those who define the standard must accept responsibility for its clarity, its maintenance and its realistic execution.
A central team cannot ask local staff to be precise while communicating carelessly itself. Every new requirement has a cost in attention, training and time. That cost may be justified, but it should be understood rather than hidden. A network becomes more coherent when its centre removes unnecessary friction instead of adding layers of control that make the promise harder to deliver.
Replicate capability, not performance theatre
Before multiplying a practice, I would ask whether another team can carry it out with the resources available to it. A demonstration led by the strongest professionals is not enough to answer that question. We need to observe transmission: what a new colleague understands, where they hesitate, what help they request and which mistake they can correct independently within their role.
This is where training reveals the strength of a standard. If a practice depends on instinct, exceptional energy or an informal relationship with a particular manager, it may be valuable but it is not yet ready to be replicated. The task is not to suppress expertise. It is to make the useful part of that expertise understandable and teachable to others.
Expansion should distinguish readiness
This care is not an invitation to suspend expansion indefinitely. It is a way of choosing more carefully what deserves to grow. Some processes are clear enough to replicate, others need further training and others still depend on unresolved decisions. Treating these three situations as though they were identical makes planning less accurate and places avoidable pressure on local teams.
Readiness should therefore be understood as more than enthusiasm or a successful demonstration. It includes clear ownership, accessible guidance, appropriate support and a way to recognise when the practice is no longer producing the intended result. Growth becomes safer when the organisation knows not only how to begin, but also how to correct, pause or adapt.
A shared practice, not a distant command
For me, a brand becomes consistent when it can maintain recognisable commitments without losing its ability to learn. The shared symbol should correspond to a shared responsibility. Procedures support that responsibility; autonomy makes it possible to fulfil it in different situations; review prevents the organisation from confusing habit with quality.
Growth also increases the distance between the people who formulate the promise and those who fulfil it every day. A good network works deliberately on that distance. It explains, listens, decides and updates. When the person serving the customer understands the commitment and knows where they may act, the brand no longer depends solely on surveillance from the centre. It becomes a shared practice.