So, how can you work more efficiently and increase your chances of success? Simple answer: Hold a retrospective.
A simple tool for impressive results
My colleague, Dave Saabye, explained how he applies the practices he learned as an ambulance volunteer to improving the effectiveness of corporations. Below, I’ll provide some detail on how to capture lessons from collaboration.
A retrospective, or “retro” in agile lingo, is a simple meeting tool that, when applied consistently, increases the odds of your success.
Successful retrospectives are respected as meaningful “ceremonies” (another agile term) and thus should follow basic rules.
Carve out 30 minutes to get everyone around a table (or on a group phone or video call). Your team can be two or 20 people, but true agile teams have fewer members. I have found that keeping a time limit is most effective because it focuses everyone to think clearly and you avoid excessive navel gazing that can descend into the analysis paralysis. The purpose of a retrospective is not to relive the entire collaboration moment by moment. The purpose is to capture specific things you learned together. (A side perk I’ve discovered is when people know they need to invest just 30 minutes, they are more likely to show up and be on time.)
Share your screen to show everyone a document that is split into three sections:
- What went well.
- What could we do better next time. Be mindful of the clock: Don’t get stuck on what was so great or what was so terrible.
- Make a list of to-do items. Each one should say what will be done and who will do it.
Remind people there is no blame and total honesty is paramount, as nobody wins if someone holds back. Also, each project is different so you can learn something every time. Focus the comments on the work you did together.
At the end of the retrospective, file the document you just wrote where each person on the team can access it. Go through the same exercise at the next logical milestone of the project.
Keep at it. The real power comes only at that point when someone on the team is about to embark on a related piece of work and pulls out the document you created together. Once that person reads the list of things to do differently next time, he will be hooked. It could be a week or a year later—it depends on the nature of your collaboration. Whenever it does occur, you will have the benefit of building on what you’ve already learned.