Announcing my new book: ‘People Powered: How communities can supercharge your business, brand, and teams’
I am absolutely thrilled to announce my brand new book, ‘People Powered: How communities can supercharge your business, brand, and teams’ published by HarperCollins Leadership.
The book is designed for leaders, founders, marketing and customer success staff, community managers/evangelists, and others who want to build a more productive, more meaningful relationship with your users, customers, and broader audience.
‘People Powered’ covers three key areas:
- The value and potential of building a community inside and outside a business, how it can create a closer relationship with your users and customers, and deliver tangible value such as improved support, technology development, advocacy, and more.
- I present the strategic method that I have used with hundreds of clients and companies I consult with and advise. This guides you how to create a comprehensive, productive, and realistic community strategy that scales up, build cross-departmental skin in the game, create incentives, run events, measure community success, and deliver results.
- Finally, I walk you through how to to integrate this strategy into a business, covering hiring staff, building internal skills and capabilities, measuring this work with a series of concrete maturity models, and much more.
The book covers a comprehensive range of topics within these areas:
The book features a forward from New York Times bestseller Peter Diamandis, founder of XPRIZE and Singularity University.
It also features contributions from Joseph Gordon-Levitt (Emmy-award winning actor), Jim Whitehurst (CEO, Red Hat), Mike Shinoda (Co-Founder, Linkin Park), Ali Velshi (Anchor, MSNBC), Jim Zemlin (Executive Director, The Linux Foundation), Noah Everett (Founder, TwitPic), Alexander van Engelen (Contributor, Fractal Audio Systems), and others.
The book has also received a comprehensive range of endorsements, including Nat Friedman (CEO, GitHub), Jim Whitehurst (CEO, Red Hat), Whitney Bouck (COO, HelloSign), Jeff Atwood (Founder, StackOverflow/Discourse), Juan Olaizola (COO, Santander Espana), Jamie Hyneman (Co-Creator and Presenter, Mythbusters), and many others:
Here are a few sample endorsements:
“If you want to tap into the power that communities can bring to businesses and teams, there is no greater expert than Jono Bacon.”Nat Friedman, CEO of GitHub
“If you want to unlock the power of collaboration in communities, companies, and teams, Jono should be your tour guide and ‘People Powered’ should be your map.”Jamie Smith, Former Advisor to President Barack Obama
“If you don’t like herding cats but need to build a community, you need to read ‘People Powered’.”Jamie Hyneman, Co-Creator/Host of Mythbusters
“In my profession, building networks is all about nurturing relationships for the long term. Jono Bacon has authored the recipe how to do this, and you should follow it.”Gia Scinto, Head of Talent at YCombinator
“When people who are not under your command or payment eagerly work together towards a greater purpose, you can move mountains. Jono Bacon is one of the most accomplished experts on this, and in this book he tells you how to it’s done.”Mårten Mickos, CEO of HackerOne
“Community is fundamental to DigitalOcean’s success, and helped us build a much deeper connection with our audience and customers. ‘People Powered’ presents the simple, pragmatic recipe for doing this well.”Ben Uretsky, Co-Founder of DigitalOcean
“Technology tears down the barriers of collaboration and connects our communities – globally and locally. We need to give all organizations and developers the tools to build and foster this effort. Jono Bacon’s book provides timely insight into what makes us tick as humans, and how to build richer, stronger technology communities together.”Kevin Scott, CTO of Microsoft
People Powered Preorder Package
‘People Powered’ is released on 12th November 2019 but I would love you wonderful people to preorder the book.
Preordering will give you access to a wide range of perks. This includes early access to half the book, free audio book chapters, an exclusive six-part, 4-hour+ ‘People Powered Plus’ video course, access to a knowledge base with 100+ articles, 2 books, and countless videos, exclusive webinars and Q&As, and sweepstakes for free 1-on-1 consulting workshops.
All of these perks are available just for the price of buying the book, there are no additional costs.
To unlock this preorder package, you simply buy the book, fill in a form with your order number and these perks will be unlocked. Good times!
Just a quick note to you all. I just submitted a session to SXSW in Austin, and there is a community voting component to this. Can you guess what I would I would love you to do?
Yup, to go and vote for it. 🙂
I have never spoken at or been to SXSW, so this would help enormously! It only takes a few minutes, and I would really appreciate your help.
As many of you know, the broader goal of my work is to produce more collaborative, impactful, productive communities at work, at home, and beyond.
My session, Hack The Network Effect: Customers to Contributors, is focused on getting this potential out to the SXSW audience:
Business is changing. Gone are the days of customers passively consuming your product, with little to no interaction beyond occasional support tickets. Consumers want meaningful, connected relationships with the businesses and organizations they love.
The future of business is enabling your customers to not just play an active role in their success, but that of their peers and your brand. Done well, this can builds remarkable brand loyalty, retention, and innovation and reduce costs.
Salesforce, Star Citizen, Random House, HackerOne, Sephora, and others have done it. Now it is your turn.
Jono Bacon, author of ‘People Powered’ by HarperCollins Leadership, presents the combination of psychology, workflow, branding, and technology that delivers this, packed with pragmatic next steps.
The overall focus of the session is to provide an overview of how communities can be powerfully harnessed to build more engaging, more productive relationship between businesses and their customers. My goal is three key takeaways:
- Human beings crave roles in meaningful, impactful communities. Businesses can harness this need to enable customers to channel peer contributions.
- These communities can generate diverse contributions: support, technology, fundraising, advocacy, and more, and careful incentives builds retention.
- Marketing needs modernizing to harness this: social/content is not enough. Peer recognition, social capital, and right relationships are critical.
I would love if you could go and vote for the session (you don’t have to be an attendee of SXSW to vote). It should only take a few minutes:
What does bioscience innovation, sustainable pet food, and Shark Tank have in common? Ryan Bethencourt, that’s who.
Ryan is a pretty accomplished guy. He has studied business and biotech, molecular biopharmaceuticals, genetics, and brain tumor angiogenesis at Cambridge, Berkeley, Warwick, Stanford, and Yale. Oh, and he went on Shark Tank and raised $550k from Mark Cuban.
Ryan’s passion for biosciences took him to be an investment partner for Babel Ventures, a $26m fund focused on investing in emerging biotech companies (including Occamz Razor, Nebia, Vitagene, CUE, Forever labs, California Dreamin, Zbiotics and Finless Food) sin Seed and Series A. He is also an advisor to companies and organizations including UCSF Health Hub, Memphis Meats, Berkeley Ultrasound, The Thiel Foundation, Vitro Labs, and many others.
Most recently though, he formed Wild Earth, a company producing sustainably produced pet food. He took his company onto Shark Tank and raised one of the largest amounts for his season. He works weekly with Mark Cuban.
In this episode of Conversations With Bacon we get into how innovation has evolved in biosciences, the role of the credit crunch, the horror show that is the pet food production industry, how Ryan and his team have approached growing better food (and the R&D and more), and where the future of biosciences lies. Oh, and of course, we delve into his experience of going on Shark Tank, behind the scenes, and what it is like to work with Mark Cuban. This is a really fascinating look into what the future of food looks like.
Back in 2014, I worked at the XPRIZE Foundation, and we launched the Global Learning XPRIZE. This $15 million competition, funded by Elon Musk among others, challenged teams to build an Android tablet application that teaches kids how to read, write, and perform arithmetic, all without the aid of a teacher within 18 months. The competition showed the potential of how technology can help to bring education to 250million+ kids around the world.
Fast forward to 2019 and the prize was awarded to Team onebillion and Team KitKit School, with all entries showing incredible results in learning across literacy, maths, and beyond. What’s more, all the entries have been open sourced on GitHub.
Emily Musil Church is the director of the prize, and was involved at every step of the way from shaping the competition, to running the field trials in Tanzania, and more. She is one of the most incredible people I have ever worked with.
In this episode of Conversations With Bacon we get into the nature of the competition, the logistics of running field trials with thousands of Google Pixel tablets across hundreds of remote villages, how the teams competed and collaborated together, the broader impact of education beyond merely learning, the open sourcing of the entries, and much more. This is a really fascinating and inspiring conversation!
Kate Drane is a bit of an enigma. She helped launch hundreds of crowdfunding projects at Indiegogo (in fact, I worked with her on the Ubuntu Edge and Global Learning XPRIZE campaigns). She has helped connect hundreds of startups to expertise, capital, and customers at Techstars, and is a beer fan who co-founded a canning business called The Can Van.
There is one clear thread through her career: providing more efficient and better access for innovators, no matter what background they come from or what they want to create. Oh, and drinking great beer. She is fantastic and does great work.
In this episode of Conversations With Bacon we unpack her experiences of getting started in this work, her work facilitating broader access to information, funding, and people, what it was like to be at Indiegogo through the teenage years of crowdfunding, how she works to support startups, the experience of entrepreneurship from different backgrounds, and more.
Today I am excited to launch my brand new podcast, Conversations With Bacon!
The idea is simple: when I think back over my career, the times I have learned the most, and had the most fun learning, has been getting into detailed, interesting discussions with interesting people from all walks of life. This exchange of ideas and experience is often fascinating, and presents new ways for me to think about my own work and projects.
My aim with Conversations With Bacon is to bring on a wide range of people to explore the ideas and experiences that have shaped their work and lives. I don’t just want to discuss what they work on, I want to get into the driving forces behind their thinking and approach. The aim of all of this is to give you an interesting discussion for you to be a fly on the wall listening to, and hopefully glean some new ideas for yourself. There will be new shows about every three weeks.
For this first show, I am thrilled to bring on Todd Lewis, who created the All Things Open conference in Raleigh in 2012. He has gone on to grow the event from 600 attendees in their first year to over 4000 attendees last year. Todd is a bit of a renaissance man when it comes to events, and in this first episode of the podcast we explore what goes into great events, how to get the right balance of content and taking care of sponsors, building an open marketplace of (often contrasting ideas), and what Todd has learned over the years as he has refined his craft.
Listen to the show below, and I would love to hear your feedback for how I can improve it, and which guests you think would be interesting to bring on. Like anything, this is a learning experience, and it will take time to get the show format and content perfected: your help will help me get there faster!
Back in 2014 I worked at the XPRIZE Foundation. One of the major reasons I joined was to help launch the Global Learning XPRIZE. This was a $15 million competition, largely funded by Elon Musk, that challenged teams to build an Android app that teaches kids basic reading, writing, and arithmetic, without the aid of a teacher, within 18 months.
When we launched this prize we were astonished by the response. At the time I launched our Global Learning XPRIZE crowdfunding campaign (which raised just under $1 million with a $500k goal) and the new XPRIZE community, and the excitement was palatable. Over 180 teams submitted entries.
These teams were narrowed down to five finalists and extensive field testing trials happened in Tanzania. This in itself was a behemoth task to get tablets and electricity out to such remote areas. This video provides a good overview of this work:
Well, this week the competition came to a close. On Wednesday I flew to Los Angeles to join the awards ceremony at the Spruce Goose Hanger at Google. Peter Diamandis kicked the event off, Emily Church introduced the teams, Levar Burton (yep, the guy from Star Trek) did a short speech, and Elon Musk swung by to award the teams before jetting off (no pun intended) to do a rocket launch.
It was a fabulous evening and it was wonderful to meet all the teams and see the energy and passion from everyone there. Here are some pictures from the ceremony.
Also, here is the live stream of the event:
Just The Beginning
Now, while it was fantastic to see the awards being delivered, what was most interesting to me was the overall impact of these entries across reading, writing, and numeracy:
Clearly the teams have developed software that really does meet the goals of the challenge: to provide a marked improvement in education for kids who don’t have access to teachers. This is an incredibly encouraging start.
The good news is that all five finalist’s code has now been uploaded to GitHub. You can find the repos by clicking here. All the technology that is driving these educational gains is built for Android is now available under an Apache open source license and the general open source community is welcome to participate.
In addition to this, the XPRIZE team have set up a discussion forum. This is brand new, but I would encourage those of you who are interested in this project to go and check it out.
Now, as you can imagine, these are five pretty significant codebases, and each has unique attributes. For example, Team CCI has built an authoring platform where you can produce content without coding (similar to Flash). RoboTutor have built an AI-powered voice recognition platform so kids can read the words on the screen, it will listen, and then read back the correct word.
I really want to see this code as the beginning of a new era of educational software that can impact the 250 million+ kids that need access to high quality education delivered via tablets. I can’t think of a better opportunity to built a community around a more meaningful mission
For these projects to succeed though I believe we need to focus on the following key areas, all of which need volunteers (wink wink!):
#1. Get more people involved
With the code now available, I want to encourage you all to go and download these projects, play with them, and start participating.
File issues with bugs and feature ideas, submit pull requests, and reach out to the teams. Feel free to share your ideas and offers of help on the community forum.
#2. Modularize the best elements of the different codebase
I don’t think it is realistic to expect all five of these projects to converge under a single initiative, they are likely too different. I do though think we should try to modularize some of the key tech (such as the examples I gave above) into individual projects.
I am going to reach out to the teams to see what kind of appetite they have for this: from my discussions yesterday, it seems like there is interest in doing this. This will make it easier to collaborate and expand the contributor base.
If we can modularize these pieces and get more of the projects using the same common pieces, it will grow those foundational elements faster as more devs can contribute. As an example, TeamCCI has already offered to fund $100,000 worth of educational content development for the other teams if they use their core Pubbly platform (which is now open source in GitHub.)
#3. Increase localization
Each of these projects is available in English and Swahili, with some of the teams also being localized into Hindi.
There is an enormous opportunity to expand the translations base for these projects. When I was at Canonical, one my proudest memories was how localized Ubuntu was and continues to be: we should do the same for these projects.
These projects should be available in multiple languages, not just the strings, but the content too. With every new language there is the possibility of this software impacting kids in those regions too.
#4. Create documentation for the community and project
With five big new codebases, we could benefit from docs writers to build and maintain a wiki for the project. How to build the projects, join the community, submit pull requests, submit art/design assets…this all needs documenting. Do you want to make an impact on education around the world and do you like writing? Roll them sleeves up and get involved!
So, if you are interested in getting involved, head to the community forum, sign up, and weigh in. There is enormous opportunity here to have an impact: let’s make it happen.
When I am working with clients with community management, one of the first things I want to understand is how they, not me, define success. What metrics are they tracking?
One of the common metrics for success in communities is people who register, sign up, or otherwise provide some kind of identity to a community
Now, this is important, but we need to look at what it really means. For most public communities, I generally recommend they make their community platform open for reading and consuming without requiring an account. This provides an opportunity for people to “try before they buy”. It also means though, that these faceless strangers may get significant value out of the community (such as finding answers to their questions), without ever needing to sign up.
Now, as part of their community management dashboard (see my other pieces on ‘How To Track Community Growth In Forums‘ and ‘Measuring Community Health‘), I still want to track sign-ups, and here is an example of a client I am working with (they gave me permission to share this, anonymously):
What this graph tells me is that their community management is offering more and more personalized value to their members. Given that their forum is open to the public to read, people need a reason to sign up for an account. Most people don’t sign up for a community unless (a) they are required to, or (b) they want to feed in in some way, such as asking a question or voting in a poll. Sadly, they won’t sign up just because they like you.
As such, when we see a growth in sign ups, it tells me that more and more people are consuming value in the community and they are inspired to feed in and participate, which is a good sign. If this graph was flatlined, it wouldn’t merely just suck, it would tell me the opposite: we need to provide a clearer way for them to understand the value of participating and how they see their reflection in the community.
Now, many communities will track sign-ups as a key metric and often ignore the anonymous views of the community. But, let’s look at the same community’s data when it comes to people browsing the forum without being logged in:
Yeah, baby! This is looking almost like a hockey stick curve. What this tells me is that the value encompassed in their community forum is seeping out more broadly and pulling people in to browse the value there.
This is a critical metric. If we don’t see this graph growing, it means that either (a) the community is boring and doesn’t offer enough value, (b) people don’t know about it, or (c) both. :-/
As such, always focus on getting this anonymous traffic graph up. Here are a few recommendations:
#1. Optimize your SEO
Sure, I get it. A lot of people who waffle on about SEO seem to be talking bollocks, but it is essential. There are bags of tutorials, books, and videos about how to do SEO well. As part of your community management, focus on how you can optimize how your community web pages perform publicly and how they are indexed.
#2. Integrate into your other infrastructure
Far too many communities are not accessible from the other trappings of a project or product. Ensure people can know about your community and link to it easily from:
- Your website (ideally in the top-level nav.)
- Social media accounts.
- Blogs and other publishing mediums.
- GitHub/GitLab repositories, and
- Email messaging, newsletters, and other outreach.
- Event presentation slides, handouts, and other materials.
Don’t just do this once: keep your community in the consciousness of your users and customers week in, week out.
#3. Regularly feature community management work on social media
If you have rich, interesting content in your community, you need to post about it every week on your social media networks. Social media is a significant driver of traffic to websites, so ensure you are utilizing it as a tool to get people to your community.
Don’t just broadcast, invite participation in your community. Have calls for feedback, input, and other engagement: it all drives participation.
#4. Regularly think about how to pull people in
There always needs to be a reason for people to go to your community. What is it?
Sure, providing support is useful, but that will only bring people in when they have questions. As such, think of other ways to get them in your clubhouse.
Publish tutorials, guides, demos, and feature/release updates to your community. Promote these on social media and beyond. Give people a reason to check the community every day.
As such, many people (myself included) regularly check the community to discover these new features, learn how to use them, and more.
These are just a few suggestions scratching the surface of how you build this anonymous traffic. What recommendations do you have to grow it? I am always eager to learn new approaches and methods, so get them in the comments – thanks!
Open source community can be a tricky business, but today I want to share a quick example of the kind of open source community engagement I try to encourage more generally, and with clients. This one comes from a client of mine, Zeppelin, who builds tools for decentralized systems and smart contracts.
Well, a few days back this post appeared in their community:
@martriay works for the company and is my primary point of contact for leading their community development. Clearly the company is busy with other projects but wants Ethernaut to keep moving forward, and the community expressed an interest in helping.
When @martriay asked if people would be interested, a number of hands went up:
Given the community interest, he followed through on his promise and kicked off a new topic:
Here he tagged the individual people who had expressed interest (so it appears in their forum notifications), and provided some pragmatic next steps for ways in which the community can play a practical role.
Importantly, @martriay also made it clear that the community are welcome to come up with their own creative ideas for how to participate (instead of forcing them into a specific box of tasks). This is critical: communities thrive when they are a creative meeting of minds, but with a clear method for how people practically work together.
What followed was a discussion for different ideas for tasks and where people would like to participate:
Here @martriay continued to be responsive, playing a supporting role to help those interested community members get started (such as opening up and adding to the project’s board in GitHub.)
This is another subtle, but important point: here @martriay is working to encourage participation but to try to consolidate these contributions into the same “view”, and provide an opportunity for some community members (namely, @scammi and @paulinablaszk) to play a key role as contributors:
As things stand right now, a clear list of work assignments is forming, all based on this creative discussion and input:
Part of why I think this is a good example is that it demonstrates (a) what is possible when a company is open to contributions, (b) how the community can play a key role in adding additional value to a shared project, (c) the importance of facilitation, and (d) how this energy can be consolidated into a central way of working.
If we peel away the covers, there are 5 key principles operating here.
#1. Be Open to Contributions
When companies are building open source projects, there is typically a line drawn in the sand between where the community can contribute and influence a project and where they can’t. Some companies will be reluctant for contributions, even for projects that are unmaintained, often due to various fears (liability, trademark issues, losing control, etc.)
Ethernaut is a great candidate for community contribution: the company has other pressing priorities, and the community loves Ethernaut. Being open to contributions demonstrates (a) the maturity of the company, and (b) that the community is a valuable relationship to the company.
#2. Foster Creativity
Community members don’t want to be walled into a box. They don’t want to be given a limited set of tasks. They are not task-rabbits.
Community members want to use their creativity to explore ways to make a project better. They want to express ideas, and have an open dialog about which of those ideas have legs and which don’t.
The very best open source projects have an open, creative environment, but a clear method in which work gets done, reviewed, and integrated. As you try to build a simple, clear workflow, don’t gut this creative input.
#3. Openly Facilitate Contributor Success
Few open source communities with a primary single commercial sponsor operate entirely autonomously. You will always need someone from the company to help facilitate the overall success of your community contributors.
Doing this well requires open engagement in the community, helping to foster their creativity, and working to zone in on specific tasks that are assigned to specific individuals. If you don’t have this you will likely get a lot of, “Wouldn’t it be cool if…” ideas, but no pragmatic results.
#4. Simplify and Centralize Team Workflow
While you want to foster creativity, the way in which the team works should be as clear, simple, and as accessible as possible.
For many projects, they have an online repo (e.g. GitHub), an online issue tracker, and code contributions are made via pull requests. They will also have a central place where the project is discussed, such as a forum.
#5. Be Accessible and Engaging
Finally, the tone and way in which you engage with your contributors is enormously important. Your community members are not robots, and don’t want to be treated like robots.
They are human beings, so be human with them: be loose, engaging, and fun. Validate great contributions, provide friendly constructive criticism, make jokes, and smile both in-person and online. It sounds simple, but this is critical: build an environment people want to be a part of.
This is really important for two reasons:
- People like working in more social, fun, and engaging environments.
- Human beings mimic each other and especially their leaders. As such, if you are fun and engaging, they are likely to be so too.
So, that’s it. I just wanted to share this little example, primarily so it can illustrate what I mean when I talk about what good, collaborative, open source engagement looks like. If you have other examples, be sure to share them!
Bonus points for those of you who can guess where the main image for this post is from.
One of the interesting elements of working with a range of different companies is being able to better understand the dynamics that influence how well a community will succeed or fail. These dynamics are many and broad, and include having a solid strategy, the right balance of transparency, executive and frontline and support, simple and sensible tooling, and more. Sadly, the availability of gin plays no concrete role in this success. Bah humbug.
Within the context of companies building a community around a product, one of the most critical influences of this success, frankly, is having a product that (a) people actually want, and (b) that they can wrap their heads around it.
This may seem obvious, but it is more complex than it may seem. If you look at the rich tapestry of open source, you have some very popular projects that serve broad needs such as Kubernetes, Node.js, Git, Docker, Angular, and others. But then, you have projects that serve very niche needs such as OpenMRS, SymPy, Astropy, and eht-imaging. All of these projects are thriving open source communities.
Now, for some companies watching these projects growing in adoption and market recognition, it can generate a seemingly logical conclusion:
“Surely if we open source our struggling project on GitHub or GitLab we will attract an audience of users and developers, and therefore help our broader market success, right?”
Well, Danger, Will Robinson.
A Balanced View
While there is little doubt that open source can have a heck of an impact on projects, products, and companies, the way in which you accomplish this impact needs to pull together four key components:
- Product – firstly, you need to have a product that the market wants, that can add value for your target audience, and maps well to your chosen open source model.
- Product/Engineering Workflow – secondly, if you are going to run a public open source project, you need to ensure your product and engineering teams can operate with an open, asynchronous workflow and can interface with public contributors.
- Community Strategy – thirdly, you are going to need a clear, unambiguous strategy for how you structure your community, hire the right team members, target the right audiences, build growth, and more.
- Internal Capabilities – finally, you are going to need to develop the skills in your company to accomplish all of the above. This will require staff training, support, mentoring, and leadership.
Now, often when I am brought into a company, the client is typically very interested in focusing on points 2 – 4. After all, this is what a lot of people associate with the work I do.
My first questions though almost always focus on (1). Is the product you have suitable for open sourcing, and will open sourcing it bring you and your prospective community the value you and they want?
Open source is not a panacea. It is not a solution that will revive an uninteresting or poorly built product. I never recommend anyone goes down the open source road until they have assessed this important product suitability consideration first. Otherwise, they risk doing a lot of work for very limited benefit for anyone.
Essential Questions To Ask
Here’s the deal: open source requires a careful balance of open workflow, community/contributor management, and a clear delineation of where the lines are drawn between your open source and non-open source projects (and which teams work on what.)
To put it rather glibly, open source is not as simple as chucking some code into a public repository and blogging about it. It requires a careful balance of internal and public workflow, and needs a significant investment of time and energy to do well. As such, you want to be sure that this time and energy is not just worth it, but has a realistic chance of success for both you and your community.
When you are considering this, I recommend asking yourself 4 key questions:
#1. Is there a market need/fit for your product?
Open source has become increasingly interesting to companies who want to get developers using their product or platform. Developers are increasingly influential decision-makers in modern tech firms, and often prefer open source platforms.
Put the open source element to one side though and ask yourself the objective question, “Does your project serve a clear need and deliver enough value for your target audience?”
The #1 thing your audience are looking for is clear, valuable functionality. Does the software do something that pragmatically make your audience’s lives better? If it doesn’t deliver this, no amount of open source will save it.
So, try to understand what your core audience want and ensure your project can deliver it. If this is a new project, publish a roadmap for these key target features and focus on staffing the delivery of them. A compelling 1.0 is essential to interest both users and potential contributors.
#2. What is the on-boarding experience like for new users?
On a related note, how easy is it to get started using your project? Can a new user get up and running and experience tangible value within 10 minutes? No? Then you you need optimize your on-boarding experience.
I have seen some bloody horror stories here: projects that make users jump through endless hoops, require complicated configuration (with little to no documentation), have dependencies on obscure or unavailable services, and other dents in the experience.
This is the model I have developed over the years for thinking about building a clear onramp:
Your audience should be able to proceed simply and logically from one step to the next ultimately getting to the star, which is a piece of tangible value for them (e.g. completing a task, solving a problem, etc.).
Now, while every project will use a slightly different set of steps, an onramp generally breaks down into understanding value, setting up tools, learning skills, and using the tools and skills to produce something valuable. (1) and (6) are highlighted in the above graph because they should be on every onramp: you always need to communicate the value of your project (such as via websites, social media, etc) and validate the people who use it successfully (such as with rewards, engagement, and opportunities). The latter is especially important for building lasting relationships with your community.
Think about how to simplify the overall onramp (you should explore how muntzing can help here). Then, ensure that each transition from one step to the next step is logical and try to understand and resolve where people get stuck.
If you don’t do this, you will struggle to build a userbase for your project, which is a critical requirement before you can consider developing a contributor-base.
#3. What are your primary goals for open sourcing it?
The next question is why are you are open sourcing your project in the first place? From a company perspective this can vary and will often include one or more of the following:
- We want to increase market awareness and adoption.
- We want to increase engineering contributions to the project.
- We want people to build on top of the project (e.g. plugins or modules.)
- We want to increase the company’s brand recognition.
- . . .
This is where things can get complex: open source projects can often lead to many of the benefits listed above, but it is not just the nature of being open source that will drive these benefits, it is the focused strategy efforts you put in place that will.
For example, if your goal is “increasing engineering contributions”, putting code in a repo will not merely lead to this. Clear developer on-boarding, solid documentation, building meaningful community relationships with developers, developer focused content and outreach, and other efforts will help drive this growth.
The risk some companies face here is that they think of the value of open source primarily from their own perspective, but don’t focus enough on what value their users want to experience too. How can you build an open source community that gives your users greater information, flexibility, and communication with the project and your team? How can your users play a more meaningful role in the project? If you build an environment with your users’ needs in mind, you will build a a far more engaging and valuable community in general.
#4. What new skills and resources do you need to build in your company to do this work well?
It took me far too long to realize that a significant determining factor of community success is not just making the right strategic choices, but also baking those skills effectively into an organization.
For many companies, switching to an open source model is a significant change of workflow, policy, and how you incentivize your team. Aside from picking the right set of open source strategic steps (such as how you publish code, manage issues, build community engagement and growth etc.), you should also plan for how to bake these skills and expertise into your teams.
An an example, one key element of being an open source project is receiving and responding to pull requests with new features and fixes. This requires your team members to be able to review those PRs, test them, provide constructive feedback, and approve or reject the contribution based on merit. It requires calm and constructive feedback, often with people you don’t know and trust yet. It requires the overall code review process to happen end-to-end out in the open. Overall this needs a nuanced set of skills such as peer review, technical collaboration, open build management, and other pieces.
For companies less familiar with open source, this is all going to seem a bit weird and uncomfortable. Your team members are going to hesitant to engage, not only because it is new, but they also don’t want to put a foot wrong and get in trouble. This is entirely normal.
As such, think about how to break these skills down into simple pieces, provide the right level of training and support, and how to mentor and support people through this transition. Help them to build a habit around participation, and develop incentives, rewards, and other mechanisms to help them naturally orient to an open workflow and enjoy engaging in it.
Open source is an enormously powerful model, but focusing on these core product questions is an important part of the process. What other considerations should companies be making? Share them in the comments…