Filed under Community

When it comes to community, does size matter?

Many members of the MongoDB community are excited about the possibility of starting a MongoDB User Group in their hometown. Unfortunately, many of our MUG organizers get discouraged quickly when only a handful of people come to the first meetup. Some give up immediately. They see that the NY or DC or London MUGs regularly have 100+ people attending a lecture, and they assume that that is what success looks like.

But you don’t need 100 people to have a community. Community is about building relationships, sharing experiences, and fostering the exchange of knowledge. By that definition you only need 1 or 2 other people to have a community! And in many cases, that’s how successful tech meetups start.

I recently spoke with Van Riper, the organizer of the Silicon Valley Java User Group, about the origins of his JUG. He told me that the first meetup there were only two people and that they had dinner and drinks and talked about code. He considered it a success. Van kept organizing events, until the group grew to thousands of members.

An intimate gathering to hack, talk, study or something simliar is a completely valid way to start a user group. In fact, sometimes those meetups are even more valuable as people have the opportunity to exchange ideas in a friendly environment.

If you keep meeting consistently (ideally at the same time and in the same place) your group will naturally grow. As the group grows, it becomes easier to attract higher profile speakers and the group grows more. I’ve watched this virtuous cycle occur with all of the large MongoDB User Groups.

In NYC, even though our MUG has grown to nearly 2,000 members, I’m glad that we still organize events such as office hours and study groups to maintain some of the intimacy of the early days. Having a variety of events in a variety of formats and sizes ensures that people across the community are well served.

Ultimately, size does matter: you need to adjust your approach depending on the dynamics of your group. For the new organizers, I encourage you to keep meeting, even if your group is small, and build a core membership from which you can grow. For those running larger meetups, don’t lose sight of what a community is and provide ways for members to build relationships and share their stories. Regardless of the size, you can build a successful community with patience, hard work, and a little creativity.

Community is hygiene not heroics

I’ve been talking to an entrepreneur working on a social/mapping tool called GroupTones to connect local musicians with gigs and one another. Being a cellist in the Boston music scene, he has an intuitive sense of how to build a community around this product. He’s been visiting orchestras at local universities, engaging with people on Twitter, getting feedback on the appropriate subreddits, and starting to blog.

In a recent conversation, we discussed virality. His user base is growing steadily through word of mouth as users recommend the service, but there isn’t any one activity that is causing it to take off.

I told him to keep doing exactly what he’s doing. Building community is a never ending job. If you have a strong community, you’ll always have to manage feedback, maintain relationships, and engage users. It’s not something that you can accomplish in a heroic all-nighter but something that requires constant attention.

As my friend Sumana of the Wikimedia Foundation insightfully puts it, hygiene is more important than heroics.

For example, at 10gen, our community marketing programs started with big, one-day conferences. Those events are crucial for seeding community and continue to be important yearly milestones in each city we visit. The conferences are highly visible, somewhat heroic feats.

What many don’t see is all the work that happens between each conference. User forum posts, IRC questions, and tweets that receive timely responses. Monthly newsletters targeted for each local market. User groups that meet regularly with the financial and logistical support of 10gen. Personal check-ins with key customers and community members. That is the hygiene required to maintain a successful community.

How do you maintain good hygiene? It requires establishing patterns and habits, looking at key metrics at consistent intervals, and making the small stuff visible. I’m hoping to focus more on specific examples of this in future posts.

Measuring ROI on developer event sponsorship

I am consistently impressed by the number of great technology conferences, hackathons, and meetups organized directly by their communities. Organizers bootstrap the event with support from universities, corporations recruiting developers, and companies like 10gen that offer technology products and services.

Since 10gen frequently falls into the categories above, organizers of these grassroots events contact me about supporting them through sponsorship. Hence I thought that I would provide some insight into the evolution of my thinking when it comes to investing in community events.

