As a product team, you're always trying to find ways to not just make better decisions, but to make faster decisions too. A helpful tool that product teams can draw on is a concept review. In this article, we'll define what a concept review is, discuss how to go about conducting one, and explore how it can help you make better product decisions when prioritizing potential solutions. We'll also provide an example of a concept review in action, so you can see for yourself how you might use it in your own use-case.
A concept review is a structured process for evaluating and prioritizing different concepts – in other words, product ideas. The goal is simply to figure out which concepts are most promising and which ones should be discarded. This process is typically done as a team, with each member offering their insights and opinions.
The concept review can be a useful step in the product discovery process because it helps teams get a more concrete idea of what a potential solution might look like, ensuring more accurate prioritization and ultimately a smarter use of their time and effort. Having just a vague idea of the potential effort needed to deliver a solution often leads to poor scoping and ends with teams prioritizing features that they would never have prioritized, had they known the real effort required to pull them off. A concept review is a simple way to make more confident decisions and prevent you from investing time and money into concepts that ultimately fail to deliver value to your users.
There are several methods for conducting a concept review, but two of the most popular are ranking as a team and using the Delphi method. We’ve made a breakdown of these two approaches below.
Whichever method you choose, it's essential to have a clear evaluation framework in place. This should include criteria for assessing the potential impact, feasibility, and ultimate alignment with your desired outcomes. There is no one way to conduct a concept review, so feel free to adapt it to your way of working.
By evaluating product ideas in a structured and collaborative way, a concept review can help you make better product decisions. Here are 3 ways in which concept reviews can help you:
Let's say you're a product manager at a SaaS company, and you're looking to improve your in-app onboarding experience. You gather your team for a concept review, and together you brainstorm several different concepts, including:
The first thing you need to do is clearly define each concept. A detailed description is a must. Adding a list of ranked user stories and a rough prototype is even better.
Take the guided product tour as an example. The user stories could look something like this:
💡 Pro tip: Use ChatGPT to quickly generate user stories for inspiration.
Once the concepts are defined, you can use the ranking as a team method, with each team member ranking each concept on a scale of 1-10. Use whichever framework you like to use. A good option is to rank on Desirability, Feasibility, Viability as key factors.
Once you’ve tallied the scores, you can prioritize your solutions accordingly. Just be aware! Solving the right opportunity and having the right customer insights to make decisions confidently are still crucial for good prioritization.
A concept review is a valuable tool for product teams looking to make more informed product decisions. By evaluating product ideas in a structured and collaborative way, you can quickly identify the most promising concepts and avoid wasting time and resources on ideas that are unlikely to succeed.
Whether you choose to conduct a concept review using the ranking as a team or the Delphi method, make sure to consider the wider context of your product discovery efforts. Concept reviews can be helpful for evaluating ideas for your product, but they should not be used in isolation.
.png)
