We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Building External Evangelists

Formale Metadaten

Titel
Building External Evangelists
Untertitel
What should be the primary goal of every community team
Serientitel
Anzahl der Teile
542
Autor
Mitwirkende
Lizenz
CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
Congrats, you have a community team! Maybe if you are lucky, you have some DevRel folks too! In many companies, the community or DevRel teams are small, impossibly small for the work that needs to be done. If you are like most companies I have talked to, your job in one of these roles is to gain lots and lots of adoption, “Grow the user base,” your boss will tell you. The issue is how does a team of 1 or a handful of people build and support tens of thousands or even potentially millions of users… the answer is you don’t. Rather the goal of most teams should be to support and grow external advocates and evangelists who can do the work for you. Hiring 2 people to tell the world how awesome your software is can only reach so far… but if those 2 people get 1000 people to tell their story that has a massive reach. So how do you build such a system? How do you measure it? I will walk through what I have learned when talking to hundreds of community teams over the last 5 years and share with you what I have seen works and what does not.