Before You Scope the Consulting Engagement, Are You Sure You’re Solving the Right Problem?
SAI WHITE PAPER SERIES
Before You Scope the Consulting Engagement, Are You Sure You’re Solving the Right Problem?
How Advisors and Consultants Can Distinguish the Client’s Presenting Problem From the Condition Governing Performance
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
PUBLICATION IDENTITY
Permanent Publication Identifier: SAI-ACPP-21
Original Publication: June 2026
Current Editorial Revision: September 2026
Version: 2.0
Classification: Advisors, Consultants & Professional Services
Subject: Engagement Scoping, Problem Formulation & Governing-Constraint Diagnosis
Primary Audience: Management Consultants, Strategy Consultants, Operations Consultants, Advisors, Coaches, Fractional Executives & Other Professional-Service Practitioners
Primary Constraint Relevance: Cross-Class — All Seven Classes
SAI Discipline Stage: IDENTIFY → PRIORITIZE
Evidence Orientation: Interpretive Proposition Supported by Problem-Framing, Strategic-Problem-Formulation, Organizational Decision-Making, Cognitive-Bias, and Problem-Solving Research, Operating Observation, and Illustrative Scenarios
Executive Abstract
The client calls with a problem.
Sales are down.
Margins are shrinking.
The team is not executing.
The owner cannot get out of the weeds.
Inventory is too high.
Growth has stalled.
The consultant knows how to help.
A methodology exists.
A proposal can be written.
A scope can be defined.
And that is precisely where the risk begins.
The client has described a real problem.
But has anyone established that it is the problem governing performance?
A strategy consultant may receive a strategy problem.
An operations consultant may receive an operations problem.
A sales consultant may receive a sales problem.
An organizational consultant may receive a structure problem.
Each may be real.
Each may deserve attention.
But the engagement can still be aimed at the wrong priority.
Research on organizational problem formulation helps explain why. Strategic problems are often difficult to define, managers may overfocus on visible symptoms or obvious causes, and the way a problem is framed can materially influence the solution path that follows. [1][2][3][4]
That leads to a simple professional question:
Should the scope define the diagnosis—or should the diagnosis define the scope?
SAI’s answer is clear:
The scope should follow the diagnosis. The diagnosis should not be forced to fit the scope.
THE CENTRAL PROPOSITION
Consulting engagements are commonly scoped around the problem the client can describe and the expertise the consultant was retained to provide. Both may be legitimate. But neither establishes that the problem being scoped is the condition governing performance. Governing-constraint diagnosis adds a prior step: determine what is governing performance and what deserves priority before deciding what expertise, methodology, or engagement should be applied.
A consultant can solve the stated problem.
The harder question is:
Was it the problem that should have been solved first?
Why This Paper Matters
Consultants are trained to solve problems.
Clients hire them because they possess expertise, frameworks, methods, perspective, and experience that the client does not have internally.
That is valuable.
The risk lies earlier.
Before the methodology.
Before the recommendations.
Before implementation.
Before the deliverables.
The first professional decision is what problem the engagement is actually solving.
Research on problem formulation supports the importance of that decision.
Park, Baer, and Nickerson found that managers benefit from combining concrete attention to symptoms with more abstract examination of underlying causes when framing strategic problems. Their work emphasizes that focusing only on visible symptoms or obvious causes can narrow problem understanding. [1]
Baer, Dirks, and Nickerson argue that complex problems can be formulated too narrowly and that structured inquiry can improve problem definition before solution development begins. [2]
Nutt’s study of 177 organizational decisions found that reframing was associated with stronger decision outcomes than several more commonly used formulation approaches, despite being used less often. [3]
Laureiro-Martinez, Arrieta, and Brusoni similarly distinguish between problem-solving strategies centered on framing and those centered on implementation, showing that attention to framing changes how decision makers restructure the problem before acting. [4]
Research on strategic problem formulation also suggests that “solution jumping”—moving too quickly toward a preferred answer—can impair problem-formulation performance. [5]
None of this research validates the SAI governing-constraint proposition.
But it supports a disciplined consulting question:
Before we decide how to solve the problem, have we established what problem deserves priority?
THE QUESTION THIS PAPER EXAMINES
The client says:
“We need a strategy consultant.”
Do they?
The client says:
“Our sales team is the problem.”
Is it?
The client says:
“We need better accountability.”
Perhaps.
The consultant says:
“This fits our methodology.”
It may.
But fit with a methodology is not the same as diagnostic priority.
The question is:
What condition is actually governing the result the client is trying to change?
PART I — THE CLIENT’S PROBLEM DESCRIPTION IS EVIDENCE, NOT THE DIAGNOSIS
Clients usually describe the business through symptoms they can see.
Revenue is down.
Gross margin is deteriorating.
Execution is inconsistent.
Turnover is rising.
Inventory is growing.
Managers are not accountable.
The owner is overwhelmed.
Those observations matter.
They are not mistakes.
But they are not necessarily diagnoses.
A client may be correct that sales are weak.
The harder question is why.
The issue may be sales execution.
Or positioning.
Or pricing.
Or capacity.
Or customer concentration.
Or fulfillment problems that are damaging repeat business.
Or leadership behavior that prevents the sales team from making decisions.
The presenting problem is the starting point.
It should not automatically become the engagement scope.
PART II — EXPERTISE CAN NARROW THE QUESTION TOO EARLY
Professional expertise is valuable because it gives the practitioner a way to interpret what they see.
But expertise can create a predictable risk:
The problem begins to look like something the methodology already knows how to solve.
A sales consultant sees pipeline discipline.
An operations consultant sees throughput.
A leadership coach sees behavior.
A strategy consultant sees positioning.
An organizational consultant sees structure.
None of those perspectives is inherently wrong.
But each is partial.
The professional question is not:
“Can I solve this?”
It is:
“Is this what should be solved first?”
That distinction separates expertise from diagnosis.
Illustrative Scenario: The Strategy Engagement That Cannot Execute
A company’s revenue has stalled.
Management concludes the market strategy is outdated.
A strategy consultant is hired.
The work is competent.
Customer segments are refined.
Positioning improves.
The growth plan is clear.
But implementation stalls.
Why?
Perhaps the strategy was wrong.
But what if the strategy is sound and the governing condition is Organizational?
Three executives share authority over market decisions.
Regional leaders receive conflicting priorities.
No one owns implementation end-to-end.
The strategy engagement addressed a real issue.
The governing condition may still be elsewhere.
A good strategy cannot compensate indefinitely for an organization that cannot execute it.
Illustrative Scenario: The Operations Engagement That Improves the Wrong Metric
A manufacturer has late orders and margin pressure.
An operations consultant is retained.
Scheduling improves.
Setup time falls.
Throughput increases.
The project succeeds against its stated objectives.
But profitability remains weak.
What if operations were not governing performance?
What if the company’s product mix has shifted toward low-margin work?
What if the Market or Strategic condition sits upstream from the operational symptoms?
The operating improvement is real.
The engagement may still have been aimed at a secondary problem.
Improvement does not prove priority.
Illustrative Scenario: The Sales Problem That Is Not Really a Sales Problem
A company misses revenue targets for three quarters.
The sales team is blamed.
A sales consultant installs a stronger pipeline process.
Activity improves.
Follow-up improves.
Conversion improves modestly.
Revenue still underperforms.
What if prospects are rejecting the offer because the company’s positioning has become less relevant?
What if delivery failures have damaged Credibility?
What if capacity limitations make the company reluctant to pursue the accounts required for growth?
The sales problem exists.
It may not be governing performance.
PART III — ONCE THE SCOPE IS APPROVED, THE QUESTION CHANGES
Once an engagement is scoped, a powerful shift occurs.
The question changes from:
“What is actually wrong?”
to:
“How do we deliver what we agreed to do?”
That shift is rational.
The client approved the proposal.
The consultant committed resources.
The team expects deliverables.
Milestones have been established.
The engagement now has momentum.
Evidence that contradicts the original scope can therefore become harder to act on—not because the consultant is dishonest, but because the work is already organized around a working explanation.
That is why diagnosis belongs before scope whenever possible.
The earlier the commitment, the harder the reframing.
PART IV — WHAT HAPPENS WHEN NEW EVIDENCE POINTS OUTSIDE THE SCOPE?
This is where diagnostic integrity becomes visible.
Suppose an operations consultant begins an engagement and discovers that the principal limitation is not Operational.
It is Strategic.
Or Financial.
Or Organizational.
What should happen?
The weakest response is to force the new evidence back into the existing methodology.
The stronger response may be to:
Change the scope.
Pause the engagement.
Bring in another specialist.
Refer the client elsewhere.
Separate the secondary work from the governing problem.
Or tell the client plainly:
“The problem you hired me to solve is real. I no longer believe it is the problem that deserves priority.”
That is a difficult professional conversation.
It is also what diagnostic integrity can require.
PART V — THE SEVEN CLASSES WIDEN THE FIELD BEFORE SPECIALIZATION NARROWS IT
SAI organizes potential governing constraints into the Seven Classes of Business Constraint™:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
The purpose of the Seven Classes is not to make every consultant competent in every domain.
It is to prevent premature narrowing.
Before the engagement is scoped, the practitioner can ask:
Could the presenting Market problem actually be Operational?
Could Financial pressure be downstream from Strategy?
Could a Leadership issue actually be Organizational?
Could the apparent execution problem be Credibility?
Could a Strategic problem be constrained by a Financial structure that prevents execution?
The Seven Classes widen the diagnostic field.
The consultant’s specialization can narrow it later.
Diagnosis should widen before expertise narrows.
PART VI — THE WRONG PRIORITY CAN STILL PRODUCE GOOD WORK
This distinction matters.
A misprioritized engagement is not necessarily a bad engagement.
The consultant may deliver excellent work.
The client may improve.
The recommendations may be useful.
The organization may become more capable.
The problem may genuinely be reduced.
But the result may still fall short of what the client expected because another condition remained governing.
This is why consulting evaluation should distinguish:
Quality of execution
from
Correctness of priority
A consultant can score highly on the first and still miss the second.
Professional competence does not eliminate the need for diagnostic discipline.
PART VII — RECURRING ENGAGEMENTS ARE NOT AUTOMATIC EVIDENCE OF FAILURE
A client may hire the same consultant repeatedly for good reasons.
The business changes.
New problems emerge.
Growth creates new constraints.
The governing constraint migrates.
The client values continuing strategic support.
A prior engagement solves one problem and exposes another.
Repeat work is not inherently evidence of misdiagnosis.
But repetition can still provide useful evidence.
If substantially the same problem keeps returning, the consultant should ask:
Are we dealing with recurrence—or a new problem that merely looks familiar?
What changed after the last engagement?
What did not change?
What keeps recreating the same condition?
Did the prior scope address the governing problem—or improve a secondary condition?
Recurring work should not automatically be criticized.
It should be interpreted.
PART VIII — THE PROFESSIONAL STANDARD IS NOT “NEVER BE NEEDED AGAIN”
The goal of consulting is not to make every future advisory relationship unnecessary.
Businesses change.
Markets change.
Leadership changes.
Constraints migrate.
The client may need the same consultant again for a completely different reason.
The more defensible professional standard is:
Do not preserve your relevance by solving the wrong problem.
A strong consultant should be willing to say:
“This is not my problem to solve.”
or:
“This problem is real, but it is not the one I would address first.”
or:
“The evidence has changed. The scope should change with it.”
That is not commercial weakness.
It is diagnostic credibility.
PART IX — REFERRAL IS PART OF DIAGNOSTIC DISCIPLINE
A consultant who identifies a governing condition outside their expertise has not failed.
They may have diagnosed more accurately.
The next step may be referral.
An Operational specialist may need to refer to an Organizational specialist.
A strategy consultant may need a Financial specialist involved.
A leadership advisor may discover a Market issue.
A CPA may identify a Strategic problem.
A coach may identify an Operational condition.
The practitioner who knows where their expertise stops can be more valuable than the practitioner who insists every problem fits their method.
The client does not need every consultant to solve every problem.
The client needs the right problem identified before the wrong specialist is asked to solve it.
PART X — THE SCOPING CONVERSATION SHOULD BEGIN EARLIER
A conventional scoping conversation often begins with:
What problem are you experiencing?
What outcome do you want?
What work should we perform?
How long will it take?
What will it cost?
Those questions are necessary.
But they may be premature if the problem has not been sufficiently formulated.
A more diagnostic sequence begins earlier:
What result is being limited?
What evidence shows where the limitation appears?
What competing explanations could produce the same symptom?
Which explanation is best supported?
Which condition deserves priority?
What expertise is appropriate once that condition is identified?
Only then:
What should the engagement scope include?
The principle is straightforward:
The scope should follow the diagnosis. The diagnosis should not be forced to fit the scope.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The Business Constraint Discipline™ uses the sequence:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
IDENTIFY asks what condition appears to be governing the client’s performance limitation.
PRIORITIZE asks whether that condition deserves attention before the other legitimate problems the client could address.
RESOLVE determines what expertise, methodology, practitioner, or intervention should be applied.
CONFIRM asks whether the expected improvement occurred and whether the result supports the diagnosis.
That sequence prevents a common reversal:
Methodology first.
Diagnosis second.
SAI reverses it.
Diagnosis first. Methodology second.
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.
The finding addresses the probable governing constraint class, structural condition, why that condition appears limiting, why prior efforts may not have produced the required improvement, and the indicated corrective direction.
For an advisor or consultant, the Diagnostic can provide a structured input before the engagement is scoped.
It does not replace professional judgment.
It does not guarantee that the subsequent engagement will succeed.
It does not independently establish causation.
It does not make the consultant competent outside their field.
It does not replace specialized analysis, technical assessment, financial review, legal advice, operational expertise, market research, or other professional disciplines.
Its role is diagnostic: to help determine what deserves priority before the professional decides what work should be performed.
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 credentials.
For advisors and consultants, the CAS — Certified Axiom Strategist is particularly relevant because it adds diagnostic capability before the practitioner applies their existing specialty.
The purpose is not to replace professional expertise.
It is to determine where that expertise should be applied first.
What This Paper Does Not Claim
This paper does not claim that consultants commonly act in bad faith.
It does not claim that recurring consulting relationships are evidence of professional failure.
It does not claim that clients always misidentify their own problems.
It does not claim that consultants should refuse engagements whenever another issue exists.
It does not claim that the presenting problem is unimportant.
It does not claim that governing-constraint diagnosis eliminates uncertainty.
It does not claim that the Business Constraint Diagnostic™ is the only valid form of organizational diagnosis.
It does not claim that external research independently validates the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, the Business Constraint Diagnostic™, or SAI credentials.
The proposition is narrower:
Before an advisor or consultant scopes an engagement, there is value in distinguishing the problem the client can describe from the condition that appears to be governing performance.
Implications / Applications
The client says:
“We need a strategy engagement.”
The consultant can ask:
“What evidence tells us strategy is governing the result?”
The client says:
“Our salespeople need training.”
The consultant can ask:
“What would we expect to see if capability were the problem—and do we see it?”
The client says:
“The team needs accountability.”
The advisor can ask:
“Do they lack accountability—or authority?”
The consultant discovers halfway through the work that the problem lies outside the original scope.
The question becomes:
“What does diagnostic integrity require now?”
Sometimes the answer is to continue.
Sometimes to change direction.
Sometimes to bring in another specialist.
Sometimes to stop.
That is not a weakness in the consulting process.
It is what happens when evidence outranks commitment to the original explanation.
Limitations and Questions for Further Examination
The external literature cited here supports the importance of problem framing and formulation before solution design.
Park, Baer, and Nickerson found that both concrete attention to symptoms and more abstract consideration of underlying causes can improve strategic problem framing. [1]
Baer, Dirks, and Nickerson argue that structured problem formulation can broaden problem definition and reduce premature narrowing. [2]
Nutt found that reframing was associated with stronger decision outcomes than several more frequently used formulation tactics. [3]
Laureiro-Martinez, Arrieta, and Brusoni provide evidence that attentional focus influences whether decision makers emphasize framing or implementation. [4]
Heiman and Hurmelinna-Laukkanen found that solution jumping and dominance biases can impair strategic problem formulation. [5]
These findings support the broader importance of defining the problem before acting on it.
They do not establish SAI’s governing-constraint proposition.
Further examination should test whether governing-constraint diagnosis improves engagement scoping, changes which specialists are selected, produces consistent findings across trained evaluators, affects engagement re-scoping, and is associated with measurably different client outcomes.
Those are empirical questions. They should be tested rather than assumed.
Conclusion
The client has a problem.
That problem may be real.
It may even be urgent.
The consultant may have exactly the expertise required to solve it.
But one question belongs before the scope:
Is this the problem governing performance?
If the answer is yes, scope the engagement.
If the answer is no, change the priority.
If the evidence is uncertain, keep diagnosing.
If the governing condition falls outside the consultant’s expertise, bring in someone else.
If new evidence changes the diagnosis, change the scope.
The standard is not:
“Can I solve this problem?”
The higher standard is:
“Is this the problem that should be solved first?”
That is the discipline.
The scope should follow the diagnosis.
The diagnosis should not be forced to fit the scope.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Diagnosis before prescription.
Evidence Boundary
This White Paper advances an SAI interpretive proposition concerning engagement scoping, problem formulation, and governing-constraint diagnosis in advisory and consulting relationships.
External research cited here supports the intellectual context surrounding strategic problem formulation, problem framing, reframing, problem-solving attention, cognitive bias, and solution jumping.
It does not independently validate the Business Constraint Discipline™, the Seven Classes of Business Constraint™, the governing-constraint proposition, the Business Constraint Diagnostic™, or SAI credentials.
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 proposition that one governing constraint exists at a time is an SAI proposition and should be distinguished from findings in the external problem-formulation literature.
The Business Constraint Diagnostic™ produces a probable governing-constraint finding based on information supplied. It does not independently establish causation, guarantee engagement success, replace professional judgment, or substitute for qualified specialist analysis where that expertise is required.
References
[1] Park, C., Baer, M., & Nickerson, J. (2025). Looking at the Trees to See the Forest: Construal Level Shift in Strategic Problem Framing and Formulation. Organization Science. Citation count in retrieved record: 10. DOI: 10.1287/orsc.2024.19134.
[2] Baer, M., Dirks, K., & Nickerson, J. (2013). Microfoundations of Strategic Problem Formulation. Strategic Management Journal, 34, 197–214. Citation count in retrieved record: 285. DOI: 10.1002/smj.2004.
[3] Nutt, P. C. (1992). Formulation Tactics and the Success of Organizational Decision Making. Decision Sciences, 23, 519–540. Citation count in retrieved record: 56. DOI: 10.1111/j.1540-5915.1992.tb00404.x.
[4] Laureiro-Martinez, D., Arrieta, J., & Brusoni, S. (2023). Microfoundations of Problem Solving: Attentional Engagement Predicts Problem-Solving Strategies. Organization Science. Citation count in retrieved record: 22. DOI: 10.1287/orsc.2019.13213.
[5] Heiman, B. A., & Hurmelinna-Laukkanen, P. (2023). We’re Only Human — An Exploratory Study of Biases and Strategic Problem Formulation Performance. Innovation, 26, 433–459. Citation count in retrieved record: 3. DOI: 10.1080/14479338.2023.2236072.
Related SAI Resources
Business Constraint Diagnostic™
CAS — Certified Axiom Strategist
FDC — Foundational Diagnostic Credential
What Is a Business Constraint?
The Seven Classes of Business Constraint™
How the Seven Classes of Business Constraint™ Work Together
Why Diagnostic Credentials Matter
For Advisors
For Consultants
For Business Coaches
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.