How to Learn from Experience

We like to say experience is the best teacher. Yet everyone knows people who have done the same job for twenty years and are no better than they were in year three. Experience surrounds them; learning does not follow. Doing something once, or a thousand times, is not the same as extracting a lesson from it.

The missing ingredient is reflection. Experience supplies raw material — what happened, what worked, what went wrong — but that material only becomes durable knowledge when you stop and make sense of it. Learn to reflect deliberately and ordinary experience becomes a steady source of improvement instead of noise you pass through.

Experience is raw material, not the lesson

An experience is data. Left unexamined, it fades or, worse, teaches the wrong thing — you might conclude a project failed because of bad luck when the real cause was your planning. Reflection is the step that turns an event into an interpretation you can carry forward. Without it, you accumulate experiences the way a camera accumulates photos no one ever looks at.

The experiential learning cycle

A useful way to structure reflection is a cycle with four stages: you have a concrete experience; you engage in reflective observation, reviewing what actually happened; you move to abstract conceptualisation, forming a general principle or explanation; and you attempt active experimentation, testing that principle in the next situation. The output of that test is a new experience, and the cycle turns again. The power is in completing the loop — most people stop after the doing.

Learning by doing and project-based learning

This is why learning by doing and project-based learning work well — but only when reflection is built in. A project gives you rich, consequential experience: real problems, real feedback, real mistakes. That richness is wasted if you finish and immediately move on. A short review at the end — what did I learn, what would I do differently — is what converts the project's experience into transferable skill.

You give a presentation and it falls flat. The audience looks bored; you rush the ending. Doing alone teaches nothing except that it felt bad.

Now run the cycle. Concrete experience: the talk lost the room around the middle. Reflective observation: you replay it and notice the energy dropped when you read dense slides aloud. Abstract conceptualisation: you form a principle — slides should prompt me, not script me. Active experimentation: at your next talk you cut the text and speak to the ideas. It goes better, giving you a new experience to reflect on. The failure became a lesson only because you looped through it deliberately.

Reflection is not the same as brooding, and more experience is not always the answer. Replaying a bad day over and over without forming any principle just rehearses the bad feeling; it is rumination, not learning.

Equally, piling on more repetitions without review can cement mistakes — practising a flawed technique makes it more automatic, not more correct. The goal is a specific, forward-looking loop: examine what happened, draw a general lesson, and change what you do next. Volume of experience without that loop is not a substitute for it.

In 1984, the educational theorist David A. Kolb published Experiential Learning: Experience as the Source of Learning and Development. Building on earlier thinkers including John Dewey and Kurt Lewin, Kolb described learning as a four-stage cycle: concrete experience, reflective observation, abstract conceptualisation, and active experimentation.

Kolb's central claim is that effective learning requires moving through all four stages, not just having the experience. His model has been widely used in education, medical training, and management development, and it has also drawn fair criticism — the accompanying "learning styles inventory" that sorts people into fixed types has weak empirical support, much like learning styles generally. What has held up well is the core, evidence-consistent idea the cycle captures: reflection is the step that turns experience into learning. Take the reflective principle; be cautious about the style labels.

• "Experience automatically teaches you." Only if you reflect; unexamined experience often fades or teaches the wrong lesson.
• "Reflection means thinking about how it felt." Useful reflection forms a general principle and changes your next action, not just your mood.
• "More repetitions always mean more learning." Repetition without review can cement mistakes as easily as skills.
• "Kolb proved everyone has a fixed learning style." The cycle is his durable contribution; the fixed-style inventory attached to it has weak support.

Pick one thing you did this week that did not go as planned. Walk it through four steps in writing: what happened, why you think it happened, the general lesson, and the one change you will test next time. Notice how the event only becomes useful at step three, when it turns into a principle you can reuse.

Think Like a Maester: Experience gives you the raw material; reflection is the work that turns it into something you can actually use.

1. Why can someone accumulate years of experience without improving?
2. Name the four stages of Kolb's experiential learning cycle in order.
3. What distinguishes useful reflection from rumination?
4. Why does project-based learning need a built-in review to pay off?
5. Which part of Kolb's work has held up well, and which part is weakly supported?

Experience is raw material, not a finished lesson. What converts one into the other is reflection: reviewing what happened, forming a general principle, and testing it in your next attempt — the loop Kolb described in 1984 as concrete experience, reflective observation, abstract conceptualisation, and active experimentation. Learning by doing and project work are powerful because they generate rich experience, but only when you deliberately close the loop. Do the thing, then make sense of it, and ordinary experience becomes steady improvement.

• Learning Through Mistakes
• Teaching Yourself Anything