17 Feb
4 steps to building simple software using a child.
My 10 year old daughter has been my “usability tester” on virtually every application I have built over the last 4 years. Usually, I do not have the money nor the time for formal usability group testing, instead I figure “if my daughter can solve various tasks in my product - then at least 80% of adults should be able to as well”. Personally, I am happy with 80% of anything.
4 steps to building simple software using a child.
1. Secure a child between the ages of 6 and 11.
The ages between 6 and 11 tend to be the optimal age range for testing software for “simpleness”. Since reading is still a newer concept to our testers - they tend to “guess” how to execute a specific task, instead of “reading” what to do. Children 12 and older are already more advanced compared to most adults, which ultimately will skew the results.
2. Define your Tasks.
Be very specific in what your tasks are. For example: “Sign up for this website”, “Search for a Photo”, “Send this X to a friend”.
Avoid using words that are written on the website to define your task. e.g. “Sign up for this Website”, when the copy on the site reads “Create an Account”.
3. Observe and BACK OFF.
While the child is solving the task, no matter what… DO NOT HELP. You will be frustrated, confused and maybe even angry as you watch your test subject hop around the page blindly, but YOU have to remain out of the experiment. Observe where the child moves the mouse, what items they click or almost click, the pieces of information that they try to read, the images that draw their attention, etc. WATCH EVERYTHING with intense attention and the cracks of your software will present themselves.
4. Rinse and Repeat.
You can do these steps until the child finally gives up.
The clearer mind of a child is a great place to test for simplicity, and a great way to keep the developers own higher consciousness in check.
As any proud father, I have to give props to Maddy’s own website property Kedet.com - kid powered news.
Tags: usability
Respond to this post