When I joined 10gen, we were completely focused on adoption, educating the community about MongoDB, and gaining traction. We spoke at local user groups and any conferences that would be interested in learning about NoSQL. We sponsored events to get exposure, but we had a tiny marketing budget so I always negotiated the lowest tier.

As the company grew and hired a sales team, it became necessary to think more critically about how we invest our marketing dollars into developer events. We also had lead generation targets to meet, and events seemed like a great way to accomplish that. It soon became clear that we needed to be more systematic in how we evaluated participation in events.

Initially, it was tempting to measure the success of our participation in an event by looking at the number of leads we gathered, and the subsequent activity. Leads are a concrete, measurable metric, and we can clearly track the conversion to a sales opportunity. This approach biased us towards doing larger sponsorships where we could have a booth. When we have had booths at events, we are able to scan visitors, get their contact information, and sell to them. And with a bigger marketing budget, it seemed logical that we invest in a larger presence at events.

However, after investing in many expensive trade shows, it became evident that the value of a few hundred email addresses couldn’t justify the tens of thousands of dollars that we would have to spend on a booth rental, travel, handouts, and staff time. In addition, the people we met in these booths were generally new to MongoDB. I felt that the conversations we had were valuable for adoption, but most of the leads were not ready for a conversation with a sales rep.

Anecdotally, I knew that the interactions at these events were having an impact. For example, at a MongoDB conference this year, I spoke with a large enterprise customer who told me that they first heard about MongoDB at OSCON two years prior, when one of my colleagues presented. We didn’t sponsor that year, so our investment was just travel and time. It was impossible to track that particular conversion, but that presentation was clearly crucial to that customer’s adoption of MongoDB.

We needed a broader framework for measuring value of each component of event participation. For each event, we started to look at all of the benefits of participation, and assign monetary values to them. What is it worth to us to have 100 people sitting in a room listening to a presentation about MongoDB? How about an attendee speaking with an engineer? How many of those conversations can we have at an event? What’s the value of everyone at the conference going home with a MongoDB coffee mug?

We enumerate each of the items of value associated with participating in the event, assign dollar values, estimate the number of impressions, and total. We then compare to the cost and use this data to prioritize the events. We try to align our budget according to the company expansion and sales goals, so that we are investing in the right territories and so that we don’t end up spread too thin.

Interestingly, I feel that we’ve come full circle: we started as a scrappy startup doing small sponsorships, talking to people at user groups, networking in the hallway track. We experimented with bigger events, but came to the conclusion that the real value of events isn’t in a huge booth, but in the meaningful interactions that we have with individuals. It’s harder to measure this, but it’s a philosophy that is increasingly informing my thought process. Over time, I have started to internalize the values from this model and it’s immediately evident the type of investments we should make.

Based on this model, our approach is increasingly shifting from large trade shows to supporting lots of small community events with small sponsorships. When we participate in an event, we emphasize sending the right speaker and encourage them to work the hallway track. I think that this approach maximizes our reach.

In the next few weeks, I will write a follow up post about how we measure the value of our MongoDB conferences, using some more concrete values.

On hiring developer evangelists and community managers

I’ve been talking to a number of small, technology focused companies about developer outreach. Many are beginning to realize that they need staff dedicated to marketing and developer outreach, but they aren’t sure where to start in terms of finding someone to do this type of work. It’s a challenging role to hire for, as you need someone with a skill set at the intersection of technology and marketing. In addition to profiling a few of my colleagues in the space, I thought I’d provide some insight into places that companies can explore to find candidates for these roles.

Look at your community

Leaders naturally emerge in technical communities. The people within your community who are excited about your technology, who are answering questions on the forum and in IRC, and who are organizing local meetups are the ones that are likely to be effective in a developer evangelism or community management role. And if there isn’t anyone engaged with your product at that level, consider looking at similar communities.

Nathen Harvey strikes me as an excellent example of this approach. While web ops manager at CustomInk, he organized the DC MongoDB and DevOps meetups. As he became more involved in the community, specifically around evangelism of Chef, it was no surprise when OpsCode hired him as their community manager.

