The Blame Machine

On Monday morning, the elevator in the Ministry stalled between floors.

It wasn’t dramatic at first. The lights stayed on. The air stayed cool. Three people stood inside with the polite silence of strangers who had agreed, without speaking, to pretend this was normal: a junior policy adviser named Elena, a communications director named Mark, and a minister named Karras who had learned to make calm look effortless.

Then Elena’s phone buzzed.

A headline, already spreading: “Funding Cuts Trigger Service Breakdown.”

The minister didn’t reach for his phone. He didn’t have to. Mark, whose job was to feel the public mood like weather, exhaled softly as if he had just tasted something bitter.

“Elena,” Karras said, “what happened?”

It sounded like a request for information. Elena recognized it for what it really was: the opening move in a familiar ritual. When something goes wrong, the first question is rarely what went wrong. The first question is where can we safely place the weight.

Elena swallowed. “The cuts went through last quarter. The procurement backlog grew. Staffing stayed frozen. The system — ”

Karras nodded at the word system the way people nod at a cushion being placed under a heavy object. “So,” he said, “implementation.”

Mark’s eyes brightened, almost imperceptibly. He had just heard a usable sentence forming: implementation failures in the bureaucracy. A phrase with a remarkable quality: it could be true and still protect the people who needed protecting.

“Elena,” Mark said, “we need a framing in fifteen minutes. The press is asking if the Minister takes responsibility.”

The elevator did not move. The building was doing an unintentional metaphor and no one laughed.

Karras looked up at the ceiling panel as if answers lived behind it. “I take responsibility,” he said, “for ensuring the system learns. But we can’t allow a few administrative missteps to undermine the reforms.”

Elena felt the small, sick relief in her own chest — relief that the blame was already leaving the room. It moved like water, finding the lowest point. Somewhere below them, in an office that did not have press cameras, it would pool around a department head with an unlucky job title.

She caught herself. Relief is cheap, she thought. And it always costs something later.

Mark, meanwhile, had begun to assemble the statement in his head. He could almost see it on paper:

• Emphasize good intentions.
• Use the language of modernization.
• Isolate the failure as technical.
• Promise accountability without naming anyone who matters.

He wasn’t cynical. He would have rejected that label. He was practical. There was a difference, he believed, and the difference was what allowed him to sleep.

“You’ll say,” Mark began, “that these were necessary efficiency measures, that the goals are sound, and that the disruption is due to unforeseen operational challenges.”

Karras nodded. “Yes. And we’ll commission an independent review.”

Elena stared at him. “A review of what, Minister?”

“Of procedures,” Karras said, gently. “Of implementation.”

A review could be many things. Elena knew the architecture: a committee with a broad mandate, a narrow appetite, and an end date far enough away to let the news cycle die. A review was a way of making action look like change. It moved responsibility forward in time, where it could evaporate.

The elevator shuddered. Somewhere, a motor sighed. It remained stuck.

Elena heard her own voice before she had fully decided to speak. “May I ask a question?”

Mark’s face tightened in the careful way of someone trained to recognize danger without calling it danger.

Karras gestured. “Please.”

Elena took a breath, and with it came an odd sensation: the discomfort of complexity. She had spent years trying to avoid that discomfort. Everyone did. Complexity was expensive. It demanded time, data, and the willingness to admit you might not like what you find.

“We keep asking,” Elena said, “who can be punished. Who can be blamed. But if we keep doing that, the same thing will happen again. Because the conditions will still be there.”

Mark opened his mouth. Elena continued before he could stop her.

“What made this outcome likely?” she asked. “Which incentives pushed people to delay? Which reporting rules hid the backlog? Which staffing constraints turned minor failures into collapse? And who benefits when we pretend the problem is one person’s mistake instead of a predictable result of how we set things up?”

For a moment, there was only the hum of the ventilation fan. The elevator waited, indifferent.

Karras looked at Elena with an expression that was not anger, exactly. It was calculation. Ministers were not selected for their love of unvarnished questions.

“You’re suggesting,” he said slowly, “that we focus less on fault and more on conditions.”

