Webmaker/Engagement Ladder: Difference between revisions
< Webmaker
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/93ly8t8o.png | https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/93ly8t8o.png | ||
=SPRINT 1: DEFINITIONS v2 (April | =SPRINT 1: 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. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE]) | |||
* '''Goal''': | * '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: '''webmaker-dev, mozteach''' | ||
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]''' | [http://mzl.la/O9h44g File one of these tickets] | |||
<onlyinclude> | |||
<bugzilla> | |||
{ | |||
"product": "webmaker", | |||
"component":"Engagement Ladder", | |||
"whiteboard": "[definitions-v2]", | |||
"include_fields": "id, summary, whiteboard, assigned_to, status", | |||
"maxrows":"50", | |||
"order": "bug_id" | |||
} | |||
</bugzilla> | |||
</onlyinclude> | |||
=SPRINT 1: DEFINITIONS v3 (April 11)= | |||
** v3 sprint: Focus on moving people from user to contributor. | ** v3 sprint: Focus on moving people from user to contributor. | ||
| Line 27: | Line 41: | ||
"product": "webmaker", | "product": "webmaker", | ||
"component":"Engagement Ladder", | "component":"Engagement Ladder", | ||
"whiteboard": "[definitions]", | "whiteboard": "[definitions-v3]", | ||
"include_fields": "id, summary, whiteboard, assigned_to, status", | "include_fields": "id, summary, whiteboard, assigned_to, status", | ||
"maxrows":"50", | "maxrows":"50", | ||
Revision as of 19:30, 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 SPREADSHEET (draft) -- Conversion Points. A detailed list of engagement tasks, responses, and incentives.
- CONTRIBUTION DASHBOARD (prototype) -- starting to pull in and visualize contributor data
- ENGAGEMENT LADDER. How Webmaker contributors TEACH, BUILD and ORGANIZE
SPRINT 1: 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] | File one of these tickets
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
SPRINT 1: DEFINITIONS v3 (April 11)
- v3 sprint: Focus on moving people from user to 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
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)
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)]