Look at your existing staff

Sometimes it’s helpful to look within the company to see if there is someone on the staff that might be well-suited for an evangelism role. There are some engineers that naturally gravitate towards community outreach, but may not realize that this type of position can be a career path for them. Look at the team and see who enjoys interacting with the open source community, attending meetups, and speaking at conferences already.

Some developers may be apprehensive about giving up their engineering responsibilities in order to focus on marketing. In approaching them about a change in their role, I recommend sharing these great blog posts from developer evangelists that I respect tremendously:

Poach

Another approach is to find someone who’s just done it before. There are more technology companies than ever employing engineers in technical evangelism roles. Think about the companies that do amazing work with developer outreach, and find out who is behind that. Participate in events like Community Leadership Summit, local user groups, and technical conferences where technical leaders congregate.

More Resources

I’m not aware of many lists or job boards for these types of roles, but here are a few places to start:

If you have other suggestions, please post in the comments section!

Community Manager Profile: Ana Hevesi of Nodejitsu

Over the past few months, several people have asked me how to find and hire people to do community management and developer outreach. I decided to profile the community managers that I respect the most on my blog in order to provide some insight into the types of people that do this work, as well as their day-to-day activities.

To kick things off, I conducted a short interview with Ana Hevesi, the head of community at Nodejitsu, a company that provides node.js cloud products and services. I met Ana through the Union Square Ventures network when she was working at Shapeways. She has always impressed me with her insights on community, so I’m pleased to share her story here.

Tell me about the community that you manage.

I work with the node.js developer community; these are the people who are pushing the boundaries of server-side Javascript. The community is driven by open source, and it’s attracting a lot of industry veterans as well as hackers who are new to the game. People are passionate about this technology and in many cases they’re coming together across different companies and disciplines to help it succeed.

Describe your role and day-to-day activities.

One of the best things about Nodejitsu is that our company was built out of the node.js community itself. My role is to expand the greater node ecosystem and to build out the people-facing side of Nodejitsu. Specifically, this means I handle all of our sponsorships, our engagement at events (hackathons, conferences, meetups), collaboration with friends and partners on community initiatives, our user feedback pipeline, and keep a watchful eye on engagement with our open source projects. Most recently, I’ve been on a mission to connect to organizers of independently run node meetups around the US (and soon, the world!).

How did you become community manager at nodejitsu?

I’d been working as a community manager for a few years, most recently at Shapeways, but had always found myself drawn to hanging with and working with developers. At the beginning of this year, I decided to start learning Javascript. I’d known HTML and CSS for years, but was frustrated that my front-end development skills stopped there, so I hunkered down and realized that I really loved it. The Nodejitsu team actually found me online, met with me in person, and convinced me to come on board. It was kind of the luckiest thing ever.

You can find Ana on Twitter at @anoemi. Get Ana’s perspective on community by following her awesome blog, Enemy Gate Down.

WhereToMeetup: Connecting Meetup Organizers and Hosts

I’m the co-organizer for four technology meetups in New York City (MongoDB, C++, Python, and Prince Building Tech Talks), and a participant in many, many others (170+ according to my meetup profile). Through my work with the technology community, people have started coming to me for help with their meetup groups. Organizers are almost always looking for space to host their events, and there isn’t an easy way for them to find hosts. I’ve fielded so many space requests that sometimes I joke around that I feel like a broker!

I also speak with lots of New York area companies experiencing rapid growth that want to connect with technical professionals. Yet, these companies are not sure how to engage the technology community.

Several months ago I bounced an idea off of my friend Andy, who is a loyal attendee of both the NYC Python and MongoDB meetups: How about we build a web app to pair meetup groups and organizers together? Andy started prototyping an app, bringing his initial ideas to last week’s Python project night. Andy recruited my friend Dan and several other hackers to talk through the idea and look at ways to use the Meetup API and its directory of spaces to help pair up groups and meetups.

