Nobody Is Failing. The Result Still Is.
SAI WHITE PAPER SERIES
Nobody Is Failing. The Result Still Is.
How Competent People Can Produce Poor Organizational Outcomes When Execution Breaks Between Functions
Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™
PUBLICATION IDENTITY
Permanent Publication Identifier: SAI-OPE-01
Original Publication: September 2026
Current Editorial Revision: September 2026
Version: 1.0
Classification: Organizational Performance & Execution
Subject: Execution Architecture, Cross-Functional Coordination, Interdependence, Handoffs, Priority Alignment & System-Level Performance
Primary Audience: Business Owners, Executives, Operating Leaders, Functional Leaders & Advisors
Primary Constraint Relevance: Cross-Class — All Seven Classes
SAI Discipline Stage: IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
Evidence Orientation: Interpretive Practitioner Proposition Supported by Research on Organizational Coordination, Cross-Functional Integration, Interdependent Work, Performance Measurement & Relational Coordination
Executive Abstract
Organizations often respond to poor results by asking a familiar question: Who failed? Sometimes that question is necessary. But there is another class of organizational failure in which capable people perform their assigned responsibilities, departments meet their internal requirements, procedures are followed—and the business still produces the wrong result.
Sales completes its work. Operations completes its work. Finance follows its controls. Purchasing follows procedure. Managers meet departmental targets. Yet the customer waits, the project slips, rework increases, decisions stall, margin deteriorates, or a strategic initiative loses momentum.
The problem may not exist within any one function. It may exist between them.
This White Paper examines the distinction between local performance and system-level execution. It proposes that when organizational outcomes depend upon multiple interdependent functions, competent performance inside each function does not ensure competent performance across the whole system.
The paper introduces the SAI Execution Coherence Test, a five-part practitioner structure examining:
Result Clarity
Interdependence
Handoff Integrity
Priority Alignment
Confirmation
The central proposition is:
THE CENTRAL PROPOSITION
An organization can contain competent people, successful departments, and compliant processes—and still fail at the result level because execution is produced by the system connecting them.
Local performance and organizational performance are different levels of analysis. When an outcome depends on multiple interdependent functions, each part can satisfy its own requirements while the combined system fails to produce the intended result. The diagnostic task is therefore not only to ask who performed poorly, but whether the execution architecture enabled individually competent work to combine into the required outcome.
Four distinctions are essential.
Individual Performance
Did the person perform the assigned responsibility?
Functional Performance
Did the department produce its expected output?
Execution Performance
Did work move effectively across the dependencies required to produce the result?
Organizational Performance
Did the business outcome actually occur?
These levels can align. They can also diverge.
A department can succeed while the organization fails.
Why This Paper Matters
When an important result fails, organizations often begin by looking for the responsible person. Who missed the deadline? Who failed to communicate? Which department dropped the ball? Who did not follow through?
Those questions are sometimes appropriate. Individual performance failures are real. Accountability matters. But they can also begin the diagnosis at the wrong level.
Consider a customer order requiring:
Sales → Credit → Purchasing → Scheduling → Production → Quality → Shipping → Billing
Every function can perform its assigned work correctly. The order can still arrive late. Why?
Because organizational results are often produced across functions, not inside one of them. The handoff may fail. The information may be incomplete. The priorities may conflict. Decision authority may become unclear precisely where responsibility shifts. No single person may own the complete result.
Local competence does not automatically create execution coherence.
That distinction matters because replacing, coaching, reprimanding, or reorganizing individuals will not resolve a structural problem if the system connecting their work remains unchanged.
The Business Result Does Not Respect the Organization Chart
Organizations divide work into functions because specialization creates expertise. Customers experience something very different. They experience the result.
A customer does not care that Sales entered the order correctly if Operations never received the information required to produce it. The customer does not care that Purchasing achieved its cost target if the selected source causes the delivery commitment to be missed. The customer does not care that Finance followed the approval procedure if the approval cycle causes the opportunity to disappear.
The organization chart shows where work resides. It does not necessarily show how value is produced.
Okhuysen and Bechky describe coordination as the integration of interdependent tasks and identify accountability, predictability, and common understanding as conditions supporting coordinated activity (Okhuysen & Bechky, 2009).
That creates an important paradox:
Specialization can improve each function.
Interdependence can make the overall result more fragile.
Specialization improves the pieces. Coordination determines whether the pieces produce the result.
Everyone Can Be Right—and the Organization Can Still Be Wrong
Imagine five functions. Sales wants responsiveness. Operations wants schedule stability. Purchasing wants lower cost. Finance wants control. Quality wants compliance.
Every objective is legitimate. Now place them inside one customer order.
Sales accepts a short lead time to protect the relationship. Operations resists disrupting the schedule. Purchasing chooses the lower-cost source despite a longer lead time. Finance requires an approval because the order exceeds an exception threshold. Quality will not release the product until documentation is complete.
Who is wrong? Possibly no one. Each function may be doing exactly what leadership designed it to do. The combined result can still fail.
That is the execution problem.
Steven Kerr's classic work on organizational reward systems demonstrated the broader problem of organizations rewarding one behavior while hoping for another (Kerr, 1975).
The same conflict can appear through:
Metrics
Targets
Procedures
Authority
Incentives
Operating rules
People can respond rationally to the system they were given while the organization behaves irrationally as a whole.
This is why execution failure cannot always be diagnosed by locating the person closest to the failed result. The visible failure may be downstream. The governing condition may be structural.
THE SAI EXECUTION COHERENCE TEST
The SAI Execution Coherence Test is a practitioner-developed structure for examining whether competent local work can combine into the intended organizational result.
It does not presume that people are performing well. It does not excuse individual underperformance. It asks a different question:
If capable people perform their assigned responsibilities, does the system make the intended result reasonably achievable—or does success still depend on escalation, workarounds, heroics, or luck?
The test examines five conditions.
1. RESULT-CLARITY TEST
What end-to-end result is the organization actually trying to produce?
Functions frequently know their own deliverables better than they know the organizational result those deliverables exist to support.
Sales knows the booking target. Production knows the schedule. Purchasing knows the cost target. Finance knows the approval requirement. Shipping knows the dispatch date.
But what is the complete result?
Not:
Order entered.
Not:
Material purchased.
Not:
Product manufactured.
A stronger system-level definition might be:
Customer order accepted → delivered completely, profitably, and within the commitment made to the customer.
For a project:
Project authorized → completed to specification, within required economics, and within the agreed timeframe.
For a strategic initiative:
Initiative approved → capability implemented → intended performance condition measurably changed.
If functions are optimizing different definitions of success, execution incoherence may be built into the system before the work begins.
2. INTERDEPENDENCE TEST
Whose work depends upon someone else's work before the result can occur?
Organizations often describe activities separately even when the outcome depends upon them collectively.
Production cannot proceed without material. Purchasing cannot order without specifications. Engineering cannot finalize specifications without customer requirements. Sales may be waiting for the customer. Finance may be holding expenditure approval until assumptions are confirmed.
That is not five independent processes. It is one interdependent result.
Bolton, Logan, and Gittell's systematic review of relational coordination research emphasizes the role of shared goals, shared knowledge, mutual respect, and timely problem-solving communication in work crossing roles and boundaries (Bolton, Logan, & Gittell, 2021).
The diagnostic issue is not simply whether departments communicate. It is whether the dependencies are understood and managed.
Ask:
Whose output becomes another person's input?
Where must work occur in sequence?
Where must decisions occur simultaneously?
Where can one function's reasonable action create difficulty elsewhere?
Interdependence is where local performance becomes organizational performance.
3. HANDOFF-INTEGRITY TEST
When responsibility moves, does everything required to continue the work move with it?
A handoff is not simply the transfer of a task. It may require:
Context
Specifications
Authority
Timing
Customer commitments
Exception history
Decision criteria
Risk information
A handoff can appear complete to the person sending the work while remaining unusable to the person receiving it.
One employee says: “I sent it.” The next says: “I couldn't act on it.” Both may be correct. The problem may exist in the transfer standard.
The Handoff-Integrity Test asks:
What must move?
In what form?
By when?
Who determines whether the transfer is usable?
What happens when something is incomplete or ambiguous?
A completed handoff is not the same as a successful handoff.
Organizations frequently measure whether something was transferred. They measure less often whether the receiving function could successfully continue the work.
4. PRIORITY-ALIGNMENT TEST
When legitimate priorities conflict, what determines which one governs?
Cross-functional execution inevitably produces competing objectives.
Speed vs. Efficiency
Cost vs. Availability
Control vs. Responsiveness
Standardization vs. Customer Accommodation
Utilization vs. Flexibility
The problem is not that one side is wrong. The problem appears when the organization lacks a disciplined way to determine which objective has priority in the circumstance being decided.
Research by Li and colleagues involving 410 Chinese manufacturing firms found associations between forms of cross-functional coordination, customer coordination, and operational performance, while also showing that different forms of coordination do not operate identically (Li et al., 2021).
The managerial question is therefore not:
Do our departments coordinate?
It is:
Can the organization resolve competing functional priorities in favor of the result that matters most?
If Sales wants speed and Operations wants stability, what governs? If Purchasing can lower unit cost but increase lead time, what governs? If Finance requires another approval while the opportunity is expiring, what governs?
If the practical answer is:
Whoever escalates hardest,
then the organization does not have priority alignment. It has conflict resolution by pressure.
5. CONFIRMATION TEST
Does the organization measure whether the total result occurred—or mainly whether every function completed its part?
An organization can report:
Sales target achieved.
Purchasing savings achieved.
Production efficiency achieved.
Finance controls achieved.
Shipping utilization achieved.
And simultaneously report:
On-time delivery declined.
Rework increased.
Margin deteriorated.
Project cycle time lengthened.
Customer dissatisfaction increased.
No single mismatch proves an execution constraint. But repeated local success accompanied by poor organizational outcomes creates a diagnostic signal.
If every part is succeeding and the whole is failing, the definition of success may be incomplete.
Confirmation asks:
Did the business outcome improve?
Not:
Did everyone complete their activity?
Five Signals That the Execution System Deserves Examination
Certain patterns should cause leadership to investigate execution architecture before assigning blame.
1. Problems repeatedly appear at departmental boundaries
Inside each function, work appears controlled. Failure appears during transfer.
2. Senior leaders repeatedly resolve routine cross-functional conflicts
The organization functions because executives have become the integration mechanism.
3. High performers become informal coordinators
They chase approvals. Recover missing information. Interpret exceptions. Translate between functions. Correct broken handoffs.
4. Local metrics improve while the business result does not
Functional success and system performance move in different directions.
5. One experienced employee leaves—and the process suddenly becomes unstable
What appeared to be process capability may have been undocumented knowledge embodied in one person.
These conditions do not prove a governing constraint. They tell leadership where diagnosis should deepen.
Three Illustrative Execution Scenarios
The following scenarios are illustrative constructions. They are not documented SAI client histories or independently verified case studies.
Their purpose is to demonstrate how execution can fail without requiring an incompetent actor.
Illustrative Scenario 1 — Every Department Was On Time. The Customer Order Was Late.
Sales entered the order on time. Credit approved it within its required window. Purchasing released the material according to procedure. Production completed the work within its internal schedule. Shipping dispatched the finished order promptly.
The customer still received the order after the promised date. No departmental report identifies the failure.
Closer examination shows that Sales establishes the delivery commitment before material availability and production capacity are confirmed.
Every function performs according to its rules. The rules do not combine into a reliable customer promise.
The execution failure exists between the functions.
Illustrative Scenario 2 — The Project Nobody Delayed
A cross-functional launch finishes six weeks late. No department reports missing its own service standard.
Marketing waited for final specifications. Engineering waited for regulatory interpretation. Legal responded within its standard review period. Operations waited for final design. Finance approved the capital request within policy.
Every delay has an explanation. The project is still six weeks late.
The better question is not:
Which department was late?
It is:
Was anyone managing the complete chain of dependencies required to make the launch date possible?
Illustrative Scenario 3 — The Employee Who Makes the System Work
A senior operations manager is considered indispensable. When an order becomes stuck, she knows whom to call. When information is incomplete, she finds it. When Purchasing and Production disagree, she resolves the issue. When the customer commitment is at risk, she secures the exception.
Her performance may be exceptional. It may also be evidence. The formal system does not reliably coordinate the work without her.
Leadership sees a star employee. Diagnosis may reveal a star employee and an execution dependency.
The organization's strength and vulnerability can occupy the same chair.
When Your Best People Become the Process
High performers often prevent structural weaknesses from becoming visible. They know which procedure can be bypassed safely. They know whom to call before a handoff fails. They remember the exception nobody documented. They understand what one department means when another department hears something different.
They make the organization work. That is valuable. It can also be dangerous.
Because every successful intervention prevents the weakness in the formal system from producing its full consequence. The immediate problem gets solved. The structural condition remains.
Over time, the organization may begin to treat exceptional human compensation as normal process capability.
A workaround that succeeds often enough can become indistinguishable from the process it is compensating for.
Until the person is unavailable. Promoted. Overloaded. Or gone.
Coordination Does Not Mean More Meetings
When execution breaks between functions, organizations often prescribe communication.
Another meeting. Another dashboard. Another status call. Another report. Another collaborative platform.
Some may help. None automatically produces coordination.
Okhuysen and Bechky's review is useful because it focuses on what coordination mechanisms are intended to create:
Accountability
Predictability
Common Understanding
A meeting that improves none of these conditions may simply consume time. A dashboard displaying incompatible priorities may make conflict more visible without resolving it. A status report may document the delay without changing the dependency causing it.
The relevant question is:
What dependency is this coordination mechanism designed to manage?
If the organization cannot answer, it may be surrounding the execution problem with communication rather than resolving it.
Execution Failure Does Not Identify the Constraint Class
The Seven Classes of Business Constraint™ are:
Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility
Execution failure can appear in any of them.
A late delivery may indicate an Operational condition. But the delay may actually be produced by a Financial constraint limiting working capital. An Organizational constraint may have created unclear authority. A Strategic decision may have committed the organization beyond available capability. A Leadership pattern may require one executive to approve every important exception.
The visible execution problem identifies where performance is breaking down. It does not necessarily identify what is governing the breakdown.
Location is not diagnosis.
Otherwise, every execution failure becomes a process-improvement project merely because the symptom appeared in a process.
Using the SAI Business Constraint Discipline™
The sequence is exact:
IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM
IDENTIFY
Determine the structural condition producing or materially governing the execution failure. Do not automatically assign causation to the person nearest the failed result.
PRIORITIZE
Determine whether the execution condition deserves attention first. An execution problem can be real without being the governing constraint.
RESOLVE
Select corrective action appropriate to the identified condition. The response may involve:
Role clarity
Process design
Decision rights
Measurement
Capacity
Technology
Incentives
Organizational structure
Leadership behavior
CONFIRM
Determine whether the performance limitation changed.
Did the end-to-end outcome improve? Did the delay disappear? Did rework fall? Did the dependency weaken? Did the result hold?
Completion is not confirmation. Implementation is not confirmation. Activity is not confirmation.
Implications / Applications
For owners and executives, the principal implication is simple: Do not begin every failed result by searching for someone to blame. Begin by locating the level at which the failure occurred.
Ask:
What result failed?
Which functions had to combine to produce it?
Where did dependency become friction?
Were the handoffs usable?
Were local priorities compatible with the organizational result?
Who owned the complete outcome?
How was success confirmed?
This does not weaken accountability. It makes accountability more accurate.
When an employee fails to execute a clear responsibility inside a coherent system, individual accountability may be appropriate. When capable employees are working inside contradictory measures, incomplete handoffs, unclear authority, incompatible priorities, or unmanaged dependencies, replacing one person may simply install a new person inside the same condition.
The SAI Execution Coherence Test is therefore most useful when organizations see:
Recurring delay
Rework
Customer dissatisfaction
Project slippage
Cross-functional conflict
Executive escalation
Dependence on informal high performers
The objective is not perfect coordination. It is something more practical:
An execution system in which ordinary competent performance can reliably produce the intended result without requiring extraordinary intervention.
What External Research Adds
External research provides important context for this proposition.
Okhuysen and Bechky's integrative review positions coordination as central to integrating interdependent tasks and identifies accountability, predictability, and common understanding as important conditions for coordinated activity (Okhuysen & Bechky, 2009).
Bolton, Logan, and Gittell's systematic review emphasizes shared goals, shared knowledge, mutual respect, and effective communication as relevant to coordinating complex interdependent work across boundaries (Bolton et al., 2021).
Li and colleagues found associations among several forms of cross-functional coordination, customer coordination, and operational performance in a study of 410 Chinese manufacturers (Li et al., 2021).
Kerr's work provides longstanding evidence of the organizational consequences that can occur when systems reward one behavior while expecting another (Kerr, 1975).
Together, these sources support the broader propositions that:
Interdependent work requires coordination.
Local responsibilities do not automatically create system integration.
Shared goals and information matter when work crosses boundaries.
Organizational systems can encourage behaviors that diverge from desired outcomes.
They do not independently validate the SAI Execution Coherence Test, prove that structural execution failure is more common than individual failure, or establish that improving coordination will necessarily improve every organizational result.
Limitations and Questions for Further Examination
Not every poor organizational result is structural. Individuals can underperform. Managers can avoid decisions. Teams can lack capability. People can ignore sound processes. External conditions can disrupt coherent systems.
The existence of cross-functional interdependence also does not prove that more coordination is always better. Coordination consumes time. It consumes attention. It can create bureaucracy. It can slow decisions.
The SAI Execution Coherence Test is practitioner-developed. The external research cited in this paper supports the broader relevance of coordination, interdependence, shared goals, performance systems, and cross-functional integration. It does not constitute independent empirical validation of the SAI framework.
Execution failure also does not, by itself, identify the governing constraint. The structural cause may reside in any of the Seven Classes.
Questions for Further Examination
Further practitioner and empirical examination should consider:
When do local performance measures conflict with end-to-end organizational outcomes?
Which forms of cross-functional dependency create the greatest execution exposure?
How can organizations distinguish productive coordination from unnecessary bureaucracy?
When are high-performing employees masking structural weaknesses?
Do end-to-end result measures improve cross-functional execution?
What evidence most reliably distinguishes individual underperformance from execution-architecture failure?
Conclusion
Organizations need competent people. They also need an execution architecture capable of converting competent work into a coherent result. That conversion is not automatic.
A department can achieve its target while the customer experience deteriorates. A manager can follow procedure while the project slows. A high performer can repeatedly save the organization while hiding the structural weakness that made saving necessary.
Everyone can be busy. Everyone can be competent. Everyone can be doing what the organization told them to do. And the result can still fail.
The diagnostic question therefore cannot stop at:
Who failed?
It must also ask:
What prevented competent individual work from combining into the result the organization required?
Sometimes the answer will be:
A person.
Sometimes:
A process.
Sometimes:
Authority.
Measurement.
Information.
Capacity.
Priorities.
Structure.
Leadership.
And sometimes the governing constraint will exist somewhere that the execution symptom did not initially suggest.
That is why diagnosis must precede prescription.
Nobody has to be failing for the execution system to be failing.
Evidence Boundary
This White Paper presents a practitioner-developed SAI framework for examining the relationship between local performance and system-level execution.
The cited external literature supports broader concepts involving organizational coordination, cross-functional integration, interdependent work, shared goals, performance systems, and relational coordination.
Those sources do not independently validate the SAI Execution Coherence Test, the Seven Classes of Business Constraint™, or the SAI Business Constraint Discipline™.
This paper does not claim that execution failure is always structural, that competent individuals cannot cause poor outcomes, or that increased coordination necessarily improves organizational performance.
The illustrative scenarios are explanatory constructions. They are not represented as documented SAI client histories or independently verified case studies.
The SAI contribution is the organization of these concepts into a practitioner assessment structure examining:
Result Clarity
Interdependence
Handoff Integrity
Priority Alignment
Confirmation
before corrective action is selected.
References
Bolton, R., Logan, C., & Gittell, J. H. (2021). Revisiting relational coordination: A systematic review. The Journal of Applied Behavioral Science, 57, 290–322. https://doi.org/10.1177/0021886321991597
Kerr, S. (1975). On the folly of rewarding A, while hoping for B. Academy of Management Journal, 18(4), 769–783.
Li, S., Wang, K.-D., Huo, B., Zhao, X., & Cui, X. (2021). The impact of cross-functional coordination on customer coordination and operational performance: An information processing view. Industrial Management & Data Systems, 122, 167–193. https://doi.org/10.1108/IMDS-04-2021-0265
Okhuysen, G. A., & Bechky, B. A. (2009). Coordination in organizations: An integrative perspective. The Academy of Management Annals, 3, 463–502. https://doi.org/10.1080/19416520903047533
Related SAI Resources
Everyone Did Their Job. Nobody Owned the Result.
The Process That Nobody Owns
Authority Assigned. Accountability Missing.
The People Were Not the Bottleneck
The Seven Classes of Business Constraint™
What Is the SAI Business Constraint Discipline?
Related SAI materials extend the diagnostic context of this paper. They should not be interpreted as independent evidence for claims attributed to the external literature.
About the Author
Lawrence M. Schneider is Founder and CEO of the Schneider Axiom Institute and developer of the SAI Business Constraint Discipline™. His work draws upon more than fifty years of CEO-level operating experience across manufacturing, distribution, construction, land development, franchising, and multi-entity businesses.
Lawrence M. Schneider founded U.S. Lock Corporation and served as its Chairman and CEO for almost twenty years. Under his leadership, the company grew to more than 250 employees, 15,000 customers, and 1,100 authorized dealers. U.S. Lock is now owned by The Home Depot.
The SAI Business Constraint Discipline™ developed from Schneider's effort to formalize recurring operating observations about diagnosis, prioritization, structural causes, and the sequencing of corrective action. His operating experience is a source of practitioner observations, recurring questions, distinctions, and propositions for further examination; it is not controlled empirical evidence and does not, by itself, establish generalizability, causation, transfer, effectiveness, or independent validation of the SAI framework.
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.