Lets dish out some quick ways to test and improve your product. Long tests with a lot of tasks certainly can have their place (for example in the early stages of a design). However, many of our customers are improving their website by running multiple, recurring, and short tests.
Recurring tests are easy to setup and manage. They are of the ‘set and forget’ type. Participating only takes a couple of minutes and is fun to do. It’s also a good example of agile design: small improvements can be made to the existing product quickly. Can’t you just taste the low hanging fruit?
On to the examples!
1. Time and measure your main call-to-action
Test your call-to-action by asking “Where would you click to start to use this product?“. This way you can find out how long it takes users to make a decision, and if that decision was correct. This will measure the effectiveness of your call-to-action button inside the context of the rest of your product. See the post by Paul on a call-to-action comparison of different sites to see how other sites perform on this test.
Call-to-action test on Vimeo.com
2. See how users go about contacting you
Don’t have your doors closed to your customers. Make it easy for them to find you and contact you with testing the effectiveness of your contact link with a Usabilla test. On most sites only a small portion of your visitors will click on the contact button or link on your site. This means web analytics will not give you a lot of useful data to work with. With a Usabilla test, you can find out which element users click when you ask them to drop you a line. You can also see how long it takes them.
3. Get context-sensitive feedback on design elements
Imagine you are a web designer and made a header for a new site. Instead of directly asking around for feedback, setup a Usabilla test with the design, and invite a couple of friends and/or respected peers. You can explain what kind of feedback you are looking for and wait for the results. Because the participants can stay anonymous, feedback will tend to be more honest. Also, the feedback will be visible right on the design. This makes confusing feedback about ‘that third yellow button on the right’ a thing of the past.
4. Find out which elements makes people trust you
A Usabilla test can give thorough insights in your product with subjective questions like: “Which elements make you trust on this website, and why?“. Usabilla visualizes feedback in heatmaps, so you can see which elements people pick out. Participants can also can leave notes behind, right where they click. See our test about trust of the Mint website for details on measuring trust.
Collected feedback on the task “Which elements do you trust, and why?”
5. Test the wording used in your product
The wording of your copy, hyperlinks or other elements on your page can have a big impact on your users. You can A/B test your designs with different wording as explained by Sabina in the post about different worded copy on the NesCafé site. You would be surprised how intriguingly worded content can make your users more eager to explore your site.
What to take away from this
With tools like Usabilla, usability testing is no longer restricted to expensive face to face solutions. You can ask your following on Twitter or Facebook to help, mail your newsletter subscribers or poll users on your site. The way Matthew setup his test is a good illustration of how to quickly find participants.
Using recurring small remote tests, testing your product is not a one-off deal anymore. You can easily integrate them in your day to day workflow. The results will be worth it. Setup your free account, so you can test your own product.