Why The Backbone Method™ Treats the Company as a Decision System

The Backbone Method™ treats companies mechanically because explanations about people are exceptionally easy to produce and considerably harder to establish, not because people do not matter.
 

A founder is controlling. Management lacks courage. The organization avoids conflict. The leadership team does not trust one another. Employees resist change. The culture has become political.
 

Any of these interpretations may be accurate, but none should be necessary for establishing whether the company contains a structural condition.
 

The diagnostic question is narrower:
 

Who held authority over the decision?
What required consent?
Could that authority actually be exercised?
Which rule governed the situation?
Was the rule applied consistently?
Where did responsibility for the outcome sit?
Could the decision reach closure?
What changed when the decision was contested?
What commitments had already been made by the time uncertainty became visible?

​

Instead of asking whether a leader was decisive enough, the examination can establish whether the leader possessed sufficient authority to close the decision.
 

Instead of concluding that a team has an accountability problem, it can examine whether responsibility for an outcome corresponds with authority over the decisions producing it.

Instead of describing a culture as inconsistent, it can examine whether established rules remain binding when following them becomes inconvenient.
 

Instead of attributing repeated reconsideration to indecision, it can examine whether the organization has a reliable mechanism by which decisions become final.
 

The purpose is to remove unsupported judgments about people from the diagnostic conclusion, because structural analysis should not require a theory about somebody's personality, motives or competence to explain what the company can and cannot do.

Why Structural Conditions Need to Be Codified

Terms such as authority, accountability and decision-making are easy to use loosely. Used loosely, they have little diagnostic value.
 

A slow decision does not establish a Decision Velocity condition. An exception does not establish a failure of Operational Rule Integrity. Disagreement does not establish an Authority condition. A poor outcome does not establish an Accountability condition. A significant investment does not establish a Capital Commitment condition.
 

The Backbone Method™ codifies Structural Conditions so that the same distinction can be made repeatedly between an event and a pattern, between an interpretation and an observable mechanism, and between something that happened inside a company and something the company is structurally capable of reproducing.
 

Once a condition can be named precisely, evidence can be examined against it. Different manifestations can be recognized as expressions of the same underlying mechanism, while superficially similar situations can be kept separate when their mechanisms differ.
 

The objective is not to produce more terminology around organizational behaviour, but to reduce the amount of interpretation required to establish what is happening.

The Diagnostic Protects Individuals by
Examining the Mechanism

Organizational failure is remarkably easy to personalize.
 

When outcomes deteriorate, explanations accumulate around the people closest to them. Someone should have acted earlier. Someone failed to take ownership. Someone did not communicate clearly enough. Someone lacked commercial judgment. Someone should have challenged the decision.

Those conclusions can be made while leaving the decision conditions themselves untouched.
 

If responsibility was assigned without sufficient authority, replacing the person does not resolve the condition. If decisions can be reopened indefinitely, demanding greater decisiveness does not create closure. If informal veto power overrides formal authority, changing the organization chart does not necessarily change who can decide. If critical operating rules depend on individual memory, appointing a new executive does not transfer the logic that made previous decisions coherent.
 

A structural diagnostic therefore creates an important boundary around attribution.
 

It asks what the person could actually decide, what information and authority were available, which constraints were binding and what the organization permitted at the time.