Webmaker/Engagement Ladder

What we're shipping in Q2:

• Three key sprints:
  • 1) DEFINITIONS -- user stories. "When users do x, we want to count and respond like y." Conversion points, user behaviors and responses we want. To tee up the other two sprints below.
  • 2) INFRASTRUCTURE -- the plumbing we need to a) count and b) send out those responses.
  • 3) COMMUNICATIONS -- the copy and messages those responses require. Encouragement and further calls to action when users do good stuff.

Key documentation for these sprints

• DEFINITIONS SPREADSHEET -- http://mzl.la/contribution_pathways -- Contribution Pathways. User stories that list the counting and responses we need. Broken down by sprint
• CONTRIBUTION DASHBOARD (prototype) -- Pulling in and visualizing contributor data
• ENGAGEMENT LADDER. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.

DEFINITIONS SPRINT

• v2= MVP. Covering the essentials: sign-up, events, etc.
• v3= From users to contributors.
• v4= Badge-related stuff. Dependent on BadgeKit.

DEFINITIONS v2 (April 2) (COMPLETE)

• Goal: Counting and recognizing contributors. Ensure the key uses stories that matter most are documented. For signing up, hosting an event, contributing a kit, and having one of your makes remixed. (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 (April 9) (Complete)

• Goal for v3 sprint: Focus on moving people from user to contributor. Now that the MVP use cases are covered off, what are the next key priorities?

• Roles: R: Michelle A: Claw C: Amira, Jbuck, Andrea I: webmaker-dev, mozteach
• Bugzilla: Component: Engagement Ladder | Whiteboard tag: [definitions-v3]

No results.

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

INFRASTRUCTURE v1 (April 11)

We need to a) count and b) respond to contributors. And deliver them segmented engagements -- custom responses to specific behaviors.

• 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]
• Milestones: (to come)

No results.

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

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.
• 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

Recognize and celebrate contributors. Send them targeted communications with the right follow-ups and Calls to Action.

• Bugzilla: Component: Engagement Ladder | Whiteboard tag: [communications-v2] | File one of these tickets
• Milestones: (to come)

Drafts:

• Event email copy -- draft of current copy we're using for event email responses

No results.

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

Quick Links

Engagement Ladder tickets

• File a ticket
• See all tickets
• [Watch the Engagement Ladder component (to come)]