What is product discovery?by Jeff Humble Dear Reader, So, there's this secret term that product leadership uses to describe your work behind your back. And today, I want you to be crystal clear on what it is. It's a word they use to describe it when you do extra research to ensure you're designing the best possible idea. It's a phase of work that you might call UX, but they call it something else. They call it "product discovery." What is Product Discovery?The term comes from consultant and author Marty Cagan [source]. It was invented in 2007 to help product managers understand that their real job is discovery, not delivery. Product discovery is the opposite of product delivery. It's deciding what should be built collaboratively (ideally) using whatever data you can gather or generate.
For designers, product delivery is designing the product, and product discovery is deciding what to design.
It's where you decide what problems are worth solving and which solutions are worth designing. Since it's a term that comes from product managers, the scope of work is bigger than you might be used to as a designer. When Marty coined the term in 2007, there was a perception that a product manager's job was to create requirements and tell everyone what to do. Sadly, some product managers still act like that in 2024. Some product organizations skip discovery altogether and make all the designers and developers deliver poorly vetted ideas. Product discovery is about letting the entire team vet ideas before assuming they will be 100% successful. Since the product team decides what gets built, this can be very good for designers, who would have more say in the process. What part of my work as a designer is discovery?This is a bit awkward, but um... If you're a UX designer, service designer, or a design researcher, all of it might be discovery. Your entire process might involve getting ideas ready for delivery, a.k.a. handing them off to UI and devs. Some things you might do in discovery:
These are product discovery activities because they help ensure that you are "building the right thing" (product discovery), not "building the thing right" (product delivery). Hopefully, you realize that product discovery is another word for the research that prepares us to deliver a well-designed experience. To learn more, check out the full article:
Source
Until next time, y'all! ✌️ |
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
I Bought a Mac Mini to Try OpenClaw, the Most Hyped AI Tool of 2026 by Jeff Humble Dear Reader, You've probably heard of OpenClaw 🦞 by now. 145,000 GitHub stars. Headlines everywhere. "The AI that actually does things." This tool is the O.G. dream of AI...automation, not slop. This was the missing piece to my automation system. I had to try it. So I bought an entry-level, 2024 M4 Mac Mini for €590 (on sale in Germany, but they're reportedly selling out in the U.S.) and spent two days trying...
Why Decisions Feel So Hard Right Nows By Hannah Baker Dear Reader, Over the last few months, I’ve been talking with design and product leaders across very different organizations, large companies, smaller teams, fast-moving environments, and slower ones. And I keep hearing the same thing. Their teams are being asked to make decisions faster than ever, and yet, deciding feels heavier than it used to. Not slower, exactly. Just harder. At first, people often explain this in familiar ways: too...
When Speed Stops Being the Bottleneck by Jeff Humble Dear Reader, Quick question: What happens when the thing that used to take 12 weeks now takes 4 days? I've been watching this play out across the industry, and it's wild. Lots of companies aren't sharing their new speeds, but a few are: Code and Theory (an agency that works with Microsoft and Amazon) is building dashboards in 40 minutes that used to take a week. They report cutting time-to-prototype by 75%. Coinbase reports a 2-5x increase...