Andy and Dan decided to devote some time to the app during Saturday’s Battle of the Braces hackathon at Meetup HQ. They hacked all day, building out WhereToMeetup. Their demo presentation even included several embarrassing pictures of me. After their demo, Kathryn Fink, the community manager at Meeutp, commented that the #1 problem for meetup organizers is finding space, which reinforced the importance of this project.

Dan and Andy ended up winning a prize for the best use of the Meetup API at the hackathon. Even better, before the prizes were announced they already had a bug fix from someone in attendance at the event! It’s still a work in progress, but you can find the project up on Github.

Thanks again to Andy, Dan, and the rest of the community for running with this idea!

During this whole process, I’ve been thinking about how many companies have great event space that they don’t make available to meetup groups. In some cases, the company doesn’t know how to connect with the community. Usually there are a few interested employees that get discouraged when “the powers that be” starts asking about the group. In particular, Andy has been very enthusiastic about holding more Python project nights, and has been looking for ways to justify to HR the value of hosting a group. To close this post, I thought I’d outline a few key reasons that companies should consider hosting or sponsoring a meetup group.

1. Raising the company profile

Hosting a user group raises the profile of your company within the community. It’s a great opportunity to promote your company, your brand, and your product. Some of the organizers of MongoDB User Group offer development services, hosting platforms, and even a MongoDB monitoring tool. Engaging with the community helps get the word out about the exciting work that they are doing.

2. Passive recruiting

Hosting meetups is a great way for companies to engage in passive recruiting. A tech meetup will bring dozens of skilled, enthusiastic developers into the office. The host of the NY MongoDB User Group mentioned to me that he had hired 4-5 people from the group over the past year. Think about it: using a contingency recruiting agency, he could have spent over $100,000 to hire 4-5 people. In comparison, hosting a meetup seems like a deal! To do this right, you need to have employees on hand to “work” the room. Rather than making a company pitch, the most effective hosts usually focus on getting to know the attendees and showing them a good time. For example, one of our meetup hosts often gives attendees a tour of the office to show off their very cool space. Others give out swag. Still others present on the cool technology that they are building.

3. Building a fun work environment

Engaging with the community creates a fun work environment for the staff. It shows that the company is committed to the employees’ professional development and makes working at the company fun!

Community Leadership Summit and OSCON 2012

This year I participated in Community Leadership Summit (CLS) and OSCON (Open Source Convention). Community Leadership Summit brings together community managers around the world for a free, two-day unconference the weekend prior to OSCON. Like last year, it was an amazing event and I look forward to sharing what I learned on my blog.

A participatory event

In an unconference, the attendees drive the content. Any attendee can pitch a session in the morning, and together we organize the schedule on a giant poster board. Unlike a traditional conference where attendees attend sessions and receive information from a series of individual presenters, an unconference forces everyone to participate and share their expertise. This gives attendees access to the diverse experiences and knowledge from all of the people at the event.


CLS attendees swarm around to schedule sessions for the first day of the conference!

Community managers are diverse

Co-located with OSCON, CLS draws leading community professionals from major open source projects. While the event is skewed towards open source communities, the diversity of attendees at CLS never ceases to amaze me. People come from around the world to share their experiences working on open source projects, managing user groups, sheparding online forums, and more. In addition to the open source crowd, there were participants from major technology companies such as Google, Oracle, and Adobe, community managers at early stage startups, academics, local Portlanders, and even someone building a live/work space in San Francisco.


CLS group photo!

Community management as a profession

In the past few years, community management has emerged as an inter-disciplinary profession. CLS is a rare opportunity for me to connect with other lots of other people who do what I do and share best practices in a variety of areas. I left CLS inspired by many great ideas about metrics, forum management, cultivating speakers, and creating better online events (as well as a second copy of The Art of Community).

CLS wiki

