MLMillionaire LessonIdeas for builders
Uncategorized11 min readUpdated Sep 27, 2026

Mistakes Were Made (But Not by Me) by Carol Tavris & Elliot Aronson is most useful when read as a book about cognitive dissonance and self-justification as forces that protect identity after bad decisions. The value is not in memorizing slogans. It is in recognizing the underlying mechanism, deciding when it applies, and knowing when the same idea becomes misleading.

Bottom line: The strongest lesson from Mistakes Were Made (But Not by Me) is that better outcomes usually come from changing the structure of attention, incentives, information, or interaction—not from relying on motivation alone.

The central problem

The book’s practical question can be stated simply: what makes people behave differently even when the visible facts look similar? In Mistakes Were Made (But Not by Me), the answer centers on cognitive dissonance, self-justification, and confirmation bias. Those ideas matter because they shift attention away from personality stories and toward the conditions surrounding a choice.

That distinction is especially valuable for readers interested in psychology. A weak reading says, “use this trick.” A stronger reading asks which constraints are active, what the other person is optimizing for, what information is missing, and what second-order effects the intervention may create.

How the mechanism works

1. Cognitive Dissonance

Within Mistakes Were Made (But Not by Me), cognitive dissonance is best understood as part of a system rather than an isolated tactic. It interacts with accountability and self-justification. In practice, that means the same behavior can help in one setting and fail in another because the incentives, relationship, timing, or information environment changed.

A useful test is to ask what observable behavior would be different if cognitive dissonance were actually driving the situation. That turns an abstract idea into a hypothesis. You can then look for evidence, compare alternatives, and avoid explaining every outcome after the fact.

2. Self-Justification

Within Mistakes Were Made (But Not by Me), self-justification is best understood as part of a system rather than an isolated tactic. It interacts with cognitive dissonance and confirmation bias. In practice, that means the same behavior can help in one setting and fail in another because the incentives, relationship, timing, or information environment changed.

A useful test is to ask what observable behavior would be different if self-justification were actually driving the situation. That turns an abstract idea into a hypothesis. You can then look for evidence, compare alternatives, and avoid explaining every outcome after the fact.

3. Confirmation Bias

Within Mistakes Were Made (But Not by Me), confirmation bias is best understood as part of a system rather than an isolated tactic. It interacts with self-justification and memory reconstruction. In practice, that means the same behavior can help in one setting and fail in another because the incentives, relationship, timing, or information environment changed.

A useful test is to ask what observable behavior would be different if confirmation bias were actually driving the situation. That turns an abstract idea into a hypothesis. You can then look for evidence, compare alternatives, and avoid explaining every outcome after the fact.

4. Memory Reconstruction

Within Mistakes Were Made (But Not by Me), memory reconstruction is best understood as part of a system rather than an isolated tactic. It interacts with confirmation bias and escalation of commitment. In practice, that means the same behavior can help in one setting and fail in another because the incentives, relationship, timing, or information environment changed.

A useful test is to ask what observable behavior would be different if memory reconstruction were actually driving the situation. That turns an abstract idea into a hypothesis. You can then look for evidence, compare alternatives, and avoid explaining every outcome after the fact.

5. Escalation Of Commitment

Within Mistakes Were Made (But Not by Me), escalation of commitment is best understood as part of a system rather than an isolated tactic. It interacts with memory reconstruction and apology. In practice, that means the same behavior can help in one setting and fail in another because the incentives, relationship, timing, or information environment changed.

A useful test is to ask what observable behavior would be different if escalation of commitment were actually driving the situation. That turns an abstract idea into a hypothesis. You can then look for evidence, compare alternatives, and avoid explaining every outcome after the fact.

6. Apology

Within Mistakes Were Made (But Not by Me), apology is best understood as part of a system rather than an isolated tactic. It interacts with escalation of commitment and accountability. In practice, that means the same behavior can help in one setting and fail in another because the incentives, relationship, timing, or information environment changed.

