Ant Murphy Profile picture
Feb 15 6 tweets 2 min read
Pre-Mortems are one of the most underused tools in your #ProdMgmt toolkit.

Unlike Post-Mortems which most are familiar with, rather than waiting until the end when everything has already gone wrong. A Pre-Mortem is done at the start of a project or item of work.

/1
During a Pre-Mortem the team and relevant parties will seek to predict what might go wrong and then work backwards to identify ways in which they could mitigate those things from happening.

A framework I like to use to facilitate Pre-Mortems is the matrix above.

/2
It’s a risk matrix which looks to prioritise according the risk's likelihood of occurring and the impact.

High Likelihood + High Impact = Avoid
Low Likelihood + High Impact = Reduce/Exploit
High Likelihood + Low Impact = Share/Transfer
Low Likelihood + Low Impact = Accept

/3
❌ AVOID
These are your high impact & high likelihood risks and therefore should be avoided.

🔻 Reduce/Exploit
High impact risks but low likelihood risks. Seek out ways to reduce their impact or exploit them in order to gain a benefit from (risk vs reward).

/4
🤝 Share/Transfer
High likelihood risks however low impact. Look for ways to either transfer or share the risk between other parties.

✅ Accept
These are low impact and low likelihood risks, therefore the cost to avoid or reduce these risks often outweigh the benefits.

/5
Anyone with experience with Pre-Mortems I’d love to hear about it in the comments!

Do you regularly run Pre-Mortems at your organisation?
What benefits have you found from them?

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Ant Murphy

Ant Murphy Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ant_murphy

Feb 5
Sick of Jira?
Struggling to manage your Product Backlog?
Lost in the vastness of your backlog?

Here are 8️⃣different ways to organize your Product Backlog 🧵👇

(including templates)
1️⃣ User story Map

User Story Maps are a great way to quickly build out your backlog for the first time, it’s also a powerful tool for release planning.

For more mature products I’ve often split my user story map by customer archetype, JTBD and even problem spaces.
2️⃣ Funnel Backlog

Literally a funnel! A great way to visualise your backlog and to actually physically restrict the number of product backlog items that are at the “top” (well “right”) of the backlog.

This form of backlog is great to help with prioritisation and focus.
Read 10 tweets
Oct 28, 2022
Acquisition vs Activation:

Acquisition is when you get them on board

But activation is when you get them to use your product in a meaningful way.

It’s worth understanding the difference.

A 🧵 (incl. inactive vs disengaged users)

/1
Each product will define this differently.

eg. I had a FinTech client that was tracking DAU however, how many ppl check their bank acc daily? Not many. MAU would be more applicable - better: understand cust behaviour and define how to measure the behaviour you want to see.

/2
Acquisition is getting them in the door. Typically, did they buy it/sign up?

This differs from Activation... because you can sign up for Netflix but never watch a movie… you can download Uber and never take a ride.

/3
Read 10 tweets
Oct 14, 2022
Q: "If only the most important Product Backlog Items are prioritized at the top anyways. Who cares if you have an infinitely long Product Backlog?"

The first problem is that things change.

👇👇

1/
Market, customer, business needs and priorities change over time. The product changes too.

Something that was put on the backlog even 6 months ago can quickly become obsolete. Not to mention something that was added years ago - how likely is that to still be relevant now?

2/
The second problem is management:

It's hard to keep a track of what's in a backlog when it's hundreds of items long.

This can lead to duplication and wasted time and energy trying to manage it.

3/
Read 6 tweets
Oct 9, 2022
Paradoxes of Prod Mgmt (*brain dump)

♥️ Solve customer problems vs 🎯Achieve biz goals
🛠 Good enough vs 🤩Amazing experience
💪 Confident vs 🤷‍♀️Uncertain
🎨 Creativity vs 📦Reality
🔨 Pragmatic vs 🚀Ambitious
💡 Invention vs 🧰 Maintenance
🕰 Short-term vs 🛣 Long-term

/1
📈 Growth vs 🔒 Retention
📊 Data vs 🤔Intuition
✅ 'Come up with ideas like you're right' vs ❌ 'Test them like you're wrong'
🏋️‍♀️ Challenging the team vs ⚔️ Protect the team
🏆 Give credit vs 🙋‍♀️Take responsibility for failures
💯 All responsibility vs 👌Zero authority

/2
⚠️ Take risks vs 👷🏾‍♀️Play it safe
🚧 Safe to fail vs 🚀Deliver successfully
📦 Sell the current product vs ⭐️Sell the dream
✨ Communicate the vision vs 📣 Communicate progress
🔝Where we going vs 🔜What do we do next
🙌 "Amazing job" vs 💪"We can do better!"

/3
Read 4 tweets
Sep 1, 2022
@philaraujo1 asked on LI: "What will be ur first advice for a new Product Manager?"

Not a perfect list, but the first to come to mind were...

💭You can't make all the decisions:

Find ways to empower those around u to make smart decisions. Don't be the bottleneck!

/1
🦸‍♀️🦸You can't save the world:

Seems strange, but it was something a mentor said to me ages ago that stuck. Basically a reminder that u can't do everything.

Ruthlessly prioritise: prioritise the work/cust/ur day/ decisions/etc. Accept that u will miss things/be imperfect.

/2
🫶🧑‍🤝‍🧑Every problem is a human problem:

From your stakeholders, the team, to your users. It's all about people. Therefore I've found that learning about behavioural economics and human psychology has been one of the highest leverage things I've learned as a product person.

/3
Read 8 tweets
Jul 12, 2022
Driver + Navigator

This is one of my favourite models to encourage collaboration and bring clarity to the messy nature of product work.

Rather then having your typical RACI or accountability framework, map out:

🚗 Who is ‘driving’? and
🗺️ Who is ‘navigating’?

1/
For example, let's take a look at the product process through the lens of the product trio.

At the start we're prioritising, setting the strategy and deciding on what to focus on. During this phase, it's typically led by the PM - they would therefore be the ‘driver’.

2/
But any good PM knows they shouldn’t do this alone.

This is where the ‘navigator’ comes in.

They drive the activity forward and are responsible for making sure it happens but they do it collaboratively with design and engineering (and others). These people are ‘navigators’.

3/
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(