Every prototype is a simulation of reality, in which you create the basic conditions needed to test how something will perform or be received by its target audience. Prototypes come in all shapes, sizes, and methods, running the gamut from super-involved to slap-dash. These pro tips will help you save money and time when prototyping and testing with users.
Tip 1: Always write down your goal before you begin
Having a very specific goal for any test will help you choose the right prototype for the job, and save you a lot of time in being able to extract conclusions from what you observe. A good goal is also specific, for example “See if people understand what this new feature is supposed to do for them.” One very important caveat: testing with prototypes (like other market research techniques) won’t tell you accurately if people will purchase something in real life, so try to stay away from that goal when prototyping.
Tip 2: Choose your method based on how much you already know
Quick, low-resolution methods:
Choose these if you are at the beginning stages of developing a new product or feature, and want to see what the reception to it might be. These methods are also good if you’ve already blown a lot of resources building a new product or service, but realize that you don’t actually know much about how it will be received. (Whoops!)
Role-play or “wizard of oz” prototyping is often the fastest and cheapest way to simulate a product or an interaction. This is when you assign a person on your team to play the role of the product, and have people interact with that person. It sounds silly and feels sillier to enact, but it is a fantastic way to gain insights quickly.
Pen, paper, and other props are great as well: draw out the thing you are planning to show users, to the best of your ability, capturing only the main elements of it, rather than every detail.
Slower, high-resolution methods:
Choose these if you have done previous investigations and are somewhat sure of what the reception to your product will be. These methods are more costly, and take more time than the low-resolution ones. However, they can be used to gain more specific insights, or insights about a specific detail of the product - something that isn’t usually possible with the faster methods.
Prototype visual interfaces using tools such as invision, sketch, or figma if your test relies heavily on a certain visual design, if you need a very detailed interface, or if you’re ready to test a product which is almost ready for release.
One last category of prototype is simply the beta or pre-release version of your product. It doesn’t have to work well, and doesn’t have to be finished, as long as the main elements are in place.
Tip 3: Find and incentivize testers carefully
Find at the very least 5 people (the magic number in user testing!) who match the profile of those people that your product is meant for. One trick is to offer incentives that will only appeal to people who are relevant. For example, if you’re planning to test an app for teaching music, offering free access to lessons as the incentive to participate in the test will both filter out people who aren’t your target market, and create a realisting motivation to interact with the product during the testing session. Plan for each person in your testing sessions to interact with your prototype for a specific length of time, probably 5-30 minutes depending on complexity.
Tip 4: Be disciplined about how your record data
Last but definitely not least: be very methodical and disciplined about the way you record information. I like to record most of my sessions because then it’s easier for team members to refer to them later. Recording users’ answers in an organized google sheet so they can be compared to each other is also a good idea, and keeps you disciplined about making sure that every user in your test is completing all the relevant questions or flows. Summarize conclusions as soon as you can, when your observations are fresh in your mind.
What are your best tips for getting the most out of prototyping?
Happy testing!