How I Kill Bad Ideas Before They Waste My Time

My 'Pre-Mortem' Playbook: How I Kill Product Ideas Before They Drain My Time and Sanity

I remember it like it was yesterday. I’d spent weeks, maybe even two months, pouring my heart and soul into building a new SaaS tool.

It was going to be revolutionary, solving a problem I thought a lot of people had. I was so excited to launch.

Then came the launch. And… crickets.

Absolute silence. I’d built something I was proud of, but nobody actually wanted it.

It was a brutal lesson in wasted effort, and it happened more times than I care to admit in my early days.

This painful cycle of building and realizing nobody cared was a huge drain on my time, my sanity, and my dwindling savings. I knew I had to find a better way to validate ideas before I got too emotionally and physically invested. That's when I developed my "pre-mortem" playbook.

The goal is simple: kill bad ideas before they kill my motivation. It’s about being brutally honest with myself and potential users early on.

My 3-Step 'Pre-Mortem' Playbook

This isn't about overthinking. It's about smart, focused validation. Here’s how I do it:

Step 1: The 'Funeral' - Imagine It Failed

This is the most important step, and it’s surprisingly effective. I force myself to imagine the product has already launched and, predictably, it’s a complete flop. Then, I brainstorm why.

I grab a notebook or open a blank document and write down every single reason I can think of for its failure. Think of it as writing the eulogy for your product idea.

• Did no one understand the problem?
• Was the solution too complex?
• Was there no real market demand?
• Did competitors already solve this better?
• Was it too expensive to build or too expensive to buy?
• Did I target the wrong audience?

By facing the worst-case scenario upfront, I can proactively identify potential pitfalls and start thinking about solutions or, more often, reasons to abandon ship.

Step 2: The 'User Interview Blitz' - 5 Targeted Conversations

Once I've a clearer picture of potential failure points, I need to get real-world feedback. I aim for five targeted conversations with people who I believe actually experience the problem I'm trying to solve.

These aren't casual chats. I come prepared with specific questions designed to uncover their pain points and see if my proposed solution aligns with their reality.

I avoid asking "Would you use this?" Instead, I ask things like:

• "How do you currently solve [the problem]?"
• "What's the biggest frustration you've with your current solution?"
• "If you could wave a magic wand, what would the ideal solution look like for you?"

The key here is to listen more than I talk and to look for genuine enthusiasm or, conversely, polite dismissal.

Step 3: The 'Pain Point Ranking' - Quantifying Severity

After those five conversations, I've a lot of qualitative data. Now, I need to quantify it. I go back to my notes and rank the severity of the problem for each person I spoke to.

I use a simple scale, maybe 1-5, where 1 is "a minor annoyance" and 5 is "a critical, time-wasting, soul-crushing problem." I also note down how much they'd ideally pay to solve it, even if it's just a hypothetical number at this stage.

If most people I talk to rank the problem as a 1 or 2, it's usually a sign that it's not a big enough pain point to build a product around. If they're consistently ranking it as a 4 or 5, and expressing a willingness to pay, then I know I’m onto something.

This step helps me filter out ideas that might sound good but don't have enough market heat.

The Takeaway: Kill Ideas Ruthlessly, Build Smarter

This pre-mortem process has saved me countless hours and a ton of frustration. It’s not about being negative; it's about being pragmatic.

Here’s how you can start applying this today:

1. Embrace the 'Funeral': Before you write a single line of code, spend 30 minutes imagining your idea has failed and list all the reasons why.
2. Talk to 5 People: Identify five potential users and schedule brief calls to understand their pain points without pitching your solution directly.
3. Rank the Pain: Quantify the severity of the problem based on your conversations. If it's not a significant pain, it's probably not a viable product.

By doing this, you drastically reduce the risk of building something nobody wants. You can then focus your precious time and energy on ideas that have a genuine chance of success.

It’s better to kill a bad idea on paper than to kill your enthusiasm by building it. Happy validating!