Why do alpha testing?
Alpha evaluations, also known as alpha testing, can be a crucial way to reduce the risk of launching a product that will not be accepted by your customers. When alpha testing is done well, this can provide crucial insights on how well your final product is going to be valued by customers and what is not. A good early understanding of these product attributes will save you considerable effort and expense during your product development. Essentially, this effort will tell you how to best transform your innovative science into products your customers will want (and purchase).
Alpha evaluations are:
- Run by R&D not Product Management
- These efforts should provide R&D with the insights they need to make changes to the product performance and/or feature set. Further R&D may be necessary if the current prototype does not meet the performance expectations of your target customers. Remember to keep product management in the loop during this effort though.
- Tests of very early prototypes to gauge customer acceptance of proposed product
- For software products, consider creating a mockup of what the software will be like using PowerPoint slides. You walk the evaluator through what each tab and feature might be like very quickly with a minimum of up-front effort.
- For reagent products or kits, don’t worry about any fancy labels or packaging. Prepare some samples and use them with your tester. It is important not to just send them to the tester and ask for feedback but really to work side by side with them in your lab or theirs to maximize getting the most relevant feedback on your current concept.
- For instrumentation or equipment, bring ‘bread-board’ version or other mock up prototype to tester’s lab or invite them into yours, for the evaluation. This does not need to be ‘pretty’ and not all of the functionality needs to be in place. You want to get feedback on the core function of your instrument or equipment to see how well they accept it.
- A source of customer insights that will change your final product
- Unlike beta testing, changes to the product will be made based on alpha evaluator feedback. Be sure to get feedback on the desired (or expected) performance characteristics of your proposed product (e.g. acceptable linear dynamic range, sensitivity limits, through-put, ease of use etc.)
Important safety tip
Beware the danger of this effort becoming a research project (leading to time and cost overruns not to mention confounding your commercialization plans). Alpha testing is not feasibility testing or discovery research. The goal of this effort is to see if the current concept for your product will be valued by potential customers. At this point, it is assumed that the underlying science works. Set specific goals for what you hope to learn and stick to that.
When not to do alpha testing
Alpha evaluations may not always be appropriate. If you are making a better version of an existing product (yours or a competitors) alpha testing is most likely not needed since you already have plenty of information on what customers like and don’t like about the current offering(s). Use alpha testing when you can’t easily answer “yes” to this this statement.
“The design of my current product offering will meet or exceed the expectations of my customers.”