“I’m suggesting,” Elena said, “that blame is not only an emotion. It’s a tool. It rearranges responsibility. It protects some actors and exposes others. And it narrows what we’re allowed to discuss.”

Mark gave a short laugh that wasn’t amusement. “Elena, people are angry. They want a name. If we don’t give them one, they’ll invent worse.”

“That’s the trap,” Elena said. “We treat outrage like a demand for punishment. But what people really want is confidence that it won’t happen again. Punishment is emotionally satisfying. Change is harder.”

“Change,” Mark repeated, as if testing the word for taste, “requires admitting we set up something that failed.”

“Yes,” Elena said. “And that’s why we avoid it. Because responsibility threatens our self-image. It’s cognitively expensive. And” — she looked at Mark — “blame signals loyalty.”

Mark went still. Elena had named something people prefer to leave unspoken: that in institutions, blaming the right target is a form of belonging. You prove you’re on the team not by asking better questions but by sharing the same enemies.

Karras glanced at his watch. “This is all very interesting,” he said, in the voice of someone closing a door. “But we have a press conference.”

Elena felt the familiar gravity return. The ritual would proceed. Someone would be offered to the public as proof of accountability. A phrase would be chosen that made the outcome sound inevitable. Alternatives would disappear from the official story like they had never existed.

But she also felt something else: a thin thread of resolve.

She said, “Minister, may I offer a framework? A field guide, almost. For how we respond when things go wrong.”

Mark’s eyes narrowed. “Now?”

“Now,” Elena said. “Because if we don’t build new habits in the moment of crisis, we never will.”

Karras raised an eyebrow. The elevator’s silence gave them a strange privacy.

Elena held up one finger. “First: Who are we naming, and who are we implying? If we talk about ‘the system’ and ‘procedures’ without naming the decision-makers, we’re shifting responsibility, not explaining it.”

A second finger. “Second: Active or passive language. ‘We cut funding’ versus ‘funding levels were adjusted.’ Passive voice is not just style — it’s a way of removing hands from the act.”

A third. “Third: Individualized or structural explanations. If we sacrifice a scapegoat, we protect the deeper pattern that produced the failure.”

A fourth. “Fourth: alternatives. If the story makes the outcome sound inevitable, ask what choices are missing from the story. The absence of alternatives is its own construction.”

Mark stared at her as if she had just described his job too accurately.

Karras said nothing for a long moment. Then he nodded once, reluctantly, as if acknowledging an uncomfortable truth.

“You’re not wrong,” he said. “But you’re not accounting for politics.”

Elena’s voice softened. “I am. That’s why I’m calling blame a social technology. It governs events. It protects power. It’s political precisely because it feels personal.”

The elevator jolted again and, with a sudden sigh, began to descend.

Mark’s phone buzzed again. More headlines. More anger. The world, impatient, wanted a villain.

Karras straightened his tie. His calm returned like a mask sliding back into place. “We will do the press conference,” he said. “And we will conduct the review.”

Elena watched the floor numbers tick downward. She knew what would happen. The statement would be smooth. The accountability would be ceremonial. The system would return, quietly, to business as usual.

Unless, she thought, someone refused to let the story end there.

As the elevator doors opened to the lobby, the minister stepped out first. Mark followed, already composing sentences that would sound responsible without becoming vulnerable.

Elena lingered half a second behind them.

She felt the old temptation rising — the temptation to blame. Not the bureaucracy, not the market, not the parents these days. But them. The people above her, the people with microphones.

It would feel good. It would be cheap. It would offer that quick relief.

Instead, she did something harder.

She asked herself: What made this outcome plausible?

And in that question, she felt the beginning of a different year — one in which she would no longer settle for villains when the real story was a system.

Outside, the cameras were already setting up. The minister approached the podium.

Someone in the crowd shouted, “Whose fault is this?”

Karras smiled, the practiced smile of a man who knew how to survive.

Elena listened — not for the answer, but for the strategy behind it.

Because once you learn to see blame avoidance, you start seeing it everywhere.

[embed]Thinking Otherwise: Blame, Power, and the Politics of Problematization Thinking Otherwise: Blame, Power, and the Politics of Problematization [Michaelides, Andreas] on Amazon.com. FREE…amzn.to