SAI WHITE PAPER SERIES

When Accountability Without Diagnosis Becomes Punishment

Why Responsibility, Authority, and Structural Cause Must Be Aligned Before Performance Is Judged

Lawrence M. Schneider
Founder & CEO, Schneider Axiom Institute™

Original Publication: June 2026 · Classification: Constraint Identification & Diagnostic Reasoning · Publication Identifier: SAI-CIDR-02
Current Revision: September 2026 · Version: 2.0

EXECUTIVE ABSTRACT

Accountability is essential to organizational performance. People must know what results are expected, what decisions they own, and what standards they are responsible for meeting. But accountability becomes more complicated when the person being judged does not control the structural conditions governing the result.

A sales team may be accountable for declining conversion while the more consequential limitation lies in positioning, pricing, product-market fit, credibility, or strategy. An operations team may be accountable for delivery performance while capacity decisions, capital constraints, or organizational design materially limit what the team can produce. The performance gap is real, and individual execution may also be imperfect.

But those facts do not establish that the person closest to the result is also the person controlling its governing cause. This White Paper does not argue that employees should be protected from legitimate performance standards. It does not argue that every performance problem originates above the employee. And it does not suggest that structural constraints excuse weak execution.

It advances a narrower proposition:

Accountability is most defensible when responsibility, authority, and structural control are sufficiently aligned. When people are held responsible for outcomes they cannot materially influence, accountability can become punitive rather than corrective while the governing constraint remains unresolved.

The Schneider Axiom Institute therefore treats accountability as a question that follows diagnosis rather than substitutes for it. The sequence remains:

IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM

Before deciding who should be held accountable for a performance gap, leadership should first determine what condition is actually governing the result.

THE CENTRAL PROPOSITION

WHY THIS PAPER MATTERS

Organizations routinely evaluate performance through metrics, assigned responsibilities, and individual results. Those measures are necessary, but they do not by themselves identify what is governing the result. When accountability is directed toward the person closest to the symptom rather than toward the condition most responsible for producing it, leadership can intensify pressure without materially improving performance—and may make the underlying constraint harder to see.

Accountability is not the problem. Misaligned accountability is. The critical distinction is between owning a result and controlling the conditions required to produce it. Those concepts overlap. They are not identical.

A PERFORMANCE GAP IS NOT YET A DIAGNOSIS

Suppose a sales team has missed its close-rate target for three quarters. The performance gap is real. Leadership may reasonably examine training, coaching, compensation, pipeline discipline, sales management, and individual execution. All are legitimate areas of inquiry.

But a weak close rate does not establish that sales execution is the governing cause. The same symptom may also be consistent with poor positioning, weak differentiation, pricing misalignment, declining credibility, deteriorating market conditions, an inappropriate customer segment, or product limitations.

Performance data tells leadership what happened. Diagnosis asks what is governing why it happened. That distinction matters because accountability normally follows the explanation assigned to the performance gap. If the explanation is incomplete, the accountability may be misdirected.

ILLUSTRATIVE EXAMPLE: SALES PERFORMANCE

Consider a company with declining conversion. Management concludes that the sales team is underperforming. Coaching increases, pipeline reviews become more frequent, compensation is revised, and some representatives are placed on improvement plans.

Sales practices may genuinely improve, yet overall conversion remains weak. A broader diagnostic inquiry might indicate that the more consequential limitation lies elsewhere: positioning has deteriorated, the target customer has changed, competitors now offer a stronger value proposition, or salespeople are being asked to overcome objections created upstream.

The sales team may still be responsible for competent execution. But leadership should distinguish between:

accountability for execution

and

accountability for the condition governing the result.

They do not necessarily belong to the same person or organizational level.

ILLUSTRATIVE EXAMPLE: OPERATING CAPACITY

An operations team repeatedly misses delivery commitments. Leadership interprets the problem as weak execution. Schedules tighten, reporting increases, and performance targets become more aggressive.

But suppose demand consistently exceeds the productive capacity created by earlier capital decisions. The team may still have process deficiencies, and managers may still make avoidable mistakes. Those issues deserve attention.

Yet performance pressure cannot create equipment, labor capacity, throughput, or investment authority the team does not possess. If capacity is the more consequential limitation, accountability directed solely toward operating execution will not resolve it.

