Out of the 6 steps laid out here, the first 4 are done during discovery.
Think of product discovery like an equivalent to mise en place in professional cooking – it’s where you collect all the necessary ingredients to build your product.
After discovery, all you need to do is put them together and develop your product.
And by doing product discovery, you’ll prevent the same from happening to your company.
A good example of successful idea validation is the online shoe retailer Zappos.
Back in 1999, founder Nick Swimmum did an experiment – his hypothesis was that customers would be willing to purchase shoes online.
So, he teamed up with local shoe stores, took pictures of their inventory, and promised he would buy the shoes at full price if customers purchased them online.
And they did – the rest is history.
Minimizes risk
Another major benefit of product discovery is that it minimizes the risks involved in developing a product.
But, how does doing product discovery minimize these risks?
Of course, product discovery isn’t a silver bullet – you still need to properly manage your product’s development.
However, doing discovery gives you all the tools you need to create a clear and focused development roadmap.
And that alone will help you minimize most of these risks.
But, product discovery also minimizes the biggest risk of all – not having a product-market fit.
And that’s why discovery is so important.
Top product discovery tools
Now, let’s take a look at some of the top product discovery tools you should use:
Contentsquare – a digital experience platform, Contentsquare offers advanced analytics that show you how users interact with your product.
Figma – Figma is a collaborative design tool you can use to create wireframes, user flows, and prototypes during discovery.
Google Workspace – a suite of productivity and collaboration tools, Google Workspace is a good choice as an all-in-one platform to organize your product discovery process.
Hotjar – Hotjar is a heatmap and digital analytics tool that tracks how users interact with your product, so you can identify problem areas and see how users actually use your product.
Jira Product Discovery – a dedicated product discovery tool in Jira, Jira Product Discovery will help you organize the data, ideas, and insights you gather during discovery.
Maze – Maze is a continuous product discovery platform that allows you to conduct user testing at scale and iterate your product based on user feedback.
Miro – Miro is a digital whiteboard tool that supports real-time collaboration, making collaboration easier if you discovery team is remote.
Productboard – a product management tool, Productboard is versatile and has a number of features that will help you manage your discovery efforts effectively.
Slack – a cloud-based messaging app built for businesses, Slack is a great tool for organizing communication between members of your discovery team and other stakeholders.
Of course, you should pick the tools that suit your specific business needs, but these tools are good choices if you don’t know where to start.
Now, let’s cover how to do product discovery step-by-step.
How to do product discovery
Here, we’ll discuss the steps you need to take for successful product discovery, which are:
Assemble your discovery team
Start with market research
Research your users
Ideate and create a product hypothesis
Create wireframes and user flows
Test and validate your idea
Pivot or continue with development
We’ll also give you key tips for each step.
Let’s go!
Assemble your discovery team
Before starting product discovery, you need to assemble your discovery team.
Getting this step right is crucial for the success of your product discovery process.
So, what should your discovery team look like?
For starters, your team should be cross-functional.
And there’s good reasons for that.
A Harvard Business Review study found that teams that are more cognitively diverse solve problems faster and adapt better to change than non-diverse teams.
Cross-functional teams in product discovery are a perfect example of cognitive diversity in action.
Also, another Harvard Business Review study found that cross-functional teams supported by executives reached a 76% project success rate.
In short, cross-functional and cognitively diverse teams are the way to go.
But, which roles should you include? And how big should the team be?
For starters, you need to include the product trio in your team.
These 3 roles are key to the success of your discovery process and will form your core discovery team.
Of course, you can include other relevant stakeholders or extra designers and engineers, depending on your needs.
But, your discovery team should include between 4and7 team members, not more.
Just make sure that your hypothesis is falsifiable i.e. that it can be disproven.
And it can be as simple as “our users will find value and enjoy using our product”.
But, you should develop a more detailed hypothesis to validate your product idea properly.
Let’s say you’re building a fitness app.
Learn from a software company founder.
Make your software product successful with monthly insights from our own Marko Strizic.
One of your hypotheses can be: “We believe that adding a social networking feature to our app will result in a 20% increase in our user engagement rate”.
Then, your next step is validating that hypothesis.
But, you also need to design your product before fully validating it – and that means creating wireframes and user flows.
Key tips for ideation and creating a product hypothesis
Create a safe and inclusive space for ideation – make sure that all team members can share their thoughts and ideas openly and without fear
Create several hypotheses – you should create several product hypotheses to thoroughly validate your idea
Include diverse perspectives – including diverse perspectives and insights during ideation and brainstorming will make those sessions more productive and well-rounded
Create wireframes and user flows
Once you’ve done your research and decided on your product’s features, your next step is creating wireframes and user flows.
They’ll form the basis of your product’s final design, and they’re some of the most important deliverables you get from product discovery.
And you can use them to validate your product hypothesis, too.
But, what exactly are wireframes and user flows?
Wireframes are initial sketches of your product’s user interface (UI) – think of them like a blueprint for your product.
And they can be as simple as a hand-drawn rough sketch.
Wireframes are great visual guides that illustrate how your product will work.
But, wireframes by themselves aren’t enough – you also need to create user flows.
User flows are diagrams representing the typical user’s path when using your product to complete a task.
The main benefit of user flows is that they’ll show you if your users will experience friction when using your product.
User friction refers to any obstacle they face using your product, like overly complicated navigation.
And solving that friction and improving your product’s design is key to a good user experience (UX).
Key tips for creating wireframes and user flows
Start with low-fidelity wireframes – create rough, low-fidelity wireframe sketches to get the basics of your design done quickly
Focus on UX – when you’re creating wireframes and user flows, focus on how your users will use your product and how you can improve their experience
Iterate based on feedback – get feedback from stakeholders and users and use it to improve your wireframes and user flows
Test and validate your idea
After you’ve done your initial research, created a hypothesis, and drafted your initial design, your next step is to test and validate your idea.
We’ve mentioned that validating your idea is one of the main benefits of product discovery.
It’s also an ongoing process throughout product discovery – every previous step we’ve covered also serves to validate your idea.
But, once you’ve done all of them, you still need to fully validate your idea.
The game wasn’t very successful, but their communication tool showed promise. So they pivoted in order to fully focus on building Slack.
The rest is history. In December 2023, Slack had a market capitalization of $26.51 billion.
But, what should your next steps be if your idea is validated?
If you’ve built an MVP, you need to gather all the feedback you’ve received and prioritize which features you’ll add next.
You should also implement continuous discovery.
This way, you’ll be on top of your users’ evolving needs and keep your product relevant.
And that’s key to its long-term success.
Key tips
Create a feedback loop – having a feedback loop in place will help you consistently iterate based on your users’ feedback
Iterate on your MVP – if you’ve built an MVP to validate your idea, iterate on it and add new features and functionalities
Assess the risk of pivoting/continued development – once you’re done with discovery, make sure to do a thorough risk assessment before you pivot to another idea or continue with development
Product discovery: FAQs
Product discovery is the process of researching your market and validating your product idea before developing it.
Product discovery is important because it validates your product idea before you commit to full development – this will help you minimize the risks involved and develop your product faster.
The key steps for successful product discovery are:
Assemble your discovery team
Start with market research
Research your users
Ideate and create a product hypothesis
Create wireframes and user flows
Test and validate your idea
Pivot or continue with development
Your core discovery team should include the product trio (product manager, product designer, and solution architect/lead engineer) but you can include other team members and relevant stakeholders, depending on your needs.
Need discovery for your product?
Do you have a great product idea but don’t know how to turn it into reality?
Don’t worry, we’ve got your back.
With our thorough product discovery process, we’ll make sure your idea fits the market and meets your users’ needs.
If you want to learn more, check out our process and feel free to get in touch with us.
Ivan is truly passionate about what he does. In his role as Lead Product Manager, his strength is shaping products that not only meet market needs but also wow their users. And with over a decade of experience at software companies and startups, he knows all the ins and outs of building successful products.
In his spare time, he enjoys staying active, whether it's hitting the gym, playing sports, or hiking. His dream office? A terrace in Komiža on the island of Vis, taking in the warm Adriatic sun.
AI is revolutionizing the way we work and product discovery is no exception. In this article, we'll discuss 5 ways you can use AI in product discovery.
Product discovery workshops are a great way to generate ideas and align everyone with your discovery goals. Here, we'll show you how to lead one step by step.