So, you have decided that an application is a solution to your problem. First, beware, your user may not want it.
This applies to all types of applications (web, mobile, etc). The key issue is gaining user interest. I’m not talking about the general desirability of your application. You would have already tested that by following Design Thinking methodology. However, that was a rough paper prototype. So, what now?
No ad to show here.
Make sure that your app user experience (UX) is flawless. An app that is easy and fun to use has fewer resistance factors.
Prototype! Prototype! Prototype!
I hear you saying, “I don’t have the time to build a pretty looking prototype right now!” Well, there is some good news. UX and user interface (UI) are different and complementary things. UX is all about the journey when using the app, while UI just changes how the app looks.
Both of these toolsets are important, however, sometimes a UI designer and a UX designer have very different opinions. More good news though, it does not matter.
‘What do you mean? Who’s opinion counts?’
This is a simple one — the “customer” and only the “customer” matters!
So, the solution is simple: choose the best method to create a prototype for UX testing with customers. Just a few of the options are:
Meteor (for higher fidelity prototypes): This requires some extensive coding background.
Axure: This requires some training but can build very good prototypes that can be easily deployed.
InVision: Use this for building click-through demos, quickly.
This is a short list of possibilities but with all the tech around today, the choices are almost endless. Using something like InVision, you can create pen and paper drawings, take some pictures or scans and create a click-through.
With a slightly better-looking prototype, customers will get even more excited.
User experience testing time! But how?
By now you have researched different tool options and found some interesting applications to use. You quickly put one together, now what? It’s time to test!
UX testing may well be different to your accustomed customer testing. First, have your goals clear. Make sure you have defined all the tasks that you want the user to complete. Throughout the testing process keep the user talking, they should be explaining what they are seeing and what they intuitively want to do.
In the testing session, you should ideally have three people:
Facilitator: This person explains the purpose of the testing and what they intend to achieve. They will also be telling the user about the following tasks.
Observer: This person should be watching the expressions and body language of the user to detect their non-verbal emotions.
Note-taker: This person should be taking notes of where the user is in the process and what they are seeing and doing.
In the testing sessions, the facilitator is the only person — other than the user — that does any talking! There should be no guiding the user in any way. They should be left to figure out the task and if they can’t after some time, they fail and move on.
Recording the session, both audio and video, if possible, is a good idea for later review. Each task will be rated on a scale (that you have defined) to determine:
- Whether the user passed or failed
- How intuitive and easy it was to complete the task.
- When a user fails, it really means that your user experience design has failed and needs to be iterated.
Go forth and develop!
At this stage, you will have tested several iterations of your prototype and will be ready to build your application. This entire process has ensured that your users will be able to easily use your app when it is released. All this hard work means there will be much less resistance to adoption — your ultimate goal.
Brett Terespolsky is the CEO and a co-founder at Switch Innovation
Featured image: Switch Innovation CEO Brett Terespolsky
