3 / Retrospectives: the 🔑 to long-term product success

Welcome to Issue 3!

Retrospectives are one of the most overlooked rituals on a product team. And I get it — when you're racing to ship, it's hard to hit pause and reflect.

But skipping that time to look back has always cost us. Retros help build team cohesion, clarity, and institutional knowledge. They create space for honest conversations about how things are really going and, more importantly, how to get better.

In last week’s Technically Lit podcast, I talked with Jason McCarty about how different teams approach retros and why they matter. Beyond improving your day-to-day product practice, retros give you the chance to zoom out and ask the big question: are we actually shipping things users value?

Some of the best teams I’ve worked with didn’t start that way. They became great through consistent, intentional reflection. So if you're not running retros, now’s a great time to start. And if you are, try going a step further: use them to evaluate not just how you build, but what you’re building.

Let’s get Technically Lit,

Nick

Fresh content

A little something different

I love a good gradient and the Inflight website delivers. Enjoy!