The question that must precede intensified accountability is therefore:

What condition is actually limiting the result?

RESPONSIBILITY AND CONTROLLABILITY ARE DIFFERENT QUESTIONS

Organizations often assign responsibility through hierarchy. A manager owns the number, a department owns the metric, and a regional executive owns the territory. That administrative ownership is useful.

But ownership of a metric does not prove control over every important condition producing it. A person may be responsible for an outcome while lacking authority over variables that materially determine the outcome.

This creates a central performance-management question:

How much accountability is reasonable when control over the result is incomplete?

The answer is rarely all or nothing. Organizational results usually emerge from interacting conditions. That is why diagnosis matters.

The purpose is not to remove accountability whenever complexity exists. It is to distinguish the portion of the result the person can reasonably influence from the portion the organization must address elsewhere.

WHEN ACCOUNTABILITY BECOMES PUNITIVE

Accountability can become punitive when the organization repeatedly demands an outcome without addressing material barriers the accountable person cannot change. The person may be told:

“You own the result.”

Yet authority over the conditions producing the result sits elsewhere. A manager may be accountable for service levels without controlling staffing. A regional executive may be accountable for market share without controlling the product offering. A plant manager may be accountable for throughput without controlling capital investment. A salesperson may be accountable for conversion while pricing, positioning, and product credibility are determined upstream.

None of those examples proves the person is performing well. They demonstrate something narrower:

Responsibility can exceed authority.

When it does, accountability can shift from a corrective mechanism toward pressure applied to the visible owner of the metric.

THE PERSON CLOSEST TO THE WORK MAY HOLD RELEVANT EVIDENCE

Employees close to the work often possess evidence senior leadership does not see directly. Salespeople hear customer objections, operations teams see recurring bottlenecks, customer-service teams hear repeated complaints, and middle managers encounter decision delays and authority conflicts.

That proximity does not make employees automatically correct. People can misdiagnose their own performance problems and attribute avoidable shortcomings to systems, leadership, resources, customers, or circumstances. Their interpretation should therefore be examined rather than presumed true.

But their observations remain evidence. A sound accountability process should allow for the possibility that the person being evaluated possesses information about structural conditions affecting the result. When disagreement is treated automatically as defensiveness, potentially useful diagnostic evidence can be lost.

EXECUTION FAILURE AND STRUCTURAL CONSTRAINT CAN COEXIST

This is one of the most important distinctions in the paper. A person can be underperforming and operating inside a structural constraint. A sales representative may need stronger prospecting discipline while the company also has a serious positioning problem. An operations manager may have weak scheduling practices while production capacity remains inadequate. A department leader may require better management discipline while authority remains structurally unclear.

Both can be true. A structural constraint does not erase individual responsibility. And individual execution problems do not establish that the individual is the governing constraint.

The diagnostic task is comparative:

Which condition is most consequential?

Which deficiencies are secondary?

Which performance expectations remain reasonable under the existing operating conditions?

Those questions are more useful than forcing a choice between:

“It is the person.”

and

“It is the system.”

Often the evidence will implicate both. Priority still has to be determined.

THE RISK OF MANAGING THE METRIC INSTEAD OF THE RESULT

When people are evaluated heavily on measures they cannot materially influence, they may begin optimizing what they can control. Sometimes that improves performance. Sometimes it produces goal displacement.

A sales team evaluated primarily on conversion rate may tighten qualification criteria. A service organization evaluated on call duration may shorten conversations. A production team evaluated on unit output may defer maintenance. A manager evaluated principally on headcount may preserve staffing targets while work accumulates elsewhere.

The measurement improves. The underlying organizational outcome may not. Steven Kerr's classic observation about organizations “rewarding A, while hoping for B” illustrates the broader problem: incentive and measurement systems can encourage behavior different from the result leadership actually intends.

The lesson is not that metrics are harmful. It is that a metric should not be mistaken for a diagnosis.

ACCOUNTABILITY, FAIRNESS, AND LEGITIMACY

Research on organizational justice indicates that employees respond not only to outcomes, but also to how decisions and procedures are perceived. That does not mean an unfavorable performance review is unfair. It means accountability is more likely to be regarded as legitimate when expectations correspond reasonably to authority, resources, process, and opportunity to perform.

