The Consultant Delivered Exactly What You Asked For. Was It the Wrong Problem?
SAI WHITE PAPER SERIES
The Consultant Delivered Exactly What You Asked For. Was It the Wrong Problem?
Why the Quality of a Consulting Engagement Depends on What Happens Before the Scope Is Written
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
PUBLICATION IDENTITY
Permanent Publication Identifier: SAI-ACPP-29
Original Publication: June 2026
Current Editorial Revision: September 2026
Version: 2.1
Classification: Advisors, Consultants & Professional Services
Subject: Consulting Scope, Problem Definition, Organizational Diagnosis & Governing-Constraint Identification
Primary Audience: Business Owners, Executives, Advisors, Consultants & Professionals Responsible for Scoping Improvement Engagements
Primary Constraint Relevance: Cross-Class — All Seven Classes
SAI Discipline Stage: IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Evidence Orientation: Interpretive Proposition Supported by Research on Consulting Diagnosis, Problem Definition, Organizational Problem Formulation, Intervention Design, Problem Representation, and Practitioner Observation
Executive Abstract
The consultant did what the scope required.
The deliverables were completed.
The methodology was applied correctly.
The client could point to genuine improvement.
And yet the performance problem that justified the engagement remained.
That outcome does not necessarily mean the consultant failed.
It may mean the engagement was professionally executed against a problem that was real—but not the problem governing performance.
Research on consulting, organizational diagnosis, and problem formulation has long recognized the importance of defining the problem before selecting the intervention. Kilmann and Mitroff warned that entering the consulting process at the solution stage increases the risk of solving the wrong problem. [1] Later work has continued to emphasize diagnosis, problem representation, and intervention fit as important parts of effective organizational change. [2][3][5][6]
This White Paper advances a narrower SAI proposition:
The quality of a consulting engagement depends not only on how well the scope is executed, but on whether enough diagnostic work occurred before the scope was written to establish that the engagement is aimed at the problem deserving priority.
A clear scope can define the work precisely.
It cannot, by itself, establish that the work is aimed at the right problem.
That requires diagnosis.
THE CENTRAL PROPOSITION
A consulting engagement can be well scoped, professionally executed, and genuinely valuable while still failing to resolve the condition governing the client’s performance limitation. The risk arises when the scope is written from the presenting problem before sufficient diagnostic work has established whether that problem deserves priority. The professional question is therefore not only whether the scope is clear. It is whether the scope is aimed at the right problem.
The distinction is fundamental:
Execution quality and diagnostic accuracy are different questions.
A consultant can perform the engagement exactly as promised.
The organization can still discover that it commissioned the wrong work.
Why This Paper Matters
Most consulting engagements require a scope.
The scope establishes boundaries, responsibilities, deliverables, timing, resources, and expectations. Without one, an engagement can become vague, unmanageable, or difficult to evaluate.
The problem is not the scope.
The problem is what happens before it.
If the client arrives saying:
“Our problem is sales.”
the consultant may reasonably begin thinking about sales.
If the client says:
“Turnover is killing us.”
the engagement may naturally move toward retention.
If the client says:
“We need a new CRM.”
the work may move quickly toward technology selection and implementation.
Each problem may be completely real.
But there is another question:
Why does this problem deserve to become the target of the engagement?
That question requires more than defining requested work. It requires examining whether the presenting problem is the condition governing the larger performance limitation, one contributor to it, or the place where another condition has become visible.
Kilmann and Mitroff described a related consulting risk decades ago: beginning with solutions before the problem has been adequately defined can result in solving the wrong problem. [1]
McFillen and colleagues similarly argue that organizational diagnosis affects the appropriateness of the intervention selected. [3]
Research on organizational problem formulation also shows that how organizations define and represent a problem materially shapes what they subsequently attempt to solve. [4][5]
The SAI contribution is more specific:
Before the scope converts a problem into a funded intervention, the problem should pass a diagnostic gate.
THE QUESTION THIS PAPER EXAMINES
A company believes it has a sales problem.
Pipeline is weak.
Revenue has stalled.
The consultant is experienced.
The proposal is strong.
The scope calls for prospecting redesign, sales-process improvement, CRM discipline, manager accountability, and conversion measurement.
The consultant executes all of it professionally.
Sales activity improves.
Revenue barely moves.
Was the engagement poorly executed?
Maybe.
Was implementation incomplete?
Possibly.
Did market conditions change?
Perhaps.
Or was the larger limitation somewhere else?
Maybe the offering had become undifferentiated.
Maybe service failures had weakened credibility.
Maybe pricing no longer fit the target market.
Maybe leadership had committed the company to the wrong segment.
The question is not:
“Was sales a problem?”
The question is:
“Was sales the problem that deserved to define the scope?”
PART I — THE SCOPE IS A COMMITMENT
Once a consulting scope is approved, the organization has done more than describe work.
It has committed money, attention, management time, employees, and organizational energy.
It has also defined success.
In effect, the organization has said:
This is the problem we are going to work on.
That makes the pre-scope decision unusually important.
A scope converts an interpretation of the problem into an intervention.
If the interpretation is sound, the scope creates disciplined execution.
If the interpretation is weak, the scope can create disciplined execution against the wrong target.
Professional execution cannot compensate for a target that was never adequately tested.
PART II — A REAL PROBLEM IS NOT AUTOMATICALLY THE PRIORITY PROBLEM
One of the most important distinctions in diagnostic work is between a problem that exists and a problem that deserves priority.
A company may genuinely have weak sales, high turnover, slow production, margin pressure, poor delegation, inconsistent execution, or customer attrition.
None of those conditions should be dismissed.
But an organization can contain several legitimate problems at the same time.
The consulting question is therefore not simply:
“Is this problem real?”
It is:
“What evidence indicates that this problem is governing the performance limitation we are trying to change?”
That is a higher standard.
A problem can justify attention without necessarily justifying priority.
And a problem worthy of attention may still be the wrong basis for the next consulting engagement.
PART III — HOW THE WRONG PROBLEM CAN ENTER THE SCOPE
Three pathways deserve particular attention.
The Client Names the Problem
Clients often know where the pain is.
They may know exactly which metric has deteriorated, which function is struggling, or where costs are appearing.
That knowledge matters.
But proximity to the pain does not automatically establish causation.
The client’s description should begin the inquiry.
It should not automatically end it.
The Consultant Recognizes a Familiar Pattern
Expertise creates pattern recognition.
That is one reason organizations hire specialists.
A sales consultant recognizes sales problems.
An operations consultant recognizes process problems.
A leadership advisor recognizes leadership patterns.
A technology consultant recognizes systems deficiencies.
That depth is valuable.
But specialization can narrow the diagnostic field too early.
When the method arrives before the diagnosis, the method can begin defining the problem.
The Proposal Process Rewards Speed
Clients want answers.
Consultants need enough specificity to price and scope the engagement.
That creates practical pressure to move from problem description to proposed intervention quickly.
There is nothing inherently wrong with that.
But the faster the movement from complaint to solution, the more important it becomes to test whether the underlying problem definition is strong enough to support the scope.
PART IV — WHY PROBLEM DEFINITION DESERVES ITS OWN STEP
Problem formulation is not merely administrative preparation for solving a problem.
It is part of the problem-solving process itself.
Lyles and Mitroff’s empirical work examined how organizations formulate problems and how managerial characteristics can influence that process. [4]
More recent research synthesizing multiple organizational literatures likewise emphasizes that complex problems require organizations to develop and revise problem representations before effective action can follow. [5]
That matters for consulting because the scope is downstream from the representation.
If the problem is represented as:
“We need more leads,”
the intervention may become marketing or sales.
If the problem is represented as:
“Prospects enter the funnel but do not see sufficient differentiation to choose us,”
the scope changes.
If the problem is represented as:
“The owner is overloaded,”
the engagement may become time management.
If the problem is represented as:
“Decision authority is concentrated at the top and managerial roles lack sufficient authority,”
the scope changes again.
How the problem is defined changes what work appears reasonable.
That is why diagnosis belongs before commitment.
PART V — EXCELLENT EXECUTION CAN MAKE THE DIAGNOSTIC ERROR HARDER TO SEE
Poor execution is visible.
Deadlines are missed.
Deliverables are incomplete.
Recommendations are vague.
Implementation breaks down.
The client knows something went wrong.
Excellent execution creates a different risk.
The consultant delivers.
The team participates.
Measures improve.
The engagement feels successful.
That success can temporarily reduce curiosity about whether the larger limitation changed.
Consider an illustrative example.
A manufacturer hires an operations consultant because output per labor hour has deteriorated.
The consultant redesigns workflow, reduces movement, improves scheduling discipline, and increases throughput.
Those improvements are real.
Six months later, the company still cannot meet customer demand reliably.
Further examination reveals that significant production decisions continue waiting for owner approval.
The operations work was not wrong.
The engagement created value.
But the larger limitation may have been connected to decision architecture rather than production technique.
The consultant solved a real problem. The business still had to determine whether it had solved the governing one.
PART VI — THE SAI PRE-SCOPE DIAGNOSTIC GATE
Before a significant consulting scope is approved, SAI proposes five questions.
These questions do not replace professional judgment.
They create a disciplined pause between problem description and funded intervention.
1. THE PROBLEM TEST
What problem are we actually asking the consultant to solve?
The answer should be specific enough to distinguish the observed condition from the desired result.
“Growth” is not a problem definition.
“Sales are weak” may still be too broad.
The organization should be able to state what is occurring, where it is occurring, and how it is limiting performance.
2. THE EVIDENCE TEST
What evidence indicates that this problem is governing the performance limitation?
This is different from asking why the problem matters.
The question is why it deserves priority.
Visibility is not the same as causation.
3. THE ALTERNATIVE-CAUSE TEST
What other conditions could plausibly produce the same symptom?
Weak revenue can arise from several different conditions.
Turnover can have several causes.
Margin pressure can originate in pricing, operating efficiency, purchasing, customer mix, financing, strategy, or a combination of conditions.
If plausible alternatives have not been considered, the scope may be premature.
4. THE PRIORITY TEST
Why should this problem be addressed before the other legitimate problems in the business?
Organizations rarely have only one problem.
Priority therefore requires evidence.
The answer should connect the proposed target to the performance result the organization is trying to change.
5. THE CONFIRMATION TEST
What result would tell us that the scope was aimed at the right problem?
This question belongs before the engagement begins.
It establishes what evidence would support the diagnosis.
It also establishes what result should cause the organization to reopen it.
Together, these five questions form the:
SAI PRE-SCOPE DIAGNOSTIC GATE
Problem → Evidence → Alternatives → Priority → Confirmation
Its purpose is simple:
Do not allow a presenting problem to become a funded consulting scope until the organization can explain why THAT problem deserves to be the target.
PART VII — ILLUSTRATIVE SCENARIO: THE PIPELINE PROBLEM
A professional services firm believes its revenue problem is an insufficient pipeline.
The diagnosis appears obvious.
Too few opportunities.
A consultant builds a stronger prospecting cadence, qualification framework, and accountability process.
Pipeline volume rises substantially.
Revenue does not rise proportionately.
What did the engagement establish?
Not that sales consulting does not work.
Not that the consultant chose the wrong methodology.
It established that increasing pipeline activity alone did not remove the larger performance limitation.
Further examination may find that prospects are entering the funnel but choosing competitors because the firm’s offering is poorly differentiated.
The original sales problem was real.
But it may not have been governing.
The improvement narrowed the diagnosis.
That is useful information.
PART VIII — ILLUSTRATIVE SCENARIO: THE TURNOVER PROBLEM
A hospitality company experiences persistent employee turnover.
An HR consultant improves onboarding, compensation benchmarking, manager communication, and recognition.
Turnover improves.
Then it begins rising again.
That pattern has several possible explanations.
Implementation may have weakened.
Labor-market conditions may have changed.
Manager behavior may have deteriorated.
Compensation may again be uncompetitive.
Or another structural condition may remain.
Further diagnosis might find that scheduling unpredictability is the condition employees continue finding unsustainable.
If so, the HR engagement may still have created real value.
The mistake would be concluding that because the interventions were useful, they necessarily addressed the condition governing turnover.
Improvement is evidence. Recurrence is evidence too.
Both should inform the next diagnosis.
PART IX — THE SCOPE SHOULD FOLLOW THE FINDING, NOT REPLACE IT
A scope answers important questions:
What work will be performed?
By whom?
Over what period?
With what deliverables?
At what cost?
Using what methodology?
Those are essential questions.
But they are downstream questions.
The diagnostic questions come first:
What condition appears to be limiting performance?
What evidence supports that conclusion?
What competing explanations remain plausible?
Why does this problem deserve priority?
What result would confirm that the target was correctly identified?
The relationship between the two should therefore be:
Diagnosis informs scope.
Not:
Scope becomes diagnosis.
The required diagnostic depth will vary with the consequence, complexity, uncertainty, and cost of the engagement.
Not every consulting project requires weeks of analysis.
But significant engagements should be built on an explicit problem hypothesis strong enough to test.
PART X — WHEN THE CLIENT IS RIGHT
A disciplined diagnostic process must allow a straightforward conclusion:
The client identified the right problem.
Diagnosis is not an exercise in proving the client wrong.
An owner may say:
“Our operational throughput is limiting growth.”
The evidence may support it.
Alternative explanations may be considered.
The issue may clearly deserve priority.
The scope should proceed.
The value of diagnosis is not that it always changes the answer.
The value is that it establishes why the answer deserves confidence.
Diagnosis before prescription does not mean distrust the client. It means test the problem before funding the solution.
PART XI — WHEN THE CONSULTANT IS RIGHT
The same principle applies to professional expertise.
A consultant may identify the problem quickly because they have seen the pattern many times.
That recognition can be correct.
The pre-scope discipline should not suppress expertise.
It should test it.
Experienced consultants often form useful hypotheses rapidly.
The distinction is between:
a hypothesis that guides inquiry
and
a conclusion that closes inquiry.
The consultant’s expertise should accelerate diagnosis.
It should not eliminate it.
PART XII — THE SEVEN CLASSES WIDEN THE FIELD BEFORE THE SCOPE NARROWS IT
SAI organizes potential governing constraints into the Seven Classes of Business Constraint™:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
The purpose is not to force every engagement through seven equal possibilities.
It is to prevent the presenting symptom or consultant specialty from narrowing the field too early.
A revenue decline may initially appear to be a Market problem.
But Strategic positioning, Operational failure, Credibility loss, Leadership decisions, Financial restrictions, or Organizational execution may also warrant examination.
A production problem may genuinely be Operational.
Or operations may simply be where another limitation becomes visible.
Before the scope narrows the intervention, diagnosis should widen the inquiry.
Then the evidence narrows it again.
PART XIII — DESIGN THE CONFIRMATION STANDARD BEFORE THE WORK BEGINS
A consulting engagement should not wait until completion to decide what success means.
Research on organizational interventions emphasizes understanding the starting situation, aligning intervention logic with objectives, and evaluating the relationship between intervention, process, and context. [6]
For consulting scope, that suggests a practical discipline:
define the confirmation standard before implementation begins.
What should change?
By how much?
Over what period?
What should remain improved after the consultant leaves?
What result would weaken confidence in the original problem definition?
That last question is especially important.
If no possible result could cause the organization to reconsider the diagnosis, the diagnosis has become an assumption rather than a testable finding.
PART XIV — WHEN THE EXPECTED RESULT DOES NOT APPEAR
If the engagement does not produce the expected result, the response should not automatically be:
more implementation,
a new consultant,
or a larger version of the same intervention.
Nor should the organization automatically conclude that the diagnosis was wrong.
Implementation may have failed.
External conditions may have changed.
The intervention may have been insufficient.
A constraint may have migrated.
Or the scoped problem may not have been governing performance.
The professional task is to distinguish among those explanations.
A result that fails to confirm the diagnosis should reopen the diagnosis.
That is how consulting work becomes cumulative learning rather than a series of disconnected engagements.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The Business Constraint Discipline™ uses the sequence:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The SAI Pre-Scope Diagnostic Gate sits primarily between IDENTIFY and RESOLVE.
IDENTIFY asks what condition appears to be limiting performance.
PRIORITIZE determines whether that condition deserves attention before competing problems.
Only then should the engagement be scoped around RESOLVE.
CONFIRM determines whether the expected improvement occurred and whether it held.
The scope is therefore not the beginning of the reasoning process.
It is the operational expression of reasoning that should already have occurred.
Where the Business Constraint Diagnostic™ Fits
The Business Constraint Diagnostic™ is SAI’s structured instrument for examining the probable governing constraint class and structural condition indicated by the information supplied.
It contains 81 questions, typically takes approximately 30 minutes, costs $89, and produces a 2,200+ word written finding within 72 hours.
In the context of consulting scope, its role is narrow:
to provide an additional structured diagnostic input before a significant engagement is aimed at a presenting problem.
It does not guarantee that the resulting scope will be correct.
It does not eliminate implementation risk.
It does not establish causation with certainty.
And it does not guarantee that consulting results will hold.
Its relevance is sequencing:
diagnostic examination before scope commitment.
Guarantee: “If your written finding does not identify a clear, actionable governing constraint, your $89 will be refunded.”
Where the SAI Credentials Fit
The FDC — Foundational Diagnostic Credential develops foundational diagnostic capability for business owners and leaders.
The CAS — Certified Axiom Strategist is designed for advisors and consultants and includes the FDC curriculum.
The CAE — Certified Axiom Executive is designed for C-Suite executives and includes the FDC and CAS curricula.
The Business Constraint Diagnostic™ is the common prerequisite for all three.
Their relevance here is diagnostic capability: helping the owner, executive, or advisor distinguish a presenting problem from the condition that appears to deserve priority before an engagement is scoped.
A credential does not guarantee correct diagnosis.
It develops a disciplined way to ask better diagnostic questions before intervention begins.
What This Paper Does Not Claim
This paper does not claim that consultants generally solve the wrong problem.
It does not claim that clients are usually wrong about what is limiting their businesses.
It does not claim that every consulting scope requires an extensive diagnostic project before work begins.
It does not claim that a presenting problem is merely a symptom in every case.
It does not claim that recurrence proves the original diagnosis was wrong.
It does not claim that strong execution cannot create substantial value even when the larger performance limitation remains.
It does not claim that the Business Constraint Diagnostic™ guarantees a correct scope or that SAI credentials guarantee better consulting outcomes.
And it does not claim that external research independently validates the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, or the SAI Pre-Scope Diagnostic Gate.
The proposition is narrower:
Before a significant problem becomes a funded consulting scope, the organization should establish why that problem deserves to be the target.
Implications / Applications
For the business owner, the question before signing the next consulting proposal is:
“What evidence tells me this is the problem I should be paying someone to solve first?”
For the consultant:
“Am I scoping the problem the client described—or the problem the evidence indicates deserves priority?”
And for both:
“What should change if this scope is aimed at the right problem?”
If those questions cannot yet be answered, the engagement may still prove useful.
But the organization should understand what has not yet been established.
Limitations and Questions for Further Examination
The external literature provides meaningful support for the importance of problem definition, organizational diagnosis, problem representation, and intervention design.
Kilmann and Mitroff argued that entering the consulting process at the solution stage increases the risk of solving the wrong problem. [1]
Ma describes diagnosis as an essential phase of the consultancy cycle and emphasizes context-specific investigation of underlying organizational issues. [2]
McFillen and colleagues argue that more rigorous organizational diagnosis can improve the appropriateness of interventions chosen. [3]
Lyles and Mitroff’s empirical study demonstrates that problem formulation is itself an organizational process influenced by managerial interpretation. [4]
Ananth, Baer, and Deichmann synthesize research across multiple organizational literatures showing that the way complex problems are represented matters to how organizations subsequently address them. [5]
Von Thiele Schwarz and colleagues emphasize understanding the starting situation, explicating intervention logic, and evaluating intervention, process, and context together. [6]
These sources support the intellectual context for the paper.
They do not independently validate the SAI proposition that every business is governed by one constraint at a time.
They do not validate the SAI Pre-Scope Diagnostic Gate.
They do not establish that consulting engagements commonly fail because scope precedes diagnosis.
Those propositions remain appropriate for further empirical examination.
Future research could test whether explicit pre-scope diagnostic review materially changes engagement scope, improves intervention-target alignment, reduces repeated problem-framing errors, or produces better confirmation learning after the engagement.
Those questions should be tested rather than assumed.
Conclusion
A consultant can deliver exactly what the client requested.
On time.
On budget.
With professional excellence.
And the business can still discover that it asked for the wrong work.
That possibility does not diminish consulting.
It raises the standard for what should happen before consulting begins.
The scope should tell the consultant what to do. The diagnosis should tell the organization why that work deserves to be done.
Those are different professional acts.
The most important question before signing the next engagement may therefore not be:
“Is this a good scope?”
It may be:
“What makes us confident this scope is aimed at the right problem?”
Because execution begins after the scope is approved.
But the quality of the engagement may have been determined before the first deliverable was ever written.
Evidence Boundary
This White Paper advances an SAI interpretive proposition concerning consulting scope, problem definition, organizational diagnosis, and governing-constraint identification.
External research cited here supports the intellectual context surrounding problem definition, organizational diagnosis, problem formulation, problem representation, intervention design, and evaluation.
It does not independently validate the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, the Business Constraint Diagnostic™, SAI credentials, or the SAI Pre-Scope Diagnostic Gate.
The scenarios in this paper are illustrative. They are not presented as verified client histories, documented SAI case studies, or proven causal outcomes.
The Seven Classes of Business Constraint™ are Market, Operational, Financial, Organizational, Strategic, Leadership, and Credibility.
The SAI Pre-Scope Diagnostic Gate is a practitioner framework proposed for examination. It has not been independently validated.
The proposition that one governing constraint exists at a time is an SAI proposition and should be distinguished from findings in the external consulting and organizational-diagnosis literature.
References
[1] Kilmann, R. H., & Mitroff, I. I. (1979). Problem Defining and the Consulting/Intervention Process. California Management Review, 21, 26–33. DOI: 10.2307/41165304.
[2] Ma, X.-T. (2023). The Diagnostic Phase of the Consultancy Cycle. Management Consulting Journal, 6, 7–14. DOI: 10.2478/mcj-2023-0002.
[3] McFillen, J. M., O’Neil, D. A., Balzer, W. K., & Varney, G. H. (2013). Organizational Diagnosis: An Evidence-Based Approach. Journal of Change Management, 13, 223–246. DOI: 10.1080/14697017.2012.679290.
[4] Lyles, M. A., & Mitroff, I. I. (1980). Organizational Problem Formulation: An Empirical Study. Administrative Science Quarterly, 25, 102–119. DOI: 10.2307/2392229.
[5] Ananth, P., Baer, M., & Deichmann, D. (2024). Developing Problem Representations in Organizations: A Synthesis Across Literatures and an Integrative Framework. Journal of Management, 51, 2212–2244. DOI: 10.1177/01492063241291532.
[6] von Thiele Schwarz, U., Nielsen, K., Edwards, K., Hasson, H., Ipsen, C., Savage, C., Richter, A., Lornudd, C., Mazzocato, P., & Reed, J. E. (2020). How to Design, Implement and Evaluate Organizational Interventions for Maximum Impact: The Sigtuna Principles. European Journal of Work and Organizational Psychology, 30, 415–427. DOI: 10.1080/1359432X.2020.1803960.
Related SAI Resources
Business Constraint Diagnostic™
FDC — Foundational Diagnostic Credential
CAS — Certified Axiom Strategist
CAE — Certified Axiom Executive
Before You Scope the Consulting Engagement, Are You Sure You’re Solving the Right Problem?
The Method Is Not the Diagnosis
Same Problem. Different Consultant. What Constraint Keeps Surviving?
Are You Advising the Client—or Protecting the Relationship?
The Seven Classes of Business Constraint™
For Business Owners
For Advisors
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.