AllHands/Funnel Inside
Learning from Users: user testing our Engagement Ladder
Time: 9:30 Wednesday
Let's do usability testing on our engagement ladder, to see where people are getting stuck and increase our conversation rate. 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?
Context: http://mzl.la/Pu9ulB + http://openmatt.org/2014/04/04/product_testing/
Lead: Cassie/Karen Smith
Collaborators: Cori Schauer + Tony Santos (User research) + Kat
Tags: [allhands] [usability]
Deliverable: Run a usability test for account creation, event creation, and the new /explore page.
Prepping the Webmaker/explore writing sprint
Prepping for a book sprint to create an open "textbook" or "cookbook" for teaching web literacy. 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
Lead (for prep and logistics): Matt
Collaborators: Kat, Michelle, Claw, Cassie, Kate, Drushka, Fuzzy
Deliverable: Document our roadmap. For shipping the textbook, plus celebrating the community contributing to it. (Kat's Webmaker series)
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.
Lead: Brett
Collaborators: Atul, WebmakerUX team, Doug, Paula, Dev team, Fuzzy, Chloe, Mike Larrson, Jess
Deliverable:
* Documentation for the life cycle of a prototype.
* Documentation for how to talk about and "sell" key current protoypes like the Web Lit Mapper.
Appmaker: Getting Input on User Value 
Time: 9:30-12:30 Wednesday
Goal: test Appmaker strategy against MoCo market research team analysis of the opportunity and need. 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?
MoFo point: Bobby (+Ben)
SF local contacts: 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)
Proposed length: 4-6 hours
Deliverable:
- Document Appmaker audience segmentation & analysis
- Document work plan for feeding audience research into Appmaker product strategy
Working with the GSMA
Time: 12:30-4:30 Wednesday
Goal: design first set of engagements w/ GSMA around Spreadtrum phone, Appmaker, Webmaker. Plus produce a 15 slide aligment deck for internal stakeholders
MoFo point: Mark (+Ben)
SF local contacts: 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?)
Proposed length: 4-6 hours
Deliverable:
* Ship internal slide deck on the mobile development opportunity for Mozilla
* Scope 3 actionable demo collaborations between MoCo + MoFo
Review and iterate Webmaker.org information architecture
Time: 12:30 Wednesday
Goal: Take stock of all the pages on webmaker.org. 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?
Lead: Cassie
Collaborators: Matt, Kat, Kate, Adam
Deliverable: A complete list of all current pages with "jobs" and notes on next steps for each
Resource: Google doc: Every Page Has a Job
Email like a Bawse
Goal: Now that we are sending out emails based on user events, let's make sure that they're as effective as can be.
Lead: Andrea:
Collaborators: Jbuck (infra), Aki (figure out HTML emails), Sabrina (design), Drushka (words)
Deliverables:
* Review existing emails for engagement ladder
* Add "email drafting" to the Encyclopedia Best Practica
* Design attractive HTML emails sent from Webmaker.org
* Build proper HTML email delivery for Webmaker postal service
Building a Webmaker QA Community
Time: Wednesday 12:30
Lead: Jbuck
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.
Collaborators: rbillings, JP, Cade
Deliverables:
Setting up Webmaker in MozTrap
Creating Webmaker tests in MozTrap
Creating Webmaker tasks in "one and done"
Deciding what the next appropriate automated test would be
