I love a good retrospective.

If you've ever replayed an argument in your head during your morning shower, you probably love retros too.

Something I learned over the years is retros aren't just for wrapping up a sprint. They're great for evaluating the effectiveness of 1:1s, incident responses, training sessions. Perhaps most importantly, it's the BEST opportunity for any good manager to build trust with the team.

While all retros get to the heart of the matter: what worked, what didn't, what should change, varying the questions just slightly can really draw people in (or turn them away.) And as a manager, you really have to push your team to give you good feedback. In my case it was asking: "What do you think can't change, and have given up on trying to change?"

Not only did it give me insights on festering frustrations, it also gave me a very simple task list of what I needed to resolve (and, in doing so, build further trust with my team by showing I'm accountable to them.)


Let's Clear Up The Ambiguity!

FAQs for a Software Engineering Hiring Manager

7 Steps to Writing an Amazing Resume

7 Steps to Building your Portfolio MVP

On Systems Debt