Webmaker/Engagement Ladder: Difference between revisions
< Webmaker
Jump to navigation
Jump to search
No edit summary |
|||
| Line 38: | Line 38: | ||
* '''Goal''': Trigger counting and communications for 3 - 5 top use cases documented in the "definitions" sprint. | * '''Goal''': Trigger counting and communications for 3 - 5 top use cases documented in the "definitions" sprint. | ||
* '''Roles''': R: '''Jbuck''' A: '''Brett''' C: '''Adam, Michelle, Andrea''' I: '''mozteach, webmaker-dev, engagement team''' | * '''Roles''': R: '''Jbuck''' A: '''Brett''' C: '''Adam, Michelle, Andrea''' I: '''mozteach, webmaker-dev, engagement team''' | ||
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[infrastructure]''' | [File one of these tickets | * '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[infrastructure]''' | [http://mzl.la/engagement_infrastructure_ticket] File one of these tickets] | ||
* '''Milestones''': (to come) | * '''Milestones''': (to come) | ||
| Line 58: | Line 58: | ||
* '''Goal''': Send targetted communications for 3 - 5 top use cases documented in the "definitions" sprint. | * '''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''' | * '''Roles''': R: '''Lainie''' A: '''Brett''' C: '''Amira, Jbuck, ErikaD''' I: '''mozteach, webmaker-dev, engagement team''' | ||
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[communications]''' | [File one of these tickets | * '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[communications]''' | [http://mzl.la/engagement_communications_ticket File one of these tickets] | ||
* '''Milestones''': (to come) | * '''Milestones''': (to come) | ||
Revision as of 15:40, 2 April 2014
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:
- 1) DEFINITIONS -- completing our draft spreadsheet. Listing the key conversion points, user behaviors and responses we want.
- 2) INFRASTRUCTURE -- the plumbing we need to a) count and b) drive 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 (draft) -- Conversion Points spreadsheet. A detailed list of engagement tasks, responses, and incentives.
- ENGAGEMENT LADDER. How Webmaker contributors TEACH, BUILD and ORGANIZE
- CONTRIBUTION DASHBOARD (prototype) -- starting to pull in and visualize contributor data
SPRINT 1: DEFINITIONS v2 (April 11)
Start with the 3 - 5 uses stories we care about most. (e.g., user signs up for an account; user adds an event; user's teaching kit get remixed / localized.) Rather than trying to do everything to start.
- Goal: Define conversion points when people take action. Showing how they move from User-> Supporter-> Contributor
- Roles: R: Michelle A: Claw C: Amira, Jbuck, Andrea I: webmaker-dev, mozteach
- Bugzilla: Component: Engagement Ladder | Whiteboard tag: [definitions] | File one of these tickets
- Milestones: (to come)
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
SPRINT 2: INFRASTRUCTURE v2 (May 1?)
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 3 - 5 top use 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: [infrastructure] | [1] File one of these tickets]
- Milestones: (to come)
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
SPRINT 3: 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] | File one of these tickets
- Milestones: (to come)
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);