When things don’t quite go as planned, the first instinct is to figure out why. The goal is not just to patch up the current situation but also to set up safeguards to reduce the chances of a repeat occurrence. But here’s the challenge: these problem-solving meetings can quickly turn into a blame game, with finger-pointing left and right. Or, they might turn into frustrating talk circles where it feels like progress is being stalled.
One strategy I’ve found super effective is starting the meeting with a basic, rough model of the situation. It’s like laying a simple map on the table right from the get-go. Now, I know this map isn’t going to capture every little detail (after all, the map isn’t the territory), but it is an amazing conversation starter. Everyone in the room can then add their own insights, pointing out what the model misses and sharing their unique perspectives on constraints and limitations.
This approach does two awesome things. First, it shifts the focus from blaming people to examining the parts of the process that went wrong. Second, it makes our discussions way more efficient. We can easily move from one topic to another, ensuring that we’re not repeating the same pain points in roundabouts.
As the meeting progresses, action items naturally start to pop up. These are practical suggestions for how various system parts can be tweaked. This clear, focused approach really encourages team members to step up and take ownership of these action items.
Give this technique a try at your next post-mortem meeting. I’m super eager to hear how it works out for you!
Be First to Comment