I'm looking for ideas to improve the retro process. In general, our team does what went well, what didn't and kudos. There are a few action items that come out but those go into the void despite being tracked. What are some of the ways to improve the process and make sure feedback/action items is actually addressed? Thank you!
There's 2 separate issues here, so I'll split my response up into 2 comments:
This will mainly come from expanding the kudos section. Here's some ideas I've seen/played around with:
For resources on how to be a more helpful teammate, I recommend these:
At Instagram, we had a problem where follow-up tasks from SEVs (term for bad production outages at Meta) weren't being done because engineers would ignore them and prioritize roadmap feature work instead. Over time, this led to our quality and system health suffering, so many senior/staff engineers (including me) started being the "moms" of our team and poking engineers to do them. If they truly didn't have the bandwidth, we would:
Being a "mom" and telling people to be responsible isn't the most exciting job in the world, but it's important and one of the more unsung ways senior/staff engineers fill in the gaps on their team. Since you're a senior engineer, you can talk with your manager about being the person to fill in such a role. Seems like good scope for a staff promotion!
Here's some other good resources to check out: