3 Lessons from DevRel Experts on Building Developer Communities Ashley Dotterweich
This week, we brought together a panel of developer community experts from Devada, Weaveworks, RingCentral and IBM to discuss their experiences creating and running developer communities. Moderator Jesse Davis, EVP of Product and Technology for Devada, led a great conversation about how devtools teams can engage with and foster the communities that grow around their products. Here are a few things that we learned about building developer communities during the session.
When You’re Marketing to Developers, Your Competitors Aren’t Your Biggest Competition
Developer communities can provide a lot of value to marketing and sales teams looking to stay connected with their audience — but that connection can’t be taken for granted. Mike Stowe, Sr. Manager of Developer Product Marketing at RingCentral, raised an essential point about leveraging communities in this way. “When you’re marketing to developers, your real competitor isn’t other tools; it’s the time they want to spend with their families, watching Netflix, or learning other technologies,” said Mike during the panel.
From an organization’s perspective, a community can be valuable for marketing and sales initiatives. Focus on providing value to the developers in your community first and foremost, to ensure that your users find participating worth their time — it will pay off in the long run.
To Understand Your Value, Measure and Track Everything You Can
One thing that all the panelists agreed was the importance of measuring your community-building efforts. “You’re going to fail, and you’re going to fail a lot. That’s why it’s important to measure things — something is going to hit, and that’s what you’re going to want to double down on.” said Dave Nugent, Developer Advocate for IBM Developer SF.
Tamao Nakahara, organizer of DevRelCon and Head of DX at Weaveworks, said that her team is encouraged to log everything in Salesforce. When a deal closes or a customer is upsold, the DevRel team can then show the impact they had. Mike echoed this sentiment, reiterating that careful tracking of the community activities helps tie your efforts to revenue, customer happiness and other topline goals: “At the end of the day, if you can share the value of the community, it gives your company a reason to continue to invest in that community.”
Take the Conversation to Community
After opening up the panel to questions from the audience, the conversation turned towards getting a new developer community up and running. The audience asked questions about everything from community-building tech stacks to how soon is too soon to get started. The panel agreed that it’s never too early to start building relationships with and between your customers.
Tamao advised against spending too much effort spinning up your own, standalone community platform in the early days: “Be aware of existing platforms and forums, and go for the easiest way to engage with people. If all your users are on StackOverflow, taking the conversation to them instead of trying to build your own standalone platform.” Engaging with users where they’re already having conversations about your product will reduce the friction and overhead needed to start having those meaningful conversations.
Learn More about Building Developer Communities
Want to watch the whole panel? Subscribe for updates from Heavybit and we’ll let you know when we’ve posted a recording of the session. In the meantime, check out our ongoing series from Josh Dzielak of DeveloperMode on Collaborating with Developer Relations for more insight into building a vibrant developer community.