Your Franchise Unit Is Below System Average. What Is Actually Causing the Gap?

SAI WHITE PAPER SERIES

Your Franchise Unit Is Below System Average. What Is Actually Causing the Gap?

How Franchisees Can Distinguish System Conditions From Unit-Specific Governing Constraints Before Blaming the Brand—or Themselves

Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™

PUBLICATION IDENTITY

Permanent Publication Identifier: SAI-ACPP-05
Original Publication: June 2026
Current Editorial Revision: September 2026
Version: 2.0
Classification: Franchise Systems
Subject: Franchisee Performance, System Conditions & Unit-Level Diagnosis
Primary Audience: Franchisees & Multi-Unit Franchise Owners
SAI Discipline Stage: IDENTIFY → PRIORITIZE
Evidence Orientation: Interpretive Proposition Supported by Franchise Research, Operating Observation, and Illustrative Scenarios

Executive Abstract

Your franchise unit is below system average. The franchisor has the data. You have the same data.

Revenue may be lower. Margins may be weaker. Customer scores may lag. Labor costs may be higher. Growth may be slower.

And the natural question is:

Why?

The answer is not automatically that you are failing to execute the franchise system. It is not automatically that the franchisor has failed you. It is not automatically that the location is wrong.

And it is not automatically that your unit has a particular governing constraint.

A below-average result tells you where the unit is performing relative to a benchmark. It does not tell you what is governing the difference.

Being below system average is a performance finding—not a diagnosis.

The gap may reflect a system-level condition. It may reflect a unit-specific governing constraint. It may reflect an interaction between the system and your local operating conditions.

Or the apparent gap may partly reflect differences in unit age, market potential, local competition, capital, ownership involvement, real-estate economics, or other conditions that make direct comparisons imperfect.

Before blaming the brand—or blaming yourself—the first task is to determine:

What condition is actually governing the result?

That distinction protects the franchisee from two equally weak assumptions:

“The franchise system must be the problem.”

and

“If other units are performing better, I must be the problem.”

Either conclusion may prove partly correct. Neither should be the starting diagnosis.

Why This Paper Matters

A franchisee operating below system average does not have unlimited time or capital to keep treating the wrong problem. A system-level intervention aimed at a unit-specific condition may change little. A unit-level intervention aimed at a system-wide condition may consume money and management attention without changing the governing cause.

And a franchisee who mistakes correlation for diagnosis may spend months changing staffing, marketing, pricing, scheduling, or leadership behavior without knowing whether any of those conditions actually govern the result.

The consequences are practical. Field-support time is consumed. Capital is redirected. Performance plans multiply. Franchisee confidence can deteriorate. Franchisor-franchisee tension can increase. And the original performance gap may remain.

The cost of a wrong diagnosis is not merely analytical. It is operating time, money, attention, and confidence spent on the wrong level of the problem.

This paper matters because the franchisee needs to answer a more precise question than:

“Why am I below average?”

The better question is:

“What condition is governing the difference between my unit’s result and the result I am trying to achieve?”

System Average Is a Benchmark, Not a Diagnosis

System average is useful. It gives the franchisee a comparison point. It may reveal that the unit is lagging peers. It may show deterioration over time. It may indicate that the performance gap is material enough to deserve attention. But system average does not identify causation.

A unit may be below average because of local market characteristics, unit maturity, real-estate economics, capital structure, owner leadership, staffing architecture, execution, competitive density, customer mix, financial pressure, franchisor decisions, system economics, or several interacting conditions.

Two units can be equally far below system average for completely different reasons. Two units can also perform very differently while sharing the same system-level pressure.

Being below system average tells you where your unit is performing. It does not tell you why.

That is the conceptual starting point for diagnosis.

Why Below-Average Performance Is Ambiguous

The franchise model deliberately creates commonality. Units may share the brand, operating standards, technology, training, products or services, marketing resources, supply arrangements, pricing guidance, and field support. But franchise units are not identical operating environments.

They have different owners, managers, workforces, cost structures, lease obligations, competitors, customer behavior, capital positions, market histories, and local economic conditions.

Research reflects that complexity. A systematic review by Bui, Jambulingam, and Amin found franchisee performance associated with multiple categories of influence, including franchisor-related factors, franchisee-related factors, relationship factors, and external environmental conditions. [1] That supports a restrained conclusion:

A performance gap should not be attributed to one level of the franchise relationship before competing explanations are examined.

Three Explanations Should Be Considered

A System-Level Condition

The unit may be operating inside a condition that affects more than one franchisee. Examples could include pricing architecture, brand positioning, supplier economics, technology, marketing strategy, training design, or operating requirements. If comparable units deteriorate simultaneously, the system belongs in the diagnostic inquiry.

That does not mean the system caused the problem.

It means the system should not be excluded.

A Unit-Specific Condition