During each CLS session, we appointed someone to take notes on the conversation. We generated an amazing body of knowledge on the CLS wiki, so if you couldn’t attend this year, you can still access information on the topics discussed. Jono Bacon also wrote a great summary of the event on his blog, and Andy Oram of O’Reilly wrote a detailed post on the CLS session on social networks. In the coming weeks, I hope to write some more detailed posts on some specific CLS sessions that I found the most informative.

Interviews with community managers

During CLS, the Kaltura community team interviewed several attendeess about their experiences at the event. I was honored to be featured alongside Jono Bacon (the founder of CLS), Angie Byron of Acquia, my colleague Adam, and many other prominent members of the CLS community. The interviews are available on the Kaltura blog.

My OSCON talk

At OSCON, I gave a talk on scaling community, a presentation similar to the one I gave at Open Source Bridge. In addition to the two blog posts I wrote leading up to OS Bridge on this topic, my slides are posted on SpeakerDeck and the kind folks at Stoic Security and Compliance wrote a summary of my talk on their blog. One of the great things about attending CLS before presenting at OSCON was having so many community managers attend my talk, ask questions, and provide feedback. It made the experience a lot more fun.

Thoughts on Open Source Bridge

This week I attended Open Source Bridge, a completely community and volunteer run conference in Portland. Having attended many large corporate trade shows, OS Bridge felt incredibly refreshing. The diversity of the audience impressed me: in addition to open source developers I met project managers, designers, entrepreneurs, and even a lawyer. I also saw greater participation from women than I’ve seen at any other tech event. The schedule included technical sessions as well as presentations on culture, community, and business. Participants were encouraged to make notes and share knowledge on the sessions using the event wiki. The conference also included some fun perks, including excellent, locally catered food, a massage therapist on site, and a yoga class.

During the two days that I spent at the event, I attended several other fascinating talks. Here are some highlights from my favorite sessions.

Be Bold: An Origin Story

I arrived on Tuesday morning to attend Sumana’s keynote on being bold. Her inspiring talk covered her upbringing, her parents, and her interest in computers as a child. It included a great call to action about empowering young people to get involved in open source.

Text Lacks Empathy

I learned about the challenges of geek communication in Text Lacks Empathy, where Noirin Plunkett and Michael Schwern gave several practical suggestions for reducing miscommunications over email, forum discussions, and bug reports:

  • Perception is reality and by default, when we read factual text we assume the worst emotion
  • State your feelings or use emoticons
  • Geeks can lack tact so it’s always important to apply a little bit of tact in communications by default
  • Consider paraphrasing what the other person is saying to reduce confusion
  • Assume sincerity instead of sarcasm
  • IM is better than email, phone is better than IM, Skype/Video chat is better than phone, but in person communication is best
  • Use the passive voice: “Someone broke the build” implies accusation or blame, so consider “The build is broken.”
  • Start with the summary, then go to the detailed explaination

How We Went Remote

Immediately prior to Text Lacks Empathy, I attended a session from VM Brasseur on How We Went Remote. The challenges that the presenter discussed exemplified many of the concepts covered in Text Lacks Empathy. After discussing the benefits of building a remote team, including access to talent and reduced cost, VM gave some practical tips:

  • Being “in the office” is being logged into the team chat room
  • Documentation is critical! VM would open tickets for her team to update the docs so that it was included in their daily workflow.
  • Getting the team together in person a few times a year is important in order for the staff to gel

What We Talk About When We Talk About Project Management

On Wednesday, I participated in a fun and interactive session called What We Talk About When We Talk About Project Management. Presenter Amye Scavarda, a Drupal Project Manager from Acquia, clearly defined the role of a project manager. She then proceeded to pull up several job descriptions for project managers, demonstrating how a very specific skill set is becoming a catch-all for many companies. The group reviewed and debated the different job listings in a fun and lively discussion.

Scaling Community By Nurturing Leaders

I also presented on Wednesday, giving the presentation version of my recent blog posts on scaling community and why we should invest in community leaders. I posted my slides on SpeakerDeck and look forward to your feedback.

