Blame the Algorithm

Tactics of Organizational PoliticsInformation and NarrativeA tactic to guard againstAlso known as Algorithmic Authority

Routing a controversial decision, such as resource allocation, through a model or AI system lets leadership present the outcome as objective, so no executive has to defend it.

An example

Reporter headcount at a digital news publisher was now allocated across desks by an "audience value model" built by a vendor. Its first run cut the regional desk from twelve reporters to seven and grew the lifestyle desk by four. The regional editor asked who had decided that. The chief product officer answered that nobody had; the model optimized for audience value. When the editor asked what audience value meant, she was told the weights were the vendor's intellectual property. Her desk's investigative work, which brought in subscribers slowly and kept them for years, scored poorly on thirty-day engagement. Two months later a data scientist on the product team, uneasy about it, showed her the configuration file. Leadership had chosen thirty-day page views as the objective and had left subscriber retention out of the inputs. The cuts had been made before anyone outside the product team saw that file.

Why it works

Accepting the output is easy: there is no named author to confront and no decision narrative to contest, and the halo of objectivity makes the verdict feel settled. Challenging it is costly, because the challenger has to learn enough to critique a system they cannot audit, risk looking anti-data in a culture that prizes rigor, or name executives as the real decision-makers. Audiences without the statistical literacy to audit the model are the most exposed, especially in organizations that built their credibility on being data-driven, where weights and training data are protected as vendor or trade secrets and nobody inside reveals how leadership chose the objective and the inputs.

The thinking behind it

Niccolò Machiavelli The Prince (1532) advises rulers to leave affairs of reproach to the management of others and keep acts of grace in their own hands, as Cesare Borgia did with a harsh deputy he later had executed. A model can play the deputy's part: the cuts belong to the system, and the executives keep their hands clean. The defense is to find the human choices behind the model, its objective and inputs, and attach names to them.

Robert B. Cialdini Cialdini's Influence (1984) describes the tendency to defer to those who appear to hold legitimate expertise or position. An algorithm presented as data-driven borrows that authority, so its outputs are questioned less than the same decision announced by a named executive. Showing how the outputs change when leadership's choices change returns the borrowed authority to the people who made those choices.

Warning signs

Every challenge to an allocation is answered with the model's output. No named executive defends what the model was told to optimize. The weights and inputs are confidential, often as vendor property. Questions get reframed from whether a criterion is right to whether the math is right. Controversial outcomes, such as cuts, rejections, or rankings, arrive with the explanation that the system computed them, and critics are described as against data.

How to defend yourself

Fighting the outputs means fighting on the system's ground. Look upstream for the human choices.

  • Ask who chose the objective, the input features, the training data, and the thresholds. Each one is a leadership decision.
  • Ask for a named human owner for each criterion, and for that person to defend it.
  • Find a credible technical reviewer, inside or outside, who can show how the outputs change when those choices change.
  • Ask that an auditor or the compliance function be given access to the design choices.

Once the human choices are visible and open to challenge, the claim of objectivity falls away.

How a leader shuts it down

Every objective, input, and threshold in a model used for consequential decisions needs a named owner and a written rationale. Make those choices reviewable by the people they affect, and keep a sign-off chain for high-impact automated decisions. Avoid buying models whose criteria you cannot disclose to your own staff. When the model decides something contested, answer for the decision yourself.

Back to the catalog