Webmaker/Engagement Ladder

From MozillaWiki
Jump to navigation Jump to search

ry8lxg84.png

What we're shipping in Q2:

    • 1) DEFINITIONS -- 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) NEW: USABILITY TESTING -- User test 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.

Key links

8riscpl0.png

1) DEFINITIONS

DEFINITIONS v2 (April 2) (COMPLETE)

  • Goal: MVP user stories. Covering the key bases: signing up, entering an event, etc. (COMPLETED HERE)
  • Roles: R: Michelle A: Claw C: Amira, Jbuck, Andrea I: webmaker-dev, mozteach
  • Bugzilla: Component: Engagement Ladder | Whiteboard tag: [definitions-v2]

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


DEFINITIONS v3 & v4 (April 9) (COMPLETE)

  • Goal: From user to contributor. Additional use cases beyond the MVP: signing up for training, presenting on a community call, etc.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


2) Infrastructure

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

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


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

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


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.

Key links

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


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.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


4) USABILITY TESTING v1 (April 25)

  • Do initial user testing for the 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.

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