861862 - Prepare for usability / user testing: capture testing and recruitment criteria, scenarios, and process for feedback

Status: RESOLVED FIXED

(Webmaker Graveyard :: webmaker.org, defect)

Comment 1

[inactivate account for kate]

Attachment: User/application flow for sign-up/sign-in

To be discussed, a possible application/user flow for signing in and signing up. Defers creation of user details until after user has already signed in

Comment 2

[Cassie McDaniel [:cassiemc]]

Comment on attachment 738690 [details]
User/application flow for sign-up/sign-in

This makes sense to me, Kate. I'd be interested to verify with the Personas team to see if users can get put back on the page where they began the login / signup process once they are logged in, to keep the jarring-ness to a minimum. Is now a good time for me to reach out to Crystal?

Comment 3

[Cassie McDaniel [:cassiemc]]

This bug has shifted quite a bit since it was filed. New goal is to create content / process that can be turned into a kit for use by the mentor team. Here are the current thoughts: https://etherpad.mozilla.org/usertestingwmo

Possible duplicate of bug 894981?

Comment 4

[Matt Thompson (@OpenMatt :OpenMatt)]

yep its a dupe. :) Cassie: which one do you want to use going forward?

Comment 6

[Cassie McDaniel [:cassiemc]]

Marked the other one a dupe, this one has some tracking on it already for this week.

Comment 7

[Laura Hilliger [:epilepticrabbit]]

We probably need 2 separate plans for user testing. The Mentor team/community is much more likely to be collecting data during actual workshops than scheduling formal user testing and focus groups. 

Every event the Mentor team facilitates outputs ideas/thoughts/bugs/feature requests from community. How can we be more systematic about feeding back? Sometimes we're very good at documenting things: 

For example: the massive spreadsheet from Reps Training Days when we asked 40+ Reps to write down the things MoFo could do to help them help us. https://docs.google.com/a/zythepsary.com/spreadsheet/ccc?key=0Aku8434q8_LPdHVHSU9CNlpkZVRZQ0U5Q0VtS0RhMHc#gid=6

Sometimes we have a bunch of post it notes in our bags that we intend to file as bugs. (JBuck can attest the number of times I've run a workshop in Toronto and delivered him post its to his desk.)

Just some thoughts to consider.

Comment 8

[Cassie McDaniel [:cassiemc]]

These were helpful thoughts Laura, and Kat/Karen/Brett and I discussed some process for all this today. We'll have 3 ways of giving feedback:

1) we will translate testing questions into scenarios where feedback can be provided via google forms. Anyone can use these links to provide feedback online on their own, or with a mentor/leader guide at a maker party.

2) We'll do some formal user testing as well, thanks to Karen's help.

3) We'll create a section on our website, like webmaker.org/feedback, to house links for these google forms. There will also be a training video for how to gather good user feedback.

Our full meeting notes are here: https://etherpad.mozilla.org/usertestingwmo-meeting

Am going to close this bug as next steps are to break this into lots of smaller tasks. Karen and I will be translating the to-do tasks from that meeting into individual bugs (also as a bugzilla training session). Here's a minified list:

* prioritization of what we want to test that can be written into scenarios - brett
* guidelines/documentation for tagging on bugzilla - brett
* training - will create a video/guidelines on best practices in user testing - kat & karen, feat. on wm.org + demo it at webmaker call
* Kits / google forms:
    writing scenarios - cassie & karen
    translating to google forms - karen
    translating into bugs - cassie or brett
* Website page / general feedback form (webmaker.org/feedback) - Cassie
* Formal user testing - Karen