The system may be operating as intended while one unit contains a condition that materially affects its result. That condition might involve local market fit, workflow, financial structure, authority, leadership, credibility, staffing, or another unit-specific condition. If comparable units perform materially better under similar system conditions, the unit deserves closer examination.

That is not blame.

It is evidence.

A Mixed Condition

A system-level condition may affect the entire network while a unit-specific condition determines how severely one franchisee experiences it. A pricing change may challenge all units. A financially constrained unit may be less able to absorb it.

A new labor requirement may affect the network.

A unit with weak management structure may struggle more severely. A system-only explanation would therefore be incomplete. So would a unit-only explanation.

The condition may sit in the interaction between the franchise system and the individual unit.

What Better-Performing Units Can—and Cannot—Tell You

A franchisee below average naturally looks at units performing above average. That comparison can be useful. But it has limits.

A top-performing franchisee may have a stronger trade area, lower occupancy costs, greater capital, a more experienced manager, different customer demographics, a longer operating history, or a more favorable competitive position.

So another unit’s stronger performance does not prove that the underperforming franchisee is executing poorly. Peer comparison becomes more informative as the units become more comparable. If two units share similar markets, unit age, system requirements, pricing, supplier economics, and operating conditions—but their results diverge materially—the differences inside the units deserve closer examination.

The question is not:

“Why can they do it and I cannot?”

It is:

“What relevant conditions differ between the two units?”

That is a diagnostic question rather than a judgment.

What Franchise Research Adds

External research does not validate SAI’s Seven Classes of Business Constraint™ or the governing-constraint proposition. It does support the narrower conclusion that franchisee outcomes can be affected by interacting conditions at several levels. Bui, Jambulingam, and Amin identify franchisor, franchisee, relationship, and environmental influences on franchisee performance. [1]

Nijmeijer, Fabbricotti, and Huijsman’s synthesis of 126 empirical studies similarly identifies business-format design, contract design, franchisor and franchisee behavior, ownership structure, support, and system characteristics among factors associated with franchise outcomes. [2]

Colla and colleagues found franchisee autonomy, network innovativeness, and affective commitment relevant to relative franchisee performance in their sample. [3] Luu and colleagues likewise report relationships among franchisor resources, franchise relationship quality, franchisee capabilities, and performance in their study. [4] These findings do not identify a governing constraint.

They reinforce the need to avoid a one-factor explanation.

Franchisee performance can be influenced by conditions in the system, the unit, the relationship, and the external environment.

Field Support and Diagnostic Inquiry Are Complementary

The franchisor’s field team can be extremely valuable. Field consultants may understand system standards, operating procedures, network benchmarks, common failure patterns, training requirements, successful unit practices, and the performance metrics the system tracks. That knowledge should not be dismissed.

But field support and structural diagnosis are not necessarily the same task.

A field consultant may identify that labor cost is too high. Diagnosis asks why. The consultant may identify that conversion is weak.

Diagnosis asks what condition is governing it.

The consultant may identify that staffing is inconsistent. Diagnosis asks whether staffing is itself the governing condition or an expression of something else.

Field support contributes system knowledge and operating observation. Structural diagnosis contributes a disciplined inquiry into what condition deserves priority.

One does not diminish the other.

Illustrative Scenario: The System-Level Condition

A franchisee has operated successfully for six years. Performance has historically tracked system average. Over nine months, revenue and margin begin declining.

The owner initially assumes local execution has weakened.

But several comparable units in different markets show similar deterioration. The franchisee also learns that the system changed pricing and promotional structure shortly before the performance shift. That timing does not prove the system change caused the decline.

But it materially strengthens the case for examining a system-level Market or Strategic condition before the franchisee undertakes a major internal restructuring.

The correct level of inquiry changes what should be investigated first.

Illustrative Scenario: The Unit-Specific Condition

A franchisee operates in a mature territory. Nearby units using the same brand, suppliers, technology, regional advertising, and core operating standards perform within the expected range. This unit remains materially below them.

The franchisee has also experienced repeated manager turnover, unclear authority between the owner and general manager, and inconsistent accountability.

Those facts do not establish a Leadership or Organizational constraint. But they make unit-specific diagnosis more relevant. The diagnostic question becomes:

What is different inside this unit that may explain why similar system conditions are producing a different result here?

Illustrative Scenario: The Mixed Condition

A franchise system introduces a new labor model. Labor costs rise across the network. The franchisee concludes that the system change is responsible for the entire margin problem.

But comparison shows that some units absorbed the change with relatively minor deterioration while this unit experienced a severe decline.

Further examination shows that the unit also has scheduling instability, weak supervisory authority, and heavy overtime dependence. The system condition is real. So are the local conditions.

The right diagnosis may therefore require both levels.

A shared system pressure can expose a unit-specific weakness without being identical to it.

