• Home
  • Blog
  • Projects
  • Bookshelf
  • About
← Back to all status updates

Zombie Retros

Published 📅: ....
Last modified 📝: ....
Location 📍: Boston, MA

Share this status update on BlueskySee discussion on Bluesky


Zombie retrospectives are worse than doing no retros at all.

A zombie retro can easily be spotted by most folks (and yet never seems to be discussed by the team, nor noticed by the facilitator), and it is one of the worst things that can happen for a team.

Retros are meant to be lively discussions about the team's process or progress over the last period of time (monthly or bi-weekly or whatever works), you should be having (respectful) disagreements and (positive) arguments with your team, it's intentionally meant as an opportunity to hash out process topics with the team as a whole. Yet, far too often these meetings actively drain the team of any and all energy they have to improve the process.

One of my former managers talks about retros frequently on , and this post really stands out to me as a call to action to kill .

their blog
zombie retros

If you're suffering from zombie retros, try giving some of those ideas a try!


Tags:

micropostTeamsCulture

Loading...

Related Posts

micropost

Tip: Secrets for Cloudflare Workers

Published: ....

Tip: GitHub Created Date Filtering

Published: ....

Link: Next.js Is Infuriating

Published: ....

Dependabot Hell

Published: ....

Link: What the hell is going on right now?

Published: ....

Recipe: Horchata Protein Latte

Published: ....

Link: How I build software quickly

Published: ....

Vacation (and streaks)

Published: ....

Polish is Important

Published: ....

<Blank> Driven Development

Published: ....

All Documentation Should Be Dated

Published: ....

Adding Microposts

Published: ....

Service Monitors and Observability

Published: ....

Leveraging service monitors properly to improve service observability.

Being Unopinionated

Published: ....

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.

Stop Snacking

Published: ....

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

No Process is Invisible Process

Published: ....

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.

Teams

Things Leaders Should Never Do

Published: ....

If you're a leader, please never do these things!

Team Memes

Published: ....

A snippet of some shared terminology/concepts (memes) from my time on the Frontend Platform team at Wayfair!

No Process is Invisible Process

Published: ....

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.

Culture

Things Leaders Should Never Do

Published: ....

If you're a leader, please never do these things!

Team Memes

Published: ....

A snippet of some shared terminology/concepts (memes) from my time on the Frontend Platform team at Wayfair!