Webmaker/Engagement Ladder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 2: Line 2:
[[File:Engagement ladder sketch.jpeg]]
[[File:Engagement ladder sketch.jpeg]]
=What we're shipping in Q2=
=What we're shipping in Q2=
* '''In Q1 we documented our engagement ladder, listed conversion points, and shipped early dashboards and prototypes.''' In Q2 we'll focus on three key sprints:
* In Q2 we'll focus on three key sprints:
** 1) '''DEFINITIONS''' -- completing our draft spreadsheet. Listing the key conversion points, user behaviors and responses we want.  
** 1) '''DEFINITIONS''' -- completing our draft spreadsheet. Listing the key conversion points, user behaviors and responses we want. This provides the documentation we need for the other two sprints.
** 2) '''INFRASTRUCTURE''' -- the plumbing we need to a) count and b) drive those responses.  
** 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.
** 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===
===Key documentation for these sprints===
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS SPREADSHEET]''' -- '''Conversion Points. A detailed list of engagement tasks, responses, and incentives'''.
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS SPREADSHEET]''' -- '''Conversion Points. User stories that list the counting and responses we need. Broken down by sprint'''  
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD] (prototype)''' -- starting to pull in and visualize contributor data
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD] (prototype)''' -- Pulling in and visualizing contributor data
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. How Webmaker contributors TEACH, BUILD and ORGANIZE
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.


https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/93ly8t8o.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/93ly8t8o.png


=SPRINT 1: DEFINITIONS=
=DEFINITIONS=
Broken into four versions:
* v2= MVP stuff.
* '''v1=''' first draft. from Q2.
* v3= Quick wins on moving people from users to contributors.
* '''v2=''' MVP stuff.  
* v4= Badge-y stuff.
* '''v3=''' Quick wins on moving people from users to contributors.
* '''v4=''' Badge-y stuff. Gated on badge kit implementation.  


===DEFINITIONS v2 (April 2) (COMPLETE)===
===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, having one of your makes remixed, etc. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE])
* '''Goal for v2 sprint''': 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. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE])
* '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: webmaker-dev, mozteach
* '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: webmaker-dev, mozteach
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''  
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''  

Revision as of 13:38, 8 April 2014

Engagement ladder sketch.jpeg

What we're shipping in Q2

  • In Q2 we'll focus on three key sprints:
    • 1) DEFINITIONS -- completing our draft spreadsheet. Listing the key conversion points, user behaviors and responses we want. This provides the documentation we need for the other two sprints.
    • 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 -- Conversion Points. 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.

93ly8t8o.png

DEFINITIONS

  • v2= MVP stuff.
  • v3= Quick wins on moving people from users to contributors.
  • v4= Badge-y stuff.

DEFINITIONS v2 (April 2) (COMPLETE)

  • Goal for v2 sprint: 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)

  • 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 (May 1?)

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

  • Goal: Send targetted communications for 3 - 5 top use cases documented in the "definitions" sprint.
  • Roles: R: Lainie A: Brett C: Amira, Jbuck, ErikaD I: mozteach, webmaker-dev, engagement team
  • Bugzilla: Component: Engagement Ladder | Whiteboard tag: [communications-v2] | File one of these tickets
  • Milestones: (to come)

Drafts:


No results.

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


Quick Links

Engagement Ladder tickets

Retrieved from "https://wiki.mozilla.org/index.php?title=Webmaker/Engagement_Ladder&oldid=962100"