The Observation Post and the Trenches. What Each Can See—and What Each Can Miss.
Why Business Diagnosis Benefits From Both Operating Experience and External Analysis
Lawrence M. Schneider
Founder & CEO
Schneider Axiom Institute
Institute for Business Constraints™
Original Publication: June 2026 · Current Revision: September 2026 · Version: 2.0 · Publication Identifier: SAI-BCD-06
EXECUTIVE ABSTRACT
Business problems look different depending on where they are observed.
An owner inside the business experiences the consequences directly. Cash tightens. Employees fail to execute. Customers leave. Inventory accumulates. Margins compress. Decisions slow. The operator sees details that may never appear in a report.
An advisor, researcher, accountant, consultant, board member, or educator occupies a different position. Distance can obscure context, but it can also reveal patterns the operator is too close to see.
This paper uses the metaphor of the observation post and the trenches to examine those two perspectives. The argument is not that one is inherently superior.
Operating experience can provide context, tacit knowledge, consequence, repetition, and familiarity with how decisions actually unfold. External analysis can provide comparative perspective, methodological discipline, specialized expertise, challenge to assumptions, and distance from the organizational pressures affecting internal judgment.
Each contributes.
Each can also fail.
An operator may mistake familiarity for diagnosis. An outsider may mistake analytical clarity for operating reality.
The Schneider Axiom Institute proposes that stronger business diagnosis requires neither unquestioning deference to experience nor unquestioning deference to frameworks. It requires disciplined use of evidence across perspectives.
That becomes especially important when the task is not merely to identify a problem, but to determine which condition is governing performance, which problem deserves priority, what should be addressed first, and whether the corrective action actually worked.
SAI organizes that inquiry through the Seven Classes of Business Constraint™ and the sequence:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
This paper does not establish that operators diagnose better than outsiders, nor does it establish that external professionals systematically miss governing constraints.
It advances a narrower proposition:
Diagnostic quality may improve when operating knowledge and disciplined external analysis are treated as complementary sources of evidence rather than competing authorities.
THE CENTRAL PROPOSITION
Operating experience and external analysis reveal different forms of evidence. Neither perspective is sufficient merely because of where it stands. Stronger business diagnosis requires a disciplined method for integrating what people inside the business know with what structured analysis can reveal from outside it.
The person inside the business may know things no external report contains. The person outside the business may see relationships internal participants have normalized.
The operator possesses proximity.
The external analyst possesses distance.
Both can create insight.
Both can create blindness.
The important question is therefore not:
Who has the better vantage point?
It is:
What evidence does each vantage point reveal—and what can each cause us to miss?
THE OBSERVATION POST AND THE TRENCHES
The original version of this paper drew a sharp distinction between people who operate businesses and people who analyze them from outside. Accountants, advisors, educators, and critics were described as occupying an “observation post,” while the business owner occupied the “trenches.”
The metaphor remains useful.
The conclusion originally drawn from it was too absolute. The observation post is not inherently detached from reality, and the trenches are not inherently free from error.
Both positions create information.
Both positions create limitations.
A person standing above an operating system may see the whole process more clearly. A person inside it may understand friction invisible from above.
The strongest diagnosis should not force a choice between those perspectives.
It should ask what each contributes.
WHAT THE TRENCHES CAN SEE
Operating experience provides forms of knowledge that are difficult to reproduce through observation alone.
An owner knows what happened before the numbers changed. A plant manager may know why production slowed even when the dashboard records only missed output. A sales leader may know that customers are rejecting an offer for reasons no CRM field captures.
A founder may understand how one executive's behavior is slowing decisions even though the organizational chart appears rational.
Operators experience sequence, context, informal workarounds, unwritten relationships, organizational history, decision consequences, employee behavior, customer reactions, and the difference between how a process is designed and how it actually operates.
That knowledge can be diagnostically valuable.
It is one reason practitioner experience deserves serious treatment in business analysis.
But proximity alone does not make a diagnosis correct.
WHAT THE TRENCHES CAN MISS
People inside a business also become accustomed to the business. That familiarity can create blind spots.
A process may appear normal because it has always been done that way. A founder may defend a structure because they created it. A management team may interpret recurring failure through the same assumptions that helped produce it.
Political incentives may discourage uncomfortable conclusions. Success can reinforce beliefs that no longer fit current conditions, while urgency can push management toward the loudest symptom.
People who live with a problem every day may also become exceptionally skilled at managing around it without recognizing the structural condition producing it.
Operating experience is therefore not self-validating.
Living inside a business does not guarantee that the business has been diagnosed correctly.
WHAT THE OBSERVATION POST CAN SEE
External analysis creates different advantages.
Distance makes comparison possible. A specialist may recognize a pattern because they have seen similar conditions across many organizations. An accountant may identify a financial trend managers have normalized.
A consultant may recognize that what appears to be a personnel problem is actually a structural authority problem. A board member may see strategic drift management has rationalized quarter by quarter. A researcher may identify relationships that individual operating experience cannot establish reliably.
A disciplined outside observer can bring comparative benchmarks, specialized methods, structured questioning, independent challenge, cross-industry perspective, formal analysis, and distance from internal assumptions.
Those advantages are real.
External analysis should not be dismissed merely because the analyst is not carrying the operating responsibility.
WHAT THE OBSERVATION POST CAN MISS
Distance also has costs.
Reports can contain accurate numbers and incomplete explanations. Dashboards can measure outcomes without revealing mechanisms. Interviews can capture what people say rather than what actually happens.
A consultant may understand a functional domain deeply but examine the organization primarily through that specialty. A financial professional may see the financial expression of a problem without knowing whether its governing cause is financial.
An operations specialist may identify inefficiency without knowing whether fixing it deserves priority. A strategist may identify positioning weaknesses even though another condition is more consequential.
The issue is not professional competence.
It is diagnostic scope.
Specialization creates depth.
It can also create a lens.
The analyst must therefore distinguish:
What is true within my domain?
from:
What deserves priority across the business?
Those are not the same question.
THE DANGER OF TURNING VANTAGE POINT INTO AUTHORITY
Both operators and outside experts can make the same mistake: they can confuse vantage point with authority.
The operator says:
I know this business because I have lived it for twenty years.
The advisor says:
I know this problem because I have solved it in fifty companies.
Both statements may contain useful information.
Neither establishes the diagnosis.
Experience is evidence. Expertise is evidence. Financial data are evidence. Customer behavior is evidence. Operational metrics are evidence. Employee observations are evidence. Market conditions are evidence.
But evidence must still be interpreted.
A diagnostic discipline should therefore resist two shortcuts:
The person closest to the problem must be right.
and
The expert with the framework must be right.
Neither follows automatically.
DESCRIPTION IS NOT DIAGNOSIS
A business can be described accurately without being diagnosed correctly.
Suppose gross margin is falling.
The accountant may report the decline perfectly. That is valuable.
But the declining margin does not, by itself, tell management why the decline is occurring. Pricing may be wrong. Product mix may have changed. Input costs may have increased. Discounting may have expanded.
Operational waste may be rising. Competitive pressure may have changed. Customers may be migrating toward lower-margin products.
The financial statement records an important condition.
It does not necessarily identify the governing cause.
The same distinction applies elsewhere. Employee turnover is evidence. Missed deadlines are evidence. Weak sales are evidence. Customer complaints are evidence. Owner overload is evidence.
None automatically identifies the governing constraint.
Diagnosis begins when competing explanations are considered.
THE PROBLEM OF PROFESSIONAL LENSES
Professional specialization is necessary.
No executive can know every discipline deeply. Organizations therefore rely on accountants, attorneys, bankers, consultants, strategists, coaches, technologists, researchers, educators, and other specialists.
The value of specialization is depth.
The limitation is that specialists naturally examine evidence through the disciplines they know best.
A finance professional may legitimately identify financial risk. An operations professional may legitimately identify process failure. A marketing specialist may legitimately identify demand problems.
An organizational advisor may legitimately identify accountability problems. A strategist may legitimately identify competitive misalignment.
Several specialists may all be correct.
The unresolved question is:
Which condition deserves priority?
That is where business-wide diagnosis becomes necessary.
THE OPERATOR HAS A LENS TOO
The same caution applies to the owner.
Operators are not neutral observers. Founders may interpret every constraint through their own history.
A sales-oriented CEO may assume the company needs more revenue. An operations-oriented CEO may assume execution is the problem. A financially conservative owner may see cash preservation as the answer.
A founder who built the company through personal relationships may underestimate the importance of institutional credibility.
The operator therefore also brings a framework.
It may not be written in a textbook.
But it exists.
Experience creates mental models. Those models can be exceptionally valuable, and they can also become outdated.
The purpose of diagnosis is not to remove judgment.
It is to discipline it.
WHEN INSIDE KNOWLEDGE MATTERS MOST
Some diagnostic questions cannot be answered adequately through external data alone.
Why did the customer really leave?
Why does the management team avoid one decision?
Why does the formal authority structure differ from the actual authority structure?
Why does one supposedly simple process fail every month?
Why does an initiative lose momentum after the executive meeting?
Why are employees working around a system management believes is functioning?
These questions often require access to people who live inside the operating reality.
Internal evidence is not weak merely because it is internal. It becomes stronger when multiple observations converge, when behavior corroborates testimony, when records support recollection, and when competing explanations are considered.
The task is to improve the quality of the evidence—not dismiss its source.
WHEN EXTERNAL PERSPECTIVE MATTERS MOST
Other questions benefit greatly from distance.
Is management underestimating a competitive change?
Are current margins outside relevant norms?
Is the organization treating a recurring structural problem as a temporary exception?
Are leaders defending assumptions that evidence no longer supports?
Is the company confusing historical success with current market fit?
Could another explanation account for the same symptoms?
External perspective is particularly valuable when the organization has become unable to question its own premises.
A disciplined outsider can ask the question people inside the business have stopped asking.
THE GOVERNING-CONSTRAINT QUESTION
SAI proposes that these perspectives become especially important when the objective is to identify the governing constraint.
A business can contain many valid problems simultaneously. Those problems can arise across different classes:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
The existence of a Financial problem does not establish that Financial is governing. The existence of an Operational problem does not establish that Operations deserves priority.
A Leadership problem may be serious without being governing. A Market weakness may be visible while the more consequential condition lies elsewhere.
The diagnostic task is therefore comparative.
Which explanation is best supported?
Which condition has the greatest current structural consequence?
Which one should receive priority?
What evidence would cause us to reject that conclusion?
Those questions require both operating knowledge and analytical discipline.
IDENTIFY
Identification asks:
What condition does the evidence indicate?
The operator contributes context. The specialist contributes domain knowledge. External evidence contributes comparison. Internal evidence contributes operating detail.
The diagnostic task is to distinguish symptoms from structural conditions and consider plausible alternatives.
Identification should not begin with:
Which framework do we want to apply?
It should begin with:
What does the evidence indicate is happening?
PRIORITIZE
Prioritization asks which legitimate condition deserves attention first.
This is where narrow professional lenses become especially problematic. Every specialist may have something useful to improve, but the organization cannot assume that the most visible problem, the most measurable problem, or the problem supported by the strongest internal advocate deserves to go first.
SAI proposes that prioritization should follow the evidence across competing conditions.
The governing constraint is the condition judged most consequential at that point in time.
That judgment should remain challengeable.
RESOLVE
Resolution means addressing the diagnosed structural condition rather than merely managing its expressions.
If the wrong condition was prioritized, technically competent execution may still fail to produce the expected improvement.
This is why SAI uses the principle:
Diagnosis before prescription.
The external specialist may contribute resolution expertise. The people inside the company may contribute implementation knowledge.
Neither replaces the other.
The strongest intervention may require both.
CONFIRM
Confirmation prevents the organization from declaring victory simply because an intervention occurred.
What changed?
Did the predicted mechanism change?
Did performance improve in the expected direction?
Did the improvement persist?
What alternative explanations remain?
Did another condition become more consequential?
Confirmation also provides a check on both internal and external authority. If the operator's diagnosis was wrong, evidence should expose it. If the advisor's diagnosis was wrong, evidence should expose that too.
The purpose is not to protect the reputation of the person who made the diagnosis.
It is to determine whether the diagnosis held.
FIFTY YEARS IN THE TRENCHES: WHAT THAT CAN LEGITIMATELY CONTRIBUTE
My perspective on this question comes from more than fifty years of operating businesses.
I founded companies. I managed people. I bought inventory. I borrowed money. I made payroll. I negotiated with vendors. I dealt with customers.
I watched decisions succeed.
I watched decisions fail.
I saw problems recur after competent people had addressed what appeared to be the obvious cause.
That experience matters to the development history of SAI, but it should be classified correctly.
My operating history can provide practitioner observations. It can contribute cases. It can generate propositions. It can help identify recurring questions.
It does not independently establish that the Seven Classes are exhaustive.
It does not prove that every business has exactly one governing constraint at every moment.
It does not prove that SAI diagnoses more accurately than experienced executives, consultants, or alternative frameworks.
And it does not eliminate the value of external research.
Operating experience helped generate the questions.
Independent examination must help determine how well the answers hold.
WHAT EXTERNAL SCHOLARSHIP CONTRIBUTES
The relationship between experience and knowledge has been examined across management, entrepreneurship, professional learning, and organizational research.
Experience can contribute to learning. Reflection can transform events into more generalizable understanding. Critical incidents can change how practitioners interpret future situations.
Case research can also help develop propositions from complex organizational settings.
At the same time, accumulated experience does not guarantee expertise. Repeated exposure can reinforce incorrect assumptions as easily as correct ones if learning is not disciplined.
That is why SAI should not position operating experience and research as rivals.
They perform different functions.
Practitioner experience can reveal phenomena worth examining. Research can test whether interpretations travel beyond the cases that produced them.
External analysis can challenge internal conviction.
Operating reality can challenge elegant theory.
A serious constraint discipline should be willing to learn from both directions.
A BETTER RELATIONSHIP BETWEEN THE TRENCH AND THE OBSERVATION POST
The useful question is not:
Who should win?
The operator?
The advisor?
The academic?
The accountant?
The consultant?
The researcher?
That framing produces the wrong contest.
A better model is:
The operator contributes operating evidence.
The specialist contributes disciplinary depth.
The outsider contributes distance.
The researcher contributes methods for testing propositions.
The diagnostic process integrates the evidence. The intervention follows the diagnosis. The result is then confirmed.
No participant receives authority merely because of title, credential, experience, or proximity.
The evidence remains the governing standard.
A PRACTICAL DIAGNOSTIC EXAMPLE
Consider a company whose revenue has declined for eighteen months.
The owner believes the sales team has become complacent. The sales leader believes pricing is uncompetitive. The marketing advisor believes positioning has weakened.
The operations executive believes delivery problems are driving customer attrition. The CFO believes margin pressure has limited reinvestment. A board member believes leadership has delayed necessary strategic decisions.
Every explanation is plausible.
Several may be true simultaneously.
A weak diagnostic process chooses the explanation with the strongest advocate. A specialist-led process may choose the explanation most aligned with the specialist's discipline. An operator-led process may choose the explanation most consistent with the owner's experience.
A stronger process asks:
What evidence supports each explanation?
What contradicts it?
Which explanation best accounts for the observable pattern?
Which condition appears to have the greatest structural consequence?
What intervention would test that diagnosis?
What change should occur if the diagnosis is correct?
That is the discipline the observation post and the trenches should serve together.
COUNTERARGUMENT: EXPERIENCED OPERATORS ALREADY DO THIS
A reasonable objection is that experienced executives already integrate information intuitively.
Many do. Senior operators often become skilled at seeing relationships across functions precisely because they have accumulated experience.
SAI's proposition is not that executives are incapable of diagnostic judgment without a formal methodology.
The question is whether an implicit capability can be made more explicit, teachable, repeatable, and examinable.
Formalization may be especially useful when leaders disagree; specialists recommend competing interventions; less experienced managers must learn the process; organizations want diagnostic reasoning to survive leadership transitions; or institutions want to teach the capability systematically.
The value of formalization must still be demonstrated.
COUNTERARGUMENT: OUTSIDERS OFTEN SEE THE PROBLEM BETTER THAN INSIDERS
Another reasonable objection is that external advisors are often hired precisely because internal management cannot see the problem clearly.
That is true.
The outsider's independence can be a major diagnostic advantage. SAI should therefore reject any rule suggesting that governing constraints can only be identified from inside the organization.
External practitioners may identify conditions internal leaders have missed for years.
The more defensible proposition is that high-quality diagnosis requires sufficient access to operating evidence, regardless of whether the diagnostician is internal or external.
An outsider who understands the operating reality may diagnose exceptionally well.
An insider who never questions assumptions may diagnose poorly.
Position alone determines neither.
COUNTERARGUMENT: DATA SHOULD OUTWEIGH EXPERIENCE
A third objection is that disciplined analysis should rely on objective data rather than subjective operating impressions.
Where reliable data exist, they matter greatly.
But business evidence is rarely confined to one form. Some conditions are measured directly; others require interpretation. Some involve customer confidence. Others involve authority, trust, leadership behavior, decision speed, informal organizational structures, or strategic assumptions.
The appropriate standard is not:
data versus experience.
It is:
What combination of evidence provides the strongest basis for the conclusion?
A diagnostic process should seek corroboration. It should distinguish fact from interpretation. It should make uncertainty visible.
And it should remain open to competing explanations.
LIMITATIONS AND QUESTIONS FOR FURTHER EXAMINATION
This paper advances a conceptual proposition about diagnostic perspective.
It does not demonstrate that external advisors systematically diagnose less accurately than operators. It does not demonstrate that operators systematically possess superior causal knowledge.
It does not establish that combining perspectives necessarily improves outcomes. It does not establish the reliability or validity of the Seven Classes of Business Constraint™.
It does not independently validate the Business Constraint Diagnostic™.
And it does not establish that SAI's methodology produces superior organizational outcomes relative to alternative diagnostic approaches.
Further examination should compare diagnoses produced by internal leaders, external specialists, multidisciplinary teams, and structured SAI methods. Researchers could examine diagnostic agreement, classification reliability, decision quality, intervention selection, and outcomes after corrective action.
The observation-post/trenches metaphor should therefore be treated as a framework for inquiry—not as evidence that one vantage point has already been proven superior.
IMPLICATIONS FOR BUSINESS OWNERS
Owners should take operating knowledge seriously.
They should not assume it makes them diagnostically infallible.
When the same problem returns repeatedly, the appropriate response may not be greater confidence in the previous explanation.
It may be a better question.
What are we seeing?
What are we assuming?
What could explain the same symptoms?
What evidence are we missing?
What would an informed outsider challenge?
What do the people closest to the work know that senior management does not?
And of all the real problems present:
Which one deserves priority?
IMPLICATIONS FOR ADVISORS AND CONSULTANTS
Advisors should value professional expertise without allowing expertise to become a diagnostic shortcut.
The client may know things the advisor does not. The advisor may see things the client cannot.
The objective is not to establish who has authority.
It is to build a sufficiently complete evidence base before prescription begins.
A specialist who asks broader diagnostic questions does not weaken specialization.
It makes specialization more likely to be applied where it matters most.
IMPLICATIONS FOR BUSINESS EDUCATION
The observation-post/trenches distinction also has teaching value.
Students can be given the same business case from two perspectives. One version can contain management reports, financial data, customer metrics, and organizational charts.
The other can contain operating interviews, informal practices, executive recollections, employee observations, and critical incidents.
Students can then be asked to identify what each perspective reveals, what each omits, which claims are facts, which are interpretations, what competing explanations remain, and what additional evidence is required before naming a governing constraint.
That exercise teaches something larger than framework application.
It teaches diagnostic humility.
CONCLUSION
The observation post can see things the trench cannot.
The trench can see things the observation post cannot.
Neither vantage point deserves automatic authority.
Operating experience matters because businesses are lived before they are analyzed. External analysis matters because people inside organizations can become blind to what they have normalized.
Specialists matter because complex problems require depth. Cross-functional diagnosis matters because the existence of a legitimate problem does not establish that it deserves priority.
SAI proposes that the stronger discipline is not:
inside instead of outside.
Nor:
experience instead of research.
Nor:
operators instead of experts.
It is:
evidence before conclusion.
And then:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
The operating question remains:
Of all the real problems in front of the business, which condition deserves attention first?
The observation post may contribute part of the answer.
The trenches may contribute another.
The diagnostic task is to determine what the evidence indicates when both are taken seriously.
That is a stronger basis for judgment than either perspective standing alone.
REFERENCES
Cope, J., & Watts, G. (2000). Learning by doing—An exploration of experience, critical incidents and reflection in entrepreneurial learning. International Journal of Entrepreneurial Behaviour & Research, 6, 104–124.
Eisenhardt, K. M. (1989). Building theories from case study research. Academy of Management Review, 14(4), 532–550.
Kolb, D. A. (1984). Experiential Learning: Experience as the Source of Learning and Development. Prentice-Hall.
Politis, D. (2005). The process of entrepreneurial learning: A conceptual framework. Entrepreneurship Theory and Practice, 29, 399–424.
Schön, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.
Winkler, C., Fust, A., & Jenert, T. (2021). From entrepreneurial experience to expertise: A self-regulated learning perspective. Journal of Small Business Management, 61, 2071–2096.
RELATED SAI RESOURCES
The Seven Classes of Business Constraint™
The Governing Constraint Principle
How the SAI Business Constraint Discipline™ Works
The U.S. Lock Story. The Operating Experience That Helped Shape a New Constraint Discipline.
Some Got Close. Close Does Not Get You the Prize.
Critical Examination & SAI Responses
The SAI White Paper Library
Commercial participation is not required to examine, question, criticize, or challenge the propositions advanced in this paper.
Lawrence M. Schneider
Founder & CEO
Schneider Axiom Institute
Institute for Business Constraints™
SAI-BCD-06 | Version 2.0 | September 2026