Webmaker/Engagement Ladder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(100 intermediate revisions by 5 users not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
[[File:Engagement ladder sketch.jpeg]]
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
=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:
* 1) '''USER STORIES''' -- '''Document the on-ramps'''. As user stories. "When users do x, we want to count and respond like y."
** 1) '''DEFINITIONS''' -- completing our draft spreadsheet. Listing the key conversion points, user behaviors and responses we want.  
* 2) '''INFRASTRUCTURE''' -- '''Wire the on-ramps.''' So we can a) count and b) respond when people walk through them.  
** 2) '''INFRASTRUCTURE''' -- the plumbing we need to a) count and b) drive those responses.  
* 3) '''COMMUNICATIONS''' -- '''Communicate to the on-rampees.''' The messages users receive once they walk through. With the right calls to action to do more.
** 3) '''COMMUNICATIONS''' -- the copy and messages those responses require. Encouragement and further calls to action when users do good stuff.
* 4) '''TESTING''' -- '''Usability testing for 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 documentation for these sprints===
==Documentation==
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS]''' (draft) -- '''Conversion Points spreadsheet. A detailed list of engagement tasks, responses, and incentives'''.
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 USER STORIES]''' -- http://mzl.la/contribution_pathways -- Conversion points. Contribution Pathways. User stories for counting and responding, triaged into sprints.'''  
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. How Webmaker contributors TEACH, BUILD and ORGANIZE
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ MOFO CONTRIBUTION DASHBOARD]''' -- Pulling in and visualizing contributor data
* [http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD (prototype)] -- starting to pull in and visualize contributor data
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.
* '''EMAIL LIST SEGMENTS'''. From BSD https://etherpad.mozilla.org/Webmaker-email-segments
* CONVERSION RATE -- strategy for increasing our conversation rate into sign-ups by 3% to 6% during Maker Party: https://etherpad.mozilla.org/conversion-rate


https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/93ly8t8o.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/8riscpl0.png
 
=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]''' | [http://mzl.la/O9h44g File one of these tickets]
* '''Milestones''': (to come)


=1) USER STORIES =
'''SPRINT v2 (COMPLETE)'''
* '''Goal''': Document our MVP user stories in a spreadsheet. "When users do x, we need to count y and respond to z."  ([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
* '''Tickets''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''
<div>
<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>
</div>
'''SPRINT v3 & v4 (April 9)'''
* '''Goal''': Document more of the user stories from user to contributor. Additional use cases beyond the MVP: signing up for training, mentors training and skill-sharing with other mentors, etc.
<div>
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
Line 26: Line 43:
"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",
Line 33: Line 50:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
</div>


= SPRINT 2: INFRASTRUCTURE v2 (May 1?)=
=2) INFRASTRUCTURE=
'''We need to a) count and b) respond to contributors'''. And deliver them segmented engagements -- custom responses to specific behaviors.
''* Building what we need to '''count''' and '''respond''' to those user stories''
* '''Goal''': Trigger counting and communications for 3 - 5 top use cases documented in the "definitions" sprint.  
=== 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'''
* '''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 (coming soon)]
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev1'''
* '''Milestones''': (to come)
<onlyinclude>
<div>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev1",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
=== 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
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev2",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>


= 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]''' | [http://mzl.la/1dNhNox File one of these tickets]
<div>
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
Line 46: Line 105:
"product": "webmaker",
"product": "webmaker",
"component":"Engagement Ladder",
"component":"Engagement Ladder",
"whiteboard": "[infrastructure]",
"whiteboard": "[communications-v2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 53: Line 112:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
</div>
=== 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.
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[communications-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
= 4) USABILITY TESTING v1=
* Do initial user testing for the V1, 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.
* <b>Whiteboard tags</b>: [engagement] [testing]
<div>
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"whiteboard": "[engagement] [testing]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>
==More 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


= SPRINT 3: COMMUNICATIONS (May 1?)=
Lower priority:
Goal: Recognize contributors. Nudge others towards contribution. Make sure our key uses cases are supported by good communications responses when people take the key actions we want.
** Sign up and on-boarding for Webmaker training (???)
* Roles: R: Lainie A: Brett C: Amira, Jbuck, ErikaD I: mozteach, webmaker-dev, engagement team
** Attend and present in a Webmaker community call (???)
** Translation and localization (???)
** Participate in Webmaker QA or testing (???)


=Quick Links=
===Quick Links===
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webmaker&component=Engagement%20Ladder File a Webmaker Engagement Ladder ticket]
'''Engagement Ladder tickets'''
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=9811999&query_format=advanced&component=Engagement%20Ladder&product=Webmaker See all Webmaker Engagement Ladder tickets]
* [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]

Latest revision as of 13:12, 5 May 2014

ry8lxg84.png

What we're shipping in Q2:

  • 1) USER STORIES -- 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) TESTING -- Usability testing for 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.

Documentation

8riscpl0.png

1) USER STORIES

SPRINT v2 (COMPLETE)

  • Goal: Document our MVP user stories in a spreadsheet. "When users do x, we need to count y and respond to z." (COMPLETED HERE)
  • Roles: R: Michelle A: Claw C: Amira, Jbuck, Andrea I: webmaker-dev, mozteach
  • Tickets: Component: Engagement Ladder | Whiteboard tag: [definitions-v2]

No results.

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


SPRINT v3 & v4 (April 9)

  • Goal: Document more of the user stories from user to contributor. Additional use cases beyond the MVP: signing up for training, mentors training and skill-sharing with other mentors, etc.

No results.

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


2) INFRASTRUCTURE

* Building what we need to count and respond to those user stories

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?)

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.

Key links

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%);


4) USABILITY TESTING v1

  • Do initial user testing for the V1, 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.
  • Whiteboard tags: [engagement] [testing]

No results.

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


More 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

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