Thanks to everyone at OSB for an amazing and inspiring event. I look forward to next year’s conference, and hopefully I will see some of my new friends at OSCON in a few weeks!

Why invest in community leaders?

Last week I met with my friend Sumana from the Wikimedia Foundation. She works from home and comes to the 10gen office periodically to co-work, and while she was visiting we discussed my upcoming Open Source Bridge talk about scaling community by nurturing leaders. As we were talking, I realized that in my previous post and in my draft slides, I was providing a “how to” on investing in leaders, without really explaining “why.” In this post, I’d like to address the main reasons that investing in community leaders is important.

The Psychological Reason

Creating advocates and brand ambassadors within your community can be incredibly powerful in validating your product. The message about your product is always more powerful coming from another user than coming from a vendor. People also respond better to individualized contact from people that they know. Think about it: are you more likely to respond to a call to action in a newsletter sent to 100,000 people, or to a direct request from someone that you know? Surely the conversion rate on the latter is going to be better.

The Economic Reason

Investing in leaders is also an economical marketing tactic. You can invest a small amount in developing a community leader, and expect a potentially large return from that investment. The most obvious example here is the MongoDB User Group network. Let’s build a quick economic model, assuming that I have $50,000/year to spend and one person’s time. If we take the user group approach, we could effectively support each user group with about $3,500 per year. Here is a rough breakdown of how that investment could be used:

Item Amount Cost
Meetup.com fees Annual Membership $150
T-shirts 100 @ $10/tee $1,000
Stickers 1,500 @ $0.25 per sticker $375
Pizza Once a quarter $1,000
Speaker travel Fly in a guest speaker once a year $1,000
Total Cost   $3,575

With $50,000, we could effectively support 13 user groups with some cash to spare. We would need someone on staff to coordinate those user groups, work with local leaders to organize them, find a venue, and connect speakers.

Assume that each group runs smoothly and achieves an average membership of 300 people. (Some markets, like New York City and San Francisco, could exceed that with over 1,000 members of a tech group, while smaller markets might be successful with 100-150 members.) Our $50,000 investment has reached and engaged 3,900 members of the community across 13 different cities, with each group meeting monthly to discuss our technology.

Now let’s compare that investment to sponsoring a corporate trade show, with the assumption that you already own a booth for these types of events.

Item Amount Cost
Sponsorship Fee Per Show $5,000 (this is on the low end for industry shows)
T-shirts for booth 100 @ $10/tee $1,000
Stickers for booth 1,500 @ $0.25 per sticker $375
Bag insert (literature or something similar) 1,000 $350
Staff travel 2 people $2,000
Booth labor and equipment rental Most shows charge you for things like carpet, electricity, etc. and require that you use the labor at the venue $1,000
Total cost   $9,725

With this cost structure, we could invest in about five trade shows. Let’s say that there are 1,000 people at each show. Overall, we will have had a small interaction with 5,000 people via our bag insert and physical presence at the show. And if we can successfully drive traffic to our booth, we might speak with and gain contact information for 25% of the total show attendance, acquiring 1,250 leads that we can market to. Those leads will be of mixed quality: while some will be interested in our product, most will be unqualified leads requiring lead nurturing and consistent follow up before they become customers.

In this model, you can see that the distributed user group model reached and engaged more people than the trade shows at a similar price point. You could build a model for search engine marketing and other marketing strategies, and my guess is that you will find similar results. While the trade show approach is more straightforward and easier to execute on, the user group model can provide a much greater ROI.

The Sustainability Reason

In the example above, we see that an investment in community can be more cost effective than other marketing strategies, like a trade show. The other major benefit of the community approach is the self-sustainability. At 10gen, we initially invest a lot of time and money into our user group organizers. Over time, those organizers often become completely self-sufficient. The user group leaders build a network of speakers and they identify local companies to sponsor their events. The small investment continues to grow into a large, sustainable user group, often with many more than 300 members. We can then shift our attention and resources to developing user groups in new cities. In contrast, our trade show and SEM dollars, once spent, do not provide that kind of continual return.

