Webmaker/Engagement Ladder: Difference between revisions
| Line 62: | Line 62: | ||
{ | { | ||
"product": "Webmaker", | "product": "Webmaker", | ||
"status_whiteboard": "infrastructurev1", | "status_whiteboard": "infrastructurev1", | ||
"bug_status": "__open__", | "bug_status": "__open__", | ||
Revision as of 18:14, 14 April 2014
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.
1) DEFINITIONS
- 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: 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]
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
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.
- Roles: R: Michelle A: Claw C: Amira, Jbuck, Andrea I: webmaker-dev, mozteach
- Bugzilla: Component: Engagement Ladder | Whiteboard tag: [definitions-v3]
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
2) Infrastructure
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)
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
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
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
COMMUNICATIONS v3 (April 22)
- Roles: R: Lainie A: Brett & Matt C: Amira, Jbuck, ErikaD, Andrea
- Goal: Write the emails. Plus optimization and housekeeping from v2.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1
Quick Links
Engagement Ladder tickets