How the Seven Classes of Business Constraint™ Work Together
Why the Symptom You See May Not Be in the Same Class as the Constraint Producing It
A sales team says it needs more leads. The owner blames marketing. Marketing blames the website. Six months and three new hires later, the underlying issue turns out to be something nobody on either team had the authority to fix: no one owns the handoff at the moment a lead becomes a customer. The symptom appeared in sales. The structural cause was Organizational.
The Seven Classes of Business Constraint™ do not operate as seven isolated categories. Conditions in one class can produce symptoms that appear to belong to another, and different structural causes can produce remarkably similar visible problems. Understanding these relationships is therefore central to diagnosis: the class where the symptom appears may not be the class containing the condition governing performance.
Section One
A Constraint Can Present Through Symptoms of Another Class
A governing constraint is not identified by the location of its most visible symptom. The effects of a condition in one class may appear in sales, cash flow, staffing, execution, customer retention, decision-making, or another part of the business. The examples below show how each of the Seven Classes can produce symptoms that could initially be attributed to something else.
The Market Constraint Can Present As:
A pricing problem. "We're too expensive" may trigger a price reduction when the deeper issue is market fit—the business may be priced appropriately for a customer segment it is not effectively reaching.
A sales team problem. A team that is "not closing enough" may be trying to convert buyers who do not sufficiently value what the business offers. The visible problem is closing performance; the underlying condition may be Market.
A product problem. "We need to add features" may reflect a product deficiency—or a product being presented to a segment whose needs never matched the offer.
A marketing problem. "We need more leads" may actually mean the business needs better-fit leads—buyers attracted by positioning and messaging aligned with the market the business is equipped to serve.
A competition problem. "The market just got tougher" may reflect a competitive shift—or a business that has not adjusted as its best-fit customer, market position, or competitive environment changed.
The Operational Constraint Can Present As:
A hiring problem. "We need more staff" may describe a workflow containing a structural bottleneck that additional headcount alone will not remove.
A quality problem. "Our people need more training" may be correct—or the recurring quality failure may originate in the process people are being asked to follow.
A customer service problem. Complaints handled by customer-service representatives may originate upstream in fulfillment, production, scheduling, or another operational process.
A growth problem. "We can't scale" may describe a process that functioned at lower volume because informal workarounds absorbed its weaknesses. As volume increases, those weaknesses become increasingly visible.
A vendor problem. Apparent supplier unreliability can sometimes originate inside the business—for example, in inconsistent forecasting, ordering, scheduling, or communication.
The Financial Constraint Can Present As:
A sales problem. "We need more revenue" may actually reflect a gap between reported revenue and when that revenue becomes usable cash.
A spending problem. "We need to cut costs" may focus attention on visible expenses while the more consequential issue is a mismatch between cash inflows and required outflows.
A growth problem. "We're growing too fast" may mean the underlying financial structure or cash-conversion cycle cannot adequately support the pace of growth.
A banking problem. "Our credit line isn't big enough" may indicate insufficient financing—or that financing is being used to compensate for a recurring structural cash gap.
A pricing problem. Thin margins may originate in pricing, but they can also reflect a cost structure that is absorbing margin despite otherwise viable pricing.
The Organizational Constraint Can Present As:
A hiring problem. "We need more headcount" may actually reflect unclear boundaries, responsibilities, or decision rights among existing roles. Adding another person does not necessarily resolve an undefined structure.
A communication problem. "Our teams don't talk to each other" may describe teams that communicate regularly but still lack clear ownership of the work passing between them.
An accountability problem. "Nobody takes ownership" can occur when several capable people reasonably believe responsibility belongs to someone else because ownership was never structurally defined.
A process problem. Better procedures can improve execution, but documenting a process does not resolve an underlying ambiguity about who owns the work, decision, or outcome.
A technology problem. "We need a better CRM" may be true, but technology cannot by itself resolve an undefined responsibility or decision right.
The Strategic Constraint Can Present As:
An execution problem. "We're just not executing well" may describe capable execution spread across too many competing initiatives. The underlying limitation may be insufficient strategic prioritization rather than execution capability.
A resource problem. "We need more budget" may mean resources are genuinely inadequate—or that adequate resources are being divided among too many simultaneous priorities.
A morale problem. A team that feels scattered may be responding to competing priorities, shifting direction, or insufficient clarity about what matters most.
A growth problem. "Nothing is gaining traction" can occur when multiple reasonable initiatives compete for the concentration, resources, and time required for any one of them to produce meaningful results.
A leadership problem. Apparent indecision can sometimes reflect not an inability to decide, but an unwillingness to choose among competing strategic priorities and stop pursuing the others.
The Leadership Constraint Can Present As:
A sales problem. Deals may stall when capable salespeople lack sufficient authority to make decisions that repeatedly require owner or executive approval.
A talent problem. Difficulty retaining capable people can sometimes reflect limited delegated authority, repeated second-guessing, or decision rights that exist formally but not in practice.
A culture problem. A team that appears to lack initiative may have learned that independent decisions are routinely reconsidered, reversed, or escalated.
A speed problem. Slow decision-making may originate not in the initial decision itself but in repeated review, escalation, reversal, or re-decision after authority was supposedly delegated.
A succession problem. Difficulty establishing a capable second-in-command may sometimes reflect a role carrying responsibility without sufficient authority to exercise it.
The Credibility Constraint Can Present As:
A sales problem. Prospects choosing a competitor may reflect differences in price, product, or fit—but it can also reflect insufficient confidence in the organization or person making the promise.
A pricing problem. Difficulty commanding an appropriate price can sometimes reflect a gap between actual capability and the market's confidence in that capability.
A hiring problem. Difficulty attracting senior talent may persist even with competitive compensation when candidates lack sufficient confidence in the organization, role, leadership, or opportunity.
A partnership problem. A capable company may be ready for larger strategic relationships before prospective partners have developed sufficient confidence in its ability to deliver.
A succession problem. Formal authority can transfer immediately while confidence in a new leader develops more gradually. When that gap materially limits the leader's ability to produce action, Credibility warrants diagnostic examination.
The examples above illustrate a central diagnostic problem: the location of the symptom does not establish the location or class of its cause. Sometimes they will coincide. Sometimes they will not. Diagnosis therefore requires evidence capable of distinguishing among plausible structural causes rather than assuming the class from the place where the pain is most visible.