A useful test is to ask what observable behavior would be different if apology were actually driving the situation. That turns an abstract idea into a hypothesis. You can then look for evidence, compare alternatives, and avoid explaining every outcome after the fact.

Where people misuse the idea

Leadership

For leadership, Mistakes Were Made (But Not by Me) is most actionable when you use the idea to design clearer decisions, feedback loops, and expectations rather than relying on charisma. The point is not to force the book’s vocabulary into every situation. The point is to make hidden assumptions explicit enough to test.

Negotiation

For negotiation, Mistakes Were Made (But Not by Me) is most actionable when you translate the concept into preparation: interests, alternatives, information gaps, emotional temperature, and next moves. The point is not to force the book’s vocabulary into every situation. The point is to make hidden assumptions explicit enough to test.

Sales and persuasion

For sales and persuasion, Mistakes Were Made (But Not by Me) is most actionable when you use it to improve diagnosis and message fit while preserving the buyer’s ability to say no. The point is not to force the book’s vocabulary into every situation. The point is to make hidden assumptions explicit enough to test.

Personal decisions

For personal decisions, Mistakes Were Made (But Not by Me) is most actionable when you apply the framework before a high-stakes choice, then record what you expected so hindsight does not rewrite the story. The point is not to force the book’s vocabulary into every situation. The point is to make hidden assumptions explicit enough to test.

Team design

For team design, Mistakes Were Made (But Not by Me) is most actionable when you ask whether the environment rewards the behavior you say you want, and whether status or fear blocks useful information. The point is not to force the book’s vocabulary into every situation. The point is to make hidden assumptions explicit enough to test.

A decision-useful way to apply it

Limit: Not every defense mechanism is dissonance reduction. This matters because a useful framework can become a bad doctrine when readers stop asking what evidence would change their mind.

Limit: Institutions amplify individual incentives. This matters because a useful framework can become a bad doctrine when readers stop asking what evidence would change their mind.

Limit: Insight alone may not change behavior. This matters because a useful framework can become a bad doctrine when readers stop asking what evidence would change their mind.

Another limitation is transfer. Examples that work in one company, country, negotiation, classroom, or relationship may not travel cleanly. The safer approach is to preserve the mechanism while adapting the behavior. That is slower than copying a script, but it produces better judgment.

A practical 7-step reading-to-action process

  1. Name the concrete decision or behavior you want to improve.
  2. Identify which idea from the book is actually relevant.
  3. Write down the mechanism you believe is operating.
  4. List at least one competing explanation.
  5. Choose a small action that can produce observable feedback.
  6. Define in advance what result would count as improvement.
  7. Review the result without rewriting your original prediction.

Questions to ask before applying Mistakes Were Made (But Not by Me)

  • Am I using cognitive dissonance as an explanation because evidence supports it, or because it is memorable?
  • What would self-justification look like in observable behavior?
  • Could confirmation bias be creating a different outcome than the book’s example?
  • What incentive does the other person face?
  • What information would change my decision?
  • What happens if everyone in the system copies this tactic?

Who should read it?

Mistakes Were Made (But Not by Me) is a strong fit for readers who need a practical lens on cognitive dissonance and self-justification as forces that protect identity after bad decisions. It is less useful for someone looking for a universal formula. The best use is selective: take the concepts that match a real problem, compare them with evidence from your context, and discard what does not survive contact with reality.

Application note 1: testing cognitive dissonance in Mistakes Were Made (But Not by Me)

Readers often lose value from Mistakes Were Made (But Not by Me) when they move directly from recognizing cognitive dissonance to assuming they understand the whole situation. A better sequence is observation, interpretation, intervention, and review. For this book, write down the behavior you can actually see, the outcome you want, and the constraint that seems to connect cognitive dissonance with self-justification. Then ask whether changing information, incentives, timing, environment, or relationship structure would be more effective than simply asking people to try harder. That keeps Mistakes Were Made (But Not by Me) from becoming a collection of labels.

