Hanlon's Razor: Assume Incompetence Before Malice

A customer emails your support inbox in all caps, accusing your company of "deliberately" hiding a price increase. The on-call marketer forwards it to legal with a subject line reading "possible lawsuit." Two hours and three escalations later, someone actually reads the ticket: the customer missed a banner notice, got confused by a confirmation email, and just wants a refund.

Quick Summary

• Hanlon's Razor: never attribute to malice what is adequately explained by incompetence, carelessness, or a communication gap.
• The name traces to Robert J. Hanlon, whose one-line submission won a contest for Murphy's Law Book Two in 1980, then spread through programmer culture via the 1990 Jargon File.
• Marketing sees this constantly: a heated customer complaint, a competitor's sudden aggressive move, an internal team that "went around you," all read as attacks until you check.
• Assuming malice first triggers legal escalations, PR overreactions, and burned internal relationships that a five-minute fact-check would have prevented.
• The razor has a limit: it explains honest mistakes, not patterns. Repeated, provable bad-faith behavior is a different problem, and pretending otherwise is its own mistake.

The Principle and Its Origin

Hanlon's Razor states it plainly: never attribute to malice that which is adequately explained by stupidity (or, in gentler modern phrasing, incompetence). The name is a nod to Occam's Razor, the older idea that the simplest explanation is usually the right one.

Robert J. Hanlon of Scranton, Pennsylvania submitted the line as a contest entry for a 1980 sequel to the Murphy's Law joke-book series. It got picked up in the 1990 Jargon File, a glossary of programmer slang, where engineers used it to remind each other that most bugs are honest mistakes, not sabotage. A near-identical idea shows up even earlier, in Robert A. Heinlein's 1941 novella Logic of Empire, where a character debunks the "devil theory" by pointing out that people mistake stupidity for villainy constantly.

The mechanism behind it is simple. Malice requires someone to plan, coordinate, and choose to harm you. Incompetence just requires someone to be tired, rushed, or missing information, which describes most people on most days.

That is the whole test: which explanation requires fewer assumptions to be true.

A Marketing Scenario Where Assuming Malice Backfired

Picture a mid-size SaaS company. A customer posts a furious public thread claiming the company "buried" a feature deprecation to force an upgrade.

The marketing lead's first instinct is defensive: this looks coordinated, maybe even planted by a competitor. She loops in legal, drafts a firmly-worded public statement, and prepares to name the customer's account status publicly to "set the record straight."

Nobody checked the actual changelog first. It turns out the deprecation notice went out in a product email with a subject line about "performance improvements," which the support team itself had flagged as confusing two weeks earlier and nobody had escalated. The customer was not attacking the company, they were confused, like several other people quietly were.

This pattern repeats in three places inside marketing teams. A competitor drops prices right after your launch, and it reads as a coordinated strike, when a quarterly pricing review scheduled months earlier is the far more common cause. An internal team ships a campaign without looping in your channel, and it reads as being cut out, when the more common cause is a missed CC or an unclear RACI chart. A customer complaint reads as bad faith, when most public complaints are simply escalations from a support process that already failed once, not a customer looking for a fight.

Checking the boring explanation first costs minutes. Skipping straight to "they're out to get us" costs a legal escalation, a defensive public statement, or a damaged relationship with a team you still have to work with next quarter.

When the Razor Should Not Apply

Hanlon's Razor is a starting assumption, not a permanent blindfold. It explains a single confusing event. It does not explain a pattern.

If a competitor has undercut your pricing the same week as your last three launches, that is no longer "adequately explained" by coincidence, that is a signal worth investigating properly. If one internal stakeholder has repeatedly excluded your team from decisions after being asked directly to loop you in, incompetence stops being the simpler explanation once it happens on purpose, three times, after a direct request.

The razor is a filter for your first reaction, not a rule that forbids ever concluding bad faith exists. Genuine bad actors, saboteurs, and competitors who do coordinate exist, and treating every red flag as innocent confusion is its own kind of naivety.

The goal is proportional response. Start with the boring explanation, verify quickly, and only reach for the malice conclusion once the pattern actually earns it.

Key Takeaways

• Hanlon's Razor: never attribute to malice what incompetence, carelessness, or miscommunication already explains, a 1980 contest entry that spread through 1990s programmer culture and now applies well beyond code.
• Marketing's highest-risk moments for this bias are angry customer complaints, sudden competitor moves, and cross-team friction, all of which feel personal in the moment they happen.
• A five-minute fact-check (read the actual email, check the actual timeline) is cheaper than the legal escalation or PR statement that assuming malice triggers.
• The razor is a first assumption, not a permanent one. Repeated, direct-warning-ignoring behavior earns a real bad-faith investigation.
• Match your response to the evidence: one confusing incident gets a quiet fix, a proven pattern gets escalated for real.