Contribute/Archive/Community Building Team/Meetings/2014-08-Workdays

From MozillaWiki
Jump to: navigation, search


  • Sean Bolton
  • David Boswell
  • Jennie Rose Halperin
  • Christie Koehler
  • Michelle Marovich
  • Pierros Papadeas
  • William Quiviger
  • Larissa Shapiro
  • Emma Irwin (Tues/Wed)
  • Dietrch Ayala
  • Mary Ellen Muckermann (Tues/Wed)
  • Kristin Baird (Tues/Wed) 
  • Caneel Joyce (Tues/Wed)


  • Portland space
    • Room: Hair of the dog and Alameda


1) We get on the same page about what's been happening
2) We figure out how we want to be working together
3) We make a plan for working together for the rest of the year


        1. CBT understands goals and structure of Grow Program and its role
        2. Review of all community building content
        3. Review of pathways/state of teams for all contribution areas 
        4. Review of project planning process goals, strategy, next steps
        this one is probably only relevant to a sub-portion of the team

  • 11:00-12:00 Grow Program Overview & CBT’s Role
  • 12:00-1:00   Lunch
  • Unnamed thing "Grow Content Teams" Or, possibly "How events are supporting top line goals."
  • 1:00-2:00    Content Kick Off - Part Deux (for those that missed the kick off on Monday due to travel) 
  • 2:00-3:00    Project Planning Discussion 
  • 3:00-4:00    Alignment/Review of contribution areas and content (strategy documents)
  • 4:00-5:00    Review of community building content (All)
  • 5:00        Open Questions 

  • Wednesday, August 13 (Hair of the Dog until 12 / Alameda afternoon)
    • Theme: Getting on the same page about our work together
      • 9:00-9:30: Celebrating (David)
        • Our passion -- and how it aligns with what the organization needs now
          • Our  passion is awesome, and also needs to be harnessed so we can work  together - we're here to build a system to harness our project's  community's / passion
        • Our results -- we set out to be trusted partners and we have done that
          • our teams need us to be their partners and helping them be successful
            • and we've been successful! even though we've only been doing this a year and it is still brand new
          • "Without CBT's partnership this would still be a thought and not a reality." - Rob Middleton
          • "The  exercise we did was fantastic too.  It was not long and drawn out.  It  was quick, to the point, and got done what we needed." -- Darren Herman
          • “This  has been a fantastic initiative. It has demonstrated in my view, how a  little investment can make a big difference.” JB Piacentino
          • “I see good changes happening on the map for India.” - Ravikumar Dandu
          • "Thank you for all your support and energy and drive to do good for Mozilla. I'm really happy that you are here!" -- Chris Beard
        • Jennie: really excited about new vouching system; loved getting vouches from many volunteers and giving vouches to others
        • Larissa: happy to see how much work we've done on metrics and getting visibility
        • William: working in more integrated way, with fewer silos, feeling of working together as one team is really crystallizing
        • Michelle: Visibility of Wiki Working Group. 
        • Mary Ellen: Openness of team. Ability to take new people in and in a way that is in the spirit of moving forward with everyone.
        • Sean:  Intentionality around creating a sense of belonging in our community  building and that we have the opportunity to participate in that.
        • Caneel: Bravery in creative destructive. Intentionality. 
        • Larissa: Value how much people on team really listen.
        • Kirsten: 2nd what Mary Ellen and ? said.
        • Michelle: David, for leading by example. Giving us leeway for discussion, communication is subtle but there is teaching there.
        • Pierros: Pioneering community building across organization, setting standards for community building.
        • William: Brought chocolate to celebrate.
      • 9:30-9:45: What do we all need over the next three days?  Roles, norms, etc.
        • Our alliance:
          • Don't interrupt
          • One person talking at a time
          • lower screen unless taking notes or watching notes – be present!
          • be prepared
          • assume good intent...
            • ask for clarification
            • believe people have a plan
            • don't weaponize the alliance
            • alliance is not to silence people
          • speak if something isn't working
          • value the pause
          • stay on topic
          • focus – make sure we land somewhere with the discussion
        • Roles
          • Temperature taker: William (emo/bio guardian)
          • Note taker (Larissa, Caneel, Kristin, Christie, Jennie, Sean)
          • Take stack (Current Facilitator)
      • 9:45-11:00: Partnerships Status Sharing (Michelle)
      • Homework for this session:  Come prepared to answer (in this format) for EVERY partnership you have (
        • What stage of the lifecycle are they in?
        • What problems are they trying to solve?
        • What are their blockers?
        • Where are they succeeding?
        • Where do you see your interactions with them being most useful to them as clients?
        • I'd  suggest adding a point about how the work in the partnership ties back  to supporting one of our key project goals (Scale Firefox OS, Grow usage  of Firefox, etc)
      • simplified team/goal table:
      • For reference: partner dashboard is at
    • 11:00-11:15: Break
    • 11:15-12:00: Partnership discussion continued
    • 12:00-1:00: Lunch
    • 1:00-3:00: Improving visibility (Michelle/Sean)
      • Frame: Proving that the experiment with intentionality was a success
      • Creating the components of a communications campaign for the work we are doing. 
        • Our Principles of Trusted Partnership
        • 3 Main Audiences and Messages
        • How our Stories Fit into them
        • Create communications calendar for telling those stories.


Audience: Executives
Message: Business impact to top line goals
Outcome(s): 3-4 stories: how do we affect these very specific things
2015 resources
community supported through policy
2015 community goals will reflect out learnings
<--WIN WIN -->

Audience: Community
Message: What we do to listen and empower them/ opportunities to make things better
Primary = unpaid contributors
Secondary = C.B. on the D.L.
Outcome(s): increase participation in working groups, use our work to remove roadblocks, align community w/ goals, participate in sentiment
Stories: (combat community debt) Increase community participation on working groups
use our work to Remove Roadblocks
Align community with goals

Audience: Influences/Middle Mgmt/Early Adopters/Fast Followers
Message: Value the influencers are seeing in their partnerships
Outcome(s): Influencer speak on behalf so that they influence others and allocate time to community
Stories: WPR- Jim Cook - impact to spaces
Clint @ Director level: Michelle will ask him to talk about her impact on QA
Darren @ Steering Committee to share how her support made community possible
Privacy influencer

  • including community is a competitive advantage both for the project and for the individual contributor
  • By  2015 we want people to understand that this is a part of Mozilla and  that it's a respected way of doing things that is a legitimate part of  the organization like marketing or engineering. We need people to  understand that it's not only about 10x and so on. Making more  cheerleaders in the organization.
  • Integrating community into our process by default
  • Getting people to include CBT to plan things from the beginning, and that's how we will optimize the community involvement
  • The true test of a trusted partner is that they say you're awesome when you're not there

2015 ultimate success = community is 1st answer

                Need to reschedule to another time:

  • 3:30-5:00: Lifecycle Doc Sprint (Michelle/Christie)
    • Edit the doc at:
    • What needs to be in the lifecycle beyond scale?  eg, addressing community debt
      • relationship  between pathways/lifecycle/commitment curve - what are these and how do  we provide guidance that "maps" to what people actually want to do

  • Thursday, August 14 (Hair of the Dog until 12 / Alameda afternoon)
  • Theme: Improving team dynamics
  • 9:00-9:45: Spectrogram (William)
    • What are the 3 or 4 other relevant themes?
      • we all need to be handling our partnerships the same way
      • end of the year detailed summary documentation vs. regular documenting
      • our team is all about getting staff to design for participation vs. our team is all about getting staff to design for participation AND connecting them with volunteers
      • it's important to have a weekly meeting rather than a bi-weekly one
      • we should write PPPs every week to inform the team of your progress
  • 9:45-10:45: Future state imagining (Michelle)
  • 10:45-11:00: Break
  • 11:00-11:30: Conversation with Mark Surman (David's vidyo room)
  • 11:30-12:00: Open time
  • 12:00-1:00: Lunch
  • 1:00-2:00: Getting to that future state (David)
    • Revisiting our alliance / group norms
    • Is there anything additional that we need to agree to, to get us to that future state?
    • What needs to be added, changed or removed?
  • 3:30-4:00: Break
  • 4:00-7:00: Happy hour / game hour
    • We're  all in different offices most of the time and don't get to hang out  much.  Let's hang out and play some games together to fix that :)
      • Trivial Pursuit?
      • Apples to Apples?
      • Catan! +1
      • Sentinels of the Multiverse- cooperative
      • Hoopla-- Cooperative
      • Forbidden Island-- Cooperative
  • 6:00: PDX Tech Crawl starts
  • 7:00: Dinner at Andina


  • 2:00-3:30: Working Groups (Larissa)
    • Each  WG come up with 5 (ish) key learnings from the last 6 months.   Then each group gives the 5 (again ish) key goals of the next 6   months... then lets think about the relationships between them and what   to focus on (preview for next week)

  • Friday, August 15 (Alameda all day)
  • Theme: Planning for the rest of the year
  • 9:00-10:00: Delivering impact (David)
    • What do each of us need in order to deliver impact through our partnerships for the rest of the year?
    • William: Impact for WPR with transition to David Slater
      • William needs backup in his conversation with Dave Slater
      • Focus  on making connection between impact of events on community, impact of  community at events on product ( top line goals), and the money these  spaces will cost. 

  • Larissa: 
    • For privacy and policy, focus on people seeing the link between goals
      • Making that connection between top-line goals and the partnership -- esp. for policy
      • It's about developing a small group of Internet policy activists (from Reps, largely) bring Mozilla policy 
      • Privacy is one of the most compelling stories from Firefox
      • Policy can make space *for* firefox
    • GROW
      • what will happen??
      • need support in getting the right thngs to happen
    • Get involved page
      • we need a roadmap of the get involved page integrated into bugzilla
    • not a lot of agency, but what is going to happen will make a positive impact
      • need support in having agency to get the right things to happen with the backend
  • Jennie
    • about:mozilla newsletter (contributor facing newsletter that goes to 65k people)
      • despite a new RACI ownership has been murky
      • newsletters have been going out *almost* on schedule
      • giant too-many-people process set out in March caused a lot of problems
      • Jennie is the only person who considers it a P1
      • the people who have the key to shipping it don't see it as a P1 (exact target)
      • Ask of the team: please uplevel good stories for the newsletter - no need to fill out the form, just talk to Jennie
        • Useful items include: Stories: specific and timely contribution opportunities; contributors you've been working with, photos
        • All Jennie needs is: story, who to talk to
  • Sean
    • Creating continuity after his internship -- for example, he is building momentum with user research
    • support and implement contribute.json (
    • info for how to influence Get Involved page
    • stories for internal marketing campaign (w/ Michelle)
  • Christie
    • need help because don't have enough time working more on education and culture stuff
      • helps impact retention
    • L10n challenges are too much to handle on own – need team to help here
      • "L10n partnership sprint" to bring in expertise from team to solve initially
    • WebDev overlap with product areas others on the team have; too many stakeholders?
    • Christie will set up an L10n partnership sprint
    • Mozilla WebDev conference??
    • Backburner WebDev and then do a sprint for L10n. 
    • Carve out protected space for curriculum
      • Bring in outside resources like Open Source doc sprint
  • Pierros
    • partnerships are going okay
    • Pierros  needs to hear more about hardware in general - whatever is going on  with the open hardware space at mozilla (battery development etc)
    • We need a shift of positioning between what we own and get the things that we want if they're run by people who cannot run them
      • Safeguarding initiatives and projects
    • Expanding Systems and Data to talk about more systems at Mozilla than just Baloo
      • Building bridges and expanding beyond the initial scope of our working groups
  • Michelle
    • Content Services is going to make a big impact when they learn to work with community
    • They need an influencer program in the community - which Michelle needs help designing. 
    • Trust is the biggest thing for them
    • If they have open meetings and have influencers join, then it will start to build something interesting
    • Possible  models: Reps SIGs, WebFWD Scouts? How much do you want given people to  "apply" vs a totally open thing where people can come and go. How much  commitment do you need from an influencer? Model of getting one or two  key contributors *on the team* in the way that Ben Kerensa is on RelMan
    • QA:
      • need to support Clint moving to choose a community manager
      • Jennie and Michelle to work together 

  • 10:00-10:45: Working with limited Business Intelligence resources (Pierros)
  • 10:45-11:00: Break
  • 11:00-12:00 Preparing for 2015 (David)
    • What  have we learned this year and what do we recommend for next year?   Having a crisp expression of our learnings and recommendations will be  very useful for upcoming discussions with Mark and Mary Ellen.
      • Learning:  We're seeing a lot of churn and are finding that connecting people to  an initial contribution opportunity is not the main challenge but  rather  keeping them actively involved is.
        • Communication:
        • Recommendation: Expand our goals from connecting contributors to also retaining them
        • Resources needed to do that: None -- this would provide direction for the partnership and Working Group activity above (is that true? if so lets be explict about how)
      • Learning: Dedicated time and attention to building communities around a project produces positive results
        • Recommendation:  We do more partnerships and expand the types of partnerships to include  regional and product focused relationships
        • Resources  needed to do that: More experts on our team and/or having people be  dedicated experts instead of the current split between helping partners  and running working groups
      • Learning:  Teams want participation resources and building them in an open  collaborative way produces results that support the needs of a range of  teams and communities (vs. the way resources and tools have been built  in silos in the past and that produce things that serve the specific  needs of individual teams)
        • Recommendation: We expand our investment into the Working Groups
        • Resources  needed to do that: More people participating in Working Groups and/or  having people be dedicated to Working Groups instead of the current  split between doing that and helping partners
        • Questions: what kind of resources do we mean and are working groups the most effective way to build them? (they might be!)
      • Learning:  We're finding that not all partners are ready to scale and other types  of work are sometimes needed first, such as addressing community debt  for project areas that have been active for a long time (such as QA and  L10n)
      • Learning:  Participation expertise is something that can be learned and we have  many opportunities to grow our skills (taking classes, learning from  other organizations that have done this before, etc).
        • Recommendation:  Identify and cultivate participation skills among staff and volunteers  and identify and cultivate relationships with other orgs (such as the  Red Cross) that we can learn from
        • Resources needed to do that: None -- this would provide direction for the partnership and Working Group activity above
      • Other learnings?
        • setting 2015 for a 2016 that looks like:
          • Mozilla is not a product company with a mission; it's a mission driven company that makes products
          • We are making products in the service of the Web the world needs. People drive the products.We help bring the people.
        • integrate Mitchell’s “build, empower, teach, shape” language into how we communicate – especially the communication campaign
        • word  cloud: build, shape, health, regional, deepen, connect, productize,  manifesto, retention, experiment, expand, impact, alignment, 
          • better know who is coming in
          • by focusing on numbers we are ignoring the overall health of communities
        • we need specification around what a healthy community means
        • "build x number of healthy functional/regional communities" where we define build, healthy, communities
          • health involves reducing churn
        • productization of community to become a vertical inside Mozilla
          • community building becomes a product line of itself; community is still embedded in other product teams
      • "build and empower healthy sustainable global communities that impact key initiatives and support our mission"
        • health measures –
          • retention
          • renewal/growth
          • development
          • sentiment
          • capacity for sustainability
  • 12:00-1:00: Lunch and team photo
  • 1:00-1:30 Preparing for 2015 (continued)
  • 1:30-2:30: Upcoming meetups and team meetings (David)
  • 2:30-3:00: Break
  • 3:00-3:30: Meetups (continued)
  • 3:30-4:00: Closing (David)
    • Our  team is being successful this year because a lot of things are working  right.  Let's close by writing down 3 positive things that we're  thankful for.  Questions to consider are:
      • What is one thing that helped you this week?
      • How is my job better today than it was a year ago?
      • What have others on the team done that has supported me?
    • There's even science that shows that expressing appreciation and gratitude among the team members fosters cohesion