Product ideation involves the whole product team and entails a sequence of steps.<\/p>\n
What is a product ideation process?<\/h2>\n
While for many teams it may be synonymous with brainstorming, there’s much more to the product ideation process.<\/p>\n
For starters, brainstorming is just one part of it. To make brainstorming sessions productive, it needs to be based on data, so it requires prior customer research.<\/a><\/p>\n Once the ideas are generated, the product ideation process guides the team and helps them choose the best product ideas, tweak them, present them to the stakeholders to get their buy-in, and then implement them.<\/p>\n Overall, the product ideation process is methodical and structured and goes beyond individual idea-generation sessions.<\/p>\n The product ideation process is an essential part of the product development process, critical to its success.<\/p>\n Product ideation helps teams identify ways of improving the product.<\/p>\n The process involves customer research. By gathering user feedback<\/a> or customer requests<\/a> teams are able to pinpoint specific parts of their product that need improvement.<\/p>\n User feedback<\/a> and product usage data <\/a>allow product managers and product owners<\/a> to gain an intimate understanding of user needs.<\/a> They can use the insights to create new and original ideas to solve user pain points<\/a> and satisfy their desires.<\/p>\n This approach to improving the product is superior to simply copying the features that competitors offer.<\/p>\n That’s because the latter basically means constantly playing catch-up with your rivals. In the best-case scenario, it allows a team to build only a parity product <\/a>that is very difficult to differentiate.<\/a><\/p>\n Developing a product based on user feedback<\/a> and customer requests<\/a> enables you to satisfy their needs more successfully.<\/p>\n This in itself is enough to improve customer retention<\/a> because such products deliver better value.<\/p>\n It also sends a clear signal to your customers that you care about them and this increases customer loyalty and drives retention even further.<\/a><\/p>\n Product ideation is an iterative process consisting of five key stages.<\/p>\n Gathering user feedback<\/a> and requests is the first stage in the process.<\/p>\n Listening to your users is essential to successfully diagnose the problems that you could solve for them.<\/p>\n This refers both to the problems specific to their business contexts as well as the pain points <\/a>they’re experiencing while interacting with your product.<\/p>\n Once you understand the problems, it’s time to generate creative ideas on how to address these problems.<\/p>\n There are different approaches to that, and we’re looking at some of them later on.<\/a><\/p>\n Whichever technique or method you choose, it’s key to keep these sessions relevant to ensure alignment between user problems and solutions.<\/p>\n It’s natural that some of the proposed solutions will be better than others. That’s why the aim of this stage is to whittle down the options and choose the ones that are most promising.<\/p>\n There are different techniques you could use here, like dot voting.<\/p>\n Next, prototype testing<\/a> and more customer research<\/a> are necessary to validate these ideas<\/a> and choose a single one to implement.<\/p>\n Mind you that at this stage we’re already looking at prioritizing <\/a>different solutions.<\/p>\n However, a similar process should apply earlier on also the user problems. This is to make sure that the team is working on opportunities that will drive the biggest value<\/a>.<\/p>\n Having selected the best improvement idea, it is time to implement it.<\/p>\n Implementation is an interactive process and apart from building the solutions it also involves testing<\/a> them to make sure they meet the QA standards. More importantly, they need to do the job they’re designed to.<\/p>\n When you develop the solution and test them thoroughly, it’s time to close the feedback loop <\/a>and let users know about the changes you’ve implemented.<\/p>\n In case of bigger updates, like those that involve substantial changes to the UI, it may be necessary to amend your support materials, design new onboarding flows<\/a>, and train the customer success<\/a> team.<\/p>\n That’s not the end though, because as soon as users start using the new feature or functionality, you need to get back to collecting user feedback. That’s to assess how successful the feature is and find fresh ideas for improvements.<\/p>\n There are plenty of product ideation techniques that you could use to identify problems and create ideas. Let\u2019s have a look at a few product team favorites.<\/p>\n “How Might We?” questions are a powerful technique that allows teams to turn their research insights into opportunities.<\/p>\n How do you use the “How might we” statements?<\/p>\n Start by generating as many statements as possible. They need to be related to specific user problems and detailed but not constraining.<\/p>\n For example, if user feedback shows it’s difficult to find the demo booking button, the statement could be ‘How Might We change the UI to make demo booking easier?’<\/p>\n Next, choose the questions which have the potential to deliver the most value and use them as a springboard for idea generation.<\/p>\n Brainstorming sessions are a very popular means of generating ideas and sharing them with other team members. They also have the potential to energize the team and increase their engagement.<\/p>\n However, research shows they achieve the best results when participants have a chance to prepare for the sessions individually before sharing and discussing ideas collectively.<\/p>\n That’s because individuals tend to generate more ideas individually and it helps teams avoid such antipatterns as groupthink or social loafing<\/p>\n If you still want all members to generate ideas together, why not try brainwriting instead?<\/p>\n Instead of shouting out their ideas, give participants time to write their solutions down individually. When the time is over, they pass them on to another person, who then builds upon them.<\/p>\n Storyboarding is a technique for designing the user journey <\/a>or improving existing processes.<\/p>\n A storyboard is a visual representation of the solutions and how they fit into the user experience.<\/p>\n It allows teams to focus on the impact that their ideas could have on the user. It also helps identify assumptions underpinning the solution and problems they could come across.<\/p>\n SCAMPER is a simple technique that encourages the team to look at existing solutions and tweak them to address the problem better.<\/p>\n What kind of tweaks are we talking about? The acronym stands for S<\/strong>ubstitute, C<\/strong>ombine, A<\/strong>dapt, M<\/strong>odify, P<\/strong>ut to another use, E<\/strong>liminate, R<\/strong>everse.<\/p>\n For example, if you have problems with users reaching the activation stage<\/a>, your team could look for ways to combine a few steps of the process to remove unnecessary friction<\/a>.<\/p>\n To realize the benefits of the product ideation process, the product manager or product owner needs to implement a comprehensive customer feedback workflow management system<\/a>. This means harnessing various methods to continuously collect feedback.<\/p>\n One way to collect ideas for product improvements is by collecting feature requests<\/a> in-app. After all, your users, especially the most committed ones, know their own pain points better than anybody else.<\/p>\n You can design the right form with tools like Userpilot<\/a>. Next, you add the widget to your resource center<\/a> or place it in another prominent part of the UI so that users can easily access it.<\/p>\n Of course, you still need to analyze and filter the requests<\/a>. But even if you decide not to proceed with the feature development, you can still gain some valuable insights into how to improve the product<\/a>.<\/p>\n Just like feature requests, user feedback is fairly easy to collect in-app.<\/p>\n Modern adoption tools allow you to build fully customized microsurveys<\/a> without the need for any coding.<\/p>\n And with Userpilot’s new mobile features<\/a>, you can now also easily create comprehensive and intuitive surveys and trigger them directly in your mobile apps.<\/span><\/p>\n There are three main things to remember when it comes to feedback collection.<\/p>\n First, make sure to collect qualitative feedback<\/a>. While quantitative feedback, like NPS <\/a>or <CSAT is great for tracking trends or segmenting users<\/a>, it’s not enough to get an in-depth understanding of their needs. To make up for it, simply include follow-up questions in your surveys.<\/p>\n Next, make sure to target the right user groups. Power users<\/a> may be a good group to start with, but only if you’re collecting feedback on features that are relevant to them.<\/p>\n Finally, trigger your surveys contextually, that is at the right time and in the right place. For example, asking for feedback immediately when the user interacts with a feature is more effective because the impression is still fresh in their minds.<\/p>\n No matter how well you think through the timing of microsurveys, it may not always be right for the user.<\/p>\n As they are rushing to complete their tasks, they may not be in the right mind space to respond, no matter how short or simple the questions are. It doesn’t mean they don’t want to help though.<\/p>\n That’s why apart from collecting user feedback actively, it’s a good practice to incorporate feedback widgets and collect passive feedback.<\/a><\/p>\n This gives your users the opportunity to share their thoughts at the time that is best for them.<\/p>\n Customer interviews are an essential part of the product ideation process.<\/p>\n Collecting user feedback in-app can signal there is an issue that needs your attention and shed some light on why it’s occurring. However, to truly understand the nature of the problem, you need to talk to the users.<\/p>\n That’s why always schedule interviews to follow up on your surveys.<\/p>\n Better yet, make a habit of interviewing your customers regularly to facilitate the continuous discovery<\/a> of new opportunities.<\/p>\nWhat are the main benefits of product ideation?<\/h2>\n
Identify areas of improvement<\/h3>\n
Avoid product parity<\/h3>\n
Become customer-centric and increase retention<\/h3>\n
What are the stages of a product ideation process?<\/h2>\n
User feedback collection<\/h3>\n
Idea generation based on data<\/h3>\n
Narrowing down selection stage<\/h3>\n
Implement the idea during the development process<\/h3>\n
Close the feedback loop<\/h3>\n
![\"Closing](\"https:\/\/images.storychief.com\/account_6827\/Feedback-Loop-product-ideation_47ec92beb690a32b7b7f569cd1e29cdd_800.png)
<\/picture>Popular product ideation methods and techniques<\/h2>\n
“How might we” statements<\/h3>\n
Brainstorming and brainwriting<\/h3>\n
![\"Brainstorming](\"https:\/\/images.storychief.com\/account_6827\/figjam-product-ideation-brainstorming_cdb3e74bf43773fdea1ad61344e626ee_800.jpg)
<\/picture>Storyboarding<\/h3>\n
![\"Storyboarding](\"https:\/\/images.storychief.com\/account_6827\/miro-storyboarding-product-ideation_cfde5abcd1fd08496e600b84bbaf6da4_800.jpg)
<\/picture>SCAMPER method<\/h3>\n
![\"SCAMPER](\"https:\/\/images.storychief.com\/account_6827\/scamper-product-ideation_7ea8c48770733a5099513cd10a295659_800.jpg)
<\/picture>How product managers should collect user feedback for product ideation<\/h2>\n
Collect feature requests in-app<\/h3>\n
![\"Collect](\"https:\/\/images.storychief.com\/account_6827\/submit-idea-form-userpilot-feature-requests-product-ideation_2a7861d7c082c208fae400e5cf6573d9_800.png)
<\/picture>Gather user feedback with microsurveys<\/h3>\n
![\"Jira](\"https:\/\/images.storychief.com\/account_6827\/jira-survey-product-feedback-form-product-ideation_b5fc74dde3db563832098e4baed4b2e1_800.png)
<\/picture>Use multiple UI feedback widgets<\/h3>\n
![\"Miro](\"https:\/\/images.storychief.com\/account_6827\/miro-feedback-widget-product-ideation_c18a3920e8c76a08b8a2d9bb3b62c524_800.jpg)
<\/picture>Regular customer interviews<\/h3>\n