Planning Ahead: Premortems > Postmortems
How to catch problems before they catch you using premortems
Hey, itโsย Irina! ๐ Welcome to another edition ofย The Caring Techie Newsletter. Today youโll learn about pre-mortems and how they can be very useful tools in ensuring projectsโ success. Enjoy!
Read time:ย 3 minutes
Iโm thrilled to announce that Iโve been invited to be the keynote speaker of this yearโs LeadDev Berlin conference for tech leads and engineering managers!! My talk: โ๐๐ฒ๐ฎ๐ฑ๐ถ๐ป๐ด ๐๐ต๐ฟ๐ผ๐๐ด๐ต ๐๐ฐ๐ฎ๐ฟ๐ฐ๐ถ๐๐: ๐๐๐ถ๐น๐ฑ๐ถ๐ป๐ด ๐ฐ๐ฎ๐ฝ๐ฎ๐ฐ๐ถ๐๐ ๐ถ๐ป ๐๐ต๐ฒ ๐๐ฒ๐ฎ๐บ ๐๐ผ๐ ๐ต๐ฎ๐๐ฒโ. Iโll discuss how leaders need to rethink their role in the era of โbuilding less with moreโ.
So, if youโre in Berlin between 4-5 of November, and want to learn from me and other exceptional technical leaders, join us at LeadDev. Also, as a 2024 conference speaker, I have a 14% off code to share with you:ย ๐๐ฅ๐๐ก๐๐ญ๐ฑ.
In last weekโs article, we talked about how disappointing it can be to invest time and energy into projects that fail. More than being a blow to moraleโit can also hurt your career growth and be extremely costly for the organization.
If you missed the article, you can read it here:
In complex projects, failure often feels like it sneaks up on usโbut in reality, many of the warning signs are there from the beginning. The challenge is recognizing them early enough to act. This is where shifting from reactive learning to proactive planning can make all the difference.
Many of us have heard about postmortems, which are part of incident management. They happen after something goes wrong, to identify issues and learn from them. I wrote about postmortems in more detail here:
But what if you could do a similar exerciseโbefore things go wrong? This is where premortems come in. This flips the usual approach on its head. Instead of just planning for success, you brainstorm all the ways things could go wrong. It's like preparing for a rainy day.
Today youโll learn:
How premortems help
Why I think premortems are fun
How to run a premortem meeting
Why projects fail (and how premortems help)
Many projects fail because of unmanaged risks, unrealistic expectations, or simply unforeseen events. A premortem helps you identify potential pitfalls before you hit them, giving you the chance to reduce risk and avoid nasty surprises.
Postmortems require participants to use their imagination, put a hypothetical negative hat on, and ask: "What if this fails? How can we prevent it?"
The basic premise is to imagine a future where the project has already failedโand then work backward to identify the causes. This taps into a psychological principle called prospective hindsight, which helps shift focus to realism by eliminating 2 common cognitive biases:
Optimism bias: It forces the team to identify risks they might overlook when focused on success.
Hindsight bias: It documents risks upfront, preventing the i-knew-it-all-along effect later.
Why I think premortems are fun
There are several reasons why I believe premortems are not only effective but also fun:
They increase the likelihood of project success
Being able to anticipate and proactively address roadblocks makes things run more smoothly.
The whole team is involved from the start
People feel more invested because their opinions are valued early, not just after problems arise avoiding the โwell if you had asked me sooner, I couldโve told you that โฆโ moments.
They reduce anxiety for me as a lead
Knowing weโve prepared for the worst makes me feel more confident and at ease. It's reassuring to know that even unexpected curveballs wonโt catch us off guard.
You are reading a free article of The Caring Techie Newsletter. I post weekly-ish articles on career growth, leadership and communication for high performing ICs and leaders. If youโre learning new things and want me to continue creating these articles, please consider becoming aย paying subscriber. See theย benefits here.
How to run an engaging premortem meeting
Yes, a premortem requires a dedicated meeting. But this is not one of those sit-down-and-listen-to-someone-else-speak-at-you meetings. Instead, itโs an engaging session where everyone contributes actively.
Different organizations use different formats, but I like to keep things simple. Hereโs the structure I recommend:
Provide context:
Start a clear description of what youโre trying to build, the project roadmap, and the feature set.
Set the stage:
Make sure everyone knows their roles within the project.
โBack to the Futureโ moment:
Ask the team to imagine that the project has failed spectacularly.
Brainstorm what went wrong:
Have each team member independently list all the ways things could have gone wrong. This should be done quietly to avoid groupthink.
Collect and triage the issues:
Gather everyoneโs answers and assess each one based on three key factors:
Impact: How severe would the consequences be?
Likelihood: How probable is it that this will happen?
Reversibility: If it happens, can it be undone or corrected?
Discuss prevention strategies and solutions:
Discuss ways to address each issue. The goal is to come up with actionable strategies to prevent problems.
Review the project plan:
Depending on the impact, likelihood, and reversibility of the issue, consider changing the project plan to incorporate prevention strategies from the start.
Keep track of your premortems with this template
To make it easy to document and follow up on your premortem findings, hereโs a free template you can use: Premortem Notion Template.
I hope this article was helpful and that you give premortems a try if you havenโt!
Until next time,
Your Caring Techie
Did you enjoy this article? Hit the โค๏ธ button or share it with a friend or coworker. ๐๐ป
Do you want to grow your career? Here are 3 ways I can help:
1-1 coachingย - I have 2 coaching spots left for the rest of the year, email me atย thecaringtechie@gmail.comย or DM me to learn more!
Book a one-hour callย where we can tackle your most pressing issues.
Teaching private cohortsย ofย โImpact through Influenceโ, if youโre a manager or leader interested in this for your teams, reach out!
I love that you included a template, you rock, Irina!