AllHands/Funnel Feeding: Difference between revisions
Brett Gaylor (talk | contribs) |
Brett Gaylor (talk | contribs) |
||
Line 11: | Line 11: | ||
/>* press kit for Science Lab<br | />* press kit for Science Lab<br | ||
/><br | /><br | ||
/> | |||
===Partnerships: becoming a closing machine=== | ===Partnerships: becoming a closing machine=== |
Revision as of 04:41, 26 April 2014
Getting Real About Marketing + Press
This is critical. We have to pour as many people into the top of our funnel as possible. Press is a huge and proven way of doing this. For example, if we landed two Lifehacker articles per quarter, we'd be tripling our users. We don't currently have solid press kits/marketing kits for our products. Let's make some. Plus work out the details for how we're going to pitch Webmaker to press going forward.
Lead: Erica S and Lainie
Collaborators: Amira, Erin K, Kaitlin T, Erika D, Sabrina, Dave Steer, Hannah, Kaitlyn, Erin Kissane, Dan Sinker
Note: Loop in Moco Marketing?
Time Window: 3-4 hours
Deliverables:
* press kit for Webmaker, Maker Party and Training Launch
* press kit for Open News
* press kit for Science Lab
Partnerships: becoming a closing machine
We now work from an integrated pipeline. It contains partners that bring us funding, contributors, or both. This means two things: (i) further integrating our recruitment, product, and management of partners, and (ii) become a closing machine.
Goal: Cultural: Shift to being 'closers that care'. Practical: Log and start to action all of our leads. Account for managed growth through grants.
Lead: Ben Moskowitz
Collaborators: Geoff MacDougall, Matt Thompson, Hannah, Lynn Melander Moore, Amira Dhalla
Time Window: 2 hours
Deliverable: Prototype an interface between Webmaker requirements and Fundraising lead generation
QUESTION: what does that deliverable mean? What are we going to document or make?
+1 (GM)
Going Global: Three new markets for Webmaker in 2014
What they need from us and how we'll win. We have funded partnerships planned in Bangladesh, Brazil and more. Let's focus on where we are funded and do it well. Show where geographically anchored / regional funding is; talk about creating more visibility about the data we have; leverage planned Maker Parties in these key locales; and measure where in the world Mozilla can make impact.
Lead: Ben Moskowitz; Adam Lofting
Collaborators: Michelle, Chris, Geoff, An-Me, Amira
+1 (BG) +1 (MT)+1AMC +1 BM +1 (PLD)
Deliverable: Document our plan for new markets ( and link to it here: https://wiki.mozilla.org/Webmaker/Markets https://wiki.mozilla.org/Webmaker/Markets )
Deliverable: Document a plan for informed, data-based decision making on global expansion
- Note: Synch this with the market and comms research MoCo is already doing
Driving Mozilla-wide participation in Maker Party
From Open News to the Science Lab and beyond, let's make sure this year's Maker Party includes all areas of MoFo. This can also include how to leverage upcoming MozCamps, plus Mozilla's new "gathering plan" for distributed events. Let's also pick a few likely MoCo groups and document with them what they might do as well.
Lead: Amira/Michelle
Collaborators: Winston, WPR folks for Mozilla-spaces events
Deliverable:
Open News and Science Lab document what they're going to do for Maker Party
Document with MDN what they might do as part of Maker Party
Draft a Maker Party story and CTAs targeted directly at Mozilla community members
- (could be a draft WordPress landing page on the new Maker Party site. Then shipped to Mozilla.org or elsewhere.)
Converting Maker Party event participants into contributors
How do we turn Webmaker and Maker Party event participants into users, supporters and contributors? This is one of the most important things we can do towards our 10k contributor goal this year. And it's hard. It will take a cross-team approach with engineers, community team and partnership teams working together. Let's get the key stakeholders together to agree on strategy and document a cross-team sprint together here:
https://wiki.mozilla.org/Webmaker/Events
Lead: Brett + Matt
Required: Brett, Matt, Amira, Gavin, Cassie
Requested: Michelle, Kate Hudson, Lainie
Context and reading: https://etherpad.mozilla.org/Events
Deliverable: Get consensus with stakeholders. Then document our events roadmap. https://etherpad.mozilla.org/Events https://wiki.mozilla.org/Webmaker/Events
Project:Trust -- Mozilla Campaign Coordination
Trust is an emerging theme in many campaigns going on across Mozilla: marketing, advocacy, policy, engagement, education. The leads of the campaigns have agreed to start meeting to coordinate the work, maybe ship a shared platform or two. This is the first meeting of that group.
Lead: Geoff MacDougall
Collaborators: Dave Steer, Erica Sackin, Andrea Wood, Mary Ellen Muckerman, Eric Petitt, Michelle Thorne, Alex Fowler
SF local contacts: Dave Steer, Eric Petitt
Proposed length: 90 mins
Deliverable: Document our plan and next steps for leveraging Trust campaigns
+1 (GM; this is going to happen) +1AMC
Maker Party: Real Life User Stories (the theatrical experience)
Let's role-play to see how ready we are. We've all spent a number of months building systems, content, funnels, and tools that let us engage, support, and provide value to our many types of users, supporters, and contributors. On July 15th those systems, content, and funnels will be put to the test. We need to rehearse and drill our processes. This session will see us act out (literally) the user stories in our engagement ladder work, making sure none of the users we need to engage run into walls or black holes.
Lead: Geoffrey MacDougall
Collaborators: Amira Dhalla, Chris Lawrence, Matt Thompson
Proposed Length: A morning
Deliverable: A captivating theatrical experience directed by Geoffrey MacDougall, featuring a full cast of MoFos.
Add to our current Engagement Ladder user stories where necessary. Triaged and prioritized here: http://mzl.la/contribution_pathways
Hive Documentation
Goal: Ship pages of the Hive Cookbook. Documenting and outlining existing Hive practices, strategies, goals and thinking onto the Mozilla Wiki. Started here https://wiki.mozilla.org/Webmaker/Hive
Lead: Chris L, Leah, Sam Katherine
Collaborators: Robert, Elsa, Julia, Lainie, Karen
Non MOFO invitee: Zakyia Harris
Proposed length: 1/2 day
Deliverables:
* Ship new Hive Cookbook pages for Hive Chicago, Toronto and NYC.
* Update main Hive Landing page and begin building out further Hive resource pages like FAQ
Webmaker + MDN: prepping for May workweek
Goal: Determine, plot and start hacking on easy wins in preparation for the end of May MDN/Webmaker workweek. Plus document larger strategic goals for collaborating with MDN going forward. Discuss the Thimble roadmap (and Thimble tutorials in particular) and see how MDN needs can be included.
MoFo lead: Laura/Brett
SF local contacts: Ali
Proposed length: 1/4 day
Deliverables:
* Train MDN staff to create Thimble tutorials.
* Update MDN staff on product vision for Thimble and Brackets.
* Transfer knowledge in creating MakeAPI galleries
New Communities Co-design session: make a page on mozilla.org
Lead: Dan/Erin Kissane
Collaborators: Kaitlin, Dave, Studio MoFo
Local SF contact: Jen Bersch (mozilla.org PM)
Goal: Collaborate & sprint on making a one-pager "New Communities" page on Mozilla.org. Plus getting "News" and "Science" added to the Mozilla.org "get involved" page. http://www.mozilla.org/contribute/ This can be a great way to tell the story around what Mozilla is doing in these new spaces, plus drive referral traffic and contributors to those projects.
time window: 6hrs, max
+1 DS +1 (KT)
Deliverable:
Ship the page. With copy and design that follows Mozilla.org style
Write copy for getting "News" added to the "Get Involved" page
Write copy for getting "Science" added to the "Get Involved" page
File the tickets with MoCo colleagues to get that work shipped to mozilla.org
Building a diverse pool of Webmaker contributors
Beginning first with our code contributors, we want to ensure that all contributors feel welcome in our open source project. Let's first examine what condititions and guidelines we should establish, where we're doing well, and we're we need to improve. Then we'll turn this into an inviting "one stop shopping"page at developer.webmaker.org that can onboard new code contributors.
Lead::Kate
Deliverables:
Draft of Webmaker code contributor guidelines
Prototype of developer.webmaker.org