Multiple Franchise Units Are Underperforming. Is the Problem in the System—or in the Units?
SAI WHITE PAPER SERIES
Multiple Franchise Units Are Underperforming. Is the Problem in the System—or in the Units?
How Franchisors Can Distinguish System-Level Conditions From Unit-Specific Governing Constraints Before Changing the Playbook
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
PUBLICATION IDENTITY
Permanent Publication Identifier: SAI-ACPP-04
Original Publication: June 2026
Current Editorial Revision: September 2026
Version: 2.0
Classification: Franchise Systems
Subject: Multi-Unit Performance, Franchise Support & Structural Diagnosis
Primary Audience: Franchisors, Franchise Executives & Field-Support Leaders
SAI Discipline Stage: IDENTIFY → PRIORITIZE
Evidence Orientation: Interpretive Proposition Supported by Franchise Research, Operating Observation, and Illustrative Scenarios
Executive Abstract
Multiple franchise units are underperforming at the same time.
The franchisor sees the pattern immediately.
Revenue is below system average. Labor costs are high. Customer experience is inconsistent. Local marketing is weak. Turnover is elevated.
Field-support teams respond. Performance plans are created. Training is delivered. Operations standards are reinforced.
And some units improve while others remain below expectations.
What does that mean?
It may mean the system has a problem.
It may mean individual units have different problems.
It may mean a system-level condition is interacting with unit-specific conditions.
Similar performance symptoms across multiple units do not establish which explanation is correct.
Multi-unit underperformance is a diagnostic signal—not a diagnosis.
That distinction matters because the wrong level of diagnosis produces the wrong level of intervention.
If the condition is systemic, repairing units individually may leave the system cause untouched.
If the conditions are unit-specific, changing the entire system may impose one solution on units that do not share the same problem.
If both levels are involved, either intervention alone may be incomplete.
The franchisor’s task is therefore not simply to identify which units are below average.
It is to determine:
Where does the condition governing the result actually reside?
THE CENTRAL PROPOSITION
When multiple franchise units underperform simultaneously, the pattern may reflect a system-level condition, multiple unit-specific governing constraints, or a combination of both. Similar performance gaps across units are evidence to investigate—not proof of a shared cause or shared constraint class. The franchisor’s diagnostic task is to determine which level is governing the result before changing the system, changing the unit, or deploying the same intervention across both.
Two automatic conclusions should therefore be rejected:
“Several units are struggling, so the system must be the problem.”
and
“Several units are struggling, so each franchisee must have an individual problem.”
Either may be correct.
Neither should be presumed.
Why This Paper Matters
When multiple franchise units underperform at the same time, the franchisor has to decide where to intervene.
That decision has consequences.
If the problem is assumed to be systemic when the governing conditions are actually unit-specific, the franchisor may change standards, training, pricing, support, or operating requirements for the entire network unnecessarily.
If the problem is assumed to be unit-specific when a system-level condition is governing the pattern, field teams may spend months addressing symptoms one location at a time while the shared cause remains untouched.
And if the problem is mixed, a single-level intervention may improve part of the system while leaving the underlying interaction unresolved.
The cost of diagnosing the wrong level is not merely analytical. It affects field-support time, franchisee confidence, operating consistency, system resources, and the speed with which underperformance is corrected.
This paper matters because multi-unit underperformance creates one of the most consequential diagnostic questions in franchising:
Is the condition governing the result in the system, in the units, or in the interaction between them?
The answer should determine what gets changed.
Why Multi-Unit Underperformance Is Diagnostically Difficult
Franchise systems are designed to create consistency.
Brand standards, operating procedures, training, technology, supply relationships, and marketing infrastructure may be shared across the network.
But every franchise unit also operates inside a local environment with different owners, managers, labor markets, competitors, real-estate economics, capital structures, and customer patterns.
That creates a fundamental diagnostic challenge:
The same symptom can be produced by a shared system condition, a different unit condition, or an interaction between the two.
A unit with falling sales may have a local Market constraint.
Another with falling sales may have an Operational constraint.
A third may be executing correctly inside a system whose positioning has weakened.
The performance number does not tell the franchisor which explanation is governing.
A systematic review by Bui, Jambulingam, and Amin found franchisee performance associated with multiple categories of influence, including franchisor-related factors, franchise-related factors, relationship factors, and external environmental conditions. [1]
That reinforces a basic diagnostic principle:
Franchise performance should not be explained from one level of evidence alone.
Three Different Explanations Can Produce the Same Pattern
A System-Level Condition
The same condition affects many units.
Examples could include pricing architecture, supply-chain requirements, training design, brand positioning, technology, operating standards, or unit economics.
In that case, repeated unit-level interventions may produce limited results because the condition sits above the unit.
Unit-Specific Conditions
Several units produce similar symptoms for different reasons.
One unit’s weak sales may reflect local market conditions.
Another’s may reflect owner leadership.
Another’s may reflect staffing structure.
Another’s may reflect financial pressure.
The symptoms look similar.
The governing conditions are not.
A system-wide intervention could therefore misdiagnose the network.
A Mixed Condition
The system contributes part of the exposure while unit-specific conditions determine how severely each franchisee experiences it.
A system change may be necessary.
But it may not be sufficient.
System-level and unit-level diagnosis are different levels of inquiry—not competing approaches.
Common Symptoms Do Not Prove Common Cause
Suppose twelve units show declining revenue.
That does not establish twelve Market constraints.
Suppose several units show high employee turnover.
That does not establish a shared Leadership constraint.
Suppose several units miss service standards.
That does not establish an Operational constraint across the network.
Common symptoms can reveal clustering, timing, geography, and patterns worth investigating.
They do not establish the cause.
Pattern recognition tells the franchisor where to investigate. Diagnosis determines what the pattern means.
That distinction matters especially in franchise systems because shared standards, technology, suppliers, training, economics, and brand positioning can create legitimate commonality across units.
The pattern deserves attention.
It does not deserve premature classification.
When System-Level Evidence Becomes More Persuasive
A system-level explanation becomes more plausible when the same performance change appears across materially different units.
For example, experienced and inexperienced franchisees may deteriorate simultaneously.
Different regions may show the same movement.
Company-owned and franchised units may show similar deterioration.
Or the change may follow a common pricing, supplier, technology, marketing, or operating modification.
None proves system causation.
But each strengthens the system-level hypothesis.
Research supports examining system design as part of the inquiry. Nijmeijer, Fabbricotti, and Huijsman’s review of 126 empirical studies identified business-format design, contracts, franchisor and franchisee behavior, support, ownership structure, and system characteristics among the factors associated with franchise outcomes. [2]
The implication is not:
“The system caused the problem.”
It is:
“The system belongs in the diagnostic inquiry.”
When Unit-Level Evidence Becomes More Persuasive
A unit-level explanation becomes more plausible when similarly situated franchisees produce materially different results.
Suppose two units share the same brand, pricing architecture, operating standards, technology, suppliers, and field-support system.
Yet one performs consistently and the other does not.
That does not prove operator failure.
But it strengthens the case for examining what is different inside the unit.
Leadership.
Organization.
Execution.
Financial structure.
Local market adaptation.
Credibility.
Strategic choices.
Variation is evidence. It is not blame.
The Most Important Question May Be: What Changed?
Comparison across units matters.
Change over time can be even more revealing.
If a group of units deteriorates after a system change, the timing matters.
If one unit deteriorates while comparable units remain stable, the divergence matters.
If a system-wide intervention improves some units but not others, that matters too.
The diagnostic question becomes:
What changed before the result changed—and did the change occur at the system level, the unit level, or both?
Timing does not establish causation.
But it improves the quality of the competing explanations.
The Field Team’s Advantage Is Pattern Visibility
Field consultants see operating reality across multiple units.
They see where franchisees interpret standards differently.
They see where one unit succeeds with a process another struggles to execute.
They see where a system rule creates friction.
They see where local management changes performance even though the system remains constant.
That gives field support unusually valuable pattern visibility.
But observation and diagnosis should remain distinct.
A field consultant can observe turnover, service inconsistency, inventory problems, marketing weakness, labor pressure, or owner disengagement.
Those observations matter.
The observed performance gap is not automatically the governing constraint.
The stronger field-support question is not merely:
“What is this unit doing poorly?”
It is:
“What condition best explains why this result is persisting?”
Illustrative Scenario: The System-Level Condition
A franchise system has forty units.
Over two quarters, sales decline across twenty-seven.
The affected group includes experienced and inexperienced operators, urban and suburban markets, and previously high- and middle-performing locations.
Field reports identify different local symptoms.
Then another fact emerges.
Six months earlier, the system changed its core value proposition and raised prices across the network.
That timing does not prove the system change caused the decline.
It does justify investigating a system-level Strategic or Market condition before treating twenty-seven units independently.
The pattern changes the level of inquiry.
Illustrative Scenario: The Unit-Specific Condition
Eight units operate within one metropolitan area.
They share regional advertising, supplier structure, technology, pricing guidance, standards, and field support.
Seven perform within the expected range.
One has remained materially below peers for eighteen months.
The underperforming unit has also experienced repeated manager turnover, unclear authority between the owner and general manager, and inconsistent accountability.
Those facts do not automatically establish an Organizational or Leadership constraint.
But they strengthen the case for unit-level diagnosis.
The question becomes:
What is different inside this unit that may explain why the same system produces a different result here?
Illustrative Scenario: The Mixed Condition
A franchise system introduces a more complex labor model across the network.
Labor costs rise system-wide.
That suggests a system-level Operational question.
But the increase is modest in some units and severe in others.
Further examination shows that several units adapted scheduling practices quickly while others had weak management capacity and inconsistent labor controls.
The system change matters.
So do the unit differences.
A system-only diagnosis would be incomplete.
A unit-only diagnosis would also be incomplete.
The governing condition may reside in the interaction between the common system requirement and the unit’s ability to operate within it.
Performance Cohorts Are Not Diagnostic Cohorts
Franchisors routinely group units by performance:
top quartile;
middle group;
below average;
remediation cohort;
renewal-risk cohort.
Those groupings are useful operationally.
But a performance cohort is not necessarily a diagnostic cohort.
Ten units with similar revenue performance may contain ten different governing conditions.
Conversely, units with different visible symptoms may share a common constraint class.
Performance data groups businesses by result. Diagnosis groups them by condition.
Those are not the same thing.
A performance cohort tells the franchisor which units are struggling.
A diagnostic distribution may help explain whether they are struggling for similar reasons.
Constraint Distribution Across Units
This is where multi-unit diagnosis can become especially valuable.
Suppose a franchisor examines twelve underperforming units.
The findings might cluster heavily in one class.
They might spread across several classes.
They might reveal one system-level condition interacting with several unit-level constraints.
Or they may reveal no meaningful common pattern.
Each result implies a different management response.
A concentrated distribution may justify examining whether a shared system condition is contributing to the cluster.
A dispersed distribution may argue against one network-wide corrective action.
A mixed distribution may suggest system intervention plus differentiated unit support.
The distribution itself is information.
It is not proof that the units share one governing constraint.
One System Can Contain More Than One Level of Constraint
A franchise system and an individual franchise unit are not analytically identical businesses.
The system may have a governing constraint.
An individual unit may have its own governing constraint.
Those conditions can be related.
They can also be different.
For example, a franchise system may face a Strategic constraint involving brand positioning while one franchisee simultaneously faces a Financial constraint that prevents adaptation.
The system-level condition may affect many units.
The unit-level condition may determine how severely one unit experiences it.
That does not violate the principle that one business is governed by one constraint at a time.
It recognizes that:
the franchise system and the franchise unit are different levels of business analysis.
The Seven Classes Organize the Inquiry
SAI organizes potential governing conditions into the Seven Classes of Business Constraint™:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
For the franchisor, these are categories for investigation—not labels inferred from symptoms.
Weak local marketing does not automatically establish Market.
Turnover does not automatically establish Leadership.
High costs do not automatically establish Financial.
Service inconsistency does not automatically establish Operational.
A system-wide decline does not automatically establish Strategic.
The class follows the evidence.
And in franchise systems, the level of analysis must follow the evidence as well.
What Franchise Research Adds to the Inquiry
External research does not validate SAI’s Seven Classes or governing-constraint proposition.
It does support the narrower proposition that franchise performance is influenced by multiple interacting factors operating at different levels.
Bui, Jambulingam, and Amin identify franchisor, franchisee, relationship, and environmental influences on performance. [1]
Nijmeijer, Fabbricotti, and Huijsman identify business-format design, contracts, support, ownership structure, behavior, and system characteristics among relevant factors. [2]
Perdreau, Le Nadant, and Khelil show that franchise-system performance can depend on configurations of system capabilities and ownership strategy rather than one universal formula. [3]
Perrigot, López-Fernández, and Basset document the difficulty of attributing low performance where franchisor and franchisee are interdependent. [4]
Antia, Mani, and Wathne likewise show that franchisee outcomes can be shaped by governance mechanisms and system relationships. [5]
The defensible conclusion is therefore limited:
Franchise performance should not be diagnosed from one level of evidence alone.
The Business Constraint Diagnostic™ Does Not Replace Franchise Operations Analysis
The Business Constraint Diagnostic™ is not a franchise compliance audit.
It is not an operations inspection.
It is not a legal review.
It does not determine whether the franchisee complies with system standards.
It does not determine whether the franchisor should renew, terminate, remediate, or enforce an agreement.
It does not establish that system policy caused a unit’s performance.
And it does not establish that the franchisee caused the problem.
Its role is narrower:
to examine the probable governing constraint class and the structural condition indicated by the information supplied.
That finding can be considered alongside field observations, system performance data, financial information, market evidence, and professional judgment.
What the Business Constraint Diagnostic™ Can Contribute
The Business Constraint Diagnostic™ costs $89, consists of 81 questions, typically requires about 30 minutes, and produces a 2,200+ word written finding within 72 hours.
The written finding addresses the probable governing constraint class, the structural condition indicated by the information supplied, why that condition appears limiting, why prior efforts failed, and the corrective direction suggested by the diagnosis.
For one franchise unit, the Diagnostic may help identify the condition that appears to deserve priority.
Across multiple units, the findings may also allow the franchisor to examine the distribution of probable constraint classes rather than assume that a common performance gap reflects a common cause.
But those findings should not be used to claim that:
similar classes prove a system defect;
different classes prove the system is sound;
or an identified condition necessarily caused every observed outcome.
The findings refine the inquiry. They do not eliminate judgment.
Guarantee: “If your written finding does not identify a clear, actionable governing constraint, your $89 will be refunded.”
How the Franchisor Should Use Multi-Unit Findings
The first question should not be:
“What program should we deploy?”
It should be:
“What level of condition are we seeing?”
If evidence points toward a shared system condition, investigate the system before multiplying unit-level interventions.
If evidence points toward differentiated unit conditions, do not assume one solution fits the cohort.
If evidence points toward both, design the response at both levels.
Then measure what changed.
That is diagnostic sequencing.
A Better Field-Support Conversation
Instead of:
“You are below system average and need to execute the improvement plan.”
the conversation can begin:
“We know the performance gap. We now need to determine what is producing it.”
Instead of telling the board:
“These units have an execution problem.”
the franchisor can say:
“These units share a performance pattern. We have not yet established whether they share a cause.”
And instead of telling field consultants:
“Fix the lowest-performing units.”
leadership can ask:
“Which conditions are unit-specific, which appear system-wide, and what evidence distinguishes them?”
Those are stronger diagnostic questions.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The Business Constraint Discipline™ uses the sequence:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Applied to franchise systems:
IDENTIFY whether the evidence points toward a system-level condition, unit-specific condition, or interaction between the two.
PRIORITIZE the condition that appears to be governing the required result.
RESOLVE it at the appropriate level—system, unit, or both.
CONFIRM whether the expected result changed and whether the improvement holds.
The final step matters.
A field intervention that produces temporary improvement is not automatically a confirmed resolution.
A system change that improves network averages does not automatically explain every unit outcome.
A Diagnostic finding is not confirmed merely because management agrees with it.
Resolution is demonstrated by evidence after intervention.
What This Paper Does Not Claim
This paper does not claim that multi-unit underperformance proves either a system problem or multiple unit-specific governing constraints.
It does not claim that similar symptoms indicate the same constraint class.
It does not claim that below-average performance proves poor franchisee capability or that persistent underperformance proves field support failed.
It does not claim that the Business Constraint Diagnostic™ replaces operations analysis, field consulting, legal judgment, financial analysis, or local market assessment.
It does not claim that a multi-unit distribution establishes causation or that correcting an identified condition guarantees permanent improvement.
It does not claim that the Seven Classes of Business Constraint™ have been independently validated by the external franchise research cited here.
The proposition is narrower:
When multiple units underperform, diagnosis should determine the level and nature of the governing condition before the franchisor chooses the level and nature of the intervention.
Implications / Applications
Treat Multi-Unit Underperformance as a Signal
Do not assume that a performance cluster is a diagnostic cluster.
Compare Across Levels
Examine unit, regional, and system evidence before attributing cause.
Use Variation as Evidence
Ask why similarly situated units produce different results.
Use Commonality as Evidence
Ask what shared condition may explain simultaneous movement across different units.
Separate Symptoms From Classes
Similar performance gaps do not establish a shared constraint class.
Examine Constraint Distribution
A multi-unit deployment may reveal concentration, dispersion, or mixed patterns.
Match Intervention to Level
Repair the system when the system condition governs. Address the unit when the unit condition governs. Address both when the interaction matters.
Confirm the Improvement
Do not assume an intervention worked because activity occurred.
Limitations and Questions for Further Examination
The scenarios in this paper are illustrative. They are not presented as verified SAI case findings.
Franchise performance can be influenced by system design, ownership structure, local markets, franchisee capability, capital, franchisor support, contracts, governance, labor, competition, geography, and external economic conditions.
The external research cited here supports the broader proposition that franchise outcomes are multi-factor and affected by conditions operating at multiple levels. It does not independently validate the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, or the Business Constraint Diagnostic™.
Further examination should consider how constraint distributions vary across franchise systems; how system-level and unit-level conditions interact; how field observations can inform diagnosis without prematurely assigning cause; and how post-intervention evidence should confirm whether the governing condition actually changed.
Conclusion
Multiple units are underperforming.
That fact matters.
But it does not yet tell the franchisor why.
The system may be contributing.
Individual units may be carrying different conditions.
The two may be interacting.
Or the apparent pattern may prove less structurally meaningful than it first appears.
The franchisor should not assume.
The franchisee should not assume.
The field team should not assume.
The Diagnostic should not assume.
A shared performance problem is evidence to investigate—not proof of a shared cause.
The central question is not:
“Which units are below average?”
It is:
“Where does the condition governing the result actually reside?”
In the system?
In the unit?
Or in the interaction between them?
Find that first.
Then determine what deserves priority.
Then intervene at the correct level.
Then confirm whether the result changed.
That is diagnosis before prescription.
Evidence Boundary
This paper advances an SAI interpretive proposition informed by external research on franchisee performance, franchise-system design, franchisor-franchisee relationships, governance, system capabilities, Lawrence M. Schneider’s operating perspective, and illustrative franchise scenarios.
The paper does not establish that multi-unit underperformance is generally caused by either franchise-system conditions or unit-specific governing constraints. It does not establish that similar performance symptoms indicate a common structural cause or common constraint class.
The Seven Classes of Business Constraint™ remain Market, Operational, Financial, Organizational, Strategic, Leadership, and Credibility.
The scenarios presented are illustrative. They are not verified Business Constraint Diagnostic™ findings and should not be interpreted as evidence that a particular constraint class caused a particular franchise outcome.
External scholarship supports the intellectual context concerning franchise performance, governance, support, system capabilities, interdependence, and multi-level influences. It does not independently validate the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, or the Business Constraint Diagnostic™.
The Business Constraint Diagnostic™ is a business diagnostic instrument. It does not determine franchise-agreement compliance, legal rights, renewal or termination decisions, system causation, or franchisee fault, and it does not replace qualified legal, operational, financial, or franchise-management judgment.
References
[1] Bui, T. T. H., Jambulingam, M., & Amin, M. (2022). A literature review of franchisee performance: Insights for further research. Cogent Business & Management, 9. https://doi.org/10.1080/23311975.2022.2044573
[2] Nijmeijer, K. J., Fabbricotti, I. N., & Huijsman, R. (2014). Making franchising work: A framework based on a systematic review. International Journal of Management Reviews, 16, 62–83. https://doi.org/10.1111/ijmr.12009
[3] Perdreau, F., Le Nadant, A.-L., & Khelil, N. (2023). Franchise capabilities and system performance: A configurational perspective. Industrial Marketing Management. https://doi.org/10.1016/j.indmarman.2023.07.004
[4] Perrigot, R., López-Fernández, B., & Basset, G. (2020). “Conflict-performance assumption” or “performance-conflict assumption”: Insights from franchising. Journal of Retailing and Consumer Services. https://doi.org/10.1016/j.jretconser.2020.102081
[5] Antia, K. D., Mani, S., & Wathne, K. H. (2017). Franchisor–Franchisee Bankruptcy and the Efficacy of Franchisee Governance. Journal of Marketing Research, 54, 952–967. https://doi.org/10.1509/jmr.14.0182
Related SAI Resources
The Seven Classes of Business Constraint™
About the Author
Lawrence M. Schneider is the Founder and CEO of the Schneider Axiom Institute and the founder of U.S. Lock Corporation, now owned by The Home Depot. He brings more than five decades of CEO-level operating experience across manufacturing, distribution, land development, residential and commercial construction, franchising, and multi-entity businesses. He developed the Business Constraint Discipline™ to help owners, executives, and advisors identify what is limiting a business, determine what deserves priority, and confirm whether corrective action worked.
About the Schneider Axiom Institute
The Schneider Axiom Institute is an Institute for Business Constraints. Its work is organized around a disciplined premise: diagnosis should precede prescription. Through research, practitioner education, diagnostic instruments, and credentials, SAI develops the capability to identify, prioritize, resolve, and confirm the governing constraint.