The retro is sacred.

People ask me what process they should use. Jira or Linear? Shape Up or Scrum? Two-week sprints or one? I have to tell them, earnestly: I don't know. A great process is form-fitted to the humans and circumstances it exists to serve. It's closer to improv than a pilot's checklist — interactive, emergent, iterative. The longer you refine it with one group of people, the stronger it gets.

One-size-fits-all answers don't work here. What you need is situational awareness, radical truth-telling, and a way to turn operational pain into institutional wisdom over time.

Retros turn pain into wisdom

Every team is unhappy in its own way. You don't need a heavy process. You need a reliable way to (1) identify what's not working, and (2) try relevant solutions — over time, with the whole team involved. That's what a retrospective is for.

It's a twenty-minute meeting. Everyone shares what's going well, what could be better, and what specific changes they want to try. Write it down. Actually pause to celebrate the good stuff — seriously, do that. Discuss what the team wants to address, agree on a change, and let it be so. Then, critically, read back through the changes from the last retro: are they still relevant? Did you actually make them? That last step is what makes the whole thing work. It's almost like test-driven development for your process.

Dig past the surface

The first answer is rarely the real answer. Everyone has the gut reaction of "we worked on this hard important project and it took longer than expected, ugh." But that isn't actually something to improve — it was hard and important. The real improvement might be carving out more space for hard important things, or adjusting expectations about what else fits in a cycle when you're steeped in one. Pause after the obvious complaint and dig.

Omnivorous, not doctrinaire

When I rail against one-size-fits-all answers, I'm not saying it's bad to learn how other people do things. Read widely. Steal shamelessly. Keep a notes file full of every smart idea you've ever heard. Your job isn't purity — it's discernment. Match the solution to the actual problem in front of you.

Suck less every day

There's no end point. There's no A+. One of my first bosses used to say, "suck less every day," and that's pretty much it. Do retros in good times and bad. Trust that self-assessment beats external assessment. Within a few weeks you'll have a tailor-made process — and when the team grows out of it, you'll already have the tool to notice and fix it again.