Learn it → Apply it → Save as Skill
Never assume malice when carelessness, pressure, or a broken process explains the outcome just as well. Most people are not plotting against you. They are tired, rushed, underinformed, or working inside a system that quietly makes mistakes likely.
The Dr. Wallace's Favorite Mental Models is designed to turn useful ways of thinking into reusable tools. Each model gives you a fast visual overview, deeper interactive learning, practical application exercises and an AI-ready Markdown skill you can save for future use.
Instead of merely reading about mental models, you can gradually build your own AI skills library: a collection of portable reasoning skills that can help ChatGPT, Claude, Grok and other AI assistants apply the mental models you value.
When someone's action costs you something, it is tempting to explain it by their character: they are careless, they are out to get you, they don't respect you. Most of the time, a much plainer explanation fits just as well: they were overloaded, they misread the instructions, or the process itself was built to fail this way.
Work down the list in order. Malice is the last rung, not the first guess.
The model is most useful whenever a bad outcome, a curt email, a missed deadline, or a broken promise tempts you to assume the other person meant it.
The check takes seconds, but skipping it is exactly how one assumption quietly starts a conflict that didn't need to happen.
Catch the moment you label someone's action as deliberate, spiteful, or aimed at you personally.
Ask what a rushed, distracted, underinformed, or overloaded person might have done by accident.
Check the mundane explanations: a missed message, a broken process, different instructions, a bad day.
Only treat it as malice if the evidence still points that way after the ordinary explanations are ruled out.
Open a use case to see what changes once you separate what an action looks like from what actually explains it.
The instinct is to read lateness as disrespect for your time. Before that conversation, check whether the delay traces to an unclear handoff, a dependency that broke upstream, or an unrealistic deadline nobody flagged. Address the process failure directly, and only raise it as a conduct issue if the pattern holds after that.
A billing error or a confusing checkout flow produces the same angry email as an actual scam would. Investigate the charge and the flow before assuming the customer is being unreasonable, and before assuming your own team did anything intentional either.
Being excluded feels political. It is also exactly what happens when someone replies-all in a hurry, uses an old distribution list, or assumes you were already looped in by someone else. Ask before you assume you were cut out on purpose.
Text and email strip out tone. A short reply typed between meetings on a phone reads very differently from how it was meant. Consider the format and the sender's likely context before reading coldness into it.
Repeated cancellations can mean someone is pulling away, but they can also mean someone is overwhelmed and too embarrassed to say so clearly. Ask directly what is going on before deciding the friendship is the problem.
The instinct is to look for who to blame. Most outages trace to a missed edge case, an untested interaction, or a process that let a risky change ship without review, not to sabotage. Fix the process gap first; look for intent only if the evidence actually leads there.
This is an illustrative example designed to teach the method; the team and its figures are invented for teaching purposes.
Expand for where the name comes from and how it differs from nearby ideas.
The phrase "Never attribute to malice that which is adequately explained by stupidity" first appeared in print in Arthur Bloch's 1980 anthology "Murphy's Law Book Two: More Reasons Why Things Go Wrong." Bloch credited it to a contributor named Robert J. Hanlon of Scranton, Pennsylvania, who submitted it for a book collecting reader-written corollaries to Murphy's Law.
Yes, by centuries. In an often-quoted 1774 letter, Johann Wolfgang von Goethe wrote a line usually translated along the lines of: misunderstanding and neglect create more confusion in the world than deceit and malice do, and the latter two are actually much rarer. Science-fiction writer Robert Heinlein's 1941 short story "Logic of Empire" includes a similar line: "You have attributed conditions to villainy that simply result from stupidity." Hanlon's contribution was naming a pattern people kept independently rediscovering.
Related, but not the same thing. The fundamental attribution error, studied by researchers including Lee Ross, and demonstrated in classic studies such as Jones and Harris's 1967 experiment, is a well-documented pattern in which people systematically over-explain others' behavior by their character or intent and under-weight the situation they were in. Hanlon's Razor is a folk heuristic, not a scientific finding, but it functions as a practical corrective aimed at exactly that documented bias.
No. Many modern versions swap in gentler words such as carelessness, incompetence, neglect, or pressure, partly because bad outcomes so often trace to overload and unclear systems rather than low ability. The content of the razor, look for error before you look for evil, does not depend on which word carries it.
Ruling out malice for one incident does not mean ignoring a pattern. Three "innocent mistakes" in a row from the same person is itself information worth acting on.
The razor should not be a courtesy you extend to people you already like and withhold from people you already distrust. Apply the same check both ways.
The razor lowers your starting assumption. It does not settle the question on its own. Keep checking the actual evidence.
This model is for interpreting other people's actions, not for waving away your own carelessness after the fact.
Some situations carry real, well-evidenced hostility. The razor is a starting prior, not a blindfold against clear evidence.
Naming incompetence or a broken process as the cause does not mean the outcome is acceptable or should go unaddressed.
a clear, repeated, targeted pattern exists and the ordinary explanations have already been checked and ruled out more than once.
the potential harm is severe, safety, abuse, fraud, since a charitable assumption held too long can itself cause damage. Investigate promptly rather than delaying accountability.
someone has already demonstrated a pattern of deliberate behavior. Do not re-extend the benefit of the doubt indefinitely.
This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.
Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to apply Hanlon's Razor, what questions to ask, what evidence to seek, what mistakes to avoid, and how to structure its analysis.
Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions, or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.
No. It means malice should not be your default explanation for a bad outcome. Genuine malice exists and sometimes is the correct explanation, but it should be reached after checking the more common explanations, not assumed first.
Yes, informally sometimes called Hanlon's Razor for systems: a bad outcome from an organization is more often explained by misaligned incentives, unclear ownership, or a broken process than by a coordinated plan. The same check-the-mundane-explanation-first habit applies at the team or company level.
Assuming good faith is a broad stance toward someone's intentions in general. Hanlon's Razor is narrower: it is specifically about which explanation, error or malice, best accounts for one bad outcome. You can apply the razor to a single incident without adopting a blanket assumption of good intentions in every area of the relationship.
Assuming malice tends to increase conflict, defensiveness, and retaliation, and it spends energy defending against a threat that was never real. Checking for the ordinary explanation first usually resolves the situation faster and preserves the relationship or working process either way.