When people believe they are being held responsible for results outside their meaningful control, several responses are possible. They may raise concerns, adapt behavior to the metric, disengage, or leave. They may also remain committed and continue performing.

The evidence does not justify claiming that misdirected accountability inevitably causes turnover. It does justify treating perceived controllability, fairness, and employee voice as relevant to the design of accountability systems.

EMPLOYEE VOICE IS EVIDENCE—NOT PROOF

A recurring danger in performance management is treating every employee explanation as an excuse. Sometimes it is. Sometimes it is not. The organization therefore needs a way to distinguish self-protection from diagnostic evidence.

If several capable employees independently report the same structural barrier, leadership should not automatically conclude that the barrier is governing. But neither should it automatically dismiss the pattern.

The appropriate response is examination. What evidence supports the interpretation? What evidence contradicts it? Does the claimed condition affect performance across multiple people or units? Does performance change where that condition is absent? Can the proposed explanation be tested?

Those questions convert a dispute about accountability into a diagnostic inquiry.

WHEN ADVISORS INHERIT THE CLIENT'S PERFORMANCE DIAGNOSIS

External advisors face a similar risk. A client may begin with a conclusion:

“Our managers do not hold people accountable.”

“Our salespeople are not performing.”

“We need a stronger performance-management system.”

The advisor may competently improve the requested system. But if the presenting problem is accepted as the diagnosis, the engagement may become highly effective at improving a secondary condition.

A stronger starting question is:

What evidence shows that accountability is aimed at the condition most responsible for the performance gap?

That question does not undermine accountability. It improves the probability that accountability is directed toward the right problem.

THE GOVERNING-CONSTRAINT QUESTION

SAI organizes diagnostic inquiry across seven possible classes:

Market · Operational · Financial · Organizational · Strategic · Leadership · Credibility

A performance problem may contain evidence from several classes simultaneously. Weak sales performance, for example, might involve:

a Market problem in customer selection;

a Strategic problem in positioning;

an Organizational problem in role design;

a Leadership problem in decision-making;

a Credibility problem affecting buyer confidence;

and genuine sales-execution deficiencies.

The existence of several real problems does not eliminate accountability. It makes sequencing more important. The diagnostic question becomes:

Which condition is most consequential now?

That condition deserves priority.

IDENTIFY

The first stage is:

IDENTIFY

Before intensifying accountability, leadership should identify the conditions contributing to the performance gap. What result is below expectation? What evidence confirms it? Which aspects of the result are within the person's authority? Which material conditions sit outside that authority? What competing explanations could produce the same outcome?

Identification separates observed performance from assumed cause.

PRIORITIZE

The second stage is:

PRIORITIZE

Organizations can contain several legitimate performance problems at once. The person may need coaching, the process may need redesign, resources may be inadequate, and the strategy may need correction.

Prioritization asks which condition is most consequential to the current performance limitation. Accountability should not automatically concentrate where the symptom is most visible. It should be aligned as closely as possible with the condition that deserves priority.

RESOLVE

The third stage is:

RESOLVE

Once the governing condition has been identified and prioritized, corrective action should be directed toward it. If individual execution is governing the result, accountability may appropriately focus on the individual. If organizational design is governing it, accountability may need to move upward or across functions.

If the constraint is strategic, responsibility may sit primarily with those possessing strategic authority. If several conditions contribute materially, responsibility may need to be distributed. The objective is not to protect people from accountability. It is to make accountability actionable.

CONFIRM

The fourth stage is:

CONFIRM

Any diagnosis can be wrong. If leadership concludes that the performance problem is primarily structural and changes the structural condition, performance should respond in ways consistent with that diagnosis. If it does not, the diagnosis must remain open to reconsideration.

Likewise, if individual execution is identified as the governing limitation, improved execution should produce observable change. Confirmation prevents accountability from becoming ideology. It forces the organization to ask whether the explanation actually held.

WHAT STRUCTURED DIAGNOSIS CONTRIBUTES

Structured diagnosis cannot eliminate managerial judgment. It can make the assumptions behind that judgment more explicit.

A performance review asks:

How is this person performing?

