DevRel Scribbles
  • What are Scribbles?
  • Index
  • Developer Advocacy
  • Developer Advocates
  • Life as a developer advocate
  • Modernising Red Hat’s enterprise developer program
  • Engaging 9-year-old software developers
  • Making 22-year-olds love 26-year-old software
  • Dogfooding developer products: gathering insights from internal hackathons
  • How far does your ethical responsibility stretch for the tech your devs create?
  • Outside the lecture theatre
  • How do you design programs for diversity?
  • Build the Platform Your Developers Actually Want
  • Measuring dev rel programs far beyond marketing activities
  • Developer Evangelism
    • Developer Evangelists
    • How to rock a technical keynote
    • The Art of Slide Design
    • The Art of Talk Design
    • The Art of Story Design
    • Dev events beyond 2021
  • Developer Experience
    • The Power of Content
    • Building a Developer Community in an Enterprise World
    • How to lose a dev in three ways
    • Developer relations, why is it needed?
    • The hierarchy of developer needs
    • GitHub is your documentation landing page
    • Docs as engineering
    • Commit messages vs. release notes
    • A11y pal(ly)- crafting universally good docs
    • Inspiring and empowering users to become great writers, and why that’s important
    • Solving internal technical documentation at Spotify
  • Community Management
    • Building community flywheels
    • DevRel = Community Management?
    • Creating high-quality communities
    • How to grow a healthy Open-Source community?
    • Managing communities at scale
    • Using community to drive growth
    • Useful community success metrics
    • Communities aren't funnels
    • How to mobilise your community during a pandemic
  • Managing a DevRel Team
    • Developer Relations + Product
    • Distributed developer relations
    • Understanding company goals
    • DevRel Qualified Leads (DQL)
    • Path to success for DevRel
    • How to move up in your organization
    • Four pillars of DevRel
    • Building your DevRel dream team
    • Managing the burnout burn-down
    • I messed up and I’m going to get fired
    • How to report on community relationships without being creepy about it
    • How to scale a developer relations team
  • Misc
    • Is developer relations right for you?
    • Tooling your way to a great DevRel Team
    • Planning your DevRel career
    • Success metrics as narratives
    • Get executive buy-in or else
    • Introduction to the AAARRRP devrel strategy framework
    • Strategy for developer outreach
    • Connecting dev rel and product
    • Performance DevRel
    • Ultimate cheat codes for healthier travel
Powered by GitBook
On this page
  • Summary:
  • Scribbles:
  • Potential of having a great community
  • If adoption is a future success — how can you tap into the future of your org. through Go To Community.

Was this helpful?

Export as PDF
  1. Community Management

Using community to drive growth

How you drive business growth with Community and why you need a Go-to-Community strategy, not just Go-to-Market.

PreviousManaging communities at scaleNextUseful community success metrics

Last updated 3 years ago

Was this helpful?

Summary:

  • Organizations realizing the importance of go-to-community rather than go-to-market for driving business growth.

  • Understanding the existing metrics from go-to-market.

  • Explaining how metrics for go-to-community has more impact on the community than go-to-market.

  • Sharing your story is a must when trying to grow.

  • Treat communities are ongoing research and development function.

  • Leverage community members and advocates to do the marketing for you!

  • Marketing does help you grow, but only up to a certain point, every organization depends on the community to drive growth from there.

Scribbles:

  • Making opportunities where no one loses knowledge — everyone gains knowledge.

  • Language itself can create a sense of hostility in some ways — and something that we should really take seriously.

  • Expanding the term 'developer' opens up more opportunities for all.

  • In order to get Go-To-Community integrated into the culture, you need to explain the metrics of community in terms of the known and functioning Go-To-Market strategy.

  • Tracking sentiment among developers — how did developers feel about the product and how did this influence the company strategy as a whole?

  • Community + DevRel =. how you listen to your people!

  • Market side vs Community side: Old way of thinking -- Better Culture: Synthesis of Market and Community.

  • Sharing stories is one of the most important things we can do as community builders.

  • The community team is in ways an R+D function

"I dont think there is developer market, there is a developer community, and we need a community team to reach that"

  • DevRel, Community, Marketing = all diff teams...or is DevRel & community manager = same team.

  • Let the community do the marketing for you.

Potential of having a great community

  • Product growth

  • R&D

  • Marketing!

If adoption is a future success — how can you tap into the future of your org. through Go To Community.

  • Marketing will help you grow, but there will be a ceiling to that growth. If you want to grow beyond that, you will need community. The scale possible with the community can never be possible with marketing.

  • Marketing is not community building

"Stories we share are tools for driving change" - Sam Ramji

Video