We’ve all been there: a project you and your team collaborated on for months doesn’t yield the results you’d hoped for, or a dream client decides to sign with your competitor, or maybe the business doesn’t meet its quarterly revenue goal. It’s situations like these – the ones where no one specific person or event is to blame, but rather the team as a whole misses the mark – that can be the most difficult to solve for.
Post-mortem meetings provide the perfect opportunity to sift through a project or initiative from start to finish and determine what went well and what could be improved upon. But in the cases where the initiative in question is deemed unsuccessful, you might find your team playing a round of the blame game rather than working to come up with tangible solutions. When everyone is busy pointing fingers, how do you get down to brass tacks so you can figure out what actually went wrong and prevent it from happening again?
I’ve written before about egos at the individual level, the opportunities and challenges they present in the workplace, and how to bring out the best in your specific ego type. But when you’re managing a team of egos – and trust me, you are – how do you ensure everyone is playing to their strengths instead of succumbing to their weaknesses, specifically in a post-mortem meeting when emotions are running high? It’s not always easy, but there are several steps you can take as a leader to quell the egos, ease the tension and move forward as a team.
In the decade-plus I’ve been working with executives, I’ve found that when leaders are willing to take ownership of their part in a failed initiative, the rest of the team is much more willing to follow suit. It should go without saying but whether or not your team succeeds or fails is ultimately up to you. While you probably aren’t the one executing individual tasks, you’re responsible for delegating those tasks, setting the vision and leading the charge.
Assess your role in the outcome, and be honest – with yourself and your team – about what you could do better next time. Some might be concerned that this kind of vulnerability is a sign of weak leadership, but in my experience, this approach tends to disarm egos, encouraging the rest of the team to own their part and work collaboratively toward a solution.
Rather than assume you know what went wrong, approach the post-mortem meeting with an open mind. Be genuinely curious about what took place at each step by asking pointed questions and actively listening to the answers. Encourage everyone on the team to bring their own questions, for you and their colleagues, and be prepared to answer them honestly. Ask clarifying questions until you feel you’ve established a complete timeline of events.
Do your best to frame your questions in a constructive rather than accusatory manner. In fact, it might be worth stating up front that the purpose of the post-mortem isn’t to assign blame to a single party but to establish where you are so you can map out how you can get to where you want to go. With everyone’s egos in the backseat, having already copped to their mistakes, you can have an honest discussion, identify the source(s) of the issue and decide how you might approach things going forward.
After these conversations, you should be ready to develop a solution for the next time you’re in this situation. But wait, you’re not done. There’s still one more discussion you’ll need to have as a team before you wrap the post-mortem.
In my work as a leadership coach and ego management expert, I’ve identified three types of egos: the compiler, the protector and the controller. Each of these ego types has different motivations and reasons for doing the work they do and we see these motivations most clearly in the questions and concerns they raise, especially in situations like these. For example, compilers want to be liked and crave approval and validation from those around them. Protectors, on the other hand, are driven by the need to be right and tend to be stubborn when it comes to adopting someone else’s way of doing things. Finally, controllers are the perfectionists of the bunch and tend to be results-oriented.
So what does this mean for your post-mortem meeting? The compilers on your team will be concerned with the people aspects of the proposed solution: Who’s involved? What will be required of them? How will this impact the team? The protectors will want to understand the logistics: What steps need to be taken to implement this plan? Who is responsible for what? What resources are available? And the controllers will want to know what results they can expect: What would be the tangible outcome of this solution? How will you measure success? What should they be tracking along the way?
Since you likely have a mix of each ego type on your team, take the time to consider each aspect of your proposed solution – the people, the logistics, the results – and clearly lay out how the solution you’ve agreed upon will impact each of these aspects. Document your answers in any meeting notes and ensure everyone on the team has access.
You’ll save yourself time and headaches down the road by asking and answering these questions now. You’ll also increase the likelihood that the team will buy into your plan from the jump and your solution will be a success.
Ready for Your Next Post-Mortem Meeting?
Post-mortem meetings are an invaluable exercise but they can be tricky to navigate when results are less than stellar. By following these steps, you’ll avoid assigning blame to any one person or party, keeping everyone in the “we’re a team” mindset, which is exactly what you need to conquer the next challenge.