What does it mean that reflection transforms experience into learning?

Without reflection you accumulate experiences but not wisdom.

Example: Two product managers start the same role at the same company on the same day. Ten years later, one has become a VP of Product known for sharp strategic judgment and an uncanny ability to predict which initiatives will succeed. The other is still a senior PM, competent but unremarkable, cycling through projects that feel interchangeable. Both shipped dozens of products. Both worked long hours. Both accumulated a decade of experience. The difference is not talent or effort — it is what happened after each project ended. The first PM spent thirty minutes after every launch writing down what worked, what failed, what she assumed that turned out wrong, and what she would do differently. She reviewed these notes quarterly. Over ten years, she built a personal library of extracted lessons that compounded into genuine expertise. The second PM finished each project, exhaled, and moved on to the next one. He had ten years of experience. She had ten years of learning. The gap between them is reflection.

Try this: Identify one significant project, decision, or experience from the past month that you completed but never deliberately reflected on. Set a timer for twenty minutes and write answers to these five questions: (1) What was I trying to accomplish, and did I accomplish it? (2) What assumptions did I make going in, and which ones turned out to be wrong? (3) What would I do differently if I could start over with what I know now? (4) What skill or knowledge gap did this experience reveal? (5) What is the single most important lesson I should carry forward? Do not edit or polish your answers. The goal is extraction, not presentation. When you finish, read what you wrote and circle the one insight that surprised you most. That surprise is evidence of learning that was latent in your experience but inaccessible until reflection made it explicit.