#open-share

If you only have 30 min, I would collect feedback in advance on what went well and what could be improved and have it consolidated/grouped thematically before the session. Then you can use your time together to be more focused on highlighting the most important things to continue, solving any structural challenges, or working through any feedback that warrants a live discussion

Retro template here: https://docs.google.com/presentation/d/1XoB28_wLCBRq9vTQTvMhL4oQSCCLXjButqAciVDsVa4/edit?usp=sharing

I've also done this on Miro. Give people time to drop things into Miro, then spend a few moments grouping things together. Then give people a chance to explain what they shared and why.

I typically like to ask people to be thinking about these questions in advance so they're mentally prepared for the meeting and to contribute

Thank you both!

You're welcome!

I used to do retros every other week with my dev team back when I was a product manager.

There are many frameworks. I'm a big fan of a kanban board (ala Trello) with 3 columns:
• What went well
• What didn't go well
• What should we change for next time
Then you allow each team member to briefly explain their item. If you only have 30 minutes and more than a handful of people, this may not work for you as that's too short a time.

No matter what, the key is people adding items to be reflected upon before the meeting, not during.

Super helpful thank you! shifting my strategy to collect feedback async then using the time to review it and create an action plan for future projects.