How do I stop being so hard on myself when I make a mistake?

A useful reframe: separate the mistake from your identity. A mistake is something that happened. It is not evidence of who you are. The same standard you would apply to a colleague's error, understanding the cause, identifying the fix, moving on, is the right standard to apply to your own. Extended self-criticism rarely produces better performance. It usually just reduces the willingness to take the risks that produce growth.

Reflection

How to Learn From Your Mistakes at Work

Q: Should I tell my manager when I make a mistake?

In most cases, yes, especially if the mistake affects others or will become visible anyway. Coming forward early, with an understanding of what happened and a plan for addressing it, is significantly better than being discovered later. Managers generally respond much better to someone who identified a problem and raised it than to someone who hoped it would not be noticed. Transparency builds trust. Concealment, even of small things, tends to erode it.

Q: Why do I keep making the same mistakes?

Repeated mistakes usually indicate that the review after the original mistake was insufficient. If the cause was not clearly identified, the underlying condition still exists and will produce the same result again. A genuine post-mortem that asks not just what went wrong but why, and what structural change would prevent it, is what breaks the pattern. Willpower and intention alone rarely do.

Making mistakes is unavoidable. Learning from them is not automatic. Here is how to turn setbacks into useful information rather than just sources of frustration.

3 September 2026 · 5 min read

The phrase learning from mistakes gets repeated so often that it has almost lost its meaning. Everyone agrees with it in principle. Far fewer people have a deliberate process for actually doing it. The more common pattern is to feel bad about a mistake for a while, resolve to do better, and then encounter the same conditions a few months later with the same result.

Genuine learning from mistakes requires more than intention. It requires a process: enough distance to look at what happened clearly, enough honesty to identify the real cause, and enough structure to turn that understanding into a specific change.

Create some distance before the review

Reviewing a mistake while still in the emotional response to it is not useful. The instinct to protect self-esteem is too active, which means the review either becomes self-flagellation or rationalisation, sometimes both in the same conversation. Neither produces learning.

A day or two of distance, enough for the immediate emotion to settle, produces a more honest and useful review. You can look at what happened with something closer to the curiosity you would apply to a puzzle rather than the defensiveness you bring when your identity feels threatened.

Ask why, not just what

The surface description of a mistake is rarely where the useful information lives. Saying that a deadline was missed describes what happened. Understanding why it was missed, whether because the timeline was unrealistic from the start, because a dependency was not tracked, because a conversation was avoided, is where the learning is.

A simple tool: keep asking why until you reach a cause that is actually addressable. If a deadline was missed because the brief arrived late, ask why the brief arrived late. If that happened because expectations were not set clearly at the start, you now have something specific to change. Stopping at the first answer usually stops at a symptom rather than a cause.

Identify a specific change, not a general intention

The most common output of a mistake review is a vague intention: be more careful, communicate better, plan ahead. These intentions feel meaningful in the moment and produce no change in behaviour because they are not specific enough to act on.

A useful output names a concrete change: send a project update every Friday rather than relying on informal check-ins, add a dependencies column to the planning document, confirm scope in writing before starting any piece of work over a certain size. The more specific the change, the more likely it is to stick.

Build review into the weekly rhythm

Individual mistakes are easier to learn from when there is already a habit of reflection. A weekly review that asks what worked, what did not, and what you would do differently creates a regular structure for this kind of thinking. Mistakes reviewed in that context get the same considered attention as successes, rather than being either dismissed or ruminated on without any productive outcome.

Common questions

How do I stop being so hard on myself after a mistake?

Separate the mistake from your identity. Apply the same standard you would apply to a colleague: understand the cause, identify the fix, move on. Extended self-criticism rarely improves performance. It usually just reduces the willingness to take the risks that produce growth.

Should I tell my manager when I make a mistake?

In most cases, yes. Coming forward early with an understanding of what happened and a plan for addressing it is significantly better than being discovered later. Transparency builds trust. Concealment erodes it.

Why do I keep making the same mistakes?

Repeated mistakes usually mean the review after the original was insufficient. If the real cause was not identified, the underlying condition still exists. A genuine review that asks why, not just what, and identifies a structural change is what breaks the pattern.

Reflection is how progress compounds

Weekly Reset gives you a structured space to review what worked and what did not each week so that learning becomes a habit rather than an afterthought. Free forever.