Loomio

UX: user testing process

Richard D. Bartlett PublicSeen by 64

Richard D. Bartlett

Background here: http://loomio.org/blog/user-centric-design-methodology/

Aaron and I have done a huge push of work on the UX testing this week. Aaron made a bunch of excellent paper prototypes and interviewed 2 users as they tried to navigate through Paper Loomio. I sat in the background taking notes on their responses.

Then the next job was to collate all that feedback into something intelligible. Here's our first iteration of that collation: https://docs.google.com/spreadsheet/ccc?key=0AvYex4bwI5AndG9rTGpxUWRwXzY2T0FTemtPcjFTZnc#gid=4

Each piece of user feedback gets plugged into a cell on the spreadsheet and colour coded: Red means the feature is broken or confusing, yellow means it is okay but needs work, green means good. When a user requests a new feature we colour it lilac.

The intention is that the Overview sheet is a high-level summary of the feedback we get from each of the users, to see what their priorities are. So for instance, User 2 said she'd like to hide the Flow Diagram on the Group Page. So when a dev wants to work on the Flow Diagram, they can go to the Group Page sheet and look at the Flow Diagram column for a list of all the comments users have made about that particular feature. I've also summed all the colour-coding to give an overall rating for the prototype on the overview page, e.g. User 2 picked out 3 broken features, 8 that need work, and 18 that were good.

The summarising process and the colour coding is highly unscientific and biased, so they are just a loose guide. To reduce the bias of the summary Aaron and I collaboratively work on that together, and then I run it past the tested user to make sure it is relatively accurate.

Sharp eyes will notice another colour code: admin features are coloured blue. This highlights a weak point of this first iteration of the process: we haven't done our user profiling, so that's the next challenge.

UX pro Keong suggests we make a simple survey (demographics, usage, etc) and force all our existing users to fill it in before using the app. I'm kind of okay with that idea insofar as alpha users aren't paying yet, so we could frame it in a way that wasn't too invasive.

What do you reckon?

[FYI, for this particular prototype (we're arbitrarily calling it Version 16.7) the Group Page and the Dashboard Page are folded into one unit. This will be clearer once we upload the pictures of the paper prototypes (tomorrow).]

Benjamin Knight

Awesome work dudez!

I reckon a survey wouldn't be too painful if we make it super friendly and put it in context so it's clear to people that they're helping us develop something that'll be useful for them

vivien maidaborn

Actually it is a great idea because the challenge is to. Next interst to engagement to use, an initial survey will weed those only mildly interested out early and build confidence in those really wanting Loomio during the signing on process. I like it.