Webmaker/Engagement Ladder: Difference between revisions
< Webmaker
Jump to navigation
Jump to search
| Line 100: | Line 100: | ||
</bugzilla> | </bugzilla> | ||
</onlyinclude> | </onlyinclude> | ||
=== COMMUNICATIONS v3 (April | === COMMUNICATIONS v3 (April 25 -- before All Hands)=== | ||
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea''' | * '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea''' | ||
* '''Goal''': Write the emails. Plus optimization and housekeeping from v2. | * '''Goal''': Write the emails. Plus optimization and housekeeping from v2. | ||
| Line 115: | Line 115: | ||
</bugzilla> | </bugzilla> | ||
</onlyinclude> | </onlyinclude> | ||
=== USABILITY TESTING v1 (April 25)=== | |||
* Do initial user testing for the V2 and V3 user stories listed here: http://mzl.la/contribution_pathways | |||
* Where are users getting stuck? What are quick wins for addressing them? | |||
* Blog, triage key learnings together, and then file those learnings as actionable tickets. | |||
Tickets to file: | |||
** Sign-up: do usability testing and document key learnings | |||
** Event creation: do usability testing and document key learnings | |||
** Submit a teaching kit | |||
Lower priority: | |||
** Sign up and on-boarding for Webmaker training (???) | |||
** Attend and present in a Webmaker community call (???) | |||
** Translation and localization (???) | |||
** Participate in Webmaker QA or testing (???) | |||
===Quick Links=== | ===Quick Links=== | ||
'''Engagement Ladder tickets''' | '''Engagement Ladder tickets''' | ||
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webmaker&component=Engagement%20Ladder File a ticket] | * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webmaker&component=Engagement%20Ladder File a ticket] | ||
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=9811999&query_format=advanced&component=Engagement%20Ladder&product=Webmaker See all tickets] | * [https://bugzilla.mozilla.org/buglist.cgi?list_id=9811999&query_format=advanced&component=Engagement%20Ladder&product=Webmaker See all tickets] | ||
Revision as of 15:53, 16 April 2014
What we're shipping in Q2:
- 1) DEFINITIONS -- Document the on-ramps. As user stories. "When users do x, we want to count and respond like y."
- 2) INFRASTRUCTURE -- Wire the on-ramps. So we can a) count and b) respond when people walk through them.
- 3) COMMUNICATIONS -- Communicate to the on-rampees. The messages users receive once they walk through. With the right calls to action to do more.
- 4) NEW: USABILITY TESTING -- User test the on-ramps. Where are these users getting stuck or stubbing their toe on these on-ramps? Clear away these blockers to increase our conversion rates.
Key links
- 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
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]
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
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.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
2) Infrastructure
INFRASTRUCTURE v1 (April 11)
- 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
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
INFRASTRUCTURE v2 (April 25 -- before All Hands?)
- Goal: Trigger counting and response for the V3 users stories cases documented here: http://mzl.la/contribution_pathways
- Bugzilla: Component: Engagement Ladder | Whiteboard tag: infrastructurev2
- File one of these tickets: http://mzl.la/infrastructurev2
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
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
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
COMMUNICATIONS v3 (April 25 -- before All Hands)
- Roles: R: Lainie A: Brett & Matt C: Amira, Jbuck, ErikaD, Andrea
- Goal: Write the emails. Plus optimization and housekeeping from v2.
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
USABILITY TESTING v1 (April 25)
- Do initial user testing for the V2 and V3 user stories listed here: http://mzl.la/contribution_pathways
- Where are users getting stuck? What are quick wins for addressing them?
- Blog, triage key learnings together, and then file those learnings as actionable tickets.
Tickets to file:
- Sign-up: do usability testing and document key learnings
- Event creation: do usability testing and document key learnings
- Submit a teaching kit
Lower priority:
- Sign up and on-boarding for Webmaker training (???)
- Attend and present in a Webmaker community call (???)
- Translation and localization (???)
- Participate in Webmaker QA or testing (???)
Quick Links
Engagement Ladder tickets