Named for Robert J. Hanlon (a submission to Murphy's Law Book Two, 1980), with an earlier form in Robert A. Heinlein (Logic of Empire, 1941).
Sets a default of reading harmful behavior as error, overload, or circumstance until evidence shows intent, which matches the response to the likely cause.
Eight irritations from one colleague in a quarter-end close, sorted by their most likely cause
Select an incident to read the facts, then the cause that best explains them; the box says what response fits. The razor's rule: try overload, an unclear ask, and missing information first, and choose intent only when those no longer fit the facts. The first incident is placed as an example. Show the sort to compare yours. Illustrative.
Items (select one, then a box)
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Not placedPlacedOverloadUnclearUnawareIntent
Incidents
This quarter
Overload
Unclear
Unaware
Intent
OverloadUnclearUnawareIntent
Most likely cause
Forecast late twice. He has covered two jobs since his counterpart resigned in May.Not placed yet.Forecast late twice. He has covered two jobs since his counterpart resigned in May.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Late work from someone carrying two roles is load, and help fixes it.Forecast late twice. He has covered two jobs since his counterpart resigned in May.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.Forecast late twice. He has covered two jobs since his counterpart resigned in May.Unaware: Missing information: tell them the rule and where it lives, once, without blame.Forecast late twice. He has covered two jobs since his counterpart resigned in May.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Sent last month's file. The request said to send the latest file, and the shared drive holds two files named Latest.Not placed yet.Sent last month's file. The request said to send the latest file, and the shared drive holds two files named Latest.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Sent last month's file. The request said to send the latest file, and the shared drive holds two files named Latest.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.The ask could be read two ways, and he read it the other way.Sent last month's file. The request said to send the latest file, and the shared drive holds two files named Latest.Unaware: Missing information: tell them the rule and where it lives, once, without blame.Sent last month's file. The request said to send the latest file, and the shared drive holds two files named Latest.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Old discount rule used. The rule changed in a memo to the pricing team, and he is not on that list.Not placed yet.Old discount rule used. The rule changed in a memo to the pricing team, and he is not on that list.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Old discount rule used. The rule changed in a memo to the pricing team, and he is not on that list.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.Old discount rule used. The rule changed in a memo to the pricing team, and he is not on that list.Unaware: Missing information: tell them the rule and where it lives, once, without blame.Nobody told him the rule changed.Old discount rule used. The rule changed in a memo to the pricing team, and he is not on that list.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Disputed your numbers. The third time this quarter, each time after being shown they were right, each time copying the vice president.Not placed yet.Disputed your numbers. The third time this quarter, each time after being shown they were right, each time copying the vice president.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Disputed your numbers. The third time this quarter, each time after being shown they were right, each time copying the vice president.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.Disputed your numbers. The third time this quarter, each time after being shown they were right, each time copying the vice president.Unaware: Missing information: tell them the rule and where it lives, once, without blame.Disputed your numbers. The third time this quarter, each time after being shown they were right, each time copying the vice president.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Repeated after correction, with an audience each time: overload, wires, and ignorance no longer fit.One-word reply to a plan. One word, sent at 11 at night, in the last two days of the close.Not placed yet.One-word reply to a plan. One word, sent at 11 at night, in the last two days of the close.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.A curt reply at the peak of the close is fatigue; raise the proposal again next week.One-word reply to a plan. One word, sent at 11 at night, in the last two days of the close.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.One-word reply to a plan. One word, sent at 11 at night, in the last two days of the close.Unaware: Missing information: tell them the rule and where it lives, once, without blame.One-word reply to a plan. One word, sent at 11 at night, in the last two days of the close.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Took your booked room. Your hold was marked tentative, so the calendar showed the room as free.Not placed yet.Took your booked room. Your hold was marked tentative, so the calendar showed the room as free.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Took your booked room. Your hold was marked tentative, so the calendar showed the room as free.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.The booking system said the room was open.Took your booked room. Your hold was marked tentative, so the calendar showed the room as free.Unaware: Missing information: tell them the rule and where it lives, once, without blame.Took your booked room. Your hold was marked tentative, so the calendar showed the room as free.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Missed the new cutoff. The cutoff moved to Friday in an email sent the week he was on leave.Not placed yet.Missed the new cutoff. The cutoff moved to Friday in an email sent the week he was on leave.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Missed the new cutoff. The cutoff moved to Friday in an email sent the week he was on leave.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.Missed the new cutoff. The cutoff moved to Friday in an email sent the week he was on leave.Unaware: Missing information: tell them the rule and where it lives, once, without blame.He never saw the change.Missed the new cutoff. The cutoff moved to Friday in an email sent the week he was on leave.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.Edited your signed slide. He changed the figures after sign-off again, a week after agreeing to stop.Not placed yet.Edited your signed slide. He changed the figures after sign-off again, a week after agreeing to stop.Overload: Too much on the plate: help clear it or move the deadline, and leave motive out of it.Edited your signed slide. He changed the figures after sign-off again, a week after agreeing to stop.Unclear: The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.Edited your signed slide. He changed the figures after sign-off again, a week after agreeing to stop.Unaware: Missing information: tell them the rule and where it lives, once, without blame.Edited your signed slide. He changed the figures after sign-off again, a week after agreeing to stop.Intent: A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.He agreed to stop and did it again: this one survives the razor.
Your sort matched 0 of 8.Your sort matched 1 of 8.Your sort matched 2 of 8.Your sort matched 3 of 8.Your sort matched 4 of 8.Your sort matched 5 of 8.Your sort matched 6 of 8.Your sort matched 7 of 8.Your sort matched 8 of 8.
Overload
Too much on the plate: help clear it or move the deadline, and leave motive out of it.
Unclear
The ask or the system could be read two ways: fix the instruction or the process, and confirm in writing.
Unaware
Missing information: tell them the rule and where it lives, once, without blame.
Intent
A pattern the other causes no longer explain: write down each instance, raise it directly, then escalate with the record.
The sort
Forecast late twice: Overload. Late work from someone carrying two roles is load, and help fixes it.
Sent last month's file: Unclear. The ask could be read two ways, and he read it the other way.
Old discount rule used: Unaware. Nobody told him the rule changed.
Disputed your numbers: Intent. Repeated after correction, with an audience each time: overload, wires, and ignorance no longer fit.
One-word reply to a plan: Overload. A curt reply at the peak of the close is fatigue; raise the proposal again next week.
Took your booked room: Unclear. The booking system said the room was open.
Missed the new cutoff: Unaware. He never saw the change.
Edited your signed slide: Intent. He agreed to stop and did it again: this one survives the razor.
An example
In the last week of the quarter's close, a finance manager had a list of grievances against the sales operations lead: two late forecasts, last month's file sent, the old discount rule applied, a missed cutoff, a one-word reply to her proposal, her booked room taken, her numbers called wrong in front of the vice president, and her signed slide edited. She drafted a complaint to his director.
First she asked what else could explain each item. He had been covering two jobs since May. The shared drive held two files named Latest. The discount memo had gone to a list he was not on, and the cutoff change had arrived the week he was on leave. Six of the eight had a plain explanation.
Two did not. He had called her numbers wrong three times after being shown they were right, and had edited her slide again after agreeing to stop. She dropped the complaint, fixed the file names and the memo list, and raised the two remaining incidents with him directly, with dates.
Why it works
When something goes wrong at someone else's hands, the mind reaches for intent, because a hostile motive makes a tidy story and puts the fault entirely on them. In most workplaces, though, error, overload, unclear instructions, and missing information are far more common than malice, so intent is usually the least likely explanation. Starting from it misreads the odds.
The razor corrects the starting point and so changes the response. Overload calls for help, a muddled instruction for a clearer one, a gap in information for telling someone. Treating any of these as hostility damages the relationship and leaves the cause in place. The razor does not rule malice out: a pattern that persists after the other explanations have been addressed is evidence, and it earns a firmer response.
The thinking behind it
Robert J. Hanlon Robert J. Hanlon is the name attached to the adage that warns against blaming malice for anything stupidity explains well enough. It appeared under the title Hanlon's razor in Murphy's Law Book Two: More Reasons Why Things Go Wrong! (1980), a collection edited by Arthur Bloch. Who Hanlon was is uncertain, and the thought itself is older, as the next paragraph shows. In working use, stupidity is read broadly, to cover error, overload, and confusion.
Robert A. Heinlein Robert A. Heinlein, a leading American science fiction writer, put an early form of the idea in his novella Logic of Empire (1941), published in Astounding Science Fiction. A character there warns against blaming villainy for conditions that come from stupidity. The line is a precursor; the adage's name comes from the 1980 collection. Heinlein's version is the older of the two by almost forty years, which is why both are credited here.
How to run it
Pause before naming a motive. When something feels like deliberate harm, hold the reply until you have listed the alternatives.
List the ordinary causes. Consider overload, an instruction that could be read two ways, missing information, and a broken process.
Check each against the facts. Ask what you would expect to see if each were true, and look for it: workload, the original request, who was on the memo.
Respond to the likeliest cause. Offer help, clarify the ask, share the information, or fix the process, whichever fits.
Keep a dated record. Note what happened and when, so a pattern can show itself over time.
Reserve intent for what survives. When the same act repeats after the ordinary causes are fixed, treat it as deliberate and say so directly.
Escalate with evidence. If the direct conversation fails, take the dated record to the person's manager.
Where it goes wrong
The razor becomes an excuse. A manager explains away a colleague's repeated undermining as busyness for a year, and the damage grows; spot it when the same act recurs after the supposed cause was fixed. Keep the record, and let a persisting pattern count as evidence.
The charity runs one way. People apply the razor to peers they like and skip it for those they distrust. Run the same check on everyone, and notice which incidents you skipped it on.
The cause gets diagnosed and nothing changes. Concluding that the file names were confusing does no good unless someone renames the files. Each ordinary cause found should end in a fix to the instruction, the process, or the workload.
When to use something else
Occam's Razor. When the question is which of several explanations needs the fewest assumptions, with no motive in play.
Difficult Conversations. When the incident is already understood and the hard part is raising it with the person.
Differential Diagnosis. When a problem has several possible causes and each needs a test to rule it in or out.