**Author:** [[3. Resources/Authors/Jono Bacon|Jono Bacon]] # Book Overview ![[People Powered Visual.excalidraw]] ## About the Author Jono Bacon has spent his career building and advising on communities, starting with the open-source world. He joined Canonical in 2006 as Ubuntu community manager, where he turned a small set of contributors into a global movement. He later served as senior director of community at XPRIZE and has consulted for companies including HackerOne, Deutsche Bank, and various VC-backed startups. He's the author of *The Art of Community* (O'Reilly) and runs a consulting practice focused on community strategy. His background is heavily weighted toward open-source and technology communities, which colors both the strengths and the blind spots of this book. ## Central Thesis Community isn't a marketing channel. It's not a support cost center, and it's not a side project you hand to an enthusiastic community manager while everyone else gets back to "real work." Bacon argues that community is a strategic capability -- a disciplined practice of creating environments where people can do meaningful work together, build social capital, and generate value that benefits both the organization and its members. The gap between companies that talk about community and those that actually build one is an execution gap, driven by unclear strategy, distraction, and a failure to understand human psychology. The book builds this argument through what Bacon calls the "Bacon Method" -- a ten-step process for building community strategy. It starts with choosing a Community Engagement Model (Consumer, Champion, or Collaborator), defining value for both the organization and its members, and producing "Big Rocks" -- high-level annual objectives with measurable KPIs and clear owners. From there, it moves into audience personas, on-ramp design, the Community Participation Framework (Casual, Regular, Core), culture building, incentive design, events strategy, and organizational integration. The method is meant to be followed sequentially and operated on a recurring cadence. ## Why This Book Matters Most community-building advice falls into one of two traps: it's either tactical noise (which social media platform to use, how to write better blog posts) or motivational hand-waving (community is about belonging!). Bacon's contribution is to sit between these two poles and offer a strategic framework -- a structured way to think about community that connects high-level goals to specific execution plans. For DevRel practitioners, startup founders, and anyone who's been told to "build a community" without being given a methodology, this book fills a real gap. It's practical where others are abstract, and it's honest about the difficulty of the work where others oversell the opportunity. --- # Chapter Summaries ## Foreword by Peter Diamandis Peter Diamandis, founder of XPRIZE and Singularity University, frames the book around the potential of globally connected collaboration. He draws on the XPRIZE model -- incentive prizes that produced the first private spacecraft -- to argue that communities can produce exponential results when people are given clear goals and the tools to work together. The foreword positions community as a catalyst for innovation at scale, setting up Bacon's framework as a practical methodology for harnessing this potential. ## Chapter 1: What Is a Community and Why Do You Need to Build One? The book opens with the story of Abayomi, a kid in rural Africa who walked two hours each week to spend less than an hour at an Internet cafe contributing to the Ubuntu community. He translated software, wrote documentation, and answered user questions -- all unpaid, all driven by the sense that his work mattered as part of something bigger. Bacon uses this story to introduce the Community Belonging Path: Access leads to Contribution, which builds Self-respect, then Dignity, Meaning, Impact, and ultimately Belonging. Social capital -- the unspoken currency of respect that accrues from repeated, quality contributions -- is the mechanism that drives this progression. The chapter identifies five categories of value communities generate: customer engagement, marketing and awareness, education and support, product and technology development, and business capabilities (recruiting, insight, lead generation). Bacon is upfront about the risks: there's no silver bullet, no guaranteed success, community is a cultural challenge rather than a technology one, it requires discipline, and it'll take more time and money than you think. He outlines his ten-step method and sets expectations for the rest of the book. ## Chapter 2: Consumers, Champions, and Collaborators This chapter introduces the three Community Engagement Models, which are the book's most useful organizational tool. Consumer communities are clubhouses -- places where people discuss a shared interest. The Trek BBS, with 27,000 members generating 6.9 million posts, is the example. The bar for entry is low and engagement varies widely, but the model is simple and effective for fan communities. Champion communities go further. Members don't just discuss -- they actively produce content, documentation, tutorials, and support that helps others succeed. Alexander van Engelen ("Yek") of the Fractal Audio Systems community wrote an entire free book about their products, pours hours into answering questions, and isn't on the payroll. Bacon introduces the Product Success Model (Learning, Optimizing, Mastering, Influencing) to map how members progress through Champion communities. Collaborator communities are the most complex. Members work together on shared projects -- building software, creating art, producing technology. Kubernetes, with 2,000+ contributors from 50+ competing companies, is the prime example. Bacon distinguishes between Inner Collaborators (who contribute to the core product, like open-source contributors) and Outer Collaborators (who build on top of a platform, like app developers). The chapter closes with six foundational principles: start simple, have clear leadership, set cultural expectations, focus on relationships and trust, seek and react to insight, and be surprising. ## Chapter 3: Build It and They (May) Come The chapter opens with Don, who organized a community event with coffee, snacks, content, and a booked room. Nobody showed up. The problem wasn't logistics -- it was that Don never articulated the value attendees would receive. This becomes the chapter's central lesson: value must be defined before tactics. Bacon introduces the Community Value Statement, a two-sided document capturing value for the organization and value for members. He's blunt about priority: put member value first, because organizational value follows naturally. Member value includes meeting people, content, education, skills development, mentoring, and career experience. Organizational value includes customer growth, better support, brand recognition, technology contributions, and recruiting. The chapter warns against treating the community as a sales pipeline -- communities serve the community, and your organization is one cog in that machine. The second half introduces Big Rocks -- five to seven high-level annual objectives, each with key initiatives, measurable KPIs, and a named owner. Bacon provides three concrete examples from anonymized clients, each with specific numbers (1,000 forum signups, 75% question response rate, 300 developers joined). The format is deliberately concise: four to six pages maximum for all Big Rocks combined. ## Chapter 4: Humans Are Weird This is the book's behavioral economics chapter. Bacon draws on Dan Kahneman's System 1/System 2 thinking (fast, intuitive decisions vs. slow, deliberate reasoning) and David Rock's SCARF model (Status, Certainty, Autonomy, Relatedness, Fairness) to explain why people behave irrationally in communities and how to design for those patterns. The practical output is audience personas. Bacon walks through building detailed profiles of target community members -- their skills, motivations, pain points, and what success looks like for them. These aren't marketing personas; they're designed to shape how you build on-ramps, create content, and design incentives. The chapter also covers group dynamics: how social proof drives behavior, why people mimic successful community members (diffusion chains), and how to account for the fact that most people won't contribute -- they'll watch from the sidelines, and that's fine. ## Chapter 5: Create an Incredible Adventure The meatiest tactical chapter. Bacon introduces the Community On-Ramp Model, a six-step process for converting newcomers into active participants: Discover (how they find you), Consume (first taste of value), Sign Up (join the community), Onboard (learn how things work), First Value (their first meaningful contribution), and Regular Value (sustained engagement). Each step needs to be fast, simple, and tested with real users. The Community Participation Framework divides members into three tiers: Casual (drop in occasionally, low commitment), Regular (show up consistently, developing skills), and Core (deeply invested, producing significant value, mentoring others). Bacon maps specific activities, incentives, and metrics to each tier. The chapter includes practical guidance on building quarterly delivery plans that break Big Rocks into specific tasks with owners and deadlines. ## Chapter 6: What Does Success Look Like? The metrics chapter. Bacon argues against vanity metrics (total registrations, page views) and pushes for engagement metrics that measure actual participation. He introduces maturity models -- structured assessments of how developed your community is across different dimensions (content quality, member engagement, leadership development, organizational integration). The chapter covers how to design a measurement framework that connects daily activity metrics to quarterly KPIs to annual Big Rock objectives. It includes guidance on tools, dashboards, and reporting cadence. Bacon is honest that measurement in communities is hard, partly because the most valuable things (trust, belonging, relationship quality) are the hardest to quantify. ## Chapter 7: Glue People Together to Create Incredible Things Culture is the focus. Bacon introduces the Ten Culture Cores -- ten areas where culture needs deliberate attention: openness, transparency, meritocracy, diversity and inclusion, efficiency, collaboration, sharing, trust, respect, and fun. Each gets specific guidance on how to build it into community norms. The chapter covers growth strategy -- how to systematically expand from early adopters to a broader membership while maintaining quality and culture. Bacon uses the Cadence-Based Community Cycle, where the community operates in recurring time-boxed periods (typically quarterly), each with planning, execution, review, and adjustment phases. He addresses the challenge of scaling culture: it's easy when you have 20 members who all know each other, and much harder at 2,000 when norms are transmitted through example rather than personal relationships. ## Chapter 8: Mobilize Your Community Army The incentives chapter, and one of the stronger sections. Bacon distinguishes between stated incentives (badges, rewards, recognition programs -- things members know about) and submarine incentives (psychological drivers that operate below conscious awareness). The submarine incentives are more interesting: the sense of progress, of being part of an inner circle, of having your work referenced by others. The chapter introduces the Incentives Map, a structured approach to designing incentives that move members through the Casual-Regular-Core progression. Bacon warns against over-relying on gamification -- badges and leaderboards create short-term spikes but don't build lasting engagement. The real incentive is meaning: people stay because the work matters to them and because they've built relationships they value. ## Chapter 9: Cyberspace and Meatspace: Better Together Events strategy. Bacon argues that online and in-person community activity are complementary, not competitive. He introduces the Event Evolution Path, which starts with small local meetups and scales to regional events and eventually large conferences. The chapter covers event planning, formats, content curation, and the critical importance of creating space for informal connection alongside structured programming. The practical advice includes how to support community-organized events without trying to control them, how to make virtual events engaging rather than Zoom-fatigue-inducing, and how to use events as on-ramps for converting passive members into active contributors. Bacon draws on his experience running Ubuntu community events worldwide and XPRIZE gatherings. ## Chapter 10: Integrate, Evolve, and Build The organizational integration chapter. Bacon addresses the hard problem: community strategy only works if the broader organization supports it. This means getting buy-in from executives, product teams, marketing, engineering, and support. It means integrating community feedback into product roadmaps. It means hiring community managers who have both strategic and interpersonal skills. The chapter covers hiring for community roles, building cross-functional collaboration, and the political maneuvering required to get resistant departments on board. Bacon is direct: without organizational integration, community strategy becomes an isolated effort that produces limited results and eventually gets defunded. The community team can't operate as an island. ## Chapter 11: Onward and Upward A short closing chapter that synthesizes the book's key arguments and encourages iteration. Bacon returns to the Abayomi story and frames it as the aspiration: build a community where someone will walk two hours for less than an hour of participation because the work is that meaningful. The chapter emphasizes that community building is ongoing -- it doesn't have an endpoint. You build, measure, learn, and adjust on a continuous cadence. --- # Key Themes and Highlights ## Value Must Be Bilateral This is the book's foundational principle. Community strategy starts with defining value for both the organization and its members, and member value comes first. Bacon returns to this idea repeatedly: if you treat community as a marketing channel or a cost-reduction strategy without genuinely serving your members, they'll leave. The Community Value Statement exercise -- writing out what members get and what the organization gets on opposite sides of a page -- is simple and surprisingly clarifying. ## The Three Engagement Models Provide Real Clarity The Consumer/Champion/Collaborator framework is the book's most useful contribution. It gives organizations a way to name what kind of community they're building and set expectations accordingly. A Consumer community needs discussion infrastructure and content. A Champion community needs progression pathways and recognition systems. A Collaborator community needs peer review processes, governance, and a level playing field. Mixing these up is where a lot of community efforts fail. ## Psychology Over Technology Bacon insists that community is a cultural challenge, not a technology one. The SCARF model, the Community Belonging Path, the emphasis on meaning and social capital -- these are the frameworks that matter more than which forum software you pick. The book's recurring argument is that if you understand what makes people tick, the tactical decisions become easier. Technology is the medium; human psychology is the operating system. ## Start Simple, Then Iterate Almost every chapter includes some version of "don't do this all at once." Pick one engagement model. Start with minimal infrastructure. Build growth before adding complexity. This is good advice that many community efforts ignore. Bacon has clearly seen companies try to launch with six social media accounts, a wiki, a forum, a Slack, and an event series simultaneously, and he's direct about why that fails: you spread attention too thin and can't build depth in any single area. ## Organizational Integration Is the Bottleneck The most underappreciated theme. Bacon argues that most community failures aren't about bad strategy or uninterested audiences -- they're about organizational resistance. Departments that don't want to share resources, executives who want to turn the community into a sales funnel, product teams that ignore community feedback. Without integration into the broader organization, community strategy is just a community manager talking to themselves. --- # Analytical Reading ## Main Arguments 1. Community is a strategic capability, not a marketing channel or support cost center. 2. Value must be defined bilaterally -- for both the organization and its members -- with member value taking priority. 3. Three Community Engagement Models (Consumer, Champion, Collaborator) provide frameworks for different types of community, each with different requirements and expectations. 4. Human psychology -- meaning, belonging, social capital, status -- drives community participation more than technology or incentives. 5. Community strategy requires a structured methodology: mission statements, value statements, Big Rocks with measurable KPIs, audience personas, on-ramp design, and incentive mapping. 6. Culture is built through deliberate attention to norms and values, not through declarations or documents alone. 7. Communities must operate on a cadence with regular planning, execution, review, and adjustment cycles. 8. Organizational integration -- getting buy-in from executives, product teams, and other departments -- is the difference between community strategy that works and community strategy that gets defunded. 9. Start simple, iterate based on data, and resist the temptation to overengineer the initial setup. ## Methodology The book is practitioner literature grounded in Bacon's consulting experience. He builds the argument through case studies -- some named (Ubuntu, Kubernetes, XPRIZE, Salesforce, HackerOne, Docker, Red Hat, HITRECORD, Fractal Audio Systems), some anonymized (clients in financial services, startups). He supplements these with light references to behavioral economics (Kahneman, Ariely) and social psychology (Rock's SCARF model, research on likemindedness from Bahns and Crandall). There's no systematic data collection or statistical analysis. The persuasive method is pattern recognition across his consulting engagements and personal experience: here's what worked, here's what failed, here's the framework I built from those observations. ## Strengths The book is structured and practical. Where most community books offer philosophical principles or tactical tips, Bacon provides a complete methodology -- a sequence of steps with specific deliverables at each stage. The three Community Engagement Models (Consumer, Champion, Collaborator) are genuinely useful as a first-principles framework for thinking about what kind of community you're building. The Big Rocks format -- objectives with KPIs and named owners -- is immediately actionable. The Abayomi story and the Alexander van Engelen ("Yek") example ground the theory in concrete human experience. Bacon is honest about risks, timelines, and the likelihood of failure, which is refreshing in a genre prone to overselling. ## Limitations The book's case studies skew heavily toward open-source technology communities, which makes sense given Bacon's background but limits applicability to other contexts. The methodology is presented as broadly applicable, but the examples rarely extend to non-tech industries in depth. The writing has a breezy, conversational tone that sometimes works but occasionally undercuts the seriousness of the strategic arguments -- pop culture references (Iron Maiden's manager, AC/DC lyrics, Gangnam Style) can feel like filler between substantive points. The "Bacon Method" is positioned as a complete system, but the book doesn't seriously engage with competing approaches to community building or the academic literature on online communities. The ten-step process risks feeling formulaic -- as if following the steps guarantees results, despite Bacon's own warnings to the contrary. The behavioral economics material (Kahneman, SCARF) is treated lightly rather than deeply integrated. Some frameworks feel like they're accumulating (Community Belonging Path, Product Success Model, Community Participation Framework, Community On-Ramp Model, Ten Culture Cores, Event Evolution Path) without a clear argument for why this particular set is the right one. The book also doesn't adequately address community failures at scale -- toxic behavior, platform migration, community collapse -- beyond acknowledging they exist. Given that these are among the hardest problems in community management, their thin treatment is a notable gap. --- # Personal Reflection ## Key Takeaways The most useful idea in this book is the three Community Engagement Models. Before reading this, I'd seen a lot of community efforts fail because nobody agreed on what "community" meant -- some people wanted a support forum, others wanted an advocacy program, others wanted open-source contributors. Bacon's Consumer/Champion/Collaborator framework gives you shared language for that conversation. It doesn't solve the disagreement, but it makes the disagreement productive. The bilateral value argument is the book's moral backbone. Bacon is direct that treating a community as a resource to be extracted from is a recipe for failure. Member value first, organizational value second. This is obvious when stated but routinely ignored in practice, especially by sales and marketing teams who see a community as a captive audience. ## Questions Raised - The methodology is designed for organizations with dedicated community staff. How does it scale down to a two-person startup or a solo developer? - The emphasis on measuring community health through KPIs and maturity models assumes organizational resources for tracking and analysis. What happens when you don't have those resources? - The Collaborator model depends on a level playing field and meritocratic norms. How do you handle the power asymmetry between a corporation and its volunteer contributors when their interests diverge? - The book is pre-pandemic in its events thinking. How has the shift to remote-first changed the balance between online and in-person community activity? - Social capital is presented as a positive force, but it also creates insider dynamics. How do you prevent social capital from becoming a barrier to new members? ## Connections to Other Works - [[The Art of Community]] by Jono Bacon -- Bacon's earlier book covers similar ground with more tactical depth on open-source communities specifically. *People Powered* is the more strategic and business-focused successor. - [[Working in Public]] by Nadia Eghbal -- Eghbal's analysis of open-source maintenance challenges pushes back on the idea that community contributions always create value. She exposes the hidden costs of managing community input that Bacon glosses over. - [[Execution]] by Larry Bossidy and Ram Charan -- Bossidy's emphasis on linking strategy to operations through disciplined processes parallels Bacon's insistence on connecting community strategy to organizational execution through Big Rocks and cadence-based delivery. - [[The Lean Startup]] by Eric Ries -- Ries' build-measure-learn loop maps to Bacon's cadence-based community cycle. Both argue for iterative execution with data-driven adjustment. - [[Tribes]] by Seth Godin -- Godin's argument that leadership is about connecting people who share an interest overlaps with Bacon's Consumer model, though Godin is more about inspiration and less about methodology. - [[Good to Great]] by Jim Collins -- Collins' emphasis on getting the right people doing the right things connects to Bacon's argument that community success depends on organizational integration and hiring people with both strategic and interpersonal skills. --- # Reading Notes - The Abayomi story is effective precisely because it's not about technology or strategy -- it's about a kid who walked two hours to participate for less than one hour because the work felt meaningful. That's the test for any community. - The three Community Engagement Models (Consumer, Champion, Collaborator) are the book's most useful contribution. They're a clean framework for the conversation most organizations struggle to have: what kind of community are we actually building? - Bacon's distinction between Inner and Outer Collaborator communities is sharp and underappreciated. Inner collaborators (contributing to the core product) need to be treated as team members. Outer collaborators (building on top of the platform) need a great developer experience. These are fundamentally different relationships. - The Big Rocks format -- objectives, key initiatives, KPIs, owner -- is immediately useful. It's essentially a simplified OKR framework tailored to community strategy, and it forces the question: what are we actually trying to achieve, and how will we know if we did? - The Community Value Statement exercise (member value on one side, organizational value on the other) is deceptively simple. Most community efforts skip this step and pay for it later when there's no clear answer to "why does this community exist?" - The "Don't do this" refrain appears in nearly every chapter -- don't treat your community as a sales pipeline, don't over-engineer the initial setup, don't skip value definition, don't frame your community as free labor. Bacon has clearly seen every version of these mistakes. - The pop culture references (Iron Maiden's manager, AC/DC, Gangnam Style, A League of Their Own, Star Trek) give the book an accessible tone but occasionally feel like padding between substantive points. - Bacon's treatment of community culture -- the Ten Culture Cores, the insistence that culture is evolved by participants rather than handed down -- is solid but would benefit from more engagement with the hard cases: what do you do when cultural norms conflict, or when your most valuable contributor is also your most toxic one? - The incentives chapter's distinction between stated and submarine incentives is the section's best insight. Badges and leaderboards are stated incentives that produce short-term engagement. The sense of meaning, progress, and belonging are submarine incentives that produce lasting commitment. - The book's biggest gap is its thin treatment of community failure modes. Toxic behavior, burnout of key contributors, platform migration, corporate-community conflicts -- these get acknowledged but not examined in depth. For a book about building communities, the absence of serious attention to how communities die is notable.