What we're shipping in Q2:

• 1) USER STORIES -- Document the on-ramps. As user stories. "When users do x, we want to count and respond like y."
• 2) INFRASTRUCTURE -- Wire the on-ramps. So we can a) count and b) respond when people walk through them.
• 3) COMMUNICATIONS -- Communicate to the on-rampees. The messages users receive once they walk through. With the right calls to action to do more.
• 4) TESTING -- Usability testing for the on-ramps. Where are these users getting stuck or stubbing their toe on these on-ramps? Clear away these blockers to increase our conversion rates.

Documentation

• USER STORIES -- http://mzl.la/contribution_pathways -- Conversion points. Contribution Pathways. User stories for counting and responding, triaged into sprints.
• MOFO CONTRIBUTION DASHBOARD -- Pulling in and visualizing contributor data
• ENGAGEMENT LADDER. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.
• EMAIL LIST SEGMENTS. From BSD https://etherpad.mozilla.org/Webmaker-email-segments
• CONVERSION RATE -- strategy for increasing our conversation rate into sign-ups by 3% to 6% during Maker Party: https://etherpad.mozilla.org/conversion-rate

1) USER STORIES

SPRINT v2 (COMPLETE)

• Goal: Document our MVP user stories in a spreadsheet. "When users do x, we need to count y and respond to z." (COMPLETED HERE)
• Roles: R: Michelle A: Claw C: Amira, Jbuck, Andrea I: webmaker-dev, mozteach
• Tickets: Component: Engagement Ladder | Whiteboard tag: [definitions-v2]

SPRINT v3 & v4 (April 9)

• Goal: Document more of the user stories from user to contributor. Additional use cases beyond the MVP: signing up for training, mentors training and skill-sharing with other mentors, etc.

2) INFRASTRUCTURE

* Building what we need to count and respond to those user stories

INFRASTRUCTURE v1 (April 11)

• Goal: Trigger counting and communications for MVP users stories cases documented in the "definitions" sprint.
• Roles: R: Jbuck A: Brett C: Adam, Michelle, Andrea I: mozteach, webmaker-dev, engagement team
• Bugzilla: Component: Engagement Ladder | Whiteboard tag: infrastructurev1

INFRASTRUCTURE v2 (April 25 -- before All Hands?)

• Goal: Trigger counting and response for the V3 users stories cases documented here: http://mzl.la/contribution_pathways
• Bugzilla: Component: Engagement Ladder | Whiteboard tag: infrastructurev2
• File one of these tickets: http://mzl.la/infrastructurev2

3) Communications

COMMUNICATIONS v2 (April 15)

• Roles: R: Lainie A: Brett & Matt C: Amira, Jbuck, ErikaD, Andrea
• Goal: 1) Review and write current and new email responses. For sign-up, events, teaching kits and remix.
• 2) Learn and model best practices. Learn how to get good at this.
  • (Use this for best practices: http://reallygoodemails.com/ and CC Andrea on all tickets)

Key links

• Email copy: current drafts for all email responses is here: https://teach.etherpad.mozilla.org/emailengagementtemplates
• Bugzilla: Component: Engagement Ladder | Whiteboard tag: [communications-v2] | File one of these tickets

COMMUNICATIONS v3 (April 25 -- before All Hands)

• Roles: R: Lainie A: Brett & Matt C: Amira, Jbuck, ErikaD, Andrea
• Goal: Write the emails. Plus optimization and housekeeping from v2.

4) USABILITY TESTING v1

• Do initial user testing for the V1, V2 and V3 user stories listed here: http://mzl.la/contribution_pathways
• Where are users getting stuck? What are quick wins for addressing them?
• Blog, triage key learnings together, and then file those learnings as actionable tickets.
• Whiteboard tags: [engagement] [testing]

More tickets to file

• • Sign-up: do usability testing and document key learnings
  • Event creation: do usability testing and document key learnings
  • Submit a teaching kit

Lower priority:

• • Sign up and on-boarding for Webmaker training (???)
  • Attend and present in a Webmaker community call (???)
  • Translation and localization (???)
  • Participate in Webmaker QA or testing (???)

Quick Links

Engagement Ladder tickets

• File a ticket
• See all tickets