Before You Hire a Consultant — Identify the Constraint
SAI WHITE PAPER SERIES
Before You Hire a Consultant — Identify the Constraint
Why the quality of the intervention may matter less than whether leadership has chosen the right problem to address
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
PUBLICATION IDENTITY
Original Publication: June 2026 · Current Revision: September 2026 · Version: 1.0 · Classification: Constraint Identification & Diagnostic Reasoning · Publication Identifier: SAI-CIDR-12
Subject: Diagnostic Reasoning · Intervention Scoping · Business Constraints
Primary Audience: Business Owners · Executives · Advisors · Consultants
SAI Discipline Stage: IDENTIFY → PRIORITIZE
Evidence Orientation: Practitioner Observation · External Scholarship · Conceptual Diagnostic Illustration · SAI Proposition
EXECUTIVE ABSTRACT
A company can hire an excellent consultant and still be disappointed.
It can install capable software and remain operationally frustrated.
It can recruit a highly qualified executive and discover that performance barely changes.
It can launch a culture initiative, retain a new marketing agency, or adopt a respected operating framework—and months later confront many of the same symptoms that prompted the intervention.
The immediate conclusion is often that the consultant, system, executive, agency, or methodology failed.
Sometimes that conclusion is justified.
Sometimes a more fundamental question was missed:
Was the intervention aimed at the condition that actually deserved priority?
Leadership teams rarely operate with perfect information. They see declining sales, missed deadlines, weak accountability, customer losses, cash pressure, employee turnover, owner overload, inconsistent execution, or operational disorder.
Those symptoms are real.
But a visible symptom does not automatically reveal the condition governing performance.
That distinction matters before a major commitment is scoped.
The proposition examined in this paper is not that unsuccessful interventions are generally caused by misdiagnosis. Consultant quality, implementation discipline, organizational resistance, timing, market change, resource limitations, and other factors can influence results.
The narrower argument is this:
Before leadership commits substantial money, time, authority, or organizational attention to an intervention, it should test whether the problem being addressed is actually the condition that deserves priority.
The larger cost of getting that decision wrong may not be the consulting fee.
It may be months spent improving something that was real—but secondary.
THE CENTRAL PROPOSITION
Before a major consulting engagement, system implementation, executive hire, or organizational initiative is scoped, leadership should test whether the problem being addressed is the condition that actually deserves priority. A well-designed intervention can still disappoint when it is aimed at a visible symptom, an incomplete explanation, or a secondary condition rather than the governing constraint.
WHY THIS PAPER MATTERS
Organizations do not usually invest in major interventions casually.
They invest because something hurts.
Sales have stalled.
Margins are deteriorating.
The operation cannot keep up.
Employees are frustrated.
The owner has become the bottleneck.
Execution is inconsistent.
Growth has stopped.
Customers are leaving.
Leadership naturally asks:
Who can help us fix this?
That may be the second question.
The first may need to be:
What, exactly, should be fixed first?
If the problem is defined as “we need a better ERP,” the search begins for ERP expertise.
If the problem is defined as “sales performance is weak,” the search begins for a sales consultant.
If the company needs “stronger execution,” leadership may recruit a COO.
If turnover and conflict dominate management discussions, a culture initiative may become the priority.
If leads are weak, a marketing agency enters the picture.
If the company feels chaotic, leadership may adopt an operating framework.
Each response can be reasonable.
Each may address a genuine condition.
The diagnostic question is different:
Is that condition the one currently governing performance?
THE ENGAGEMENT BEGINS BEFORE THE CONSULTANT ARRIVES
Most consulting engagements appear to begin when a consultant is retained.
In an important sense, they begin earlier.
They begin when someone defines the problem.
“We have a sales problem.”
“Our systems are terrible.”
“We need accountability.”
“We have to fix the culture.”
“Marketing isn't working.”
“We need an operator.”
“We need a management system.”
Once that interpretation becomes accepted, a sequence follows.
A solution category is selected.
Vendors or candidates are considered.
A budget is established.
A scope is written.
Success measures are chosen.
Expectations form.
By the time the external expert enters the business, one of the most consequential decisions may already have been made:
Leadership has decided what kind of problem it believes it has.
A capable consultant may challenge that assumption.
But commercial engagements often begin with a requested area of expertise. A company seeking an ERP firm receives ERP proposals. A company interviewing sales consultants receives sales-improvement proposals. A company recruiting a COO evaluates operating executives.
That is not misconduct.
It is specialization.
The risk arises when the organization moves from symptom to solution category before adequately examining competing explanations.
A REAL PROBLEM IS NOT NECESSARILY THE PRIORITY PROBLEM
This is one of the harder distinctions in management.
An organization can have a genuine problem that should not yet receive priority.
Its marketing may need improvement.
Its reporting systems may be inadequate.
Its managers may avoid accountability.
Its processes may be inefficient.
Its leadership structure may need clarification.
Its culture may contain destructive behaviors.
None of those observations establishes which condition deserves priority.
The existence of a problem answers:
Is something wrong here?
Diagnosis must answer a more demanding question:
What condition is most limiting performance now?
SAI refers to that priority condition as the governing constraint.
Within the SAI Business Constraint Discipline™, potential governing constraints are examined through seven classes:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
These classes do not convert symptoms into predetermined diagnoses.
They organize the inquiry.
A decline in sales, for example, may initially suggest a Market condition.
But similar revenue symptoms could plausibly result from poor fulfillment, weak positioning, customer-confidence problems, resource limitations, leadership decisions, or organizational execution failures.
The symptom begins the inquiry.
It does not complete it.
WHY CAPABLE INTERVENTIONS CAN STILL DISAPPOINT
A useful intervention must be competently designed and executed.
It must also be directed toward a condition important enough to justify priority.
Leadership often concentrates on the first question.
Who is the best consultant?
Which software has the best functionality?
Which executive has the strongest résumé?
Which agency has the strongest record?
Which framework is most respected?
Those questions matter.
But expertise cannot compensate for a scope aimed at the wrong level of the problem.
A cardiologist may be exceptional without being the physician a particular patient needs.
A structural engineer may be outstanding without being the expert required to solve an electrical failure.
Business intervention is no different.
Quality of prescription does not eliminate the need for quality of diagnosis.
This proposition is consistent with a broader body of scholarship on managerial problem framing and decision-making.
Herbert Simon's work emphasized that decision-makers operate under bounded conditions and must define problems before they can solve them. Donald Schön showed that professional practice often turns on how an ambiguous situation is framed before technical problem solving begins. Dorst's work on framing similarly describes problem formulation as central to the creation of useful solutions.
Systems research adds another caution. Repenning and Sterman examined how organizations can fall into “capability traps,” where plausible corrective actions and attribution errors reinforce recurring underperformance rather than resolve it.
These sources do not validate the SAI Business Constraint Discipline.
They support the broader intellectual premise underlying this paper:
How a problem is framed materially influences what decision-makers choose to do about it.
SIX FAMILIAR INVESTMENTS — AND THE QUESTION THAT SHOULD COME FIRST
The following are conceptual diagnostic illustrations.
They are not documented SAI cases and do not establish that any particular condition is a governing constraint.
Their purpose is narrower:
To show why a familiar symptom can support more than one plausible explanation—and why leadership should test those explanations before making a major commitment.
1. THE ERP IMPLEMENTATION
The company has grown.
Orders are handled through workarounds.
Inventory records are unreliable.
Employees maintain spreadsheets outside the primary system.
Management lacks timely information.
Everyone agrees:
“We have outgrown our system.”
That may be correct.
A modern ERP may materially improve visibility, transaction control, scheduling, inventory management, and reporting.
But inadequate software does not automatically mean software deserves priority.
Leadership should ask:
What can the current system not do?
Which failures originate in software limitations?
Which originate in inconsistent procedures?
Are employees bypassing the system because it is inadequate—or because process discipline is weak?
Is the company suffering from poor information, or are managers failing to act on information already available?
Would the same operating behavior simply migrate into a more expensive platform?
Evidence might include workflow mapping, transaction-error patterns, inventory discrepancies, system utilization, process adherence, and decision delays.
That evidence may strongly support a technology intervention.
Or it may indicate that another condition deserves attention first.
The diagnostic question is not:
“Do we need a better system?”
It is:
“What performance limitation are we expecting the system to remove—and does the evidence indicate that this limitation deserves priority?”
2. THE SALES CONSULTANT
Revenue is below plan.
The pipeline is weak.
Close rates are disappointing.
The sales team lacks consistency.
Leadership concludes:
“We have a sales problem.”
Perhaps.
Sales capability may be inadequate. Representatives may need stronger qualification, prospecting, coaching, messaging, or pipeline discipline.
But declining sales are an outcome, not a diagnosis.
Leadership should also ask:
Has the target market changed?
Is the offer losing relevance?
Is pricing misaligned with perceived value?
Can operations reliably deliver what sales is being asked to sell?
Has customer confidence deteriorated?
Is positioning sufficiently differentiated?
Are salespeople failing at execution—or carrying an offer that has become harder to sell?
A sales consultant can improve sales behavior.
That does not establish that sales behavior is the highest-priority limitation.
The appropriate conclusion is not:
“Sales consulting doesn't work.”
It is:
“Do not infer the cause of weak sales from the sales number alone.”
3. THE COO HIRE
The founder is overwhelmed.
Decisions accumulate.
Managers escalate routine issues.
Projects stall.
The organization depends excessively on one person.
Leadership reaches what appears to be an obvious conclusion:
“We need a COO.”
Possibly.
A strong operating executive can transform an organization.
But the title does not diagnose the structural problem.
Leadership should determine what authority, capability, and operating responsibility the organization actually lacks.
Is the founder unwilling to delegate?
Are decision rights undefined?
Do managers lack authority?
Are managers given authority but not held accountable?
Does the organization lack operating discipline?
Has growth exceeded the capacity of the current structure?
Or is the actual need narrower than a COO role?
Without that examination, a company can recruit an impressive executive into an ambiguous structure.
The new COO may inherit responsibility without authority.
Or authority without clear accountability.
Or a mandate to “fix operations” without agreement about what is limiting the business.
If the hire disappoints, the temptation will be to blame the person.
Sometimes that judgment will be correct.
But the pre-hire question remains:
Was the role designed around a diagnosed organizational need—or around the visible exhaustion of the founder?
Those are not always the same thing.
4. THE CULTURE INITIATIVE
Turnover is increasing.
Departments blame each other.
Employees complain that leaders do not communicate.
Morale has weakened.
Meetings feel adversarial.
Management declares:
“We need to fix the culture.”
Culture matters.
Trust matters.
Leadership behavior matters.
Communication matters.
But “culture” is a broad explanation.
Similar behavioral symptoms can accompany poorly defined authority, conflicting incentives, impossible workloads, weak managers, unclear strategy, repeated operational failures, or loss of confidence in leadership.
A culture initiative may be valuable.
The diagnostic question is whether the observed behaviors are themselves the condition deserving priority or partly a response to something else.
Consider a team repeatedly missing customer commitments because schedules are chronically unrealistic.
Frustration rises.
Departments blame one another.
Employees stop trusting management forecasts.
Meetings become defensive.
Those behaviors are cultural realities.
But an intervention centered only on communication and values may not address the mechanism generating the conflict.
The opposite assumption would be equally weak: not every culture problem is merely a process problem.
The evidence has to decide.
Leadership should ask:
“What is producing the behavior we are calling the culture problem?”
“Culture” may describe what people are experiencing without fully explaining why.
5. THE MARKETING AGENCY
Lead volume has declined.
Website conversion is weak.
Competitors appear more visible.
The brand feels dated.
Management decides:
“We need better marketing.”
That may be the right investment.
A skilled agency can improve positioning execution, content, demand generation, brand presentation, advertising, and conversion pathways.
But marketing outputs alone do not diagnose the limitation.
Leadership should ask:
Is there sufficient demand in the target market?
Is the offer relevant?
Is the target customer defined correctly?
Is the company's differentiation meaningful?
Are leads being converted after marketing generates them?
Are customers failing to buy because they do not know the company—or because they understand the offer and do not value it enough?
Are credibility concerns suppressing response?
Can the organization fulfill additional demand?
More promotion amplifies what is already being offered.
Sometimes that is exactly what the business needs.
Sometimes amplification exposes another weakness faster.
The diagnostic question becomes:
“What evidence indicates that insufficient demand generation is the condition that should receive priority?”
6. THE OPERATING FRAMEWORK
The company is chaotic.
Priorities change.
Meetings drift.
Projects stall.
Accountability is inconsistent.
Leadership adopts a structured business operating framework.
That response may be entirely sensible.
A disciplined framework can improve meeting cadence, goal setting, role clarity, metrics, issue identification, and execution routines.
But adoption of a framework is still an intervention.
Leadership should determine what it expects the framework to change.
Does the organization lack management discipline?
Are priorities unclear?
Are roles poorly defined?
Does leadership avoid difficult decisions?
Does strategy lack coherence?
Are resource limitations making agreed priorities impossible to execute?
Is the company attempting to impose stronger execution on a business model that is no longer working?
A framework may surface some of these issues.
It may help resolve some of them.
It may also become another layer of activity if management assumes that process discipline alone explains the performance limitation.
That does not make the framework ineffective.
It means leadership should distinguish between:
a useful management system
and
a diagnosis of the governing constraint.
They are not automatically the same thing.
THE COMMON PATTERN
The six situations differ.
The pattern is familiar.
A visible condition creates urgency.
Urgency encourages interpretation.
Interpretation points toward a solution category.
The solution category attracts a specialist.
The engagement is then scoped around the original interpretation.
SYMPTOM → ASSUMPTION → SOLUTION CATEGORY → PROVIDER → SCOPE
The missing step is the diagnostic challenge:
What competing explanations could produce what we are observing?
That question does not require management paralysis.
It requires enough disciplined inquiry to avoid confusing immediacy with priority.
THE CONSULTANT'S DILEMMA
The diagnostic responsibility does not belong only to the client.
Experienced consultants often discover that the issue described in the first meeting is not the issue they ultimately believe matters most.
A client may request a sales strategy engagement and reveal an operating-capacity problem.
A client may request process redesign and reveal unclear decision authority.
A client may request organizational restructuring and reveal strategic ambiguity.
Good consultants challenge the brief.
They test assumptions.
They examine evidence.
They resist promising outcomes the facts cannot support.
Yet consultants also face a structural tension.
The prospect arrives asking for a particular service.
The consultant has expertise in that service.
The proposal process rewards clarity.
The client wants action.
Both sides can therefore move too quickly toward solution design.
This makes diagnostic discipline valuable to both.
For the client, it improves the buying decision.
For the consultant, it improves engagement fit.
Sometimes the most professionally responsible conclusion may be:
“You have a real problem, but I am not yet convinced that the service you asked me to provide should be the first intervention.”
That sentence may reduce the probability of an immediate sale.
It may increase the probability of doing the right work.
DIAGNOSIS DOES NOT REQUIRE CERTAINTY
One objection deserves attention.
Business leaders rarely have enough evidence to establish causation with scientific certainty before acting.
That is true.
Organizations operate under uncertainty.
Markets move.
Competitors respond.
People change behavior.
Data are incomplete.
Management cannot wait until every causal relationship has been proven.
But the alternative to premature prescription is not perfect certainty.
It is better diagnostic reasoning.
Leadership can compare explanations.
Identify contradictory evidence.
Ask what would have to be true for a hypothesis to hold.
Separate observation from interpretation.
Identify what remains unknown.
Determine which condition appears sufficiently important to receive priority.
A responsible finding may therefore be probabilistic:
The available evidence indicates that this condition is the most plausible priority explanation at this time.
That is materially different from:
This has been proven to be the cause.
Diagnostic rigor does not eliminate uncertainty.
It makes uncertainty explicit.
BEFORE THE SCOPE IS WRITTEN: SIX QUESTIONS
Before committing to a major intervention, leadership can improve the decision by asking six questions.
1. What are we actually observing?
Start with evidence rather than explanation.
Revenue declined 14 percent.
Orders are late.
Manager turnover increased.
Customer complaints doubled.
The owner approves nearly every capital purchase.
Those are observations.
“Sales is weak,” “our culture is broken,” and “we need a COO” already contain interpretation.
Keep the categories separate.
2. What explanations are we assuming?
State the hypothesis clearly.
“We believe revenue declined because the sales team lacks capability.”
“We believe projects are late because our software is inadequate.”
Once an assumption is explicit, it can be examined.
3. What competing explanations could produce the same symptom?
What else could plausibly create what we are seeing?
The objective is not to produce an endless list.
It is to prevent the first plausible explanation from becoming the unquestioned diagnosis.
4. What evidence would distinguish among those explanations?
Different explanations should leave different evidence.
What would we expect to observe if the issue were primarily Market?
Operational?
Financial?
Organizational?
Strategic?
Leadership?
Credibility?
What evidence contradicts the favored explanation?
A diagnosis becomes stronger when it survives attempts to disconfirm it.
5. Why should this condition receive priority now?
Even if the problem is real, why should it come first?
What performance limitation does it create?
What other improvements are being restricted by it?
What happens if leadership improves this area while leaving a higher-priority condition unchanged?
6. What would tell us afterward that the intervention worked?
This question should be answered before implementation begins.
What observable change is expected?
Over what period?
Which measures matter?
What evidence would require the original explanation to be reconsidered?
This leads directly to the final stage of the SAI discipline:
CONFIRM.
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The SAI discipline is intentionally sequential:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The sequence matters.
IDENTIFY
What condition appears to be limiting performance?
PRIORITIZE
Does the evidence indicate that this condition deserves attention before competing problems?
RESOLVE
What intervention is appropriate for the identified condition?
CONFIRM
Did the expected improvement occur, and what does the new evidence indicate?
Organizations frequently begin at the third step.
They implement.
They hire.
They install.
They train.
They restructure.
They launch.
Action feels productive.
But resolution without adequate identification and prioritization increases the risk of improving something that was not governing performance.
Confirmation matters because even a reasonable diagnosis remains subject to evidence.
If the expected improvement does not occur, the appropriate conclusion is not automatically:
“The diagnosis was wrong.”
Implementation may have failed.
Conditions may have changed.
The intervention may have been insufficient.
A secondary condition may have become more important.
The governing constraint may have migrated.
Or the original interpretation may indeed require reconsideration.
Recurrence means reopen the diagnosis.
It does not, by itself, prove what was wrong before.
WHAT THIS CHANGES ABOUT CONSULTING
This is not an argument against consultants.
It is an argument for using them more precisely.
Specialists create value because they possess capabilities organizations do not maintain internally.
But specialization is most productive when directed at the right problem.
Instead of:
“Can you fix our sales team?”
a stronger engagement might begin:
“We have evidence that our sales conversion process appears to be materially limiting growth. Here is what we have ruled out, here is what remains uncertain, and here is the change we need to test.”
Instead of:
“Install a new ERP.”
the question becomes:
“These specific information and transaction-control failures appear to be restricting execution. Which should technology solve, which require process redesign, and how should we distinguish the two?”
Better diagnosis does not reduce the consultant's role.
It makes the role more precise.
WHAT THIS CHANGES ABOUT LEADERSHIP
For executives, the implication is more demanding.
The risk is not simply hiring the wrong consultant.
It is commissioning the wrong work.
Leaders determine what receives organizational attention.
They approve budgets.
Define mandates.
Recruit executives.
Authorize implementation.
Decide which problem the organization will attempt to solve.
That makes problem selection a leadership responsibility.
A sophisticated procurement process cannot compensate for a poorly framed problem.
An impeccable implementation plan cannot establish that the selected initiative deserved priority.
A highly credentialed advisor cannot create evidence that was never examined.
The executive responsibility therefore begins before vendor selection.
Leadership must become competent at distinguishing the problem that is visible from the condition that deserves priority.
THE ARGUMENT HAS LIMITS
The governing-constraint perspective should not become another oversimplification.
Not every intervention requires extensive diagnosis.
Some decisions are routine.
Some deficiencies are sufficiently obvious to correct immediately.
A failed server should be restored.
A regulatory violation should be addressed.
A dangerous safety condition should not wait for strategic prioritization.
A broken invoicing process may simply need repair.
Organizations also invest for reasons other than removing a current governing constraint. They may build future capability, reduce risk, comply with regulation, improve employee experience, or prepare for anticipated growth.
Those decisions can be rational.
The argument in this paper is most relevant when an organization is making a substantial performance-improvement investment and expects that investment to remove an important limitation.
In that context, the larger the commitment, the stronger the case for testing whether the proposed target deserves priority.
IMPLICATIONS / APPLICATIONS
For BUSINESS OWNERS:
Do not allow the urgency of a visible problem to determine the solution category before competing explanations have been considered.
For EXECUTIVES:
Require major improvement proposals to state both the problem being addressed and the evidence supporting its priority.
For BOARDS:
When management proposes a major transformation, ask what alternative explanations were evaluated before the intervention was selected.
For CONSULTANTS and ADVISORS:
Treat the client's requested service as a starting hypothesis, not an unquestionable diagnosis.
For EXECUTIVE RECRUITERS:
Clarify the structural condition the new executive is expected to address before defining the role around a title.
For BUSINESS EDUCATORS:
Teach students to separate problem recognition, problem framing, diagnosis, intervention selection, and outcome confirmation rather than compressing them into a single “problem-solving” step.
Across all six applications, the principle is the same:
Diagnosis before prescription.
LIMITATIONS AND QUESTIONS FOR FURTHER EXAMINATION
This paper advances a conceptual and practitioner-based proposition.
It does not present a controlled empirical test demonstrating that organizations using the SAI Business Constraint Discipline achieve better consulting outcomes than organizations that do not.
It does not establish that a single method can identify causation with certainty in complex organizations.
It does not establish that disappointing consulting outcomes are primarily caused by poor problem selection.
Other explanations include consultant capability, weak implementation, resistance to change, insufficient resources, changing market conditions, flawed strategy, unrealistic expectations, poor measurement, and execution failure.
Further examination could address several questions:
Do organizations that conduct structured pre-intervention diagnosis define more appropriate consulting scopes?
Does explicit consideration of competing explanations reduce premature solution selection?
Does separating observation from interpretation improve decision quality?
How reliably can trained practitioners distinguish a governing condition from important secondary conditions?
Does structured confirmation after an intervention improve subsequent diagnosis?
Under what conditions does a governing-constraint framework add value beyond conventional strategic, operational, or organizational analysis?
These questions should remain open.
A discipline becomes stronger by stating what has not yet been established—not by presenting proposition as proof.
CONCLUSION
The consultant may be excellent.
The software may work.
The executive may be capable.
The agency may be creative.
The culture program may be well designed.
The operating framework may be sound.
And the organization may still be disappointed.
That outcome alone does not tell us why.
But one possibility deserves more attention than it often receives:
The organization may have invested in a good solution to a problem that did not deserve first priority.
That possibility changes the sequence.
Before asking who should fix the problem, ask what the evidence says the problem is.
Before writing the scope, test the assumptions behind the scope.
Before choosing the intervention, compare competing explanations.
Before declaring success, confirm whether the expected change occurred.
The objective is not certainty.
It is better judgment before commitment.
The most expensive consulting mistake may not be hiring an incapable consultant. It may be hiring a capable one to solve the wrong problem first.
EVIDENCE BOUNDARY
This White Paper combines several forms of material that should not be treated as equivalent.
Practitioner / Operating Observation
Observations regarding how owners, executives, advisors, consultants, and organizations frame performance problems before intervention reflect practitioner experience and operating interpretation.
Internal SAI Framework
The Seven Classes of Business Constraint™, the concept of a governing constraint, and the sequence IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM are elements of the Schneider Axiom Institute Business Constraint Discipline™.
Independent External Scholarship
External scholarship cited below supports broader concepts including managerial decision-making under bounded conditions, problem framing, professional reflection, systems behavior, organizational learning, and attribution in improvement efforts.
Conceptual Diagnostic Illustrations
The ERP, sales consulting, COO, culture, marketing, and operating-framework scenarios are conceptual illustrations unless separately documented elsewhere. They are not evidence that a particular organization possessed a particular governing constraint.
SAI Proposition / Interpretation
The proposition that organizations should test whether a proposed intervention addresses the condition deserving priority before making a major performance-improvement commitment is an SAI proposition informed by operating experience, diagnostic reasoning, and related external scholarship.
Independent Validation
This paper does not claim that the SAI Business Constraint Discipline™, Seven Classes of Business Constraint™, or Business Constraint Diagnostic™ has been independently validated as establishing causal truth or guaranteeing improved organizational outcomes.
REFERENCES
Dorst, K. (2011). The core of “design thinking” and its application. Design Studies, 32(6), 521–532.
Repenning, N. P., & Sterman, J. D. (2002). Capability traps and self-confirming attribution errors in the dynamics of process improvement. Administrative Science Quarterly, 47(2), 265–295.
Rumelt, R. P. (2011). Good Strategy/Bad Strategy: The Difference and Why It Matters. Crown Business.
Schön, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.
Simon, H. A. (1997). Administrative Behavior: A Study of Decision-Making Processes in Administrative Organizations (4th ed.). Free Press.
Sterman, J. D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. Irwin/McGraw-Hill.
RELATED SAI RESOURCES
Readers examining diagnostic reasoning, governing constraints, and intervention sequencing may also find the following Schneider Axiom Institute resources relevant:
The SAI Business Constraint Discipline™
The broader framework for identifying, prioritizing, resolving, and confirming the condition limiting organizational performance.
The Seven Classes of Business Constraint™
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
Business Constraint Diagnostic™
An SAI diagnostic resource designed to support identification of a probable governing constraint class and the structural condition within that class that appears to be limiting performance.
SAI Credential Programs
Programs designed to develop diagnostic capability for business owners, leaders, advisors, consultants, and executives.
These resources are supplementary. The argument presented in this White Paper stands independently of any purchase or enrollment.
LAWRENCE M. SCHNEIDER
Founder & CEO
Schneider Axiom Institute™
Schneider Axiom Institute develops and teaches the Business Constraint Discipline™—a structured approach to identifying what is limiting organizational performance, determining what deserves priority, resolving the priority condition, and confirming whether improvement occurred.
Diagnosis before prescription.
© Schneider Axiom Institute. All rights reserved.