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.
Every 2024 Newsletter You Missed by Jeff Humble Dear Reader, It's that time of the year again! Here are all the newsletters you missed in 2024 from the Fountain Institute: A Designer's Uncertain Path to Success Design Strategy vs. Design Vision: What's the difference? Is Poor Communication Hindering Your Projects? Balancing Freelance Life with Maya McBeath Innovation by Design with Cristina Colosi Shaping the Future of the Guild of Working Designers Figma Skills Won't Get You Promoted See...
Turning Challenges into Confidence: Lessons from Dyslexia By Hannah Baker Dear Reader, When I was seven, I was an expert at pretending. I could "read" picture books without actually decoding the words, using context to fill in the gaps. It wasn’t until my mom, a teacher, noticed I was faking it that I was tested and diagnosed with dyslexia. What followed were years of frustration, advocacy, and learning how to embrace a brain that simply worked differently. While my initial reaction was...
28 Ways to Test an Idea (that is NOT an A/B Test) by Jeff Humble Dear Reader, Today I'm thankful for all the ways you can test that are not A/B tests. Executives and product people think A/B testing is the only thing on the testing menu. 🍽️ For me, it doesn't usually make sense to A/B test. Here's why: A/B tests should happen as late as possible. They might be the most scientific approach, but they require a lot of traffic. Plus, they're usually live and in code, so everything must be...