When Does a Structural Explanation Become an Excuse?
When Does a Structural Explanation Become an Excuse?
Where the line sits, and why it isn’t a matter of taste
Here is a meeting that happens in most organisations, and goes nowhere in most of them.
A manager has damaged a team. Two people have left, one of them badly, and the exit interviews were unambiguous. The executive group is discussing what to do.
Half the room wants the manager out. The behaviour was unacceptable; people managed the same pressures without behaving that way, and tolerating it tells everyone what the organisation actually permits.
The other half points out that this manager was given an unworkable brief, no authority to fix what was going wrong, and a target that made the pressure inevitable, and that the last person in the role left for the same reasons. Remove the manager, and the next one will be in the same position by spring.
Both accounts are accurate. The conversation goes nowhere, because the room is answering two different questions at once and can’t see that it is.
The objection worth taking seriously
Behind that deadlock sits a criticism that deserves a better answer than it usually gets. It is the strongest objection to explaining organisational behaviour structurally at all.
By a structural explanation I mean one that locates the cause of a behaviour in the conditions rather than in the person: what the architecture rewarded, what it made expensive, who held authority over what.
The objection runs like this. If behaviour is produced by the architecture, and people are responding rationally to what the structure rewards, then nobody is ever answerable for anything. The manager who bullied a team was under pressure. The executive who cut the training budget was reading their incentives. The director who stayed silent was accurately pricing the cost of speaking. Every act of cowardice, self-interest, or cruelty becomes a system output, and the person who committed it stops being the subject of the sentence.
Stated plainly: a theory that explains everyone’s behaviour as rational supplies a defence to everyone, and a defence available to everyone has stopped discriminating between cases.
That is not a strawman. It is a real failure mode, and I have watched people fall into it gratefully.
It has teeth for a second reason too. Responsibility in most organisations already runs in one direction — downward. That is the fault this way of thinking exists to name. But the same explanation can be used to make it run in no direction, which is not obviously an improvement. An executive who has behaved badly can now say the system made it rational. A team that has quietly stopped delivering can say the architecture doesn’t support them. Both may be entirely true. Both are also extremely convenient.
So the question isn’t whether structure shapes behaviour. It plainly does. The question is where the explanation stops, and the excuse starts. And whether there is a principled line, or whether it’s only a matter of taste when to deploy which argument.
There is a line. It has three parts, and it resolves the meeting.
First: architecture prices choice. It does not abolish it.
This is the load-bearing distinction and most of the rest follows from it.
A structure does not make people do things. It makes some things cheap and others expensive. A well-built system makes candour affordable and self-protection costly. A badly built one inverts those prices until honesty requires heroism and silence requires nothing at all.
People still choose. What changes is what the choice costs them.
Which means a structural explanation is not deterministic, and any version of it that sounds deterministic has gone wrong somewhere. When I write that someone is reading their exposure correctly, I am describing a judgement they made, not a reflex they had. The judgement was reasonable. It was still theirs.
That leaves responsibility where it was and relocates the more interesting question. Not why this person did it, but what it cost them to do otherwise, and who set that price.
Second: responsibility scales with authority
If architecture prices choices, the people who set the prices are making decisions of a different order from the people paying them.
A junior employee who stays quiet in a meeting where speaking up is career-limiting has made a small, defensible choice with a real cost attached. An executive who designed the conditions under which speaking up became career-limiting has made a much larger one, usually at no personal cost, and frequently without noticing they were making it at all.
This is why a structural explanation is not a general amnesty. It concentrates responsibility rather than dissolving it. It squarely places it onto the architects, the institution-keepers, the people with the authority to change the incentives and the comfort to leave them alone. The account that most sharply exonerates the person at the bottom implicates the person at the top most severely.
That is not a comfortable position for a structural explanation to occupy, and it is worth noticing that the executives who most readily adopt the vocabulary rarely apply it in that direction.
Third: the test is authority
When someone has no power to change the condition they cite, they are explaining their circumstances. Where they had some, the explanation weakens. Where they could have changed it and did not, it stops being an explanation and becomes an alibi.
A manager who says the system rewarded short-term numbers is describing their circumstances if they had no say over the measurement.
A director who says the culture made it impossible to raise the issue is reporting a fact, if the culture was genuinely beyond their reach.
An organisation that says its incentives drove the behaviour is diagnosing itself, if it intends to change them.
Each of those becomes an alibi the moment the speaker had the authority to change what they are pointing at. The same sentence, from three roles, and what separates them is not sincerity or tone. It is a verifiable fact about who held what.
Which settles the room
The manager is accountable for what they had the authority to do: how they spoke to people, what they chose not to escalate, whether they asked for help. They are not accountable for a brief they could not deliver or a target set elsewhere.
Both halves of the executive group were right about their own half, and wrong to think their answer made the other unnecessary. Remove the manager and change the conditions, or the same meeting happens about their successor within a year.
That second half is the one that gets skipped, and the reason it gets skipped is itself structural. Dismissing someone is visible, immediate, and defensible. Changing decision rights or a measurement system implicates whoever set them, takes longer than a quarter, and produces no announceable result. Given the choice, organisations do the one that can be shown.
What a structural explanation is actually for
It is worth being clear about the purpose, because the purpose sets the limits.
The point of locating behaviour in the architecture is not to determine who deserves blame. It is to identify what would have to change for the behaviour to stop. Those are different questions, and they frequently have different answers.
A manager who mistreats people may deserve consequences and may be responding to conditions that will produce the same behaviour in their successor. Both facts hold at once. Dismissing them answers the first question and leaves the second untouched — which is why organisations that solve problems by removing people so often find the problem regenerating around whoever replaces them.
So a structural explanation does not compete with individual accountability. It answers a different question, and it becomes an excuse only when it is offered as an answer to the first one.
The clearest way to hold both: hold people accountable for what they had the authority to do, and hold the structure accountable for the rest. The line between those is not a philosophical puzzle. It is a matter of fact about decision rights, and any organisation can establish it in an afternoon if it wants to.
The uncomfortable part
One thing deserves stating plainly, because otherwise the argument looks more comfortable than it is.
Structural explanation is a tool, and like any tool it will be picked up by whoever finds it useful. It will be used to evade. Executives will cite incentives they set. Teams will cite conditions they help maintain. The vocabulary will get thinner as it spreads, as vocabularies do.
That is not a reason to abandon it. The alternative – explaining organisational failure by the character of the people in it – has been available for a century, is wrong most of the time, and has its own well-developed uses for evasion, chiefly the removal of individuals in place of changing anything.
But it does mean the argument has to carry its own discipline. Two questions, applied to anyone offering a structural explanation, including oneself:
Could you have changed the thing you are citing? If yes, you are not explaining. You are defending.
Does the account become more demanding the further up it goes? If it exonerates the powerful as readily as the powerless, it is not structural analysis. It is an amnesty with technical vocabulary.
The short answer
A structural explanation becomes an excuse at exactly the point where authority sits.
Below that line it is an explanation, and usually a more accurate and more humane one than the alternative. Above it, it is an alibi, and the people best placed to use it as one are precisely the people it implicates most.