post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

How to build a companion product and win user trust

mission statement

Deep dive: Crafting your product vision and mission

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

5 ways to invent and simplify as an AI/ML product manager

Jordan is a Senior Product Manager at Planes Studio in London, a digital product agency. Jordan has been launching apps and website for over 8 years. She got her start in digital project management working at design agencies in Los Angeles, and has shaped her career to grow from product owner to product manager, launching global apps like Skin Rocks which has been used by millions of users. She loves gabbing with users, outcomes over output, and never launching on Fridays.

Jordan Jacobi

<p>Product managers strive to ensure the success of their products — but even the most carefully planned and executed product launches can fall short of expectations. While you can’t control everything, planning premortem exercises when you kick off new projects will mitigate risk.</p>
<h3>Lean into the negative</h3>
<p>I always say product managers are the most negative people on a product team. When user testing, we prefer to know what users don’t like, over gathering feedback on what works well &#8211; and project planning is no different. The goal of a premortem exercise is to imagine that your product launch has failed, and then to identify the possible causes of that failure. Essentially, it’s running with worst-case scenarios &#8211; fun!</p>
<p>The benefit of this negativity is that you identify potential risks and problems that could impact the success of your product launch. This approach enables you to get ahead of potential problems early, so you can take steps to address them before they become serious.</p>
<h4>Tips for conducting a successful premortem exercise:</h4>
<h5>1. Set the stage</h5>
<p>To begin, gather your team and explain the purpose of the premortem exercise. Make sure everyone understands that the goal is not to criticise or place blame, but rather to identify potential problems and develop strategies to address them.</p>
<p>When planning a new project kickoff at Planes, I include a premortem in both the internal and client workshops. This “worst-case scenario” thinking exercise can be a good ice breaker and fits into the flow of a kickoff meeting. The more your team can align on this way of thinking at the start of a project, the more they’ll work towards the same goal.</p>
<h5>2. Imagine the worst-case scenario</h5>
<p>Ask your team to imagine that the product launch has failed. What went wrong? What factors contributed to the failure? Encourage your team to think creatively and identify as many potential problems as possible.</p>
<p>What do potential problems look like? Here are a few choice examples, taken from sessions I have run which cover communication issues, poor strategy, and technical concerns:</p>
<ul>
<li>“Not having a collaborative process &#8211; team feeling as though they have no say in the end product” &#8211; Client / Key Stakeholder</li>
<li>“Product doesn’t speak to our audience because we didn’t establish primary users.”  &#8211; Product Manager / Project Lead</li>
<li>“Complex legal requirements dropped in late in the project that have substantial tech implications.&#8221; &#8211; Senior Developer</li>
</ul>
<p><em><strong>Top Tip:</strong> Run a “best case” brainstorm alongside this, to inspire ideas and establish guiding stars.</em></p>
<h5>3. Brainstorm solutions</h5>
<p>Once you have identified potential problem areas, it’s time to get into the possible solutions. Encourage your team to think outside the box and come up with innovative solutions to the problems they have identified.</p>
<p>Concerns can vary from project to project but let’s take the example comments above as a starting point:</p>
<ul>
<li>The client is worried about team contribution/communication</li>
<li>The product manager is anxious about the users</li>
<li>The developer is concerned about unknown requirements that could increase work and push out the deadline.</li>
</ul>
<p>Now there’s transparency over the potential risks, use ‘How Might We’ statements to brainstorm solutions together. For the above, these might look like:</p>
<ul>
<li>“How might we ensure cross-team collaboration”</li>
<li>“How might we prioritize the RIGHT user for the MVP launch?”</li>
<li>“How might we mitigate risks for development?”</li>
</ul>
<h5>4. Prioritise</h5>
<p>Once you have a list of potential problems and solutions, prioritise them based on the impact they may have on the success of the product launch. Focus on the problems that are most likely to occur and have the greatest impact.</p>
<p>The prioritisation task should begin by grouping your concerns under relevant categories, these could be things like communication, project management, and user experience. Once you’ve grouped the categories, assess which risks have the greatest impact for the launch, you can then set about solving the biggest concerns first &#8211; like team communication and product strategy.</p>
<h5>5. Develop a plan</h5>
<p>Finally, develop a plan for addressing the potential problems you have identified. Assign responsibilities and set deadlines for implementing the solutions you have developed. Make sure everyone on your team understands their role in ensuring the success of the product launch.</p>
<p>A set of priorities may look like:</p>
<ul>
<li>Commitment to overwhelming honesty &#8211; making sure this comes through in communication and ensuring transparency over any issues.</li>
</ul>
<ul>
<li>Keep it simple &#8211; having a good and reliable product for MVP</li>
</ul>
<ul>
<li>Mandatory stakeholder attendance at retros + key meetings</li>
</ul>
<h3>Premortems help you to de-risk</h3>
<p>Premortem exercises are an excellent way to identify potential risks that could affect the success of your product launch. By sprinkling in a bit of pessimism and conducting a premortem exercise, you can develop strategies to mitigate those risks and increase the likelihood of a successful launch.</p>
<p>&nbsp;</p>

core/freeform

Building Consumer-Grade Experiences for the Enterprise By Ciara Peter

What Makes a Great Product Manager by Graham Siener

The GIST Framework by Itamar Gilad

Scaling the Product and the Team by Rachael Shah

Decisions, Debt, and Other Dilemmas by Janna Bastow

Hacking Your Product Career by Gibson Biddle

How Medicine and Research Translates to Patients by Shree Patel

The Future of Product Management by Richard Harrison

Data Science and Digital Businesses by Ali Gulez

You Need A Product Strategy by Sam Odio

Premortems in product management; why pessimism pays

ProductTank Pune

ProductTank Kraków

ProductTank Cardiff

ProductTank Bangalore

ProductTank Mumbai

ProductTank Johannesburg

ProductTank Tauranga

ProductTank Bielefeld

ProductTank Auckland

ProductTank Vilnius

ProductTank Timisoara

ProductTank Stockholm

ProductTank München

ProductTank Düsseldorf

ProductTank Birmingham

ProductTank Norwich

ProductTank Heidelberg

ProductTank Malmö

ProductTank Amsterdam

ProductTank Barcelona

ProductTank Newcastle Upon Tyne

ProductTank London

ProductTank Curitiba

ProductTank Brisbane

ProductTank Perth

ProductTank Málaga

ProductTank Buenos Aires

ProductTank Tokyo

ProductTank Braunschweig

ProductTank Edinburgh

ProductTank Pittsburgh

ProductTank Dubai

ProductTank Vienna

ProductTank Bristol

ProductTank Washington

ProductTank Valencia

ProductTank Raleigh

ProductTank Brno

ProductTank Paris

ProductTank Orlando

ProductTank Montréal

ProductTank Bangkok

ProductTank San Diego

ProductTank Hong Kong

ProductTank Charlotte

ProductTank Exeter

ProductTank Manchester

Premortems in product management; why pessimism pays

Jordan Jacobi

Read more

Comments