Webmaker/Engagement Ladder: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(20 intermediate revisions by 2 users not shown)
Line 2: Line 2:
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
=What we're shipping in Q2:=
=What we're shipping in Q2:=
* 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''' -- 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''' -- '''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) send out 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 links===
==Documentation==
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS SPREADSHEET]''' -- http://mzl.la/contribution_pathways -- Contribution Pathways. User stories that list the counting and responses we need. Broken down by sprint'''  
* '''[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.'''  
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD] (prototype)''' -- Pulling in and visualizing contributor data
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ MOFO CONTRIBUTION DASHBOARD]''' -- Pulling in and visualizing contributor data
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.
* [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/8riscpl0.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/8riscpl0.png


=1) DEFINITIONS =
=1) USER STORIES =
===DEFINITIONS v2 (April 2) (COMPLETE)===
'''SPRINT v2 (COMPLETE)'''
* '''Goal''': MVP user stories. Covering the key bases: signing up, entering an event, etc. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE])
* '''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
* '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: webmaker-dev, mozteach
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''  
* '''Tickets''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''  
<div>
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
Line 31: Line 34:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
===DEFINITIONS v3 & v4 (April 9) (COMPLETE)===
</div>
* '''Goal''': From user to contributor. Additional use cases beyond the MVP: signing up for training, presenting on a community call, etc.  
'''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 45: Line 50:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
</div>


=2) Infrastructure=
=2) INFRASTRUCTURE=
''* Building what we need to '''count''' and '''respond''' to those user stories''
=== INFRASTRUCTURE v1 (April 11)===
=== INFRASTRUCTURE v1 (April 11)===
* '''Goal''': Trigger counting and communications for MVP users stories cases documented in the "definitions" sprint.  
* '''Goal''': Trigger counting and communications for MVP users stories cases documented in the "definitions" sprint.  
Line 52: Line 59:
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev1'''
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev1'''
<onlyinclude>
<onlyinclude>
<div>
<bugzilla>
<bugzilla>
{
{
Line 62: Line 70:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
</div>
=== INFRASTRUCTURE v2 (April 25 -- before All Hands?)===
=== 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
* '''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'''
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev2'''
* '''File one of these tickets''': http://mzl.la/infrastructurev2
* '''File one of these tickets''': http://mzl.la/infrastructurev2
<div>
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
Line 77: Line 87:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
</div>


= 3) Communications =
= 3) Communications =
Line 88: Line 99:
* '''Email copy''': current drafts for all email responses is here: https://teach.etherpad.mozilla.org/emailengagementtemplates
* '''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]
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[communications-v2]''' | [http://mzl.la/1dNhNox File one of these tickets]
<div>
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
Line 100: Line 112:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
=== COMMUNICATIONS v3 (April 22)===
</div>
=== 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.
<div>
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
Line 115: Line 129:
</bugzilla>
</bugzilla>
</onlyinclude>
</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
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]

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]

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


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.

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


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

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


INFRASTRUCTURE v2 (April 25 -- before All Hands?)

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.

Key links

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


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.

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


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]

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 403 [1] => Forbidden ) ) 1


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.allizom.org/index.php?title=Webmaker/Engagement_Ladder&oldid=972996"