Five thought-provoking questions for your software prototype testers

Software prototyping | 0 comments | by Erin Quilliam

One of the most important uses of any prototype is to test and provide invaluable insight and feedback from users on your new product. But when you are in the midst of testing, it’s important to ask the right questions and facilitate useful discussions. Here are five of the most important questions to ask your prototype testers when developing a software prototype.

Ask your testers if there is anything they would change on your prototypeIf you could change anything at all, what would it be?

If a user could change anything in the prototype without any hindrances, what would it be? Given no restriction of time, cost or feasibility was nothing to be considered, what would they do? The insight you can gain from a question like this can be remarkable. Any change they suggest could be something as simple as a different font. But it might also unearth a quirk in your navigation structure you had never noticed before, that makes no sense to the end user. Asking your users what they would change is vital to understanding where any weak points or drawbacks are. Additionally, as you have asked them for the change they would make, you identify the issue and a potential solution in one discussion.

Make sure there are no obstacles your users faceCan you do ‘X’ – Did anything get in the way of doing it?

Set them a specific task to do on the site, then ask them if they found any hindrances when completing the task. Setting a task gives a focus and sense of direction that aimlessly clicking around can’t provide. The sense of urgency also replicates a consumer when using your product. (You can even use this question to identify what scenarios they imagine they would use the software for.)

By having this focus, the tester is more likely to take notice of any hindrances that they come across when trying to complete their task. For example, if they could not find an easy way to navigate to a specific page. It also gives insight into how your users will interact with the software and their expectations of using it.

Ask your users if they would change anything about your prototypeIs there anything you don’t understand?

It is important to let your prototype testers explore your new software and what they can do with it. And although you want to know what works well for them, you want to find out what doesn’t work or seems redundant. This allows you to further refine the prototype, or make changes before the final product. It’s also important to discover if anything confuses a user at any point, as this will not only seriously detract from their experience, but might even turn them away from using the software in the future.

Ask your software prototype testers if they liked using your productWhat did you like the most when using the prototype?

Just as it is important to understand shortcomings to overcome them, it’s key to identify successes so you can learn from them and even emulate them. It’s also motivating for a team to hear about what they’ve done well, rather than just focusing on what needs to change.

Make sure your testers and users would actually want to use your product.Would you use it?

This perhaps seems the most obvious question on this list, but that’s because you already know how important it is to ask. Make sure your software prototype testers would want to use your service outside the test.

For any product to be successful, from a kitchen appliance to farming tool to software, there must be a need for it. Additionally, a user must feel comfortable using a product and be happy to use it in the future.

Even if your software is revolutionising a way of working, if your testers don’t feel happy to use it, something is drastically wrong. Trying to learn what that might be and rectifying it is vital. And if you didn’t test it and discover the fault and just launched straight to market, you’d have a catastrophe on your hands.

 

There are of course dozens of other questions you could ask your prototype testers, and all feedback will be valuable. But developing a test script for users to follow and to direct discussion can improve your testing process for yourself and your testers. Not to mention, provide far more detailed results.

If you’d like to learn more about the software prototyping process, you can sign up to our software prototyping newsletter – the evolving guide to prototyping.

Tags: , , , , ,
Image MapDesignImplementAcceptDeployAnalyze
Close

DESIGN

We will prepare the experts, process, environment and roadmap needed to achieve your goals

Close

IMPLEMENT

We will bring together talent, innovation and technology to work on your project's blueprint.

Close

ACCEPT

We will give you quick access to our people, methods and infrastructure to help improve on each project iteration.

Close

DEPLOY

We will execute the solutions to complete your --' project and transfer knowledge, while protecting your intellectual property.

Close

ANALYZE

We will define, study and clarify with you the scope and limits of your requirements.