Distributed Sensemaking Helps Leaders Use Insights From Across the Franchise System
- No one person sees every part of a franchise system, so leaders need input from across the organization.
- Distributed sensemaking helps franchisors understand how decisions affect franchisees, employees and customers.
- Better decisions come from combining systemwide data with insights from field leaders, operators and frontline teams.
Every franchise leader has seen this happen. An initiative makes complete sense at head office, but field leaders can already see where it might break down. Franchisees are worried about cost. Frontline teams know it will add three awkward steps during the rush. Customers simply experience slower service and wonder what happened.
The interesting part is that none of them is necessarily wrong. They are just seeing different parts of the same system.
While developing a framework for my doctoral work, I kept coming back to one question: Who does the sensemaking in a franchise organization? The word sounds academic, but the idea is simple. When something changes and the answer isn’t obvious, who figures out what is really going on?
The usual answer is the leaders at the top. They have the strategy, the systemwide data, and the authority to decide. But franchising is not a traditional hierarchy. Knowledge, experience, authority and risk sit in different places, and the people holding them don’t see the business from the same position.
The franchisor sees brand strategy, capital and systemwide standards. Field leaders see patterns across locations. Franchisees and general managers understand their local market, their people, and their daily operating reality. Frontline teams see what actually happens when a decision reaches the guest. Customers know whether the brand promise feels true.
No single actor sees the whole picture.
Distributed Sensemaking
That is the thinking behind a framework I call distributed sensemaking. It does not mean everyone gets a vote on every decision. It means the right knowledge has somewhere to go before a decision made in one part of the system becomes a problem in another.
Take a technology rollout. Head office may see better data, greater consistency and long-term growth. A field leader may know half the system isn’t ready. A franchisee may be calculating the labor and training costs. The employee using it may immediately see that it slows down service. The customer only knows the experience got worse.
From one perspective, the decision can be completely logical. Viewed across the system, it may be technically right but operationally wrong.
Franchise organizations are already very good at distributing execution. We document standards, build training, measure performance, and create routines we can repeat across hundreds of locations. What we are less deliberate about is how insight moves back through the system.
We ask for feedback after the decision has been made. We hear concern and call it resistance. We rely on reports that tell us what happened last month, while overlooking the people who can see what is beginning to happen now.
This is why distributed sensemaking is more than listening. Listening is asking people what they think. Sensemaking is working out what their different views are telling us.
A franchisee pushing back may be protecting their own interests, or they may be giving an early warning that the unit economics do not work. A frontline complaint may be negativity, or it may expose friction in the guest experience that no one saw during planning. A field leader’s hesitation may reflect a pattern that no single operator could possibly see.
The Franchise Leader’s Job
The leader’s job is not to treat every opinion as equally right. It is to make sure no single view, including their own, is not mistaken for the whole truth.
In practice, that can be fairly simple. Before a major decision, ask what each part of the system can see that the others cannot. During a rollout, look for signals that challenge the plan, not only the ones that confirm it. Afterward, tell people what you heard, what changed, and why.
That final step matters. When people keep offering useful information but never see any evidence that it was considered, they stop offering it. The system becomes quieter just as leadership needs it to become more honest.
None of this means leading by consensus. Franchise leaders still have to make decisions, and some choices must remain centralized to protect the brand and the system’s economics. Asking for insight is not the same as giving away authority.
But having the authority to decide doesn’t mean you are the only person capable of seeing what the decision will do.
As a franchise system grows, this gets harder. Scale creates distance. More reports, more layers and fewer opportunities for senior leaders to see day-to-day reality for themselves. By the time information reaches the top, it has often been cleaned up, simplified and stripped of the uncertainty that made it worth paying attention to.
Franchise advisory councils, field visits, pilot markets, operator forums and customer feedback can all shorten that distance. But only if they are used to understand what is happening, not to announce decisions or gather support for a conclusion already reached.
The test is straightforward. When something unexpected happens, can the system quickly identify who is seeing which part of the problem? Can those perspectives reach the people making the decision? And can leaders make sense of the tension between them without turning every disagreement into a battle between head office and the field?
Franchising has always been exceptionally good at distributing execution. The next opportunity may be learning how to distribute interpretation too.
Because when no one sees the whole system, leadership is not about pretending someone does. It is about helping the system see more of itself.