A diagnostic inquiry asks:

What condition is governing the result?

Both questions matter. They are not interchangeable. Structured diagnosis helps leadership compare individual performance with broader operating evidence before deciding where accountability should be intensified.

The purpose is not softer accountability. It is more accurately aimed accountability.

WHAT THE SAI BUSINESS CONSTRAINT DIAGNOSTIC CAN REASONABLY CLAIM

The Business Constraint Diagnostic™ is designed to collect structured operating evidence across the Seven Classes of Business Constraint™ and support identification of a probable governing constraint class and the structural condition within that class that appears to be limiting performance.

It does not determine who should be disciplined. It does not prove that an employee's explanation is correct. It does not establish that a particular leader, department, or organizational level is responsible merely because a constraint class has been identified. And it should not be described as independently validated unless and until such validation exists.

Its role is narrower. It organizes evidence so leadership can examine whether the condition governing performance appears to lie primarily in Market, Operational, Financial, Organizational, Strategic, Leadership, or Credibility factors. That finding can inform—but should not replace—judgment about responsibility, authority, corrective action, and accountability.

FIFTY YEARS OF PRACTITIONER OBSERVATION

My concern with this problem comes from operating experience. Across more than fifty years, I have seen capable people held responsible for results materially affected by decisions, structures, resources, and strategies outside their authority. I have also seen the opposite.

I have seen people invoke “the system” when the principal problem was their own execution. Both errors are costly. The first directs pressure toward the wrong person. The second protects poor performance from legitimate accountability.

Diagnosis should not begin by choosing one explanation. It should determine which explanation the evidence supports. My operating experience can support practitioner observations and propositions.

It cannot establish how frequently organizations misdirect accountability, how often such misalignment contributes to turnover, or whether the SAI methodology produces better outcomes than alternative approaches. Those questions require continued examination.

COUNTERARGUMENT: ACCOUNTABILITY IS NECESSARY EVEN IN IMPERFECT SYSTEMS

Yes. No organization provides ideal conditions. Managers cannot suspend accountability whenever employees encounter obstacles. People are routinely expected to perform under constraints.

The relevant question is not whether constraints exist. It is whether the person being held responsible has sufficient authority and influence over the relevant conditions for the accountability to be reasonable. Accountability must accommodate operating reality without becoming an excuse for avoidable underperformance.

COUNTERARGUMENT: EMPLOYEES MAY BLAME THE SYSTEM FOR THEIR OWN FAILURE

They may. Self-serving explanations are possible. An employee's claim that “the system is the problem” should therefore be treated as a hypothesis rather than accepted as fact.

The same standard should apply to management's claim that “the employee is the problem.” Both are diagnostic propositions. Both require evidence. Neither should receive immunity from examination.

COUNTERARGUMENT: BOTH THE PERSON AND THE SYSTEM MAY BE LIMITING PERFORMANCE

Frequently, both matter. A poor system can contain weak performers. A capable system can contain weak performers. A strong employee can operate inside a structural constraint. A weak employee can operate inside that same constraint.

The existence of multiple causes does not eliminate the need for prioritization. It increases it. The question is which condition is most consequential now and what should therefore be addressed first.

COUNTERARGUMENT: NOT EVERY PERFORMANCE PROBLEM REQUIRES A FORMAL DIAGNOSTIC

Correct. Many routine performance issues can be addressed through normal managerial judgment, coaching, feedback, supervision, and measurement.

A formal diagnostic process becomes more valuable when the problem persists despite competent intervention; several explanations remain plausible; responsibility and authority appear misaligned; multiple functions contribute to the result; or repeated personnel changes fail to correct the outcome. Diagnosis should be proportionate to the persistence and complexity of the problem.

LIMITATIONS AND QUESTIONS FOR FURTHER EXAMINATION

This paper advances a practitioner proposition about accountability, authority, structural conditions, and governing constraints. It does not establish that accountability without a formal diagnostic process is inherently punitive. It does not establish that employee perceptions of structural barriers are necessarily accurate.

It does not establish that misdirected accountability is a primary cause of employee turnover. It does not establish that every performance problem originates above the person being evaluated. It does not prove that the SAI Business Constraint Diagnostic™ outperforms established performance-management, organizational-development, or diagnostic methods.

