How do you get the whole network to adopt a head office decision?
In a multi-site network, making a decision is often the easy part. Updating a procedure, changing a standard, rolling out a new tool or adopting a new sales method can be decided relatively quickly. The difficulty starts afterwards. A decision made at head office is not automatically a practice applied in the network’s stores, branches or sites: between the two, there is a gap that can be considerable.
The instruction may have been sent, the information shared, the document made available and the meeting held. Yet a few weeks later, some locations apply the new practice perfectly, others partially, and others not at all.
This is a very common problem in growing networks. The more locations there are, the greater the risk of a gap between the central decision and local execution. And that gap ends up directly affecting quality of execution, the customer experience, brand consistency and sometimes even financial performance.
The question then becomes: how do you turn a decision made at head office into a new practice that the whole network actually adopts?
The 6 steps at a glance
- Decide: translate the decision into observable behaviors.
- Communicate: repeat the message in several forms and through several channels.
- Explain: share the why as much as the how.
- Support: help teams put the practice into action in the field.
- Check: measure actual application, not just distribution.
- Adjust: take field difficulties and feedback into account.
Sharing a decision does not mean it gets adopted
Let’s take a simple example. A brand decides to change one step of its customer journey. The new procedure is formalized, an email is sent to all managers, the document is placed in the document library and the topic is discussed during a network meeting. From head office’s point of view, the job may seem done: the information has gone out.
From the field’s point of view, however, several things can still happen. Some managers will understand the new rule immediately, others will read it too quickly, and others still will assume it only applies to certain situations. Some teams will keep using the old method out of habit, and some locations will run into a specific case that had not been anticipated. A few weeks later, the same procedure will be applied in five different ways.
The problem doesn’t necessarily come from a lack of goodwill. It often comes from confusing two very different steps: sharing information and establishing a new practice. The first is relatively easy to measure; the second takes more work.
Sharing vs. adoption: the difference
- Sharing means making sure the information has gone out: email sent, document published, meeting held.
- Adoption means making sure the practice is applied: the same way, in every location, and over time.
A new practice has to go through several steps
For a decision to truly become a network standard, it has to go through several phases: decide → communicate → explain → support → check → adjust.
Each of these steps addresses a different problem. Deciding defines the new rule, communicating makes it visible, and explaining clarifies why it exists and how to apply it. Supporting helps teams put it into practice, checking measures its actual adoption and adjusting takes difficulties and field feedback into account.
When one of these steps is skipped, the gap between intention and execution grows.
1. Decide clearly before communicating
Even before communication starts, the decision must be clear enough. That sounds obvious, but many difficulties start here, with an instruction decided in terms that are too general:
“Starting next month, all stores must improve customer follow-up.”
The intention is understandable, but it says nothing concrete. What changes? Who has to do what, starting when, with which tools and how often? And above all, what will show that the new practice is being applied correctly?
The vaguer the decision is at the outset, the more its interpretation will vary in the field. In a network of 10 locations, these gaps can still be corrected fairly easily. In a network of 100 or 300 sites, they can quickly become structural. A good operational decision must therefore be translated into observable behaviors.
Before sharing a decision, check that it answers these questions
- What? What concretely changes.
- Who? The people and locations concerned.
- When? The start date and frequency.
- How? The tools and method to use.
- How will we check? The criterion that shows the practice is applied.
2. Communicating is not just sending a message
Once the decision has been made, it obviously needs to be communicated, but the channel used plays an essential role. An email makes a decision official, a document library keeps the procedure on record, a meeting explains what is at stake, training material details the new method and an FAQ answers recurring questions.
The problem arises when a single channel is considered enough. In reality, an important new practice often needs to be repeated in several forms, because not everyone reads the same content at the same time. A store manager may have seen the email without having had time to discuss it with their team. An employee may have attended a training session but no longer remember the exact procedure three weeks later. A location may also join the network after the new rule was launched.
Communication must therefore be designed as a system, not as a one-off event. That is the whole point of facilitating day-to-day communication with your franchisees and centralizing your network’s information in a space where everyone knows where to find the right version.
3. Explain the “why” as much as the “how”
An imposed rule is often applied to the bare minimum. An understood rule is far more likely to be truly adopted. This is especially true in networks made up of independent entrepreneurs or local managers with a high degree of autonomy.
Saying “From now on, you must use this new process” does not have the same impact as explaining:
“We found that the old process generated too many errors, lengthened lead times and created gaps between locations. Here is what we are changing and why.”
Giving meaning to the decision makes buy-in easier. There’s no need to justify every detail for hours, but when teams understand the objective, they interpret the new practice better and are more able to apply it in unforeseen situations. To go further, discover the 5 mistakes to avoid when standardizing without alienating your franchisees.
4. Support the change in the field
This is probably one of the most important steps: a new practice doesn’t take hold through information alone; it takes hold through support.
In a network, field managers often play a central role. They are the link between head office’s decision and the reality on the ground: they explain the new rule, answer questions, identify sticking points, spot misinterpretations and observe how the practice is actually being implemented. Their visit reports then become a valuable tool for tracking the rollout location by location.
Above all, they can adapt their support to each location. Some teams will simply need a quick explanation, others more in-depth support, and others will run into a specific problem that had not been anticipated.
The field manager should therefore not just relay the instruction: they should help turn it into practice.
5. Check what is really happening
This is where many initiatives stop too early. Head office has communicated, the training has taken place, the field managers have relayed the message: so the new practice is considered to be in place. But how can you be sure?
A new practice can only be considered adopted once its actual application has been observed. This check can take different forms: an indicator, an audit, a document check, feedback from a field manager, an action campaign, compliance tracking or an on-site observation.
The goal is not to turn every new rule into a heavy control system, but simply to have a way of checking that adoption is real. Because information that has been shared is not proof of execution. On this topic, see also how to audit your franchise network to cut non-quality issues by half and the KPIs to monitor in a franchise network. And when a decision is only partially applied, part of the committed budget is lost too: see where your store budgets really go.
Discover field tracking with Cerca
Measure adoption without multiplying individual reminders
In a small network, it is still possible to contact each location individually. This method quickly reaches its limits as the network grows, and head office then needs an overall view.
The 5 questions for managing adoption
- How many locations have implemented the new practice?
- Which ones are behind?
- Which ones are running into difficulties?
- Are there areas or types of locations where adoption is weaker?
- Which issues come up most often?
The goal is not just to track progress: it is to know where to focus support. This approach makes it possible to move from reactive management to much more targeted management. Instead of chasing everyone, head office can focus its efforts on the locations that really need it.
Don’t confuse non-adoption with resistance
When a new practice is slow to be applied, it is tempting to conclude that the field is “resisting change”. That is sometimes true, but not always. A location may not apply the new rule because it hasn’t understood it, because it lacks time or because a tool isn’t working properly. A local exception may not have been anticipated, teams may not have been trained, the new procedure may conflict with another one, or the operational priorities of the moment simply took over.
Before talking about resistance, you need to understand the cause. And that is precisely why field feedback is essential.
The field must be able to respond to head office
A network transformation cannot work in one direction only. Head office sends out a new practice, but the field must be able to respond: what works, what is difficult to apply, what special cases come up, which points are misunderstood, which steps seem unnecessary or too cumbersome?
This feedback is valuable because it makes it possible to distinguish between two very different situations. In the first, the new practice is relevant but misunderstood: communication or support then needs to improve. In the second, the practice itself needs to be adjusted.
This is an important point: adjusting a decision after field feedback doesn’t mean the initial decision was wrong. It means the network is learning.
The key role of field managers
In this loop between head office and the field, field managers hold a special position. They see how decisions are received, observe the gaps between the official procedure and reality, spot issues that come up across several locations and identify difficulties that could become structural.
To play this role fully, their feedback must also be structured. If each field manager reports information differently, management may struggle to tell an isolated problem from a network-wide one. The challenge is therefore not just to collect feedback: you also need to be able to consolidate and analyze it.
That is precisely the role of Ari, our AI agent dedicated to field operations: Ari consolidates the health of each location, compares it with the network average and highlights the priority points of attention.
When does a practice truly become a network standard?
A written rule is not yet a standard. Neither is a communicated rule, and even an understood rule isn’t necessarily one. A practice truly becomes a standard when it meets several conditions.
Signs that a practice has become a network standard
- It is known and understood.
- It is applied consistently enough.
- Teams know where to find the information.
- New employees can learn it easily.
- Field managers know how to support it.
- Head office has a way of checking that it is still being applied.
The real sign of adoption appears when the practice no longer needs regular “reminders”. It has simply become part of how the network normally operates.
The more the network grows, the more essential this discipline becomes
In a young network, many things work thanks to direct exchanges. The founder knows the manager of each location, head office teams are accessible, problems surface quickly and decisions can be explained individually.
Then the network grows. Locations multiply, teams become more structured, new managers arrive and information flows increase. What used to work informally gradually becomes insufficient, and that is when the step from decision to execution becomes a genuine organizational issue.
Structure change rather than multiplying messages
When a decision struggles to be applied, the first reflex is sometimes to communicate more: send a new email, follow up, reshare the document, organize another meeting. These actions can be useful, but they don’t always solve the problem.
Before sending a reminder, identify the real blocker
- The decision isn’t clear? More communication won’t make it easier to understand: it needs rewording.
- Teams don’t know how to apply it? A reminder won’t replace support.
- The process is too complex? It may need to be simplified.
- Some locations face a specific difficulty? It needs to be understood first.
That is why the step from decision to execution must be designed as a complete process.
From decision to improvement loop
The most effective model is probably a loop. Head office decides and communicates, the network implements, teams report their difficulties, head office observes and adjusts if necessary, and then the new standard stabilizes.
The improvement loop
Decide → communicate → implement → report difficulties → observe → adjust → stabilize.
This approach changes the way change is viewed. The aim is no longer just to “get a message across”: it is to establish a new way of working. That is much more demanding, but also much more effective.
The real challenge: closing the gap between what the network decides and what it executes
In a multi-site network, the quality of execution rarely depends on a single big decision. It rests on a multitude of everyday practices: procedures, standards, habits, behaviors, methods. If each of these elements is applied differently from one location to the next, the network’s consistency ends up weakening.
Conversely, when a network’s head office knows how to effectively turn a decision into field practice, it gains in consistency, responsiveness and rollout capacity.
At Cerca, this is precisely one of the challenges we see in growing networks: the need to better connect communication, documentation and training, action tracking, audits and field feedback. But technology does not replace the process: it can simply help make it more visible, more structured and easier to manage.
Because ultimately, a decision is only valuable to a network when it actually produces change in the field.
FAQ - How do you get the whole network to adopt a head office decision?
Why isn't a head office decision applied the same way everywhere in the network?
Because sharing information and establishing a new practice are two very different steps. An instruction sent by email or presented in a meeting may be read too quickly, misinterpreted, assumed to apply only in certain cases or simply forgotten in favor of old habits. The more locations a network has, the wider the gap between the central decision and local execution is likely to become.
What are the steps to get a network to adopt a new practice?
Six steps follow one another: decide clearly by translating the decision into observable behaviors, communicate through several channels, explain the why as much as the how, support teams in the field, check actual application, then adjust the practice based on field feedback.
How do you know whether a new practice has really been adopted by the network?
Information that has been shared is not proof of execution. Adoption is checked through an indicator, an audit, a document check, feedback from a field manager or an on-site observation. A practice becomes a true standard when it is known, understood, applied consistently, easy to find and to learn, and no longer needs regular reminders.
