/gather
Back

What is \*enough\* product discovery

What is *enough* product discovery when you’re under pressure to build and launch fast? I’ve had many product managers ask me if they’ve done enough discovery, and how they can figure it out. Recently, I decided to put together a simple 'guide' to help one of them. I kept it as simple as I could because I know PMs are busy 🙃 To know if you've done enough discovery, you should generally - 1️⃣ Understand the risk of building/launching 2️⃣ Check whether you can answer a few key questions Product teams need to understand how much risk is involved in building and launching. The amount of risk and the amount of discovery should align. High risk = we need a larger amount of customer discovery to de-risk a future launch. Lower risk = we can often test in the market and adjust as we go. But even when risk is low, it’s typically not worth the cost to build a product update unless we're confident it solves user needs. Simple, right? But most product managers I've met don't systematically evaluate whether their discovery work aligns with *risk* and *confidence in the user need*. So recently, when another PM asked me if they'd done *enough discovery*, I made a flow chart of YES and NO questions to help her figure it out herself. Here's how to very quickly check if you've done enough discovery to start building. Plus, a few suggestions for the customer discovery to run next. #productdiscovery #productmanagement #prodmgmt #startup

  • ![No alternative text description for this image]()

See more comments