Hi all,
I've been doing some thinking and some research into how we might best
carry out UX testing for MediaGoblin. If you have thoughts on this
process, I'd love to hear them.
My goals for the process are:
1. Make it easy for testers, so we can test often.
2. Do our best to not color their responses, despite the fact that
many testers may be friends or colleagues.
3. Make sure feedback goes back into the project.
4. Keep it cheap, at least for now.
Based on those goals, here's my proposed workflow:
1. For each planned release set up an instance for users to test. I
think about ten days before the monthly development meeting would work
well. Give users one week to play around, do mission-based tasks and
schedule a handful of remote desktop sessions where we watch them use
the site. For now, I'm happy to do the watching myself. All feedback
goes on that version's wiki page.
2. Triage those comments and make tickets for the things we want to
change/add/fix. Maybe this is addressed in the monthly dev meeting?
Link those tickets to the wiki page.
3. Make a new page for the next version. Repeat! (And profit!)
Cheers,
Deb