A network can repeat the same color across every storefront and still deliver experiences that have little in common. Customers recognize the symbol, but they 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 trying to make consistent? The appearance, the promise, or the ability to keep that promise?
I believe expansion should begin with that distinction. I am not arguing that every location should invent its own version of the brand. I am arguing that leadership must be able to explain which commitments belong to everyone, which choices can be shaped locally, and who decides when a situation falls outside the manual. Without that clarity, a network becomes dependent on personal interpretation, even when it has extensive documentation.
Consider a fictional network that promises to resolve customer questions quickly. One location may serve mostly people passing through, while another may depend on close relationships and longer visits. Requiring both teams to follow exactly the same conversation can create artificial uniformity. Requiring every interaction to end with the customer understanding the next step protects something much more meaningful: a concrete part of the promise.
That distinction does not make procedures unnecessary. It gives them a purpose. A useful procedure explains the action, the reason behind it, and the evidence that shows whether it was fulfilled. When the form becomes the objective, a team can complete every field and still leave the customer without an answer. Leadership receives a clean status; the person in front of the brand receives an experience that does not match what was promised.
I would begin by writing the promise in observable terms. Instead of demanding excellence as an abstraction, I would define what should happen when a customer has a question, when something goes wrong, and when responsibility passes between teams. Who welcomes the person? Who follows up? How is the outcome confirmed? The answer does not need to be long. It needs to help different people recognize the same commitment.
Some decisions can remain close to the customer: how the interaction is organized, which examples are used to explain an approved service, or how validated information is presented. Other decisions change the network's commitments and require someone with the authority and competence to own them. Granting autonomy without separating these areas simply transfers ambiguity to the people on the front line.
No one should discover the limits of their responsibility only after being reprimanded. If leadership wants initiative, it must explain where initiative is welcome. If prior consultation is required in a particular situation, leadership must provide a channel that can respond. A system that demands approval for everything and takes too long to decide teaches teams to wait, even when the problem is simple.
In the fictional network, a location might test a different order for explaining a service. Before the test begins, the team should identify what changes and what remains protected: the conditions, the essential information, respectful treatment, and a record of the question. That way, a local experience can teach the organization something instead of creating an invisible custom that is discovered only after it causes conflict.
An exception may reflect a legitimate need, a mistake in application, or a rule that has lost its usefulness. Treating every exception as disobedience closes the possibility of learning. Treating every exception as a local preference dissolves the common commitment. Leadership needs to examine the specific situation and make the conclusion explicit.
That examination should include the person who carries out the work. A manual can seem perfectly clear to the person who wrote it and remain ambiguous to someone working under pressure. Listening to that difference does not mean allowing the loudest complaint to decide policy. It means gathering the information required to make a better decision. The rule still has an owner; it also gains contact with reality.
If an exception is accepted, the network should state whether it applies only to that case, opens a controlled test, or changes the standard for everyone. These are different decisions. A temporary authorization should not circulate as a new general rule through forwarded messages and informal explanations. The valid version must be easy to find, while the previous version should remain clearly identified as historical.
A location can be evaluated by its outcomes, but leadership also needs to understand how those outcomes were achieved. A good result produced through the extraordinary effort of a single person may conceal a fragile system. If that person is absent, can the team continue? If the question changes slightly, does the team understand the principle or does it have to guess?
I would make room for the review of concrete situations. A question that was resolved well, a handoff that failed, and a recent exception can reveal more than a generic presentation about quality. The purpose is to understand the path: what information was available, what decision was made, what intervention was needed, and what response was delivered. That review should protect customers and avoid turning reflection into a public search for someone to blame.
The network should also examine the work imposed by its own central leadership. Duplicate requests, contradictory instructions, and changes introduced without preparation make it harder for local teams to achieve the consistency leadership demands. Discipline has to move in both directions. Those who define the standard must accept responsibility for its clarity, its maintenance, and its realistic execution.
Before multiplying a practice, I would ask whether another team can carry it out with the resources it has been promised. A demonstration by the strongest professionals is not enough to answer that question. Leadership needs to observe transmission: what a new person understands, where that person hesitates, what help is requested, and which mistake can be corrected independently within the role.
This is not an argument for suspending expansion indefinitely. It is a way to choose more carefully what deserves to grow. Some processes are clear enough to replicate. Others need training. Still others depend on decisions that have not yet been resolved. Treating these situations as if they were identical makes planning less precise and places avoidable pressure on local teams.
A practice is not ready to travel merely because it works in its original setting. It is ready when its purpose can be explained, its essential elements can be recognized, its limits are understood, and its performance does not depend on a handful of exceptional individuals. Replication should spread capability, not just appearance.
For me, a brand becomes consistent when it can preserve recognizable commitments without losing the ability to learn. The common symbol should correspond to a common responsibility. Procedures support that responsibility; autonomy makes it possible to fulfill it in different circumstances; review prevents the organization from confusing habit with quality.
Growth also increases the distance between the people who formulated the promise and the people who fulfill 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 action is permitted, the brand no longer depends only on central surveillance. It becomes a shared practice.
The strongest networks are not those that eliminate every local difference. They are the ones that know which differences are harmless, which reveal useful learning, and which undermine the promise. Their consistency does not come from forcing every interaction into the same shape. It comes from making sure that customers can recognize the same responsibility wherever the brand meets them.
Adaptação editorial da peça publicada em https://insights.masterfranchisee.com/noticias/uma-marca-consistente-precisa-de-saber-onde-pode-mudar-pt-pt/index.html. Não é uma tradução literal do título.