Section Two
When One Governing Constraint Is Resolved, What Becomes Limiting Can Change
Resolving a governing constraint does not remove every limitation from a business. When the condition exerting the greatest limiting influence is successfully resolved and the improvement holds, another condition may become the factor that most limits system performance. SAI refers to this shift as constraint migration.
Consider a distribution company that resolves a Financial Constraint—a structural gap between when suppliers must be paid and when customers pay the company. As cash availability improves, the business gains capacity to grow. With greater volume and organizational complexity, however, the founder's continued involvement in routine approvals begins slowing decisions that a larger team is capable of making. The Financial condition is no longer governing performance; a Leadership condition may now have become the greater limitation.
Constraint migration is not evidence that the earlier diagnosis or resolution failed. It reflects a changing business system. The Discipline therefore does not end with resolution: the improvement is confirmed, the business is reassessed, and leaders remain attentive to what condition now exerts the greatest limiting influence.

Section Three
One Symptom, Seven Possible Causes
The same visible symptom can plausibly originate in any of the seven classes, depending on the specific business and the evidence behind it. Below is a single symptom—customers leaving for a competitor—with one plausible explanation from each class.

| Constraint Class | How It Could Produce the Same Symptom |
|---|---|
| Market | The business is positioned for the wrong buyer, and the customers leaving were never the right fit to keep. |
| Operational | Delivery has become inconsistent — the thing customers relied on most quietly stopped being reliable. |
| Financial | A cash timing gap prevented reinvestment in the exact service or product upgrade that would have kept them. |
| Organizational | No one owns the customer relationship after the sale closes, so nothing prompts a renewal conversation before they leave. |
| Strategic | Attention is split across too many new initiatives, and the account that left never got the proactive check-in it used to. |
| Leadership | The account manager who built the relationship needed authority to resolve a complaint and didn't have it — by the time the owner weighed in, the customer had already decided. |
| Credibility | A newer account manager's recommendation was correct and was overridden internally — the customer felt the hesitation and read it as a lack of confidence. |
Seven businesses could report the identical complaint— "we keep losing customers to a competitor"—and require seven very different responses. A diagnosis that assumes the responsible class before testing plausible alternatives risks producing an answer that sounds reasonable while missing the structural cause.
Section Four
Why the Diagnostic Tests the Whole Business, Not Just the Department That's Complaining
When a problem surfaces, the natural instinct is to investigate the department where it appeared. Sales is struggling, so examine sales. Marketing's numbers are down, so examine marketing. That is a reasonable starting point—but it is not sufficient to establish the class containing the governing constraint. As Sections One and Three demonstrate, the structural cause may reside somewhere else.
This is why the SAI Business Constraint Diagnostic™ uses 81 targeted questions spanning all Seven Classes of Business Constraint™ rather than limiting the inquiry to whichever department first reported the problem. Evaluating evidence across all seven classes provides a structured basis for identifying the probable governing constraint class and the structural condition within that class that appears to be limiting performance.
If a problem has been repeatedly assigned to one department without producing the expected improvement, the governing constraint may not be where everyone has been looking. The SAI Business Constraint Diagnostic™ examines evidence across all seven classes—not only the class associated with the loudest symptom.
81 targeted questions. Approximately 30 minutes. 2,200+ word written finding within 72 hours. $89.
"Before you can solve the problem, you must identify the governing constraint."
— Lawrence M. Schneider, Founder & CEO, Schneider Axiom Institute
Strengthen the Individual.
Strengthen the Family.
Strengthen the Company.
Strengthen America.
© 2026 Schneider Axiom Institute LLC. All Rights Reserved. The Business Constraint Discipline™, the Seven Classes of Business Constraint™, the SAI Business Constraint Diagnostic, and all credential marks — Foundational Diagnostic Credential (FDC), Certified Axiom Strategist (CAS), and Certified Axiom Executive (CAE) — are trademarks and proprietary intellectual property of Schneider Axiom Institute LLC.

