Post-mortems

It's easy to complete the transition of new capability into live operations and immediately move onto the next. It's also almost as easy to go through project post-mortems in a rote fashion without getting much out of it.  Many organisations and teams can regard project post-mortems as admin due to the lack of systems and methods to get good data and permit frank feedback. Below are a few of our thoughts on good practice:

1. Anonymise data collection
Use tools to permit the team to deliver anonymous feedback on their true thoughts.

2. Real data
Ensure your toolsets record and provide real data on performance against the plan.

3. Artificial scarcity
Rather than get unhelpful answers to questions such as 'What would you improve?', try asking things like:

  • If you could only have one more person on the team for doing this again, what type of person would that be?
  • What are your top 3 things to do better?
  • What are the top 3 things to stop doing?
  • If there was one group of activities you could have had more time for, what would they be?
  • If there was one team you could have spent more time prepping with, what would that team be?
Search