Before Your Next Hire. Before Your Next Investment. Before Any Other Decision — Do This First.
SAI WHITE PAPER SERIES
Why the Condition Governing the Result Should Be Examined Before the Next Major Commitment Is Made
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
PUBLICATION IDENTITY
Permanent Publication Identifier: SAI-BOEL-22
Original Publication: June 2026
Current Editorial Revision: September 2026
Version: 2.0
Classification: Business Owners & Executive Leadership
Subject: Decision Prioritization, Resource Commitment & Business Diagnosis
Primary Audience: Business Owners & Executive Leaders
SAI Discipline Stage: IDENTIFY → PRIORITIZE
Evidence Orientation: Interpretive Proposition Supported by Operating Observation and External Decision-Making Research
Executive Abstract
A business problem becomes expensive when the solution is selected before the condition producing the problem has been identified.
The hire may be reasonable. The equipment may be needed. The marketing program may be well designed. The new system may be sophisticated. The partnership may be attractive. The strategic initiative may be overdue.
But none of those facts answers the question that should come first:
Is this decision aimed at the condition governing the required result—or at one of the symptoms that condition is producing?
That distinction matters because significant business decisions commit scarce resources: money, people, management attention, authority, time, organizational capacity, and sometimes strategic direction that is difficult to reverse.
Diagnosis does not mean management should delay every decision until perfect information exists. Businesses operate under uncertainty. Some decisions are urgent, legally required, safety-critical, or necessary to protect customers, employees, cash, or continuity.
The proposition is narrower.
Before a significant discretionary commitment, management should examine whether the proposed action is aimed at the condition that actually deserves priority.
Diagnosis does not eliminate judgment or urgency. It improves the likelihood that the next major decision is aimed at the right problem.
THE CENTRAL PROPOSITION
Before committing significant money, people, authority, or strategic direction, management should determine whether the proposed action is aimed at the condition governing the required result—or merely at one of its visible symptoms. Diagnosis does not eliminate judgment or urgency. It improves the likelihood that the next major decision is aimed at what actually deserves priority.
This does not mean every decision requires a formal diagnostic exercise.
It means the larger the commitment—and the harder it is to reverse—the more important it becomes to understand what the decision is intended to change.
The critical distinction is between:
“What should we do?”
and:
“What condition are we trying to change?”
Too often, the first question is answered before the second is examined.
Why This Paper Matters
Business owners rarely suffer from a shortage of possible actions.
Hire someone.
Buy equipment.
Increase marketing.
Replace the software.
Enter another market.
Add a partner.
Cut expenses.
Raise prices.
Change compensation.
Restructure the organization.
Launch another initiative.
Most of those actions can be legitimate.
The problem is sequencing.
A business can choose a competent solution for the wrong problem. That is one of the most expensive forms of management error because the action may appear logical, be executed well, and still fail to produce the expected result.
A good solution aimed at the wrong condition is still misdirected.
Research on organizational decision processes supports the broader importance of how problems are framed, how alternatives are developed, and when commitment occurs. Nutt’s examination of 202 organizational decisions found that a discovery-oriented decision process was more successful than approaches organized around imposing an already preferred idea. [1]
That does not validate the SAI governing-constraint proposition.
It supports a narrower point:
The quality of the decision process matters before resources are committed.
The Solution Often Arrives Before the Diagnosis
A company misses its revenue target.
Someone says:
“We need another salesperson.”
Operations is overwhelmed.
“We need new software.”
The owner is exhausted.
“You need a COO.”
Margins are falling.
“We need to raise prices.”
Growth has stalled.
“We need more marketing.”
Each recommendation may ultimately prove correct.
But the visible problem has already been converted into a proposed solution.
The business has moved from symptom to prescription without establishing causation.
That is where diagnosis belongs.
What evidence indicates that the proposed solution is aimed at the condition actually limiting the result?
If that question cannot yet be answered, the business may still have work to do before making the commitment.
The Cost Is More Than the Money Spent
A misdirected decision costs more than its invoice.
A hire absorbs compensation, onboarding time, management attention, organizational energy, and possibly severance if the role proves unnecessary. An equipment investment can consume capital and create fixed costs. A software implementation can absorb months of attention while the underlying process problem remains.
A marketing initiative can generate more demand for an operating system unable to deliver it. A new partner can complicate authority before the company has clarified who already owns which decisions. A restructuring can move boxes on an organizational chart without changing the condition that caused the execution problem.
The cost of the wrong decision includes the opportunity cost of not addressing the condition that deserved priority.
That is why diagnosis belongs before major discretionary commitments whenever circumstances permit it.
Two Rolls of Dimes
I learned this long before I had the language I use today.
By the end of my third year in business, U.S. Lock was growing. I had a full-time bookkeeper who had replaced my wife when she became pregnant with our first child, my brother was working with me, and I was personally visiting customers.
I could reach about six customers in a day.
Six.
That was what the method allowed.
Inside the business, I also had an AT&T pay phone near the front door. Customers used it. Sometimes they used it to call competitors when I was out of stock or when they believed they might find a better price elsewhere.
I had a practical problem:
How could I reach more customers without spending the day driving from one location to another?
I decided to call regular customers instead of visiting every one personally. I could also use the telephone to reach businesses outside the territory that made economic sense for personal visits.
I went to the bank.
I got two rolls of dimes.
And I started calling.
Two rolls of dimes became a small experiment in changing the method rather than simply applying more effort to the existing one.
I measured what happened.
How many calls?
How many customers?
How much business?
Could I sell customers what I had available rather than waiting for them to come to me looking for a specific item?
The telephone changed reach.
It changed frequency.
It changed geography.
And it changed what was possible with the inventory already in the business.
At the time, I was not conducting a Business Constraint Diagnostic™. There was no Business Constraint Discipline™. I did not have the Seven Classes of Business Constraint™.
I was an operator confronting a ceiling and trying to understand what was actually producing it.
Looking back, what matters to me is not whether I can retroactively assign a formal diagnostic classification to that episode.
What matters is the operating discipline behind it:
Do not assume the visible limitation is the real one. Examine what is actually governing the result before committing more resources to the existing method.
The Question Was Not “How Do I Visit More Customers?”
That would have been the obvious question.
If I had framed the problem that way, several solutions might have followed: hire another salesperson, drive faster, change the territory, schedule visits more tightly, or work longer days.
Those actions would have tried to increase the capacity of the existing method.
The more useful question was different:
Why does customer development have to depend on a personal visit?
That changed the problem.
And once the problem changed, the possible solutions changed with it.
Experimental research has shown that even experienced managers can be influenced by the way a business decision problem is framed. [2]
The practical implication is not that managers can eliminate framing effects.
It is that how the problem is defined can influence which solutions ever become visible.
Before the Hire
Consider a business in which projects are consistently late.
The immediate conclusion may be:
“We need another project manager.”
Possibly.
But what else could be true?
Projects may lack clear authority. Priorities may change constantly. Sales may be committing delivery dates without operating input. Senior management may be overriding schedules. The workflow may contain avoidable rework. Or the business may simply have more volume than the current team can process.
Those possibilities call for different responses.
If capacity is genuinely the limiting condition, hiring may be appropriate. If authority is the issue, another person may enter the same confused structure. If priorities are unstable, the new hire may simply become another person managing instability.
Before approving the position, determine what condition the position is expected to change.
That does not guarantee the hiring decision will be correct.
It makes the reasoning examinable.
Before the Investment
A manufacturer appears to need another machine.
Demand is strong. The schedule is full. Production complains about capacity. The capital expenditure appears obvious.
Before signing the purchase order, management asks a different set of questions.
Is the current equipment actually constrained?
Where is the queue forming?
What product mix is consuming capacity?
How much downtime exists?
What percentage of production is rework?
What happens immediately before and after the apparent bottleneck?
Would another machine increase throughput—or increase inventory waiting somewhere else?
The answers may support the investment.
Or they may reveal that the investment is aimed at the wrong point in the process.
The purpose of diagnosis is not to prevent investment. It is to improve the basis on which the investment is made.
Before the Marketing Program
Growth slows.
The natural response is to create more demand.
Advertising.
Content.
Search.
Social media.
Events.
Lead generation.
That may be exactly what is needed.
But suppose the business already receives enough inquiries. The real problem may be conversion, positioning, slow follow-up, weak credibility, an offer the target customer does not understand, or insufficient delivery capacity that has caused the business to stop pursuing opportunities aggressively.
More marketing could amplify the symptom rather than correct the condition.
Before buying more attention, determine whether lack of attention is actually what is limiting the result.
Before the Partnership
An owner reaches personal capacity.
A partner appears to be the answer.
More capital.
Complementary skills.
Shared responsibility.
Additional relationships.
Again, possibly.
But partnership is a major structural commitment.
Before the agreement is signed, the business should understand what the partnership is intended to address.
Is the business missing capital?
Capability?
Leadership depth?
Sales reach?
Decision capacity?
Accountability?
Or is the owner overloaded because authority has never been distributed effectively?
A partner can help resolve some conditions.
A partner can complicate others.
Adding another owner is not a substitute for understanding why the existing structure has reached its limit.
Before the New System
Software is attractive because it appears concrete.
The company is disorganized.
Install a system. (In business, a system is a structured set of interrelated processes, components, or methods designed to achieve a specific and consistent outcome, often involving people, technology, and information. This includes documented procedures, workflows, and tools that ensure tasks are performed reliably and efficiently across the organization.)
Information is late.
Install a dashboard.
Follow-up is inconsistent.
Install a CRM.
Production is confusing.
Install an ERP.
Sometimes that is exactly right.
But technology can automate confusion as efficiently as it automates clarity.
If roles are undefined, the system inherits undefined roles. If data is poor, the system processes poor data. If people bypass the process, the software becomes another process to bypass.
Research on firm decision quality similarly suggests that more data alone is not enough. Ghasemaghaei and Calic found that the relationship between big-data use and decision quality operated through data quality and data diagnosticity rather than through data use alone. [3]
A better tool does not eliminate the need to understand the problem the tool is supposed to solve.
Urgency Changes the Sequence—but Not the Principle
Not every situation allows a prolonged diagnostic process.
A major customer is threatening to leave today.
Payroll must be funded.
A safety problem requires immediate action.
A legal deadline expires tomorrow.
A cybersecurity breach is underway.
A critical supplier has failed.
Action may have to come first.
This paper does not argue otherwise.
Diagnosis before prescription is a discipline, not a command to ignore urgency.
In an emergency, management may have to stabilize first—stop the loss, protect people, protect cash, protect customers, maintain continuity.
Then diagnosis resumes.
The distinction is between necessary immediate stabilization and major discretionary commitments being made as supposed solutions to an inadequately diagnosed problem.
Those are not the same thing.
Opportunity Can Create the Same Risk
Not every premature commitment begins with a problem.
Some begin with an opportunity.
A building becomes available.
A competitor offers to sell.
A talented executive appears unexpectedly.
A major customer asks the company to enter a new market.
A distributor proposes an exclusive arrangement.
A technology vendor offers favorable terms.
The opportunity may be real.
But urgency can cause management to ask:
“How do we take advantage of this?”
before asking:
“What result are we trying to produce, and does this opportunity address the condition currently limiting that result?”
The answer may still be yes.
The discipline is making that connection explicit before commitment.
When the Solution Starts Looking for a Problem
Sometimes the business does not begin with a problem.
It begins with a solution someone already wants.
“We need AI.”
“We need a COO.”
“We should acquire a competitor.”
“We need to franchise.”
“We should move into a larger facility.”
“We need a new CRM.”
“We should open another location.”
The proposed action then begins accumulating reasons to justify itself.
Cohen, March, and Olsen’s classic organizational-choice model described settings in which problems, solutions, participants, and decision opportunities do not necessarily move in a neat causal sequence. [4]
SAI does not treat that model as validation of the Governing Constraint Principle.
But it highlights a recognizable management risk:
A solution can gain momentum before the problem it is supposed to solve has been established.
The Governing-Constraint Question Changes the Conversation
Suppose management is considering a $500,000 investment.
The normal conversation may focus immediately on the investment.
What does it cost?
How will it be financed?
Which vendor?
What implementation schedule?
What return is projected?
Those are necessary questions.
But another question belongs near the beginning:
What condition is this investment intended to change?
Then:
What evidence indicates that condition is limiting the required result?
What alternatives could address the same condition?
What happens if nothing is done?
What should improve if the diagnosis is correct?
How will management know?
That does not make the decision automatic.
It makes the reasoning visible.
The Seven Classes Help Organize the Examination
There are Seven Classes of Business Constraint™:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
A proposed action may initially appear to belong to one area while the condition limiting the result exists in another.
A sales hire may appear to address Market performance when the limiting condition is Operational capacity.
An equipment purchase may appear Operational while the more important condition is Financial.
A marketing campaign may appear Market-related while Credibility is limiting conversion.
An executive hire may appear Organizational while Strategic ambiguity is preventing effective execution.
Those are possibilities.
Not diagnoses.
The class should follow the evidence. The proposed action should follow the diagnosis.
What Research Adds
External scholarship provides useful context for the decision discipline advanced here.
Nutt examined 202 organizational decisions and found that a discovery-oriented decision process was more successful than idea-imposition approaches and related adaptations across the decisions studied. [1]
Mowen and Mowen found framing effects in experimental business-decision settings, including among experienced managers, demonstrating that the formulation of a decision problem can influence choice. [2]
Ghasemaghaei and Calic, using survey data from 130 firms, found that the value of big-data use for decision quality depended on data quality and data diagnosticity rather than on data use alone. [3]
Cohen, March, and Olsen’s organizational-choice model described how problems, solutions, participants, and decision opportunities may not always align neatly inside organizations. [4]
Nutt’s analysis of failed organizational decisions also emphasized risks associated with premature commitments, spending resources on the wrong things, and failure-prone decision practices. [5]
This scholarship does not establish the SAI proposition that every business is governed by one constraint at a time. It does not validate the Seven Classes of Business Constraint™. It does not prove that an SAI diagnosis will make a particular decision successful.
It supports a narrower intellectual context:
How a problem is framed, what evidence is considered, when commitment occurs, and how alternatives are evaluated can materially affect decision quality.
A Major Decision Should Have a Diagnostic Thesis
Before a significant commitment, management should be able to state the reasoning in a few sentences.
Not:
“We need another salesperson.”
But:
“The result we require is X. The evidence indicates Y is limiting it. We believe this hire addresses Y. If that diagnosis is correct, we expect Z to change.”
Not:
“We need a new system.”
But:
“The result we require is X. The evidence indicates the current process is failing at Y. This system is intended to change Y. We will know it worked if Z occurs.”
That is a diagnostic thesis.
It does not guarantee success.
It gives the decision something management can later test.
What Happens When the Thesis Is Wrong?
Suppose the company makes the hire.
The expected result does not change.
Several explanations are possible.
The diagnosis was wrong.
The hire was wrong.
Implementation was weak.
The measurement period was too short.
Another condition migrated into priority.
External circumstances changed.
The required result was poorly defined.
Confirmation matters because management should not defend a decision merely because resources have already been committed.
A decision should be allowed to teach the business something.
The purpose of diagnostic discipline is not to create certainty.
It is to make learning more structured.
Perfect Information Is Not the Standard
Owners make decisions with incomplete evidence every day.
The relevant standard is not certainty.
It is whether management has examined the problem deeply enough to distinguish an informed hypothesis from a reflexive prescription.
That may take weeks for an acquisition.
Days for a senior hire.
Hours for an operating decision.
Minutes in a fast-moving situation.
The scale of the diagnostic effort should reflect the significance, reversibility, urgency, and uncertainty of the decision.
The larger and less reversible the commitment, the stronger the case for disciplined diagnosis before action.
A Practical Decision Sequence
Before a significant discretionary commitment, begin with the required result.
What are we trying to improve, protect, restore, or create?
Then examine the evidence.
What condition appears to be preventing that result?
Only then should the proposed action be evaluated.
The SAI sequence is:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
IDENTIFY the condition that appears to be governing the required result.
PRIORITIZE it against the other real problems competing for resources.
RESOLVE the condition through an action appropriate to what the evidence indicates.
CONFIRM that the expected result changed and that the improvement holds.
The proposed hire, investment, system, partnership, or strategic initiative belongs primarily in RESOLVE.
That is precisely why IDENTIFY and PRIORITIZE come first.
Five Questions Before the Next Major Commitment
What Result Are We Trying to Change?
State it precisely.
Revenue?
Margin?
Throughput?
Cash conversion?
Decision speed?
Customer retention?
Owner independence?
Without a defined result, almost any solution can appear reasonable.
What Evidence Identifies the Condition Limiting That Result?
Separate symptoms from causes.
Do not assume the most visible problem is the governing one.
Why This Solution?
Explain how the proposed action addresses the identified condition.
If that connection is weak, reconsider the prescription.
What Else Could Produce the Same Symptom?
Force competing explanations into the discussion before commitment.
What Should Change If We Are Right?
Define the evidence that will confirm or challenge the diagnosis after implementation.
A major decision becomes more disciplined when management can explain what it expects the decision to change—and why.
What the Business Constraint Diagnostic™ Can Contribute
The Business Constraint Diagnostic™ does not decide whether to hire someone.
It does not approve capital expenditures.
It does not select software.
It does not evaluate acquisition terms.
It does not determine whether a partnership should be formed.
It does not replace financial modeling, legal advice, technical expertise, strategic planning, or management judgment.
And it does not guarantee that the next business decision will succeed.
Its role is narrower.
After the required business result has been defined, the Diagnostic is designed to help determine the probable governing constraint class indicated by the information supplied and interpret the structural condition that appears to be limiting that result.
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 finding addresses the probable governing constraint class, the structural condition indicated by the supplied evidence, why that condition appears limiting, why prior efforts may not have produced the expected result, and the corrective direction suggested by the diagnosis.
Its relevance before a major commitment is straightforward:
It can help management examine whether the proposed action is aimed at the condition that appears to deserve priority.
Guarantee: “If your written finding does not identify a clear, actionable governing constraint, your $89 will be refunded.”
What This Paper Does Not Claim
This paper does not claim that every business decision requires a formal diagnosis.
It does not claim that urgent action should be delayed when immediate stabilization is required.
It does not claim that identifying a governing constraint guarantees decision success.
It does not claim that every poor decision results from misdiagnosis.
It does not claim that consultants, advisors, planning processes, financial models, or professional judgment are unnecessary.
It does not claim that the U.S. Lock two-rolls-of-dimes episode represents a verified historical Business Constraint Diagnostic™ finding.
And it does not claim that every major decision should be postponed until uncertainty disappears.
The proposition is narrower:
Before a significant discretionary commitment is made, management should understand what condition the action is intended to change and whether the evidence indicates that condition deserves priority.
Implications / Applications
Before the Hire
Determine whether the problem is genuinely insufficient capacity or capability—or whether the existing structure is preventing the current team from producing the required result.
Before the Investment
Determine whether capital addresses the actual limiting condition or merely expands the part of the system already producing the symptom.
Before the System
Determine whether the problem is technological, procedural, organizational, or behavioral.
Before the Partnership
Determine what condition the additional owner is expected to help resolve.
Before the Expansion
Determine whether the current model is ready to reproduce—or whether expansion will reproduce the existing constraint at greater scale.
Before the Strategic Initiative
Determine whether the initiative addresses the condition governing the result management says it wants.
Diagnosis first does not mean action never comes quickly. It means action should be aimed deliberately.
Limitations and Questions for Further Examination
The examples in this paper are illustrative decision patterns and should not be interpreted as verified Business Constraint Diagnostic™ findings.
The two-rolls-of-dimes account reflects Lawrence M. Schneider’s recollection and retrospective interpretation of an early U.S. Lock operating experience. It illustrates the development of his diagnostic thinking but does not establish a formal historical governing-constraint classification.
The external research cited supports the broader intellectual context concerning framing, evidence, organizational decision processes, premature commitment, and decision quality. It does not independently validate the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, or the Business Constraint Diagnostic™.
Significant business decisions also differ in reversibility, urgency, complexity, regulatory exposure, uncertainty, and potential harm. The appropriate diagnostic effort should therefore vary with the decision.
Further examination should consider how organizations distinguish stabilization from long-term resolution, how decision makers test competing explanations before commitment, how diagnostic confidence should vary with reversibility and risk, and how post-decision evidence can be used to confirm, revise, or reject the original diagnosis.
Conclusion
Before the next hire, there will be a reason.
Before the next investment, there will be a reason.
Before the next system, partnership, expansion, or strategic initiative, there will be a reason.
The question is whether that reason describes the symptom or identifies the condition producing it.
I did not understand that distinction in formal terms when I walked into a bank decades ago and asked for two rolls of dimes.
I knew something simpler.
Six customer visits per day was not enough.
And doing more of the same was not the only answer.
The telephone changed the method. The experiment changed what I could observe. And the result changed the way I thought.
Years later, that operating instinct became more disciplined:
Do not begin with the prescription.
Begin with the condition.
Do not assume the visible problem is the one that deserves priority.
Examine the evidence.
Then act.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The hire may still be right.
The investment may still be right.
The system may still be right.
The expansion may still be right.
But after diagnosis, management should know why it believes the decision is right—and what result it expects the decision to change.
That is the difference between spending resources on a solution and directing resources toward the condition that deserves priority.
Before your next major decision, do not ask only: “What should we do?”
Ask first:
“What condition are we actually trying to change?”
Evidence Boundary
This paper advances an SAI interpretive proposition informed by Lawrence M. Schneider’s operating experience, illustrative business situations, and external scholarship concerning organizational decision processes, framing, data diagnosticity, and premature commitment.
The paper does not establish that diagnosis eliminates uncertainty, that formal diagnosis is necessary before every business decision, or that governing-constraint identification guarantees a successful decision.
The Seven Classes of Business Constraint™ remain Market, Operational, Financial, Organizational, Strategic, Leadership, and Credibility.
Illustrative decision patterns in this paper are not verified Business Constraint Diagnostic™ findings and should not be interpreted as specific constraint classifications.
The U.S. Lock two-rolls-of-dimes account is presented as an operating recollection illustrating diagnostic thinking, not as a retrospectively verified application of the current SAI methodology.
External scholarship supports the intellectual context. 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 designed to interpret structural conditions indicated by information supplied. It does not replace professional advice, management judgment, financial analysis, legal review, technical analysis, or emergency decision-making.
References
[1] Nutt, P. C. (2008). Investigating the success of decision making processes. Journal of Management Studies, 45(2), 425–455. https://doi.org/10.1111/j.1467-6486.2007.00756.x
[2] Mowen, M. M., & Mowen, J. C. (1986). An empirical examination of the biasing effects of framing on business decisions. Decision Sciences, 17(4), 596–602. https://doi.org/10.1111/j.1540-5915.1986.tb00245.x
[3] Ghasemaghaei, M., & Calic, G. (2019). Can big data improve firm decision quality? The role of data quality and data diagnosticity. Decision Support Systems, 120, 38–49. https://doi.org/10.1016/j.dss.2019.03.008
[4] Cohen, M. D., March, J. G., & Olsen, J. P. (1972). A garbage can model of organizational choice. Administrative Science Quarterly, 17(1), 1–25. https://doi.org/10.2307/2392088
[5] Nutt, P. C. (2004). Averting decision debacles. Technological Forecasting and Social Change, 71(3), 239–265. https://doi.org/10.1016/S0040-1625(02)00352-9
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
SAI-BOEL-16 — Are You Building the Business—or Only Improving It?
SAI-BOEL-21 — Revenue Tells You What Happened. It Does Not Tell You Why.
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.