Retrospective: if not now, when?

There's a harrowing moment from my life that underlines the critical need for retrospectives—a time when hesitation could have had dire consequences. It taught me an invaluable lesson: the tougher the challenge, the more urgent the need to learn, adapt, and improve.

In IT world, especially for projects lagging behind schedule, I often hear, "We don't have time for retrospectives. Let’s skip them and revisit after go-live." 

It seems to be a natural instinct to postpone facing difficulties. 

Yet, my own experience tells a different story—one where delaying could have been fatal. 

I was given a car at a new job, which was thrilling, but I hadn’t driven a car for five years. I checked the basics and assumed I was set. It was night-dark early morning, when the track in front of me turned right and I realized I didn’t know how to turn on the headlights. Driving blind at high speed, panic set in.

Then it struck me—if these were my last moments, I'd regret not trying to find the light switch. That was my on-the-spot retrospective. 

I found the switch and reached my destination safely. 

This experience became a stark metaphor for my professional philosophy. No matter how intense a project gets, there must always be room for a retrospective. 

It's these moments of reflection that can steer us away from potential disasters and towards our goals.