The second test is to separate outcome quality from decision quality in a way that fits confirmation bias. A sound process can still produce a bad result when uncertainty is real, and a weak process can get lucky. When applying Mistakes Were Made (But Not by Me) to cognitive dissonance, document what you knew at the time, what you expected, and what evidence would have changed the decision. Review the result later against that record. This creates a learning loop specific to the book’s mechanism and reduces hindsight bias without pretending uncertainty can be removed.

Application note 2: testing self-justification in Mistakes Were Made (But Not by Me)

Readers often lose value from Mistakes Were Made (But Not by Me) when they move directly from recognizing self-justification to assuming they understand the whole situation. A better sequence is observation, interpretation, intervention, and review. For this book, write down the behavior you can actually see, the outcome you want, and the constraint that seems to connect self-justification with confirmation bias. Then ask whether changing information, incentives, timing, environment, or relationship structure would be more effective than simply asking people to try harder. That keeps Mistakes Were Made (But Not by Me) from becoming a collection of labels.

The second test is to separate outcome quality from decision quality in a way that fits memory reconstruction. A sound process can still produce a bad result when uncertainty is real, and a weak process can get lucky. When applying Mistakes Were Made (But Not by Me) to self-justification, document what you knew at the time, what you expected, and what evidence would have changed the decision. Review the result later against that record. This creates a learning loop specific to the book’s mechanism and reduces hindsight bias without pretending uncertainty can be removed.

Application note 3: testing confirmation bias in Mistakes Were Made (But Not by Me)

Readers often lose value from Mistakes Were Made (But Not by Me) when they move directly from recognizing confirmation bias to assuming they understand the whole situation. A better sequence is observation, interpretation, intervention, and review. For this book, write down the behavior you can actually see, the outcome you want, and the constraint that seems to connect confirmation bias with memory reconstruction. Then ask whether changing information, incentives, timing, environment, or relationship structure would be more effective than simply asking people to try harder. That keeps Mistakes Were Made (But Not by Me) from becoming a collection of labels.

The second test is to separate outcome quality from decision quality in a way that fits escalation of commitment. A sound process can still produce a bad result when uncertainty is real, and a weak process can get lucky. When applying Mistakes Were Made (But Not by Me) to confirmation bias, document what you knew at the time, what you expected, and what evidence would have changed the decision. Review the result later against that record. This creates a learning loop specific to the book’s mechanism and reduces hindsight bias without pretending uncertainty can be removed.

Application note 4: testing memory reconstruction in Mistakes Were Made (But Not by Me)

Readers often lose value from Mistakes Were Made (But Not by Me) when they move directly from recognizing memory reconstruction to assuming they understand the whole situation. A better sequence is observation, interpretation, intervention, and review. For this book, write down the behavior you can actually see, the outcome you want, and the constraint that seems to connect memory reconstruction with escalation of commitment. Then ask whether changing information, incentives, timing, environment, or relationship structure would be more effective than simply asking people to try harder. That keeps Mistakes Were Made (But Not by Me) from becoming a collection of labels.

The second test is to separate outcome quality from decision quality in a way that fits apology. A sound process can still produce a bad result when uncertainty is real, and a weak process can get lucky. When applying Mistakes Were Made (But Not by Me) to memory reconstruction, document what you knew at the time, what you expected, and what evidence would have changed the decision. Review the result later against that record. This creates a learning loop specific to the book’s mechanism and reduces hindsight bias without pretending uncertainty can be removed.

Final assessment

The lasting value of Mistakes Were Made (But Not by Me) is not that every claim should be accepted. It is that the book gives the reader a set of distinctions that can improve observation and decision quality. Read critically, test locally, and treat the framework as a tool—not an identity.

Millionaire MinuteGet the app →