Allison Leahy - How To Grow and Scale A Global Community Team
-
Upload
feverbee-limited -
Category
Marketing
-
view
2.768 -
download
0
Transcript of Allison Leahy - How To Grow and Scale A Global Community Team
Growing and Scaling a Global Community Team
Fitbit proprietary and Confiden0al 2
The Fitbit Community was re-launched in December 2013, over the first 9 months we grew from: • 0 to 250k member sessions per month • 0 to 25k posts per month • 0 to 250 feature requests per month • 5 to 8 languages • 2 practitioners & a web designer to a team of 30
advocates, moderators, and QAs across 3 sites
Background
Fitbit proprietary and Confiden0al 3
No documenta0on, new team, no worries!
Fitbit proprietary and Confiden0al 4
• Documenting your org structure through personnel heat maps
• Organizing your communications with distribution lists
• Creating feedback loops • Sharing wins!
The Prac0cal and Relevant
Fitbit proprietary and Confiden0al 5
A Winter Deluge
Fitbit proprietary and Confiden0al 6
Fitbit proprietary and Confiden0al 7
Fitbit proprietary and Confiden0al 8
Personnel Heat Mapping
Fitbit proprietary and Confiden0al 9
Personnel Heat Mapping 1. Start with a coverage clock –
24 hours is ideal 2. Standardize to one 0me zone 3. Create a color-‐coded key with
relevant community roles, split out by site
Fitbit proprietary and Confiden0al 10
Personnel Heat Mapping 1. Start with a coverage clock –
24 hours is ideal 2. Standardize to one 0me zone 3. Create a color-‐coded key with
relevant community roles, split out by site
4. Display local 0mes
Local: NOW=() Site 1: =Cell#+TIME(hours, minutes, seconds) Site 2: =Cell#+TIME(hours, minutes, seconds)
Fitbit proprietary and Confiden0al 11
1. Start with a coverage clock – 24 hours is ideal
2. Standardize to one 0mezone 3. Create a color-‐coded key with
relevant community roles, split out by site
4. Display local 0mes 5. Collect schedules 6. Add schedules as a
progression throughout the day by role/site
Personnel Heat Mapping
Fitbit proprietary and Confiden0al 12
1. Start with a coverage clock – 24 hours is ideal
2. Standardize to one 0mezone 3. Create a color-‐coded key with
relevant community roles, split out by site
4. Display local 0mes 5. Collect schedules 6. Add schedules as a
progression throughout the day by role/site
7. Beau0fy your coverage map 8. Share broadly, add it to all
relevant documenta0on, and encourage bookmarking!
Personnel Heat Mapping
Fitbit proprietary and Confiden0al 13
Personnel Heat Mapping A heat map is a graphical representa0on of data where the individual values contained in a matrix are represented as colors. To create a true personnel heat map, you can take it a step further and translate coverage into a matrix. Above is a look at our Social Advocate role over 24 hrs.
Fitbit proprietary and Confiden0al 14
Distribu0on Lists
Fitbit proprietary and Confiden0al 15
Distribu0on Lists
Fitbit proprietary and Confiden0al 16
Distribu0on Lists
Fitbit proprietary and Confiden0al 17
Distribu0on Lists
Fitbit proprietary and Confiden0al 18
Distribu0on Lists
Fitbit proprietary and Confiden0al 19
Distribu0on Lists
Fitbit proprietary and Confiden0al 20
Distribu0on Lists
Fitbit proprietary and Confiden0al 21
Distribu0on Lists
Fitbit proprietary and Confiden0al 22
Distribu0on Lists
Fitbit proprietary and Confiden0al 23
Distribu0on Lists
Fitbit proprietary and Confiden0al 24
Distribu0on Lists
Fitbit proprietary and Confiden0al 25
Feedback Loops
• Trending discussions • Cool ideas • Challenges • Goals for next week • Kudos!
Fitbit proprietary and Confiden0al 26
Feedback Loops
• Trending discussions • Cool ideas • Challenges • Goals for next week • Kudos!
Fitbit proprietary and Confiden0al 27
Feedback Loops
• The confirma0on page is a great place for a note of encouragement or a reminder of what to focus on this week.
Fitbit proprietary and Confiden0al 28
• Sebng a weekly reminder brought compliance from 60% to 95%!
Feedback Loops
Fitbit proprietary and Confiden0al 29
Sharing Wins!
• Leverage those distribu0on lists • Schedule face 0me • Report up, out, down, and all around. Everyone
loves data! • Don’t forget to make 0me for silly stuff
Fitbit proprietary and Confiden0al 30
Fitbit proprietary and Confiden0al 31
QUESTIONS?!