Local Market Conditions Are Real—but They Are Not a Universal Explanation

Location matters. Traffic matters. Demographics matter.

Competition matters.

Customer behavior matters. A weak trade area should not be dismissed simply because SAI uses a constraint framework. But market limitations also require diagnosis.

A unit may be genuinely limited by local demand.

Or the local market may be capable of supporting better performance than the unit currently produces. The existence of a difficult market does not automatically establish a Market constraint. And the existence of internal operating weaknesses does not prove that market conditions are unimportant.

The question remains:

Which condition is governing the required result now?

Revenue Gap Is Evidence—not the Cost of the Constraint

Suppose the unit produces $800,000 in annual revenue while system average is $1 million. The $200,000 difference is real. But that does not mean the governing constraint “cost” the unit $200,000.

The units may differ in market potential, operating history, capital structure, competitive environment, or unit economics.

The performance gap is therefore a useful signal. It is not automatically a causal calculation.

The revenue difference is something to explain—not something to attribute to a governing constraint before causation has been established.

That distinction protects both the franchisee and the integrity of the diagnosis.

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 a franchisee, these are categories for investigation. They should not be inferred from symptoms. Weak sales do not automatically mean Market.

High costs do not automatically mean Financial.

Staff turnover does not automatically mean Leadership. Service inconsistency does not automatically mean Operational. Conflict with the franchisor does not automatically mean Credibility.

The constraint class follows the evidence.

And the evidence must distinguish the visible performance problem from the condition governing it.

One Franchise Unit Can Have Many Problems—but One Governing Constraint

A franchisee may simultaneously face staffing difficulty, local competition, margin pressure, customer complaints, weak marketing, high occupancy costs, and management overload. All may be real. But they are not necessarily equal in diagnostic importance.

The governing constraint is the condition currently limiting the required result more than the others.

That is why diagnosis should not become a list of everything wrong with the unit. The question is not:

“What problems do I have?”

It is:

“Which condition deserves priority because it is governing the result?”

The Business Constraint Diagnostic™ Does Not Replace Franchise Analysis

The Business Constraint Diagnostic™ is not a franchise compliance review. It is not an operations audit. It is not a legal analysis.

It is not a site-selection study.

It is not a valuation. It is not a financial audit. And it is not a determination of whether the franchisor or franchisee is responsible for performance.

It does not determine whether system standards are appropriate.

It does not determine whether a franchise agreement should be renewed, terminated, or modified. It does not establish legal rights or obligations. It does not establish that a particular system decision caused the unit’s performance.

Its role is narrower:

to examine the probable governing constraint class and the structural condition indicated by the information supplied.

That finding should be considered alongside franchise data, field-support observations, financial information, market evidence, and other relevant professional analysis.

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 a franchisee, that may help distinguish between the visible gap and the condition that deserves priority. It does not prove that the franchisor caused the problem. It does not prove that the franchisee caused the problem.

It does not prove that the Diagnostic explains the entire difference from system average.

And it does not guarantee that resolving the identified condition will produce system-average or top-quartile performance.

The Diagnostic identifies what deserves examination and corrective priority. It does not promise another franchisee’s result.

Guarantee: “If your written finding does not identify a clear, actionable governing constraint, your $89 will be refunded.”

A Better Franchisee-Franchisor Conversation

The franchisee does not need to begin with:

“The system is failing me.”

The franchisor does not need to begin with:

“You are failing to execute the system.”

A stronger conversation is:

“We agree that the unit is below the performance level we want. Now we need to distinguish what is system-level, what is unit-specific, and what evidence supports each conclusion.”

Another useful formulation is:

“The performance gap is clear. The cause is not.”

And before adding another improvement plan:

“What evidence tells us which condition actually deserves priority?”

That shifts the conversation from attribution to diagnosis.

Questions That Improve the Diagnosis

Before accepting an explanation for below-average performance, the franchisee should test it against competing possibilities. Four questions are especially useful:

Is the same pattern appearing across genuinely comparable units—or primarily in mine?

What changed before the performance changed, and did that change occur at the system level, the unit level, or both?

What relevant conditions differ between better-performing comparable units and this unit?

Have previous interventions changed the result in a sustained way—or repeatedly treated the visible symptom without resolving the condition governing it?

These questions do not produce the diagnosis by themselves. They make premature diagnosis less likely.

IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM

The Business Constraint Discipline™ uses the sequence:

IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM

Applied to the franchisee:

IDENTIFY the condition indicated by the evidence—system-level, unit-specific, or interacting.

PRIORITIZE the condition that appears to be governing the required result.

RESOLVE it through the intervention appropriate to the evidence.

CONFIRM whether the targeted result changed and whether the improvement holds.

The final step prevents another common mistake. Improvement is not the same as confirmation. A temporary sales increase does not automatically establish that the diagnosis was correct.