And it does not establish that identifying a governing constraint automatically determines who should be held responsible for resolving it. Further examination should evaluate relationships among perceived controllability, responsibility, organizational justice, employee voice, accountability practices, constraint identification, and performance outcomes.

Research should also examine whether structured diagnostic inquiry changes accountability decisions, reduces repeated intervention failure, or improves alignment between authority and responsibility. Those are empirical questions. They should remain open.

IMPLICATIONS FOR BUSINESS OWNERS AND EXECUTIVES

When performance is weak, the immediate question is often:

Who owns this number?

That is important. It may not be the first question. A stronger sequence is:

What is governing the result?

Who has authority over that condition?

What portion of the performance gap remains within the individual's control?

Where should accountability therefore be directed?

That sequence does not weaken accountability. It makes accountability more defensible.

IMPLICATIONS FOR ADVISORS AND CONSULTANTS

When a client asks for a stronger accountability system, the advisor should understand the presenting concern. But before redesigning performance management, the advisor should examine whether the requested intervention assumes a diagnosis that has not yet been tested.

The question is not merely:

“How can we hold these people more accountable?”

It is:

“What evidence shows that these are the people who control the condition governing the result?”

Sometimes the client's diagnosis will be correct. Sometimes it will need refinement. That distinction can change the entire engagement.

IMPLICATIONS FOR BUSINESS EDUCATION

The accountability problem provides a useful vehicle for teaching diagnostic reasoning. Students can be given a case containing a visible performance gap and asked to distinguish:

facts from interpretations;

responsibility from authority;

performance measurement from causal explanation;

individual execution from structural conditions;

and accountability from diagnosis.

They can then compare competing explanations and identify what evidence would be needed before responsibility is reassigned.

The educational objective is not to teach students that accountability is unfair. It is to teach them that accountability becomes stronger when causation, authority, responsibility, and evidence are examined separately.

CONCLUSION

Accountability is an essential discipline of management. But accountability works best when it is directed toward something the accountable person can materially influence. A performance gap does not establish where the governing cause resides. A metric does not establish causation. A job title does not establish structural control. And ownership of a result does not always equal authority over the conditions producing it.

That is why accountability should follow diagnosis rather than replace it. The sequence remains:

IDENTIFY → PRIORITIZE → RESOLVE → CONFIRM

Identify what is actually limiting performance. Prioritize the condition that deserves attention first. Resolve it at the level where it can actually be changed. Then confirm whether the diagnosis held.

Sometimes the evidence will show that individual execution is the governing problem. When it does, accountability should be direct. Sometimes the evidence will show that the more consequential constraint sits elsewhere. When it does, increasing pressure on the visible performer will not resolve the governing cause.

The objective is not softer accountability. It is not harsher accountability.

It is accountability aimed at conditions the accountable person has sufficient authority and influence to change.

EVIDENCE BOUNDARY

The external literature cited below supports the intellectual context surrounding accountability, goal setting, organizational justice, employee voice, psychological safety, and incentive effects. It should not be interpreted as independent validation of the SAI Business Constraint Discipline™, the Seven Classes of Business Constraint™, the Business Constraint Diagnostic™, or the proposition that every organization has one governing constraint at a time.

REFERENCES

Colquitt, J. A., Conlon, D. E., Wesson, M. J., Porter, C. O. L. H., & Ng, K. Y. (2001). Justice at the millennium: A meta-analytic review of 25 years of organizational justice research. Journal of Applied Psychology, 86(3), 425–445.

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

Kerr, S. (1975). On the folly of rewarding A, while hoping for B. Academy of Management Journal, 18(4), 769–783.

Locke, E. A., & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), 705–717.

Morrison, E. W. (2014). Employee voice and silence. Annual Review of Organizational Psychology and Organizational Behavior, 1, 173–197.

RELATED SAI RESOURCES

The Seven Classes of Business Constraint™
The Governing Constraint Principle
The SAI Business Constraint Discipline™
The Business Constraint Diagnostic™
The Governing Constraint May Not Be What Leadership Thinks It Is
Why Most Improvement Efforts Fail

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™

SAI-CIDR-02 | Version 2.0 | September 2026