The Pragmatic Reason

The final reason is a pragmatic one. You simply don’t have the capacity or bandwidth to have relationships with everyone in a large community. You can attempt to broadcast your message across the entire network, but there will always be pockets that you will miss or areas that are simply inaccessible due to distance or language barriers or some other reason.

When you have a new product announcement to make, you could try broadcasting your message to the thousands of potential users. Or, you could reach out to ten people in the community that you’ve identified as leaders and ask them to test our your new feature before it’s released, provide feedback, and write a blog post about it. Each of those people could reach several thousand people with their blog post or tweet, many of which would be outside of your immediate network.

In Conclusion

I hope that in this post, I’ve made a strong argument for investing in community and in community leaders as an effective and efficient means of expanding your reach. I think that this reasoning applies to everything from open source projects to consumer products and everything in between. I intend to cover both the “how” and the “why” in greater depth during my presentations at OSCON and Open Source Bridge. Looking forward to seeing you there!

Scaling community by nurturing your power users

When I joined 10gen, the MongoDB community was relatively small. We had a passionate following of users and contributors comprised of early adopters, startuppers, and open source enthusiasts. My first, tactical task at 10gen was to send thank you gifts to all of the contributors (coffee mugs, of course!). It was a fun and informative introduction to some of the early contributors. I enjoyed building relationships with users and seeing their excitement about this new database technology.

As we built out the product and the community, adoption accelerated. It became harder and harder for me to build and maintain personal relationships with everyone in the community. And up until about a year ago, the community and marketing team was tiny (three people, myself included, who also handled finance, sales operations, random admin, and HR). It became apparent that the MongoDB community needed some mechanism to scale effectively.

We needed to develop advocates and leaders who could be the go-to person in certain subsets of the community, whether it was geography or programming language or spoken language. Some leaders emerged organically: Nathen Harvey as the organizer of the DC MongoDB User Group, Rick Copeland in the Python community, Takahiro Inoue with Japanese speakers, and several others. But we needed a way to encourage and support other new leaders.

From this need we developed the MongoDB User Group program and the MongoDB Masters.

We provide financial and logistical support to MongoDB User Groups (MUGs) around the world. My colleague, Francesca, spends time with each MUG organizer helping them find space to host events, connect with speakers, and promote their meetups through the MongoDB community. We’ve developed and documented best practices for MUGs and have a mailing list for the organizers. Francesca also worked closely with the team at Meetup.com to establish a global account on to manage the groups.

The MongoDB Masters is a program to recognize leaders in the MongoDB community, and facilitate communication between those leaders and 10gen. It’s a meta community: we’re organizing the organizers, and building a community of leaders. It started out simple, with a mailing list for discussion of new features and releases, community events, and more. We brought the group together for the first Masters Summit at MongoSV at the end of last year. We’re planning to do more regional and online events in the future.

These programs have not been without their challenges. For example, I was taken by surprise when the Masters program inadvertently became a recruiting pipeline (we ended up hiring several people who attended the Masters Summit). This means that we have to work harder to continue to recruit nominations for new members. And the success of the MUGs has been inconsistent across groups and takes constant effort to sustain.

I'm Speaking at OSCON 2012 (size 300 X 250)

At OSCON, SCALE 10x, and several other forums, I have spoken about how 10gen built the community around MongoDB. During those talks, I touched on how we work with community leaders. I’m looking forward to going into greater depth on this topic at Open Source Bridge on June 26-29, and OSCON on July 18. I’ll talk about organizing the organizers and the challenges and rewards that go along with that. I’m looking forward to getting lots of feedback on the sessions and to learn what others have done successfully. I hope to see you there!

For those of you interested in attending OSCON this year, you can register using the discount code GILL10GEN for a 20% discount on any package.

I will be sure to post my slides after the conferences.

Follow

Get every new post delivered to your Inbox.