A staffing change does not prove that staffing was the governing condition.

A new marketing program does not prove that the market was the problem.

The intervention should produce evidence that the targeted condition and the required result changed in the expected direction.

What This Paper Does Not Claim

This paper does not claim that below-system-average performance proves the franchisee has a unit-specific governing constraint. It does not claim that the franchisor is responsible for below-average performance. It does not claim that the franchisee is responsible.

It does not claim that better-performing units prove the system is sound.

It does not claim that a difficult market explains the entire performance gap. It does not claim that field consultants are incapable of identifying structural issues. It does not claim that the Business Constraint Diagnostic™ replaces field support, financial analysis, legal advice, market analysis, or franchise operations expertise.

It does not claim that the revenue difference between a unit and system average equals the financial cost of a governing constraint.

It does not claim that resolving an identified condition will produce system-average or top-quartile performance. And it does not claim that external franchise research independently validates the Business Constraint Discipline™, the Seven Classes of Business Constraint™, or the Business Constraint Diagnostic™. The proposition is narrower:

A below-average franchise unit should be diagnosed before responsibility, constraint class, or corrective action is assumed.

Implications / Applications

Treat System Average as a Benchmark

Use it to identify a performance difference—not to infer its cause.

Compare Comparable Units

The more similar the operating conditions, the more informative performance differences become.

Examine the System

Do not exclude system-level conditions simply because some units perform better.

Examine the Unit

Do not exclude unit-specific conditions simply because several units are struggling.

Examine the Interaction

Some performance problems emerge because a system condition affects different units differently.

Separate Symptoms From Causes

Visible gaps deserve investigation, not automatic classification.

Protect the Franchisor-Franchisee Relationship

Replace premature attribution with shared diagnostic inquiry.

Confirm the Improvement

Do not declare resolution simply because an intervention occurred.

Limitations and Questions for Further Examination

The scenarios in this paper are illustrative. They are not presented as verified SAI case findings. System averages may themselves be incomplete or imperfect benchmarks. Franchise systems can contain units of different ages, territories, formats, ownership structures, capital intensity, and market potential. Benchmark comparisons should therefore be interpreted in context. Franchisee performance can be affected by system design, franchisor resources, franchisee capability, relationship quality, local markets, capital, competition, labor, governance, real estate, and external economic conditions.

The external research cited here supports the broader proposition that franchisee performance can be influenced by interacting conditions across several levels. It does not independently validate SAI’s governing-constraint proposition, Seven Classes of Business Constraint™, or Business Constraint Diagnostic™.

Further examination should consider how franchise systems construct appropriate peer groups; how franchisees and franchisors distinguish system effects from unit effects; how local market differences affect system benchmarking; and how post-intervention evidence can be used to confirm whether the identified governing condition actually changed.

Conclusion

Your unit is below system average. That is important. But it is not yet a diagnosis.

The brand may be contributing.

Your unit may contain a condition that comparable units do not. The system and the unit may be interacting. Or the benchmark itself may require more context before the gap can be interpreted correctly.

The franchisor should not assume.

The franchisee should not assume. The field consultant should not assume. The Diagnostic should not assume.

Being below system average tells you where the unit is performing. It does not tell you why.

The central question is not:

“Who is responsible?”

It is:

“What condition is governing the result?”

Find that first. Then determine what deserves priority. Then apply the intervention that matches the evidence.

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, franchisee autonomy, support, relationship quality, Lawrence M. Schneider’s operating perspective, and illustrative franchise scenarios. The paper does not establish that below-system-average performance is generally caused by either franchise-system conditions or unit-specific governing constraints. It does not establish that a particular performance gap reflects one constraint class or that the difference between unit performance and system average represents the monetary cost of a governing constraint.

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, support, franchisee autonomy, system design, relationship quality, and environmental 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, franchisor or franchisee fault, renewal or termination decisions, system causation, or the level of performance a franchisee will achieve after intervention. It does not replace qualified legal, financial, operational, market, 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] Colla, E., Ruiz-Molina, M.-E., Schultz, M., Deparis, M., & Lemmet, L. (2018). Understanding franchisee performance. International Journal of Retail & Distribution Management. https://doi.org/10.1108/IJRDM-10-2017-0232

[4] Luu, T., Mai, K., Huynh, C., Phan, N.-H. T., Le, N. T., & Le, T. (2023). Performance of franchisee: The role of reciprocal resources, relationship quality and cultural sensitivity. International Journal of Emerging Markets. https://doi.org/10.1108/IJOEM-04-2022-0581

Related SAI Resources

Business Constraint Diagnostic™

What Is a Business Constraint?

The Seven Classes of Business Constraint™

How the Seven Classes of Business Constraint™ Work Together

Why Diagnostic Credentials Matter

FDC — Foundational Diagnostic Credential

CAS — Certified Axiom Strategist

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.