Let’s dive in!<\/p>\n
What is concept testing?<\/h2>\n
Concept testing is a market research method used to evaluate the chances of success of a new product idea<\/a> before it’s fully developed and launched.<\/p>\n It involves collecting feedback<\/a> from target users via surveys<\/a>, interviews, and focus groups to evaluate their perceptions as well as quantitative insights <\/a>through product analytics.<\/a><\/p>\n Usability testing and concept testing focus on different aspects of the product development process.<\/p>\n Concept testing is conducted early on in the design <\/a>process, often before a fully functional prototype is available. The aim is to evaluate whether the basic product concept aligns with users’ needs and expectations.<\/p>\n On the other hand, usability testing<\/a> is conducted later in the process, when a working prototype <\/a>or the actual product is available. It assesses how easy it is for users to navigate the product, complete tasks, and whether they can intuitively <\/a>understand and use the product’s features.<\/p>\n Concept testing should be an integral part of product development for a number of reasons. Let’s check them out.<\/p>\n Concept testing allows SaaS businesses to validate early-stage ideas through the prism of customer needs <\/a>and preferences<\/a>.<\/p>\n This makes the product development process more customer-centric.<\/a> It helps teams achieve the product-market fit<\/a> by creating a product that addresses genuine customer needs and pain points.<\/a><\/p>\n Customer feedback at the early stages of product development allows teams to identify potential problems or concerns related to the product idea.<\/p>\n For example, it can help you uncover some wrong assumptions that were made at the ideation <\/a>stage.<\/p>\n By doing so, teams are able to gradually refine the product concept during the subsequent iterations.<\/p>\n Concept testing allows teams to mitigate risks involved in product development and avert product failure.<\/a><\/p>\n By scrutinizing the product concept early on, teams are able to determine if the product is likely to be successful <\/a>before committing any resources to its development.<\/p>\n The insights from concept testing can help teams to either pivot in the right direction or kill the idea altogether and concentrate their efforts on more worthy initiatives.<\/p>\n The idea behind concept testing is to evaluate the idea before any time or money is spent on its development. That’s why the process should take place before you start building the product – during the initial product discovery <\/a>phase.<\/p>\n However, it’s not a one-off exercise but rather a continuous process. Ideally, every single feature you decide to add to your product<\/a> should be tested before you develop and launch <\/a>it.<\/p>\n The process of concept testing should involve colleagues from teams across the organization.<\/p>\n This includes the product team<\/a>, marketing team<\/a>, as well as UX designers <\/a>and developers. As all of them bring unique perspectives and expertise to the table, it makes it easier to identify potential issues and find the best ways to tailor the product to satisfy customer needs and wants.<\/a><\/p>\n Of course, it goes without saying that you should always involve customers in concept testing. Without their feedback<\/a>, you won’t have the insights <\/a>you need to iterate on the initial product idea.<\/p>\n There are 4 main types of concept tests that you may want to consider. The key differences between them are the scale and their objectives.<\/p>\n Monadic concept testing involves the evaluation of a single concept or product by a participant.<\/p>\n The aim of this method is to obtain in-depth feedback without influencing the participant with other concepts or products. It’s particularly beneficial in situations where you want to understand how users perceive <\/a>and feel about a product in isolation, without any comparative distractions.<\/p>\n This kind of concept testing is very resource-intensive because it requires individual interviews with participants.<\/p>\n In sequential testing, you present several concepts or products to participants in a sequence – each participant evaluates multiple concepts.<\/p>\n This approach provides comparative data, which makes it easier to identify the best-performing concept.<\/p>\n However, sequential testing results can be skewed by order and sequence biases, where the order of presentation can influence the evaluation or how well they’re remembered. What’s more, it might be more time-consuming and complex than other methods.<\/p>\n A comparative concept test, also known as a preference test<\/a>, involves presenting two or more concepts to participants at the same time and asking them for feedback.<\/p>\n This method is highly effective in determining which concept is better and can help you make a decision between a few well-formed concepts.<\/p>\n It’s possible to carry out comparative concept tests at scale online. However, if you choose to conduct it this way, bear in mind you will not always get in-depth qualitative feedback.<\/a><\/p>\n Protomonadic testing combines monadic and comparative testing. Participants first evaluate a concept in isolation (monadic phase) before comparing it with other concepts (comparative phase).<\/p>\n This provides both detailed insights into the strengths and weaknesses of each concept individually and comparative data on how they stack up against each other.<\/p>\n Despite its advantages, protomonadic testing can be fairly complex to administer.<\/p>\n The concept testing process consists of 5 main steps.<\/p>\n You set your goals and decide on the kind of test, prepare the test and questions to ask, recruit the right participants, collect and analyze the data, and act on the insights<\/a>.<\/p>\n Let’s dive into each of them in a bit more detail.<\/p>\n Defining clear goals <\/a>at the beginning of the concept testing process is essential for obtaining valuable insights. Without a clear focus, you won’t be able to choose the right kind of test, ask meaningful questions, or choose the right participants.<\/p>\n For example, let\u2019s imagine your goal is to increase demo bookings from your website and you want to conduct a concept test to choose the best CTA button microcopy. For this, you would choose a comparative test.<\/p>\n If, on the other hand, you want to validate a new feature idea<\/a>, a monadic test would be more suitable.<\/p>\n If you need help choosing goals, why not use a goal-setting framework<\/a>, like OKR or SMART? By doing so, you will ensure that your goals are clear and actionable. It will also help you choose the right tools to measure progress.<\/p>\n Once you have set your goals, it’s time to prepare for the actual test by choosing the right medium to conduct it and writing the questions <\/a>that will enable you to gather the insights you need.<\/p>\n In-app surveys <\/a>are an excellent way to collect customer feedback from a lot of participants.<\/p>\n Their main advantage is that they’re easy to design, and you can trigger them for specific user segments. <\/a>However, to do so, you need a product as a launchpad for the tests, so in-app surveys are more suitable later in the development lifecycle.<\/p>\n To get the best of your surveys, use them to collect both quantitative <\/a>and qualitative data. Start with a closed-ended question, for example, ‘On a scale of 1-5, how useful would you find this feature?’.<\/p>\n Follow this up with an open-ended question, for example, ‘How would this feature help you achieve your goals’ or ‘How would you improve this feature?’.<\/p>\n Make the qualitative questions optional so that users still submit the survey even if they don’t have the time to provide detailed feedback – or don’t know what to say.<\/p>\n Interviews and focus groups could be an excellent source of in-depth qualitative feedback. <\/a><\/p>\n They allow you to follow up on the initial participant responses to better understand user perceptions. This is important because your participants may not be able to express their ideas clearly to start with.<\/p>\n This makes them a great choice for monadic, sequential, and protomonadic concept tests.<\/p>\n Their downside is that they’re time-consuming and expensive to conduct. And if you don’t make the effort to prepare them and think through the questions to ask, you could end up wasting a lot of time.<\/p>\n A\/B testing <\/a>is normally used in the later stages of product development, where you have a working product in place. That’s because you need a platform to launch the two versions you’re testing and track their performance.<\/p>\n Is this your situation? If so, you could use them for comparative concept testing.<\/p>\n They’re a great tool when you’re trying to choose between two different designs, for example, menu designs or microcopy. Their main advantage is that you can use it to gather reliable quantitative data to validate your idea.<\/p>\n Its main downside, though, is that it offers no qualitative insights<\/a>. In fact, users don’t even realize they’re part of a test.<\/p>\n Choosing the right participants<\/a> for the tests is essential to gather the right insights<\/a>.<\/p>\n First of all, you need to ensure that the concept you’re testing is relevant to their circumstances. If your users don’t have any use for a feature you’re testing, they won’t be able to offer anything of value.<\/p>\n Secondly, make sure to choose a representative sample of your target audience. While getting responses from your power users<\/a> or early adopters might be easier, they only contribute a small percentage of your revenue. To get a product-market fit<\/a>, your concept needs to appeal to the majority of users.<\/p>\n How do you recruit your test participants?<\/p>\n If you have a product in place, leverage your existing user base. Use your user segmentation tool, like Userpilot, to pick the right users and approach them via in-app messages<\/a> or email.<\/p>\n If not, tools like Hotjar give you access to a pool of potential testers across different niches and can help you manage the testing process.<\/p>\n Having conducted the test, it’s time to analyze the data.<\/a><\/p>\n If you use a dedicated tool for testing, there’s a big chance it will do the quantitative analysis for you. If not, make sure to test the data for statistical significance to ensure the insights are valid.<\/p>\n Qualitative data analysis <\/a>could be more challenging. Your feedback tool may allow you to tag responses for easier analysis or even use AI <\/a>to identify patterns in user responses. If not, you can export them into a spreadsheet and then hack a generic AI tool to analyze it for you.<\/p>\n If your test reveals that the concept has no traction with your users whatsoever, kill it straight away. A failure before you commit any money or mental energy to feature development is not really a failure.<\/p>\n If concept testing shows that you’re on the right track, but the initial idea needs tweaking, iterate on the concept and conduct additional testing.<\/p>\n This iterative process<\/a> will help you fine-tune the concept until it fully aligns with customer preferences and expectations.<\/p>\n What mistakes should you avoid when concept testing?<\/p>\n Here are some of the most common ones:<\/p>\n Concept testing enables product teams to validate product, feature, and design ideas before investing any money or time into their development.<\/p>\n Apart from smarter resource allocation, it enables the product to achieve the product-market fit in less time and, in extreme situations – avoid its complete failure.<\/p>\n![\"Concept](\"https:\/\/images.storychief.com\/account_6827\/buffer-fake-door-testing-concept-testing-ux_0b78b2901c99b5bc2e0d746e91ec86a2_800.jpg)
<\/picture>Concept testing UX vs. usability testing<\/h2>\n
What are the benefits of conducting concept testing?<\/h2>\n
Validation from your target audience<\/h3>\n
Early detection of potential issues with the product idea<\/h3>\n
Reduced risk of product failure<\/h3>\n
When to conduct a concept test?<\/h2>\n
Who should be involved in the concept testing process?<\/h2>\n
The different types of concept tests<\/h2>\n
![\"Concept](\"https:\/\/images.storychief.com\/account_6827\/concept-testing-ux-methods-for-saas_3d7edab98c064713ff135840039d3c99_800.jpg)
<\/picture>Monadic testing<\/h3>\n
Sequential monadic testing<\/h3>\n
Comparative testing<\/h3>\n
Protomonadic testing<\/h3>\n
How to carry out effective concept testing?<\/h2>\n
1. Define concept testing goals<\/h3>\n
![\"okr-concept-testing-ux\"](\"https:\/\/images.storychief.com\/account_6827\/okr-concept-testing-ux_738d3b2b4f48b7ea29e88c9cc27c80b4_800.jpg)
<\/picture>2. Prepare the concept test and the questions to ask<\/h3>\n
Surveys for gathering user feedback at scale<\/h4>\n
![\"Concept](\"https:\/\/images.storychief.com\/account_6827\/in-app-survey-concept-testing-ux_f9a1dae1bbf2e869293811b022e9c9d8_800.jpg)
<\/picture>Interviews for collecting deeper insights<\/h4>\n
![\"Concept](\"https:\/\/images.storychief.com\/account_6827\/interviews-concept-testing-ux_1531c064c0915064ffedc4bc37d1353c_800.jpg)
<\/picture>A\/B testing for gathering quantitative data in-app<\/h4>\n
![\"Concept](\"https:\/\/images.storychief.com\/account_6827\/ab-test-concept-testing-ux_bb353edab1ed8d912bb2472463eba368_800.jpg)
<\/picture>3. Recruit the right test participants<\/h3>\n
![\"Recruiting](\"https:\/\/images.storychief.com\/account_6827\/beta-testing-concept-testing-ux_da188fdcd3e44bb15cef2d6dfbf4657a_800.jpg)
<\/picture>4. Conduct the concept test and analyze the responses<\/h3>\n
![\"Qualitative](\"https:\/\/images.storychief.com\/account_6827\/5-common-methods-of-qualitative-data-analysis-concept-testing-ux_45ab2d0a26746b8620606b00e52eccdd_800.jpg)
<\/picture>Iterate and repeat the test if needed<\/h3>\n
Common mistakes when conducting concept testing<\/h2>\n
\n
Conclusion<\/h2>\n