Dear Reader,
Did you know that there's a term that product managers use to describe your work behind your back?
It's a word they use to describe it when you do extra research to make sure you're designing the right thing.
It's a phase of work that you might call UX, but that's not what they call it.
They call it "product discovery."
The term comes from consultant and author, Marty Cagan [source], and it was invented in 2007 to make product managers understand their real job is discovery, not delivery.
It's where you make decisions about 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 a bit bigger than you might be used to as a designer.
Upcoming Live Courses
|
COURSE: Defining UX Strategy COURSE: Facilitating Workshops Learn to turn meetings into momentum and clear decisions. |
Back in 2007 when Marty coined the term, there was a perception that a product manager's job was to make up requirements and tell everyone what to do.
Sadly, some product managers still act like that in 2022, especially in emerging tech hubs coughcoughberlincough...excuse me.
This is a bit awkward, but um...
If you're a UX designer or researcher, all of it.
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).
I'm writing like the longest email ever because I think it's key to getting human-centered design work done inside of product orgs.
Product discovery is essentially the mentality of UX, and the Double Diamond applied to product management work...with one crucial difference: product people feel more ownership for the outcomes.
It is easier to sell because it comes from product leaders and uses the language that they care about.
Basically, "Can we get more budget for discovery?" is better than saying, "Can we get more budget for research?"
I've noticed that product managers who get into product discovery suddenly start to care more about UX design.
They start to realize the power of understanding problems, and they stop building in the face of uncertainty. That will keep you from becoming a pixel-pusher at a feature factory.
Product designers can use product discovery to become product strategists, consultants, and even product managers.
After all, "building the right thing" is a lot easier when you have UX skills like researching and prototyping.
All it takes is a little zooming out.
So what is product discovery? It's product design.
Until next week!
Jeff Humble
Designer & Co-Founder
The Fountain Institute
P.S. Hannah gave an amazing talk last week called How to Design & Run Workshops. If you missed it, catch the talk here.
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
Title of Newsletter in Titlecase By Hannah Baker Dear Reader, Before we jump into new ideas for the year ahead, we wanted to pause for a moment. If your inbox was anything like ours last year, there’s a good chance you missed a few newsletters. So instead of sending another new idea right away, we put together a curated catch-up, a handful of pieces from 2025 that capture the questions we kept returning to. If you only read a few things from us last year, these are a good place to start. 🧠...
What Can't AI Do in Design in 2026 By Hannah Baker Dear Reader, If you work in design, your feeds are probably saying the same two things on repeat: Here’s everything AI can do for you, and Here’s why you should be terrified. Most of that conversation focuses on tools and job titles: “Will designers be replaced?” “Which roles are safe?” It makes for good headlines, but it’s not how the work actually changes in real life. A few months ago, walking to my studio listening to a Planet Money...
Does the Double Diamond make sense for AI-enabled teams? by Jeff Humble Dear Reader, For twenty years, the Double Diamond has been our north star. Discover, Define, Develop, Deliver. It's elegant. It's teachable. It's in every junior's UX case study. And it made sense…when it was created. All that upfront research made economic sense when coding was the most expensive part of the process. Better to get it right before handoff because it's expensive for engineering to make changes later. But...