Key Questions to Answer Before Customer Testing "Product people - Product managers, product designers, UX designers, UX researchers, Business analysts, developers, makers & entrepreneurs 2 August 2016 True Customer Feedback, Customer Testing, Testing, Trials, User Testing, Mind the Product Mind the Product Ltd 1676 A "digital mannequin", as a placeholder for a real human customer in testing processes. Product Management 6.704
· 8 minute read

Key Questions to Answer Before Customer Testing

Anyone who wants to get a new product or service to market must be confident that what they’re selling will be successful. The process of building confidence involves work  – before the concept is decided through market research to identify the opportunity, during the build with research to gauge customer reaction and again once the product is ready for use.

A "digital mannequin", as a placeholder for a real human customer in testing processes.

I want to focus on this last element: how can you work with real customers to establish whether your product will be successful, and work out what elements need to be addressed before you launch? This effectively is beta testing, trials of a pre-released product by real users, in situations as close to real-world applications as is possible. To maximise the benefits of customer testing, consider these four fundamental questions you need to answer.

What are you hoping to learn?

Running a customer test activity is time-consuming. It’s a major undertaking to recruit an audience and then ensure that you’ve got them engaged and using the product. Once you’ve got them engaged, you then need to collect the critical information that will tell you whether the product has performed successfully…which means persuading your audience to actively participate in giving you feedback.

Before starting customer testing, it’s important to understand what you want to prove or learn, which may vary depending on your perspective. For example:

  • If you’ve invested or designed the product or service, you want feedback on its market fit – how well it meets the needs of your audience, and which user group it resonates with most.  You want to know whether your product is something that consumers can see benefit in and assign value to.
  • If you’re responsible for managing customer service, then you’ll want to identify any bugs that may have been missed in testing. Considering all the variables seen in real life, 100% testing simply isn’t practical or realistic.
  • If you’re managing the development team, you’ll want to identify any new possible features or improvements before the product ramps up to a wider audience.
  • If you’re in marketing or sales, you want to create a distinct group of loyal customers who will become evangelists for your service and give you onward referrals, as well as discovering the most effective messaging to use for the target audience.

So, to start with, it’s worth considering why you want to run the customer test so that you understand what your priorities are, and that you gain the maximum benefits from the activity.  If your objectives aren’t clear, or could be achieved by another route – perhaps by using internal test teams to find bugs rather than looking to customers to identify them – then customer testing may not be appropriate.

What information does your customer testing need to provide?

Understanding why you’re running customer testing is about asking critical questions before investing your time and effort. The same is true for understanding what the key information is that you want to measure. Are you exploring which parts of the service are most attractive? Testing the price points? Is it about validating how customers use the product in real life?

Perhaps the easiest way to tackle this challenge is to consider these steps:

  • Having understood the reasons for the trial, make sure you know exactly what information will inform your decision making. For example, if you’re assessing whether customers like a tweak to the service (consider the new Evernote interface) perhaps you can consider what new features they use, how new navigation affects behaviours and whether customers prefer it to the old interface.
  • For each of these pieces of information, you then need to consider how you will capture feedback. Will you monitor product usage via click-throughs and page views versus the original version? Or will you need to collect direct customer feedback from focus groups or survey tools? By asking the right questions, and guiding answers that assist your analysis, you are much more likely to get results that help you draw tangible conclusions.
    It’s worth investing time and effort to ensure that you ask the right questions of your audience. Take a look at this Survey Monkey blog to understand the kind of mistakes that can be made. Teams that regularly do UX or customer research can help with balanced questions that will help you really understand the issues with your products.
  • It’s now time to prioritise – think through who your trial users should be and how much feedback you’re likely to get from them. Some measures may well be “nice to have”, but not at the expense of really important metrics.
  • Finally you need to be absolutely clear about what marks success; specifically what scores must be achieved on each of the key measures you’ve identified.  This is something that must be considered in advance; ideally you should set these targets right up front when you started setting out the vision for the new product or service. It’s much easier to remain objective before you start a trial, especially if you have multiple teams involved; put another way, it’s nigh-on impossible to remain unbiased once the trial has started and the data collection begins.

If you fail to set measures then the most likely outcome is that the service launched fails to deliver a decent return on investment. For example, I decided to add a security software subscription to a premium support offering I managed – it took time to train our field engineers to sell the product and major investment in designing systems to record and communicate the sale to the third party that provided the software. However the project failed because engineers ended up offering free security installs for the majority of customers, rather than the paid-for equivalent. We had ignored the warning sign of the poor score we received for perceived value of the software because we had thought that the positive reactions in a number of other areas would compensate for this.

In summary, a clear set of measures and targets means you’ll know what success looks like, and that you have a clear understanding of what information you need and how to get it. This should also trigger the conversation about what happens if you don’t hit the metrics. Will you allow some flexibility if a few of the success criteria aren’t met, or are these absolute minimums that must be achieved for the product to move forward into production?

Who will trial your products?

A trial clearly can’t work without the audience to test the product. Probably the biggest challenge in any trial is locating the people who will test your product for you.

In order to identify what trial users you need, consider the following:

  • How many trial users do you need?  Is it possible to get fewer trial users who use the product more thoroughly?  Or are you interested in getting a wider base of individuals to gauge reaction and engagement? Do you need to test multiple potential target markets, or audience demographics?
  • What do you need the trial users to do – are you simply asking them to use the product, or to run specific trial scenarios, or even to give detailed feedback on the service?
  • How will customers react to the version of the product that you’re looking to test – will they be put off by any gaps in the product or any issues with the service?  Is there any risk they might publicly criticise the product you are trialling?
  • Do you need completely new customers or can you use existing customers to test the product?  

It’s not unusual to face a shortfall in trial users despite a creative approach to recruitment.  One option is to incentivise them, via a giveaway, competition, or discount on the product pricing.  However, you should never lose sight of the fact that the incentive is a vehicle to encourage your audience to participate in trials and give feedback on your product; it needs to be appropriate to the test and avoid unduly influencing the results you get.

Keep in mind that you want accurate, impartial views of your product. You need the hard truth about whether your product is going to be successful or not.  If friendly customers or incentivised trial participants have sugar-coated any gaps or issues because they don’t want to offend you or risk their incentive, you may end up with a rude awakening when you take your product to the wider market.

When should you trial your products?

When is the right time to beta-test the product? Too early, and there’s a high likelihood that there will be too many bugs or issues that will affect the customer experience. Too late, and you risk burning development time and effort on the wrong areas, and needlessly delaying product launch.

Generally the pressure is to trial early, which is great as long as your trial base is keen to participate and happy to accept and give feedback on glitches in the product.  However, significant numbers of product issues and bugs could end up alienating these trial customers, so it does need to be considered carefully.  Much of the art of timing is about setting the appropriate expectations with trial users during their recruitment, and balancing what they will be prepared to forgive when they are invited to be “the first trial users who will get to see our new product”.

Clearly, there is no single right answer to this question, as it very much depends on the nature of your product and the tolerance of your audience for incomplete products. As a product manager, you need to understand your audience well enough to make this judgement, and some small early trials in the development process might help you gauge this better.

Once you’ve worked through these fundamental questions, you should have a clear idea of what you hope to learn, as well as how you will get the information you need. The next step is to work out how to run your trials.

Comments 0

Join the community

Sign up for free to share your thoughts

About the author