On the morning of our workshop, we showed up bright-eyed, bushy-tailed, and fully caffeinated. Materials in place, slides loaded…we were ready. And then, no one showed up.<\/p>\n
Perhaps because 1) there was too much awesome stuff going on at the same time as our workshop, 2) we were in a back corner, and 3) we didn\u2019t proactively advertise our talk enough.<\/p>\n
After processing our initial heartache and disappointment, Emanuela, a designer on the team, suggested we try something we don\u2019t do often at Mozilla, if at all: guerrilla research. Guerrilla user research usually means getting research participants from \u201cthe street.\u201d For example, a researcher could stand in front of a grocery store with a tablet computer and ask people to use a new app. This type of research method is different than \u201cnormal\u201d user research methods (e.g. field research in a person\u2019s home, interviewing someone remotely over video call, conducting a usability study in a conference room at an office) because there is much less control in screening participants, and all the research is conducted in the public eye [1].<\/p>\n
Guerrilla research is a polarizing topic in the broader user research field, and with good reason: while there are many reasons one might employ this method, it can and is used as a means of getting research done on the cheap. The same thing that makes guerrilla research cheaper\u2014convenient, easy data collection in one location\u2014 can also mean compromised research quality. Because we don\u2019t have the same level of care and control \u00a0with this method, the results of the work can be less effective compared to a study conducted with careful recruitment and facilitation.<\/p>\n
For these reasons, we intentionally don\u2019t<\/b> use guerrilla research as a core part of the Firefox UX practice. However, on that brisk London day, with no participants in sight and our dreams of a facilitated session dashed, guerrilla research presented itself as a last-resort option, as a way we could salvage some of our time investment AND still get some valuable feedback from people on the ground. We were already there, we had the materials, and we had a potential pool of participants\u2014people who, given their conference attendance, were more informed about our particular topic than those you would find in a random coffee shop. It was time to make the best of a tough situation and learn what we could.<\/p>\n
And that\u2019s just what we did.<\/p>\n
Thankfully, we had four workshop facilitators, which meant we could evolve our roles to the new reality. Emanuela and Jennifer were traveling workshop facilitators. Phil, another designer on the team, took photos. Meridel, our content strategist, stationed herself at our original workshop location in case anyone showed up there, taking advantage of that time to work through content-related submission issues with our engineers.<\/p>\n
![\"Jennifer](\"https:\/\/blog.mozilla.org\/ux\/files\/2019\/04\/IMG_0508-300x400.jpg\")
A photo of Jennifer and Emanuela taking the workshop \u201con the road<\/p><\/div>\n
We boldly went into the halls at MozFest and introduced ourselves and our project. We had printouts and pens to capture ideas and get some sketching done with our participants.<\/p>\n
![\"Jennifer](\"https:\/\/blog.mozilla.org\/ux\/files\/2019\/04\/group-shot-blurred-300x225.jpg\")
A photo of Jennifer with four participants<\/p><\/div>\n
In the end, seven people participated in our on-the-road co-design workshop. Because MozFest tends to attract a diverse group of attendees from journalists to developers to academics, some of these participants had experience creating and submitting browser extensions and themes. For each participant we:<\/p>\n
- \n
- Approached them and introduced ourselves and the research we were trying to do. Asked if they wanted to participate. If they did, we proceeded with the following steps.<\/li>\n
- Asked them if they had experience with extensions and themes and discussed that experience.<\/li>\n
- Introduced the sketching exercise, where we asked them to come up with ideas about an ideal process to submit an extension or theme.<\/li>\n
- Watched as the participant sketched ideas for the ideal submission flow.<\/li>\n
- Asked the participant to explain their sketches, and took notes during their explanation.<\/li>\n
- Asked participants if we could use their sketches and our discussion in our research. If they agreed, we asked them to read and sign a consent form.<\/li>\n<\/ol>\n
The participants\u2019 ideas, perspectives, and workflows fed into our subsequent team analysis and design time. Combined with materials and learnings from a prior co-design workshop on the same topic<\/a>, the Add-ons UX team developed creator personas. We used those personas\u2019 needs and workflows to create a submission flow \u201cblueprint\u201d (like a flowchart) that would match each persona.<\/p>\n
![\"A](\"https:\/\/blog.mozilla.org\/ux\/files\/2019\/04\/submission-flows-with-persona-300x192.png\")
A snippet of our submission flow \u201cblueprint\u201d<\/p><\/div>\n
In the end, the lack of workshop attendance was a \u00a0good opportunity to learn from MozFest attendees we may not have otherwise heard from, and grow closer as a team as we had to think on our feet and adapt quickly.<\/p>\n
Guerrilla research needs to be handled with care, and the realities of its limitations taken into account. Happily, we were able to get real value out of our particular application, with note that the insights we gleaned from it were just one <\/b>input into our final deliverables and not the sole source of research. We encourage other researchers and designers doing user research to consider adapting your methods when things don\u2019t go as planned. It could recoup some of the resources and time you have invested, and potentially give you some valuable insights for your product design process.<\/p>\n
Acknowledgements<\/i><\/p>\n
Much gratitude to our colleagues who created the workshop with us and helped us edit this blog post! In alphabetical order, thanks to Stuart Colville, Mike Conca, Kev Needham, Caitlin Neiman, Gemma Petrie, Mara Schwarzlose, Amy Tsay, and Jorge Villalobos.<\/p>\n
Reference<\/i><\/p>\n
[1] \u201cThe Pros and Cons of Guerrilla Research for Your UX Project.\u201d The Interaction Design Foundation<\/i>, 2016, www.interaction-design.org\/literature\/article\/the-pros-and-cons-of-guerrilla-research-for-your-ux-project.<\/p>\n
Also published on medium.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Sometimes, when you\u2019re doing user research, things just don\u2019t quite go as planned. MozFest was one of those times for us. MozFest, the Mozilla Festival, is a vibrant conference and … Read more<\/a><\/p>\n","protected":false},"author":1630,"featured_media":4223,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[119,52898,246,9594],"tags":[],"coauthors":[52913,52916,52917,52919],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/posts\/4220"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/users\/1630"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/comments?post=4220"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/posts\/4220\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/media\/4223"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/media?parent=4220"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/categories?post=4220"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/tags?post=4220"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blog.mozilla.org\/ux\/wp-json\/wp\/v2\/coauthors?post=4220"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}