Albert Einstein once said that anyone can make something complex, but only a genius can make something simple. Imagine if you could read your user’s minds and understand what they really think about your product.
UPDATED TIME AND DATE
Here’s what a few people who attended the last one said:
@jockbu great talk very useful and enjoyable!
— Crisfugu (@Crisfugu) October 18, 2012
Simple usability testing tool for websites. I particularly liked that I was hooked in by someone asking for a quick favour on Twitter to test the usability of some web pages, which then showcased IntuitionHQ’s ease of use. Nice.
IntuitionHQ – Website Usability Testing
We’ve already covered in the previous articles what usability is and why you need to test it and what you need to do to prepare for your usability tests. In this thrilling* conclusion to the trilogy, we get down to the nitty-gritty of how to run the tests and how to interpret and act on the results.
* It all depends on your perspective
I recently spoke at ProductCamp London about conducting lo-fi usability, that is, easy, quick and inexpensive usability testing that anyone can run. I did a neater version when I was invited recently to present to the BBC product managers and user experience practitioners, which I’d like to share with you.
Quite a few people are put off usability testing because they think it’s complicated, time-consuming and expensive. What you may not realise is that you can run a set of usability tests in a single afternoon that will uncover eighty percent of the problems your product has. And the only specialist equipment you’ll need is a pen, some paper and the computer you need to access the software or website.
This my friends is lo-fi usability testing – a high-return, low-cost method for these cash-strapped times. In this first instalment, I’ll be discussing what usability is and why testing it is so important.
I was discussing recently the importance of getting a product installation or upgrade process right for customers. Here are some guiding principles from a usability perspective that you may wish to consider when defining your product’s requirements.
I strongly believe that all software companies should have a manifesto or a set of guidelines which set out in practical terms how they will ensure that their products are intuitive for the types of user for which they’re intended.
For product managers, even if your company or Development team doesn’t “get” usability, you can build these into your product requirements and use your Quality Assurance team to check the requirements have been delivered.