Discovery Mindset

Discovery is how product managers replace those guesses with evidence. This topic is their toolkit - the interviews, observation, and research that decide what is worth building before anyone designs it. You're learning it for two reasons: so you design the right thing, and so you can hold your own when those decisions get made.

Why Designers Need This

Discovery isn't the PM's private job. The best product decisions come from a designer, a PM, and an engineer looking at the same evidence together.

You stop guessing too.A designer who has watched real users struggle argues from evidence, not taste - and wins those arguments.

You earn a seat.Understanding risk, discovery, and opportunity is what moves you from "the person who makes it pretty" to a partner in deciding what gets built.

Assumptions & Product Risk

Every idea for a product is really a stack of guesses: people want this, they'll understand it, we can build it, and it'll make money. Each guess can be wrong, and each wrong one sinks the work in a different way. Naming these guesses - and knowing which are riskiest - is the first move in discovery.

The Four Big Risks

Marty Cagan, in Inspired, sorts product risk into four questions every idea has to survive. Ask them in this order:

Value risk:will people want it, and choose it over what they use now? The most common killer - a well-built product nobody needs.

Usability risk:can people figure out how to use it? The one designers most obviously own.

Feasibility risk:can engineering actually build it, with the time, tech, and skills on hand?

Business viability risk:does it work for your business - the model, the cost, the legal and brand limits?

An idea can be usable, buildable, and good for the business, and still fail on value. That's why value gets tested first and hardest.

Assumptions Are Bets

Turn each risk into plain assumptions and write them down. "Agencies will switch tools to get one shared status view" is a value assumption. "We can pull data from their existing tools" is a feasibility one.

Now rank them by two things: how risky (how badly it hurts if you're wrong) and how unknown (how little evidence you have). The assumptions that score high on both are what discovery goes after first. You're not testing everything - you're hunting the few beliefs that could sink the whole idea.

Pro tip: If an assumption feels obviously true, ask what evidence you actually have. "Obvious" and "untested" often sit on the exact same belief - and that's the dangerous one.

Why Designers Should Care

You already own usability risk. The move that changes your career is getting into value and viability - the risks that decide whether your design gets to matter at all.

A designer who says "before we build the dashboard, let's test whether agencies would even switch" is doing product work. It reframes you from someone who executes decisions to someone who shapes them. And it protects your own effort: the surest way to waste months of great design is to pour it into an idea whose value risk nobody checked.

Where AI Helps

Prompt: "Here's a product idea: [describe]. List its key assumptions sorted into the four product risks - value, usability, feasibility, viability. For each, rate how risky and how unknown it is, and flag the top 3 to test first."

AI surfaces assumptions you're too close to see; you judge the ranking.It's good at listing the hidden beliefs in an idea, but which ones are truly risky depends on context it doesn't have - your market, your team, your business. Use its list as a starting draft, then rank with what you know.