|
|
| (44 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | * Moved to AllHands frontpage |
| [[File:Funnel Inside.png|225px|right]] | | [[File:Funnel Inside.png|225px|right]] |
| ===Learning from Users: getting good at usability testing===
| |
| <b>Time</b>: 9:30 Wednesday
| |
| <br/><b>Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate</b>. Our engagement ladder is everything. We're asking users to perform a small number of key calls to action (like signing up for a Webmaker account, sharing a teaching kit, entering an event into our platform, etc.) How do we do smart usability testing against these tasks so we can see where users are getting stuck -- and capture quick wins to increase our conversion rate? <br
| |
| /><b>Context</b>: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/<br
| |
| /><b>Lead</b>: Cassie/Karen Smith<br
| |
| /><b>Collaborators</b>: Cori Schauer + Tony Santos (User research) + Kat<br
| |
| /><b>Deliverable: </b>Run a usability test for account creation, event creation, and the new /explore page.<br
| |
| /><br
| |
| />
| |
|
| |
| ===Prepping the Webmaker/explore writing sprint===
| |
| <b>Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy.</b> Let's get our roadmap ready for shipping awesome Webmaker teaching curriculum. Toronto will host a writing sprint May 7,8,9 to complete webmaker.org/explore. Recognizing this piece of content is crucial to our successful launch this summer, we need to hit the ground running. We will make sure each attendees has an assigned Web Lit competency and that the work is scoped so we can spend a full three days writing<br
| |
| /><b>Lead</b> (for prep and logistics): Matt<br
| |
| /><b>Collaborators</b>: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy<br
| |
| /><b>Deliverable: </b>Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it.<b> </b>(Kat's Webmaker series)<br
| |
| /><br
| |
| />
| |
|
| |
| ===Prototyping together===
| |
| '''How to tell and sell the difference between prototype and product'''. Let's work out a process for how we turn prototypes into product that will keep us agile while allowing us to meet our current commitments. We did great work last quarter turning the Web Lit Map into an exciting content direction. We've got great new extensions for the browser, 3rd party app integration and more coming up. Let's keep this going, and also be clear about expectations for sales, partnerships, and productization.<br
| |
| /><BR><b>Lead</b>: Brett<br/>
| |
| <b>Collaborators</b>: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess<br
| |
| /><b>Deliverable: </b><br
| |
| />* Documentation for the life cycle of a prototype. <br
| |
| />* Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper. <br
| |
| /><br
| |
| />
| |
|
| |
| ===Appmaker: Getting Input on User Value ===
| |
| <b>Time: 9:30-12:30 Wednesday</b><br>
| |
| <br/><b>Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need</b>. Plus review user demographics and operators in each Firefox OS market. We think there are gains in combining platform, marketplace, digital literacy. Are we teed up to provide value here? <br
| |
| />
| |
| <b>MoFo point:</b> Bobby (+Ben)<br
| |
| /><b>SF local contacts:</b> Ria Joy, if we can get her to come from Seattle, Cori Schauer (conflicts with user research session at same time, Cori available wed 9-11)<br
| |
| /><b>Proposed length: 4-6 hours</b><br
| |
| /><b>Deliverable: </b>
| |
| * Document Appmaker audience segmentation & analysis
| |
| * Document work plan for feeding audience research into Appmaker product strategy
| |
|
| |
| ===Working with the GSMA===
| |
| <b>Time: 12:30-4:30 Wednesday</b><br>
| |
| <br/><b>Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker</b>. Plus produce a 15 slide aligment deck for internal stakeholders<br
| |
| /><b>MoFo point</b>: Mark (+Ben)<br
| |
| /><b>SF local contacts</b>: Pete Scanlon, Ria Joy, Rick Fant (a meeting at some point?), someone from Bill Walker org, someone from Christopher Lee org, Irina Sandu (voice?) David Palomino (voice?)<br
| |
| /><b>Proposed length</b>: 4-6 hours<br
| |
| /><b>Deliverable: </b><br
| |
| />* Ship internal slide deck on the mobile development opportunity for Mozilla <br
| |
| />* Scope 3 actionable demo collaborations between MoCo + MoFo<br
| |
| /><br
| |
| /><br
| |
| />
| |
|
| |
| ===Review and iterate Webmaker.org information architecture===
| |
| <br/><b>Goal: Take stock of all the pages on webmaker.org</b>. Are they serving our needs? Where are there gaps? How might we improve our information architecture to support new pages like /explore and profiles? And how can we measure if its working?<br
| |
| /><b>Lead</b>: Cassie<br
| |
| /><b>Collaborators</b>: Matt, Kat, Kate, Adam<br
| |
| /><b>Deliverable: </b>A complete list of all current pages with "jobs" and notes on next steps for each<br
| |
| /><b>Resource</b>: Google doc: [https://docs.google.com/spreadsheets/d/1ejFHysKOLEGXynU6ZUQgUKn5AVlNgqDBtjrTyM8Zbk4/edit#gid=0 Every Page Has a Job]<br
| |
| /><br
| |
| />
| |
|
| |
| ===Email like a Bawse===
| |
| <br/><b>Goal</b>: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be.<br
| |
| /><b>Lead</b>: Andrea:<br
| |
| /><b>Collaborators</b>: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words)<br
| |
| /><b>Deliverables:</b><br
| |
| />* Review existing emails for engagement ladder<br
| |
| />* Add "email drafting" to the Encyclopedia Best Practica<br
| |
| />* Design attractive HTML emails sent from Webmaker.org<br
| |
| />* Build proper HTML email delivery for Webmaker postal service<br
| |
| />
| |
|
| |
| === Building a Webmaker QA Community ===
| |
| <b>Time:</b> Wednesday 12:30<br>
| |
| <b>Lead:</b> Jbuck<br>
| |
| The QA community has begun to make tests for Webmaker.org (see https://github.com/mozilla/webmaker-tests/issues/37#issuecomment-41444213)
| |
| Let's keep the momentum going and get setup within MozQA systems like MozTrap, chart out what the next set of automated tests should be, and get some advice about how to outreach to the existing QA community.
| |
| <br>
| |
| <b>Collaborators:</b> rbillings, JP, Cade<br>
| |
| <b>Deliverables:</b>
| |
| Setting up Webmaker in MozTrap<br>
| |
| Creating Webmaker tests in MozTrap<br>
| |
| Creating Webmaker tasks in "one and done"<br>
| |
|
| |
| https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/9csx7tfm.png
| |
