The symptom
Consider a network where regional managers conduct quarterly site visits as a matter of routine. The visits are consistent, scheduled, and documented. Issues that later surface at these sites — service problems, compliance gaps, declining standards — were, with some regularity, not identified during the visits that were supposed to catch them.
The instinct, when this pattern is noticed, is to look for something more interesting than the obvious answer: a conflict of interest, a reluctance to flag problems at sites with strong personal relationships, an incentive structure that rewards regional managers for calm reports rather than accurate ones. Sometimes that is exactly what is happening. But in this case, examining what the visits actually involve reveals something plainer. The visits follow a checklist covering documentation and physical condition. Regional managers spend most of the visit time in the site office, working through paperwork. The issues that later emerged were the kind that would have been visible on the operating floor throughout the visit — but the visit, as structured, rarely put anyone on the floor for long enough to see them.
Why the obvious explanation holds up
It is worth stating plainly: sometimes the first, least interesting explanation is the right one. The inspection here was superficial, exactly as it appeared to be. The method was thin rather than distorted by some deeper organisational dynamic, and understanding why does not require a structural theory about incentives or hidden conflicts — it requires looking at what a checklist-and-office-based visit actually samples, which is documentation and static condition, not live operation.
This is a useful case precisely because it resists the temptation to over-explain. Not every oversight gap indicates a governance failure in the sense of misaligned incentives or withheld information. Some indicate that the oversight instrument itself was never built to observe the thing it is meant to catch. A quarterly visit built around checking records will reliably tell an organisation whether records are in order. It will not reliably tell an organisation whether the floor, on an ordinary Tuesday, is being run the way the standard assumes — because nobody spent enough time on the floor, on an ordinary Tuesday, to know.
What makes this specific to franchise governance, rather than a generic inspection problem, is who is doing the looking and why. A regional manager visiting a company-owned site is observing a direct report’s operation, with full authority to intervene. A regional manager visiting a franchised site is observing an independent operator’s business, governed by a contract rather than an employment relationship, with intervention authority defined — and limited — by that contract. Paul Rogers and Marcia Blenko’s Bain & Company research, published in Harvard Business Review, on where organisational decisions stall identifies “centre versus business unit” as a recurring bottleneck even inside single companies. A franchise network adds a further layer on top of that bottleneck: the “business unit” here is not a subordinate unit at all, but a separate legal and economic entity, which changes both what a visit is permitted to examine and what a franchisee has reason to volunteer.
What makes franchise governance structurally different
In a single-organisation hierarchy, governance gaps are, in principle, correctable by adjusting authority: give a manager more access, more reporting lines, more standing to intervene, and the gap closes. In a franchise network, that adjustment is bounded by contract. A franchisor cannot simply decide to observe more closely or intervene more directly without renegotiating what the franchise agreement actually grants it — and franchisees, reasonably, resist governance mechanisms that function like employment oversight applied to a business they own and have invested their own capital in.
This produces a specific and recurring tension. The franchisor carries brand-level responsibility for what happens at every site, because customers experience the brand, not the ownership structure behind an individual location. The franchisee carries the actual operating authority and economic risk at that site. Governance has to work across that split — accountability sitting with one party, operating control sitting substantially with another — which is a structurally different problem from the governance challenge inside a single company, however large. Jeffrey Bradach’s study of large US restaurant chains found that networks manage this by combining several mechanisms at once — structure, control systems, career paths, strategy-making processes — rather than relying on any single lever, which is consistent with the idea that no one governance tool, including a site visit, can carry the full weight of oversight across a franchisor-franchisee relationship on its own.
The practical implication is that a franchise network cannot evaluate its own governance the way a company-owned multi-site business would — by asking whether authority and reporting lines are clear. Authority in a franchise network is deliberately split by design. The relevant question is not whether the split exists, but whether the mechanisms built to work across it — visits, reporting, escalation, contractual review points — are actually built to observe what matters, or, as in this case, built to observe what is easiest to check.
It is also worth resisting a second temptation this case raises: concluding that because the obvious explanation was correct here, oversight problems are usually simple. The library of situations this kind of pattern is drawn from suggests something closer to the opposite — roughly as often as not, what looks straightforward conceals something structural, and what looks structural turns out to be straightforward. The discipline is in checking rather than assuming either way, which in this instance meant looking at what the visit actually sampled before reaching for a more elaborate account of why it failed.
Where this shows up
People working in franchise networks will probably recognise this pattern first. The wider Multi-Site and Franchise grouping and the other sectors page show how it presents elsewhere.
Questions worth considering
- What would a site visit have to include to see what a documentation checklist cannot?
- Where in the franchise agreement is intervention authority genuinely limited, and where is it simply assumed to be limited without having been tested?
- Does the network’s current oversight model assume a single chain of authority that, in a franchise structure, does not actually exist?
Your team is facing similar challenges?
Subscribe to The Riddle Ledger
Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.