What is a premortem, and how can it benefit your projects?

You’ve probably heard of a project post-mortem. For those unacquainted with the term, it’s a meeting where the team discusses how a project went, including what went wrong and how everyone can learn from the experience. While a post-mortem is important, it’s not enough. In order to improve your chances of success, you also need to perform a project premortem.

A premortem is similar to a post-mortem, but it takes place before a project has started. The point of a premortem is to identify potential problems and risks and mitigate them before they become an issue (or figure out a good plan for damage control if they do). The goal? To keep your project on track and prevent costly disasters.

What is a premortem?

A premortem meeting is a pre-project exercise that involves visualizing a project failure and evaluating how to solve the issues. The goal of a premortem is to identify potential problems and mitigate them. Here’s how it works…

The team gathers together and imagines their project has failed. Next, they analyze related factors and work backward to determine what might have caused the failure. This exercise helps to prevent similar problems from happening in a real project.

The project manager then gathers the premortem findings, prioritizes them in a risk breakdown structure, and creates a mitigation plan.

Premortem vs. risk assessment

A premortem occurs before the project and is focused on identifying and mitigating potential problems before they become an issue. A risk assessment (or risk register), on the other hand, typically occurs after a project begins and focuses on identifying risks that could impact the project outcome.

Premortem vs. post-mortem

A premortem is focused on identifying potential problems and mitigating them before they become an issue. A post-mortem is typically conducted after a project to help the team learn from the experience, and it focuses on both strong points and setbacks in the process.

Why is a premortem important?

A premortem is important because it helps you design better projects. By envisioning how a failed project could play out, your team gains insight into which factors they should monitor more closely. It also helps you reach a consensus on how to organize the project, which improves communication and cooperation among team members.

When a project is in its early stages, it’s easy to become overconfident and overlook sources of risk, potential delays, or resource conflicts. A premortem can help your team get an accurate picture of your project’s chance of success, so you can make adjustments as early as possible.

Using this preparation tool can save time, money, and resources, as well as prevent a potentially disastrous project failure.

To summarize, here are the key benefits of a premortem:

• Helps you identify, assess, and manage potential problems
• Reduces overconfidence and encourages preventive measures
• Creates a shared understanding of the project
• Improves cross-functional teams
• Helps you avoid project failure

Who should attend a premortem meeting?

To conduct a project premortem, you’ll need to gather a group of people who are familiar with the project. This group will typically include the project manager, team members, and stakeholders. However, it’s not limited to just these individuals. Feel free to invite anyone who might be affected by the project.

The group will then brainstorm potential risks and problems that could occur during the project. Be as thorough as possible to ensure no stone is left unturned.

Top tip: Just like a post-mortem meeting, a premortem meeting should stay light and positive. Focus on how to solve or prevent problems, not on who is to blame.

How do I conduct a premortem meeting?

Now sure where to start? Allow us to guide you.

1. Prepare

As with any team-based endeavor, preparation is key. Before you hold the meeting, make sure everyone involved is familiar with the project and understands the most critical problems that could occur. You’ll also want to get everyone on the same page regarding the meeting’s goals and objectives.

A formal project plan document is handy here. You can use this document as a reference during the premortem meeting. Typically, it contains the following elements:

1. Goals
2. Success metrics
3. Stakeholders and roles
4. Scope and budget
5. Milestones
6. Deliverables
7. Schedule
8. Communication plan

You’ll also want to have the right tools available. If your team is remote, consider using a video conferencing tool like Skype or Google Hangouts, plus a chat app like Slack so that people can ping quick text messages, pics, or files to each other during the meeting.

For the prep portion, consider virtual whiteboards for sharing ideas in real-time. If your team is in person, you’ll want a meeting room with a whiteboard, along with drinks and snacks to keep everyone comfy and well-fed.

2. Ask the right questions

Next, you need to brainstorm some answers. When conducting a premortem meeting, ask plenty of questions. Here are some for starters:

• Do you have any concerns about the project?
• Are there any factors that could cause us to miss our deadline?
• What can we do to keep our project on time?
• Does this project need anything that we don’t have?
• What lessons have you learned from past projects?

Remember, there’s no such thing as a bad idea when it comes to brainstorming. The goal is to come up with as many potential problems as possible. Tell your team they can be as imaginative as they like.

3. Share reasons

Next, it’s time to look at why your team chose specific failure routes. Each team member should share their ideas, and then the team can vote on which failures they think are the most likely to occur. Give everyone a chance to speak. After all, each person will have unique insight that could help the whole group determine where the project might be most at risk.

4. Prioritize and rank your risks

Not every conceived risk is likely to happen. And some will have more of an impact than others. In order to make sure you’re focusing on the right risks, it’s important to prioritize and rank them. You can use a simple scale, such as high, medium, and low, or give them a numerical ranking.

5. Develop a mitigation plan

Once you know the risks, it’s time to develop solutions for managing these issues. A mitigation plan is essentially a list of steps you can take to prevent or reduce the impact of a particular risk. Ideally, you should have an individual mitigation plan tailored to each issue you identified.

6. Follow-up

After the meeting, it’s essential to follow up on the generated action items. This includes creating a plan for how to address each problem and assigning somebody to be responsible for each task.

• Save your discussion and action items in your team’s project management software, where everyone can easily find them.
• Set tasks and track their progress.
• Revisit the document to ensure you’re keeping a close eye on potential risks and addressing them.

It’s also a good idea to evaluate your meeting. This is where you determine whether or not the meeting was successful. If you’re not sure how to measure a meeting’s effectiveness, consider the following factors:

• Did the team come up with relevant, well-thought-out problems to address?
• Was the tone of the meeting positive?
• Did the team develop a mitigation plan for each problem?

If the answer to all these questions is yes, you can consider your meeting a success. If not, don’t worry — bad meetings happen, and there’s always room for improvement. You can always hold another meeting to further hone your team’s skills.

Premortem best practices

• Always prepare for a premortem meeting. Make sure everyone involved knows the project’s goal and the meeting so they can make valuable contributions.
• Remember to ask the right questions and share reasons for potential failure routes.
• Evaluate the meeting’s success. Consider factors such as the number of potential problems identified and whether or not a mitigation plan was developed for each one.
• Keep the tone positive. Remember, the goal is to identify potential problems, not to place blame.
• Let people get creative in the brainstorming session, and make sure everyone feels free to share ideas without judgment.
• Hold regular premortem meetings. This will help your team identify potential problems and conduct a thorough analysis of project development.

How project management software can help you run a premortem

So, there you have it — a basic guide to conducting a project premortem. By taking the time to identify potential problems and their consequences, you’ll be in a much better position to deal with issues when they do arise.

Premortem meetings typically generate a lot of data. With a project management tool like Backlog, you can easily track and manage this data and share it with other stakeholders. Staying organized and having a consistent way to communicate new developments keeps everyone informed, helping them perform their roles well.

Meanwhile, Gantt charts, Kanban boards, and task lists can be created, populated with premortem data, and shared with the team post-meeting. That way, everyone is aware of the potential risks, and you have a process in place to create tasks and manage how they’re addressed.

It’s also a good idea to revisit the premortem document on a regular basis to ensure you’re keeping a close eye on problems as they come up. Having this data readily available in a PM tool makes it easy to do just that.