You Are the Source of Your Community - CourtneyR.dev's 2nd Brain

You Are the Source of Your Community ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/media/uploaded_book_covers/profile_636263/0061121bdf4d4462a843a46d79b41b09.jpg) 🔗 **Source:** [You Are the Source of Your Community](https://davidspinks.substack.com/p/you-are-the-source-of-your-community#full) > [!note]+ Document Notes > tags: [community-building, founder-leadership, source-principle, community-strategy, open-source-governance] > author: David Spinks > source: David Spinks (Substack) > reference: https://davidspinks.substack.com/p/you-are-the-source-of-your-community > date created: 2026-08-22 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: You Are The Source of Your Community >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [You Are The Source of Your Community — David Spinks](https://davidspinks.substack.com/p/you-are-the-source-of-your-community) - [Work With Source — Tom Nixon](https://www.workwithsource.com/) — the book supplying the article's central frame - [Peter Koenig's source work](https://www.thesourcebook.co.uk/) — the practitioner tradition Nixon builds on - [The Business of Belonging — David Spinks](https://businessofbelonging.com/) — the author's own book, linked in the closing block - [Downshift](https://www.downshift.co/) — the transition program the opening anecdote describes - [Anderson Cooper interview with Rick Rubin (60 Minutes)](https://www.cbsnews.com/news/rick-rubin-60-minutes-2023-04-16/) — source of the "audience comes last" exchange - Emergent Community Design workshop (registration link in the article's announcement block) - "The Somatic Way" podcast, hosted by Hannah Keith (episode link in the announcement block) ## 📝 Summary - **What happened.** David Spinks argues that every community has a *source* — one person who takes the first risk to bring the vision into the world — and that community builders sabotage themselves by refusing to occupy that role. He grounds the claim in Tom Nixon's *Work With Source* (drawing on Peter Koenig's practitioner research), illustrates it with the Downshift program and its founder Steven Schlafman, and reinforces it with a Rick Rubin interview clip about ignoring what audiences say they want. - **Why it matters.** The piece is a corrective to a decade of community-management orthodoxy that treats the organizer as a neutral facilitator. For anyone running an open-source project, a meetup, or a program, it reframes "leadership" from administrative overhead to the creative act that makes the container exist at all. - **Key stakeholders.** Community founders and organizers; program designers; open-source maintainers and project leads; sponsors funding community work; participants who inherit the tone a source sets; and successor leaders inheriting a founded container. - **Risks and tradeoffs.** The source frame is one step from founder-worship. Applied without governance guardrails it justifies unaccountable authority, key-person risk, and the "benevolent dictator" pattern open source has spent years learning to bound. The article names the risk in one sentence ("it should always be about the collective") but supplies no mechanism. - **Bottom line.** Useful as a permission slip for organizers who are hiding; dangerous as a governance model. Take the psychological insight, refuse the implied license. ## 📖 Main Content - **The core argument in plain language.** A community is not assembled from surveyed preferences. It is emitted by a person. The founder's intention, presence, character, and actions establish what the article calls the "foundational vibrations" of the container, and everything contributors add lands on top of that base. The observable consequence: the same programming run by a different founder produces a different community. - **The source principle, defined.** In Peter Koenig's and Tom Nixon's usage, "source" is a role, not a title. It belongs to whoever took the first real risk to realize an idea, and it cannot be voted into existence or delegated by org chart. Nixon's framing is explicitly paradoxical: growth requires decentralization, but decentralization does not dissolve the source role — a source who abdicates can collapse the whole endeavor. - **The failure mode the article targets.** Spinks names a specific pathology: organizers who dilute their own vision preemptively. The listed symptoms are wanting to seem "communal," granting everyone an equal voice instead of trusting intuition, avoiding bossiness, avoiding taking up space, avoiding conflict, and people-pleasing. His diagnosis is that these are not egalitarianism but conflict avoidance wearing egalitarian clothes. - **The Rubin move.** The Anderson Cooper / Rick Rubin exchange supplies the article's epistemics: audiences know only what has already existed, so asking them what they want returns the past. Spinks transfers this from record production to community design — no one can specify the community they need in advance; they recognize it only after being moved by it. - **The succession claim.** "Source leads to source." Contributors who join bring their own source-ness, spawn subcommunities and side quests, and eventually found containers of their own. This is the article's answer to the founder-dependency objection, and it is asserted rather than evidenced. - **Terms defined.** *Container* — the bounded social space with its own norms, distinct from the world outside it. *Taking one's seat* — a therapeutic/systemic-constellations phrase meaning occupying the authority the role actually carries rather than performing smallness. *Vibration/tone* — the article's non-technical shorthand for the affective quality participants sense but can't itemize. - **Uncertainties and contested claims.** (1) Nixon's "extensive research conducted by Peter Koenig" is not cited, sized, or methodologically described anywhere in the article; Koenig's work is practitioner-derived from money-and-consciousness consulting, not peer-reviewed social science. (2) The universal "every human initiative starts with one single founder" is contradicted by well-documented co-founded projects — WordPress (Matt Mullenweg and Mike Little, 2003) is a direct counterexample from the reader's own field. (3) The claim that a form of community exists that "only you can offer" is unfalsifiable as stated. - **Genre note.** This is a newsletter essay ending in a promotional block: a free workshop, a friend's course, a podcast appearance, a coaching offer, and the author's book. The persuasive frame and the funnel are the same object; read the argument knowing that "you are the source, and you're not fully occupying it" is also the qualifying pain for the coaching call at the bottom. ### 🗒️ Notes - Not a transcript; no timestamps present. Dense notes follow in source order. - **¶1–2 (Downshift opening).** Prospective members could not have described the experience they needed — nobody would request two hours alone in a 10×10 square in the woods with no phone or journal, nor somatic work, parts work, and a fire ceremony for grieving the parts of themselves that were ending. This is the article's empirical hook: preference elicitation fails for the thing being designed. - **¶3 (attribution of tone).** All of it "had to come from a source." In Downshift's case, founder Steven Schlafman. The claim isn't that Schlafman did all the work; it's that the tone was non-substitutable. - **¶4–5 (Nixon quote and application).** The quoted passage makes a universal claim about *every* human initiative. Spinks applies it narrowly: others contributed ("we added to the soup"), but the channeling capacity was Schlafman's. - **¶7–8 (the paradox and the thesis).** Nixon's paradox — decentralize *and* keep authorship — is quoted, then Spinks lands the thesis sentence: you are the source of the communities you create. - **¶9 (the failure catalogue).** Six named avoidance behaviors. Note the rhetorical structure: each is stated in the first-person plural, which converts a criticism into a confession and lowers reader defenses. - **¶10 (escalation).** "Starting a community is an act of revolution" — the strongest rhetorical move in the piece. Starting a community is reframed as declaring the world's current design deficient and committing to change what is acceptable inside your walls. - **¶11–16 (Rubin dialogue).** Cooper asks how much to focus on audience; Rubin: "The audience comes last." Justification: audiences know only what has come before. Cooper's confusion is staged as the reader's, and Rubin's "maybe for someone else it is" declines to generalize — a nuance Spinks then generalizes anyway. - **¶17–18 (art analogy and interiority).** Community is art; you can't describe what you're looking for until you're moved by it. Therefore the specification lives in the builder, formed by lived experience, and people are already waiting for it. - **¶19–21 (guardrail and succession).** One sentence of guardrail — it should always be about the collective, and contribution is required. Then succession: joiners bring their own source, become sources of subcommunities and new communities. Each iteration is birthed through one person. - **¶22 (call).** "That person is you. Your community is waiting for you." - **¶23–29 (announcement block).** Emergent Community Design workshop (free, waitlisted last time); Alex Olshonsky's "Break Your Addiction to Overthinking" inaugural cohort; an interview on Hannah Keith's podcast "The Somatic Way" covering the author's somatic practice and an intense conflict; a free "chemistry call" coaching offer; and *The Business of Belonging*. ## 📚 References - [Work With Source — Tom Nixon](https://www.workwithsource.com/) — primary source for the quoted passages - [The Source Book / Peter Koenig](https://www.thesourcebook.co.uk/) — origin of the source-role framework - [Rick Rubin on 60 Minutes with Anderson Cooper](https://www.cbsnews.com/news/rick-rubin-60-minutes-2023-04-16/) — primary source for the "audience comes last" exchange - [The Business of Belonging — David Spinks](https://businessofbelonging.com/) — author's prior long-form treatment - [Downshift](https://www.downshift.co/) — the program described - [WordPress 2003 founding announcement — Matt Mullenweg](https://ma.tt/2003/05/wordpress-now-available/) — co-founding counterexample to the single-source universal - [Producing Open Source Software — Karl Fogel](https://producingoss.com/) — the governance literature the article's guardrail sentence gestures at without citing ## 🗣️ Paraphrase - **¶1.** When the author helped launch Downshift, a program for people in major life transitions, the eventual members could not have described the experience they needed. - **¶2.** Nobody would have asked for solitary time in a marked square in the woods, somatic and parts work, or a fire ceremony to grieve endings — and no one could have requested the specific tone the retreats developed. - **¶3.** That tone had to originate somewhere; for Downshift, it originated with founder Steven Schlafman. - **¶4.** Tom Nixon, drawing on Peter Koenig, holds that every human initiative begins with one founder — the source — the person who takes the first risk on an idea. - **¶5.** Schlafman held the vision and took the risk; his intention, presence, character, and action set the container's baseline, and while everyone contributed, no one else could have channeled what the community became. - **¶6–7.** Nixon frames a paradox: nothing starts without a founder, yet a collective endeavor can't stay about the founder — decentralization is required while founders and successors retain real authorship, and a founder who shows up badly can undo everything. - **¶8.** Applied to the reader: you are the source of the communities you create; without you they don't exist, and your presence, decisions, and actions allow a community to emerge that could only emerge through you. - **¶9.** Most communities never launch or don't last because the founder won't take the leader's seat — wanting to appear communal, granting equal voice over intuition, avoiding bossiness, avoiding taking space, avoiding conflict, people-pleasing, shrinking the vision to avoid friction. - **¶10.** Starting a community is revolutionary: it declares something missing from the world as designed and commits to changing what's acceptable inside the container being built. - **¶11–16.** In a relistened Cooper/Rubin interview, Rubin says the audience comes last, because audiences know only what already exists; Cooper objects that the music business is built on figuring out what people like; Rubin allows that this may be true for others, not for him. - **¶17.** Community isn't a song but it is art, and like good art it can't be specified in advance — its meaning registers only after the experience moves you. - **¶18.** No one can tell you the community they want, but you can know it; the totality of your lived experience makes it certain that a form of community only you can offer exists, and people are waiting for it whether or not they know it. - **¶19.** This does not mean the community should be about the creator — it should always be about the collective, and you will need others, because community requires contribution — but you remain the source. - **¶20.** Over time others bring their own source, contributing while the vision aligns with theirs, and becoming sources of subcommunities, side quests, and wholly new communities: source leads to source. - **¶21–22.** Every new iteration is born through one person bold enough to hold a vision and build a container that never existed. That person is you. - **¶23–29.** Announcements: a free Emergent Community Design workshop returning after a year (waitlisted previously); Alex Olshonsky's inaugural "Break Your Addiction to Overthinking" cohort; an interview on Hannah Keith's podcast "The Somatic Way" about somatic practice and a hard conflict; an invitation to a free chemistry call for coaching; and a pointer to *The Business of Belonging*. ## 📰 Newsletter - **The takeaway for WordPress folks:** David Spinks says every community has a *source* — the one person who took the first risk — and that most communities die because that person keeps apologizing for existing. Anyone who has watched a meetup quietly dissolve after the organizer decided to "let the group decide everything" will recognize the pattern. [Read the original](https://davidspinks.substack.com/p/you-are-the-source-of-your-community). - **Where it fits our world:** every WordPress Meetup, WordCamp track, Training team learning path, and plugin has a source. Make Teams have reps and leads precisely because someone has to hold the shape. The article is a decent argument for why "who is holding this?" is a real question and not a bureaucratic one. - **Where it doesn't fit:** the piece opens with "every human initiative starts with one single founder," which is a fun sentence to say to a project Matt Mullenweg and Mike Little started together in 2003. Open source has a whole literature on what happens when the source's authority isn't bounded, and none of it is in this essay. - **Practical use:** if you have been sanding down your own vision for a meetup, a course, or a plugin roadmap so nobody feels bossed — this is your permission slip. Pair it with an actual governance doc so the permission slip doesn't become a hall pass. [Producing Open Source Software](https://producingoss.com/) is still free and still right about succession. - **Also in the article:** a free Emergent Community Design workshop, a somatic-practice podcast interview, and the standard newsletter coaching funnel at the bottom. Worth knowing the persuasive frame and the offer are the same object. - **One line to steal for your next organizer onboarding:** the person who makes the container is not overhead — they are the thing that makes it a container. ## ✅ Action Items #### DevRel - Developer advocacy: name a single source per advocacy program (not a committee) and publish who it is, so vision decisions have an accountable author; measure whether named-source programs ship more talks and demos per quarter than committee-run ones. - Education: run one workshop designed entirely from the instructor's conviction with no pre-survey, alongside one designed from a learner survey; compare completion and NPS. - Developer experience: audit the docs set for passages written to avoid offending anyone; rewrite three with an opinionated, single-author voice and A/B the task-completion rate. - Developer marketing: stop testing campaign concepts that only reflect what the audience already recognizes; reserve 20% of the calendar for concepts the audience could not have requested. - Community management: add a "who is the source of this space?" field to every community property in the inventory; flag any with an empty value as at-risk. - Internal/external/cross-project: write down the succession path for every named source; a source without a named successor is a key-person risk on the register, not a leadership win. #### OSPO - Policy & Governance: pair the source concept with explicit decision rights — document where founder authorship ends and delegated authority begins, in writing, before the founder is unavailable. - License Compliance: not directly addressed by this source; the nearest transfer is that compliance work also needs a named owner rather than diffuse committee responsibility. - Security Management: ensure vulnerability intake never depends on one charismatic individual; the "source" pattern is exactly the failure shape a security process must not have. - Software Inventory: record maintainer-of-record for each inventoried component; treat the field as the operational version of "source" with an SLO for freshness. - Developer Support: offer founders of internal projects a governance consultation at inception, when the source is still setting the container's norms and change is cheap. - Community Engagement: when funding an upstream project, fund the source's time explicitly rather than assuming the role is free labor. - Strategic Alignment: add a founder-dependency risk metric to the OSPO scorecard — percentage of critical projects with a single unreplaceable source. #### Community - Maintainers: run a governance clinic on the distinction between authorship and authority; use the Nixon paradox as the framing case. - Contributors: create explicit paths for contributors to found subcommunities, since the article's own succession model ("source leads to source") requires that permission to be granted, not assumed. - Sponsors: ask sponsored projects to name their source and their successor plan as a condition of the grant; publish both. - Ecosystem: run a bus-factor drill — simulate the source being unavailable for 90 days and see what stalls. #### WordPress - Core: name the source for each major initiative in the release cycle rather than letting authorship diffuse across the ticket queue. - Core Performance: not addressed by this source; nearest transfer is assigning a single owner to each performance budget so regressions have an accountable reader. - Core AI: define who holds the vision for AI features and where community input binds versus advises, before the guardrails are needed. - **Core Program Team:** add "who is the source of this?" to cross-team dependency intake; track initiatives with no identifiable author as coordination risk. - Mobile: assign a single design source for the offline UX direction rather than merging survey feedback into an averaged compromise. - Playground: encourage instructors to build opinionated reproducible labs instead of feature tours assembled from requests. - Community: brief Meetup and WordCamp organizers that setting the tone is their job, and pair that message with the Community Code of Conduct so authorship never reads as unaccountability. - Training: build one learning path that starts from an instructor's conviction about what learners need rather than from the request queue; compare completion against request-driven paths. - Marketing: test one narrative the audience could not have asked for, and hold it to the same measurement bar as the safe ones. - Support: identify the source of each support workflow so knowledge-base gaps have a named owner instead of a rotating queue. - Design: run a research retro on where user requests returned only what already exists, and where they surfaced genuinely new needs; the article's claim is testable here. - Documentation: give each handbook a named editor with real editorial authority, not a committee with veto rights. - Photos: assign a curatorial source for taxonomy decisions; consensus taxonomy tends to average into uselessness. - TV: name an editorial source for content indexing and caption quality standards. - Polyglots: distinguish glossary decisions that need locale-lead authorship from those that need broad consensus. - Accessibility: this is the clearest limit case for the article — accessibility requirements are not the founder's intuition to override; codify WCAG 2.2 AA conformance as non-negotiable regardless of who the source is. - Meta: add maintainer-of-record metadata to .org project tooling. - CLI: keep command UX decisions with a named owner; document the decision rationale so successors inherit reasoning, not just code. - Hosting: cross-host defaults need an authoring source plus a ratifying group; document which is which. - Tide: name who owns scoring-criteria changes, since scoring is inherently an opinionated act. - Openverse: define who holds moderation policy authorship versus who reviews it. - Themes: give the review-guidelines document a named editor to end guideline drift by accretion. - Plugins: same — a named source for the guidelines, with a published change log of authorship decisions. #### The WPOCC - Programs: build fellowship tracks around individual sources with named visions rather than around committees; fund the person who took the first risk. - Projects: for every WPOCC-hosted project, record the source and the succession plan in the project charter at kickoff. - Funding experiments: pilot microgrants that fund a source's time for six months with milestone payouts, and publish whether founder-funded projects outlive committee-funded ones. ### FAIR - Technical independence: FAIR's own founding is a live test of the article's thesis — record who the sources were and how authorship was distributed as the network federated. - Policies and covenants: write anti-capture covenants that survive the departure or over-reach of any single source; the source principle without covenants is founder capture with better vocabulary. - Productized governance artifacts: ship a "source and succession" template as a standard charter section other projects can adopt. ## 🧪 Hypotheses - **H1.** Communities with a single, publicly named founder-source survive their first 24 months at a higher rate than communities launched by a founding committee of three or more. - **H2.** Participants asked in advance to specify their ideal community experience will describe variations on formats they have already attended, at a measurably higher rate than participants asked after attending a novel format. - **H3.** Organizers who score high on conflict-avoidance measures run communities with lower distinctiveness ratings from members than organizers who score low. - **H4.** Communities whose source departs without a named successor decline in activity faster than those with documented succession, controlling for size and age. - **H5.** "Source leads to source" is testable: the number of spin-off subcommunities founded by members predicts the parent community's longevity better than parent-community headcount does. - **H6.** Explicitly documenting the boundary between founder authorship and delegated decision rights reduces reported governance conflict without reducing perceived community distinctiveness. ### 📊 Methodology - **For H1:** retrospective cohort study over a public community registry (Meetup.com groups, Discord server directories, WordPress Meetup chapters) with founding-team size coded from launch announcements; survival analysis with Cox proportional hazards, controlling for topic, city size, and sponsor presence. - **For H2:** pre/post within-subject design at a live program. Collect free-text ideal-experience descriptions before attendance; code responses for novelty against a catalogue of existing formats by two blind raters; repeat the elicitation post-attendance and compare novelty scores. - **For H3:** pair a validated conflict-avoidance instrument administered to organizers with member-reported distinctiveness surveys; analyze at the community level with organizer as the unit and members nested within. - **For H4:** natural-experiment design using open-source projects with documented maintainer handoffs; compare commit velocity, issue response time, and contributor count for 12 months pre/post departure, split by whether a successor was named in advance. - **For H5:** network analysis of spin-off lineage in a bounded ecosystem (e.g., WordPress Meetup chapters and the WordCamps they seeded); measure whether spin-off count predicts parent survival beyond size effects. - **For H6:** field experiment across comparable community chapters; randomly assign half to adopt a written authorship/decision-rights charter; measure governance-conflict incidents and distinctiveness ratings at 6 and 12 months. - **Data sources:** public community directories, open-source repository metadata, event platform APIs, and direct organizer surveys. The article itself supplies zero data, so every hypothesis here requires original collection. ### ❓ Questions - What exactly did Koenig's "extensive research" consist of — sample, method, publication? Without that, the article's evidentiary spine is an unverified appeal. - How does the source principle handle genuinely co-founded projects, where two people took the first risk simultaneously? Does the frame predict those fail, or does it quietly redefine one co-founder as the "real" source after the fact? - What is the mechanism that stops "you are the source" from becoming "therefore my judgment is unappealable"? - If audiences only know what has come before, how do you distinguish a visionary source from a source who is simply wrong about what people need? What signal arrives before the community fails? - Rick Rubin declined to generalize his own method ("maybe for someone else it is"). Why is the essay comfortable generalizing it for him? - Is the "source" role stable, or is it just the name we assign retrospectively to whoever succeeded? What would a study of failed founders' source-ness look like? - In accessibility, safety, and legal compliance, whose intuition loses? The article never marks the boundary. ### 🔮 Future Research - **The survivorship gap.** All source-principle evidence circulating today is drawn from successful ventures. A matched study including failed founders — same conviction, same refusal to survey, different outcome — would establish whether source-ness predicts anything or merely describes winners. - **Operationalizing "source."** The construct needs a measurable definition (first-risk timing, tone attribution by members, decision-origin tracing) before any of the above hypotheses can be tested rigorously. - **Co-founded initiatives.** A dedicated study of two-and three-founder projects, coding whether members can identify a single tone-setter, would directly test the universal claim. - **Boundary conditions in regulated or safety-critical communities.** Where does founder authorship legitimately stop — accessibility, moderation, child safety, financial handling? A typology would make the frame usable rather than merely inspiring. - **Succession and the "source leads to source" claim.** Longitudinal lineage tracking in a bounded ecosystem would test whether spin-off generation actually occurs at the rate the article implies. - **Cross-cultural validity.** The source principle assumes an individualist founder narrative. Test whether it holds in collectivist contexts where initiatives are legitimately attributed to groups. ### 💡 Implications - **Practice.** Organizers should stop pre-surveying for vision and start pre-surveying for logistics; the two questions have been conflated. Name the source of every community property you run, and write down what that person does and does not get to decide. - **Policy.** Any governance document adopting this frame needs a matching accountability clause. Authorship without bounded authority is the exact failure mode open-source governance literature exists to prevent. - **Security.** The source pattern is a bus-factor-of-one pattern. Security-critical functions must be explicitly exempted: intake, disclosure, and signing authority need redundancy regardless of who founded the project. - **Education.** Instructional design that averages learner requests produces recognizable, forgettable curricula. The transferable practice is instructor conviction plus rigorous outcome measurement — conviction without measurement is just preference. - **Funding models.** If the source's time is what creates the container, funding the source's time is the highest-leverage grant available. Most community funding instead pays for events and infrastructure, which is funding the soup and not the pot. - **Open source specifically.** WordPress, Linux, Python, and Rust all illustrate that the founder question is real and that unbounded founder authority creates predictable crises. Adopt the diagnosis; supply the guardrails the article omits. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade Level ≈ 9–10; Flesch Reading Ease ≈ 60–65. Sentences are short and largely declarative; the vocabulary load comes from unglossed practitioner jargon ("somatic," "parts work," "container," "vibration," "taking one's seat"), not from syntax. ~1,051 words, roughly a 5-minute read. #### 👀 Visual learners - Present: a single header image; no diagrams, charts, or tables. - Improve: a diagram of source → container → contributors → spin-off sources; a two-column visual contrasting "surveyed community" against "sourced community"; a timeline of the Downshift launch. #### 🔊 Aural learners - Present: none in the article itself, though it links a podcast interview with the author. - Improve: add a 3-minute narrated version at the top; publish the essay as a podcast segment; offer TTS. #### 🗣️ Verbal learners - Present: strong — two extended quotations, a staged dialogue, and a memorable aphorism ("source leads to source"). Storytelling carries the argument. - Improve: gloss "somatic," "parts work," and "container" on first use; add a short glossary of source-work terms; define what "taking one's seat" means operationally. #### 🧩 Kinesthetic learners - Present: none — no exercises, checklists, or prompts to try. - Improve: add a "name your source" worksheet; a 10-minute exercise to write the community vision without consulting anyone; a decision-rights checklist to complete before launch. #### 🧠 Logical learners - Present: weak — the argument is assertion plus anecdote plus a borrowed quotation; no data, no counterargument handling. - Improve: state the claim's boundary conditions; address the co-founder counterexample explicitly; cite Koenig's research with method and sample; add a decision tree for when founder judgment binds versus when it advises. #### 🧑‍🤝‍🧑 Social learners - Present: Substack comments and a linked free workshop. - Improve: add discussion prompts for organizer peer groups; a cohort-style reading guide; a structured peer-review rubric for reviewing each other's community visions. #### 🧘‍♀️ Solitary learners - Present: partial — the essay is naturally reflective and second-person. - Improve: add explicit journaling prompts ("where have you made your vision smaller this year?"); a self-assessment on the six named avoidance behaviors. #### 🌿 Naturalistic learners - Present: incidental only — the woods, the 10×10 square, the fire ceremony are setting rather than argument. - Improve: connect community lifecycle to ecological succession; discuss the environmental footprint of retreat-based programming; use ecosystem language for the source-leads-to-source claim, which is genuinely a propagation model. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: standard Substack article structure with a real `<h1>`, paragraph elements, and a linked header image. - Improve: confirm the header image carries meaningful alt text rather than a filename; ensure the announcement block's links have descriptive text rather than "here" — the article uses bare "here" at least three times, which fails WCAG 2.2 AA 2.4.4 Link Purpose (In Context) for link-list navigation. #### Keyboard navigation - Present: Substack's default template provides focus styles and logical DOM order. - Improve: verify skip-to-content is reachable; verify the subscribe modal that Substack injects does not create a focus trap and can be dismissed with Escape (WCAG 2.1.2 No Keyboard Trap). #### Contrast and readability - Present: default Substack body text meets 4.5:1 on white. - Improve: verify the muted grey used for the announcement footer and caption text against 1.4.3 Contrast (Minimum); Substack's secondary grey frequently lands near 4.0:1. #### Text resizing and reflow - Present: responsive template; reflows at 320 CSS px equivalent. - Improve: confirm no clipping at 200% zoom in the announcement block (WCAG 1.4.4, 1.4.10); confirm sticky subscribe bars do not consume more than the permitted viewport at high zoom. #### Media and captions - Present: text-only article; no embedded audio or video, so captioning is not directly at issue. - Improve: the linked podcast interview should ship a transcript; the essay could link the transcript directly rather than a play page (WCAG 1.2.1/1.2.2 apply to the linked media, not this page). #### Forms and interactions - Present: the Substack subscribe form with a labeled email field. - Improve: verify programmatic label association rather than placeholder-only labeling (WCAG 3.3.2 Labels or Instructions); verify error messaging is announced (4.1.3 Status Messages); confirm target size for the subscribe control (2.5.8 Target Size Minimum). #### Standards reference - Primary gaps mapped: 2.4.4 Link Purpose (repeated bare "here" links), 1.4.3 Contrast (secondary text, needs measurement), 3.3.2 and 4.1.3 (subscribe form, platform-level), 2.5.8 Target Size (platform-level). The article's own authored content is largely conformant; most risk is inherited from the platform template. ### 🌍 DEIB Assessment #### Cultural breadth - Present: thin. Every named person and example is drawn from a US-centric, English-speaking, coaching-and-startup milieu — Downshift, Schlafman, Nixon, Koenig, Rubin, Cooper, Olshonsky, Keith. - Improve: include community-founding examples from collectivist cultures and from traditions where initiatives are legitimately attributed to elders' councils or extended kin groups; translate or summarize in additional languages. #### Inclusive language - Present: gender-neutral throughout; second-person address is welcoming; no exclusionary idioms. - Improve: gloss the somatic-therapy jargon — "parts work," "somatic experiences," "taking one's seat," "vibration" — which quietly restricts the audience to people already inside that practice community. A plain-language summary would widen access considerably. #### Neurodiversity support - Present: short paragraphs, clear narrative progression, concrete anecdotes before abstraction — all genuinely helpful. - Improve: add subheadings (the essay runs unbroken for ~1,000 words), a summary box up top, and bolded key sentences for scanning. The unstructured flow is the main barrier. #### Representation - Present: limited. The founder archetype presented is a venture-adjacent US male founder; the two authority figures quoted are men; the exemplar founder is a man. Two women appear, both in the promotional block rather than as sources of argument. - Improve: quote women and non-Western community founders as authorities on the thesis, not as items in an announcement list; include examples of founders without access to capital or retreat infrastructure. #### Psychological safety - Present: the first-person-plural framing of the failure list ("we want to be communal," "we people-please") shares the criticism rather than aiming it, which is a real safety choice. The article also flags an "intense conflict" in the announcement block with reasonable restraint. - Improve: the essay's core message — your smallness is why your community failed — can land hard on people whose constraints were structural (funding, caregiving, discrimination, disability) rather than psychological. A single sentence acknowledging structural barriers would prevent the piece from reading as blame. Add a content note for the grief and life-transition material. ### ✅ Logical Validity #### Strong reasoning - **Inductive, ¶1–3 (Downshift anecdote → non-elicitability).** The observation that prospective members could not have requested a fire ceremony or a silent square in the woods is concrete, falsifiable in principle, and directly supports the narrow claim that preference elicitation fails for novel experiences. Strengthen by reporting how members actually described their needs pre-program, which the author is positioned to know. - **Analogical, ¶17 (community as art).** The analogy is well-chosen for the specific property it transfers — recognition-after-experience — and the author explicitly marks its limit ("community isn't a song"). Strengthen by naming which properties do *not* transfer, particularly that art has an audience while community has participants who co-produce the artifact. - **Dialectical, ¶6–7 and ¶19 (the paradox held open).** Quoting Nixon's decentralize-yet-author paradox and then conceding "it should always be about the collective" shows the author anticipating the founder-worship objection rather than ignoring it. Strengthen by supplying an actual mechanism — decision rights, veto scope, succession — instead of a single concessive sentence. - **Causal, ¶5 (non-substitutability).** "We added to the soup, but without Steve it wouldn't exist" is a defensible counterfactual for a specific case the author witnessed firsthand. It is the article's most credible causal claim precisely because it is scoped to one instance. #### Fallacies - **Appeal to unverified authority — ¶3.** *"In his book "Work With Source", Tom Nixon shares a perspective that is bold, but validated by extensive research conducted by Peter Koenig"*. The word "validated" does real persuasive work while no method, sample size, publication, or replication is named. Koenig's source work is practitioner-derived consulting insight, not peer-reviewed research, and "extensive" is doing the job a citation should do. **Fix:** cite the research directly — n, method, venue — or downgrade the language to "developed from decades of consulting practice," which is both accurate and still interesting. Tag: `#fallacy/appeal-to-authority`. - **Hasty generalization (sweeping universal) — ¶4.** *"Every human initiative – from projects to parties to entire businesses – starts with one single founder, the source."* A single counterexample defeats a universal, and they are plentiful: WordPress (Mullenweg and Little, 2003), Google, Ben & Jerry's, most standards bodies, and essentially every constitutional founding. The frame typically rescues itself by retroactively designating one co-founder the "real" source, which makes the claim unfalsifiable rather than true. **Fix:** state it as a strong tendency — "most initiatives trace to one person's first risk" — which survives counterexamples and loses nothing the argument needs. Tag: `#fallacy/hasty-generalization`. - **False dilemma — ¶9.** *"Failing to take one's seat as a leader is why so many communities fail to get off the ground... We want everyone to have an equal voice instead of trusting our intuition."* The passage offers exactly two options: assert your vision, or shrink from conflict. It omits the large middle where founders deliberately choose consent-based, sociocratic, or co-op governance as a considered design decision — and it omits structural causes of failure entirely (no funding, no time, no venue, burnout, discrimination). **Fix:** distinguish *abdication* from *designed distribution*, and acknowledge non-psychological failure causes. Tag: `#fallacy/false-dilemma`. - **Weak analogy / faulty transfer — ¶17.** *"Community isn't a song, but it is art."* The Rubin principle transfers a producer's relationship to a finished recording onto a community's relationship to its members — but an album's audience consumes a completed artifact, while a community's members *are* the artifact. Ignoring participant input in a co-produced system is not the same act as ignoring market research on a record. Note also that Rubin himself refused to generalize his method ("maybe for someone else it is"), a caveat the essay drops. **Fix:** confine the transfer to the initial vision-setting phase and state explicitly that ongoing member feedback is load-bearing in a way audience feedback is not. Tag: `#fallacy/weak-analogy`. - **Unfalsifiable claim / appeal to certainty — ¶18.** "make it an absolute certainty that there's a form of community only you can offer." Nothing could count as evidence against this, and "absolute certainty" is asserted about an untestable proposition. **Fix:** reframe as a working stance rather than a fact — "assume it until the evidence says otherwise" — which does the same motivational work honestly. Tag: `#fallacy/unfalsifiable-claim`. - **Survivorship bias (structural, throughout).** Every exemplar — Downshift, Rubin, the author's own practice — is a success. Founders who trusted their intuition, refused to survey, and failed anyway are absent from the sample, yet they are the population that would test the thesis. **Fix:** include at least one case where source conviction produced failure, and say what distinguished it. #### Tone of voice - Warm, direct, and second-person throughout, moving from personal anecdote to gentle exhortation and ending in a benediction ("That person is you. Your community is waiting for you."). The register is coaching-adjacent and somatic-therapy-inflected — "vibration," "container," "taking one's seat" — which signals in-group belonging to readers already in that world. Criticism is delivered in the first-person plural, which is genuinely disarming and keeps the piece from moralizing. The closing announcement block shifts abruptly to promotional register; the seam is visible and worth noticing, because the essay's diagnosed pain and the coaching offer beneath it are the same thing. ### 🛡️ DARVO Analysis - **Deny:** No denial pattern present. The article makes no defense against an accusation and minimizes no harm attributed to the author or anyone else. The one conflict referenced (in the announcement block, about a podcast interview) is mentioned without characterizing any counterparty. - **Attack:** No attacks on accusers or credibility-undermining. The critical passage in ¶9 targets behaviors and is written in the first-person plural, which implicates the author alongside the reader rather than attacking anyone. - **Reverse victim/offender:** Not present. No party is recast as victim or offender. - **Emotional cues and rhetoric worth noting anyway:** the essay uses certainty language ("absolute certainty"), revolutionary framing ("an act of revolution"), and destiny framing ("people are waiting for it") — persuasive intensifiers, not DARVO. The relevant caution is different: the piece locates the cause of community failure inside the reader's psychology, which, absent any acknowledgment of structural barriers, can function as soft self-blame. That is a fairness concern, not a DARVO pattern. - **Verdict:** Not applicable to this source — DARVO requires an accusation-and-defense dynamic that this essay does not contain. ## 🎯 Conclusion - **Bottom line.** Spinks is right that communities are emitted by people rather than assembled from preferences, and right that many organizers sabotage their own containers by preemptively shrinking. He is wrong to state it as a universal, and the essay stops one sentence short of the governance mechanism that would make the frame safe to hand to a founder. - **Next steps for readers.** Name the source of every community you run, out loud and in writing. Then write the other half the article omits: what that person decides alone, what they decide with others, what they cannot decide at all (accessibility, safety, code of conduct), and who takes the seat when they leave. - **For the WordPress and FAIR context specifically.** Adopt the diagnosis, refuse the license. Open source has already run the experiment on unbounded founder authorship and has the scar tissue to prove what it costs. Source plus succession plus bounded decision rights is the version worth keeping. - **Read it for what it is.** A well-written permission slip with a coaching funnel attached. Take the permission; check the frame against your own governance before you take anything else. ## 🔄 Refactor Appendix — You Are The Source of Your Community ### 📚 Literature Atoms (H3) #### [H1] Community founders set tone contributors cannot replicate > [!quote] ID:rw_pending > "As a community creator, you are the source of the communities you create. Without you, the community doesn't exist." **Context & use**: - ¶8, the thesis sentence of the essay - This is the claim everything else in the piece supports, and the one worth carrying into WordPress Make-team and Meetup organizer conversations: the organizer is not overhead, they are the constitutive act. **Tags**: #xref #aphorisms **Highlight**: Reader-native inline highlight on ¶8  #### [H2] Audiences can only request what already exists > [!quote] ID:rw_pending > "The audience doesn't know what they want. The audience only knows what's come before." **Context & use**: - ¶14, Rick Rubin quoted from the Anderson Cooper interview - Directly usable in instructional design and DevRel program planning: separate logistics elicitation (survey it) from vision elicitation (don't). The Downshift anecdote in ¶1–2 is the concrete demonstration. **Tags**: #xref #articleseed **Highlight**: Reader-native inline highlight on ¶14 context (anchored at ¶17)  #### [H3] Founders shrink visions to avoid ruffling feathers > [!quote] ID:rw_pending > "We make ourselves and our visions smaller so that we don't ruffle feathers." **Context & use**: - ¶9, the failure catalogue - The diagnostic value is the specificity of the six behaviors; the analytic weakness is that it excludes structural failure causes. Use it as a self-check prompt, not as an explanation of why a given community failed. **Tags**: #xref **Highlight**: Reader-native inline highlight on ¶9 (also tagged `#fallacy/false-dilemma`)  #### [H4] Founding capacity propagates through joiners into new communities > [!quote] ID:rw_pending > "Source leads to source." **Context & use**: - ¶20, the succession claim - The most testable proposition in the essay and the best answer to the founder-dependency objection — spin-off generation is measurable in a bounded ecosystem like WordPress Meetups seeding WordCamps. **Tags**: #xref #aphorisms **Highlight**: Reader-native inline highlight on ¶20  ### 🧠 Permanent Candidates (H4) #### [P1] Authorship and authority are separate grants **Claim** (one sentence, Courtney's voice): The person who authored a community's vision has a real, non-transferable role in holding it, and that authorship confers no unappealable decision rights. **Evidence pointer**: [[#H1]] — the essay asserts authorship and concedes collectivity in one sentence without ever separating the two grants. **Scope & conditions**: Holds wherever a named founder exists and a governance layer is possible. Breaks down in genuinely leaderless or consensus-mandated bodies, and in safety-critical domains (accessibility, moderation, disclosure) where no authorship claim should bind. **Links** (≥1 with annotation): - [[Open Source Governance]] — because extends the founder-authority question into documented decision rights - [[Benevolent Dictator For Life]] — because contrasts on whether authorship should carry veto power - [[WordPress Make Team Structure]] — because applies-in a federated project where team reps hold shape without owning it `status: seedling`  #### [P2] Elicit logistics from participants and vision from yourself **Claim** (one sentence, Courtney's voice): Ask people what they need in order to attend, and never ask them what the thing should be. **Evidence pointer**: [[#H2]] — the Downshift anecdote and the Rubin quote both demonstrate that preference elicitation returns prior formats. **Scope & conditions**: Holds for novel experience design — programs, curricula, events, product direction. Does not hold for accessibility requirements, scheduling, cost, or safety, where participant input is authoritative and overriding it is harm, not vision. **Links** (≥1 with annotation): - [[Instructional Design Needs Analysis]] — because contrasts on where learner input should bind - [[Jobs To Be Done]] — because extends the "people can't specify solutions" insight into interview method - [[Learning Path Design]] — because applies-in Training team curriculum work `status: seedling`  ### ✏️ Fleeting Queue - [F1] Check what Koenig's "extensive research" actually is — method, sample, whether it was ever published — before citing the source principle anywhere with authority. #fleeting #inbox - [F2] WordPress had two founders in 2003. Does the source frame handle co-founding, or does it retroactively demote one? Worth a short post. #fleeting #inbox #articleseed - [F3] Where did I make a vision smaller this year to avoid ruffling feathers — post-kinds roadmap, The WPOCC programming, Outpost scope? #fleeting #inbox - [F4] Draft the missing half of this essay: a "source and succession" charter section listing decides-alone / decides-with / cannot-decide. #fleeting #inbox #articleseed ### → Things 3 (max 2 actions) - [ ] Draft a "source and succession" charter section (decides-alone / decides-with / cannot-decide) for The WPOCC project template — community governance #things - [ ] Verify Peter Koenig's source research has any published methodology before citing the source principle in a talk or post — research #things  📄 **Full text:** [[Full Document Contents/Articles/You Are the Source of Your Community.md|You Are the Source of Your Community by David Spinks]] ## Highlights - When asked, they would not have said, "Please ask me to sit alone in a 10x10 ft square in the woods for two hours without a phone or journal." They would not have asked for somatic experiences, parts work, and a fire ceremony to say goodbye to and grieve the parts of them that were ending. And regardless of the programming, they could not have asked for the specific tone and vibration that they would eventually come to feel at our retreats. ([View Highlight](https://read.readwise.io/read/01m0aptwxjaeyy11pzb3bhndnv)) - Note: A founder's specific practices can't come from user research — the article's one concrete, falsifiable illustration. - Tags: atom/literature/h1 - > > "Every human initiative – from projects to parties to entire businesses – starts with one single founder, the source. The source is the person who takes the first risk to realise an idea." > > > ([View Highlight](https://read.readwise.io/read/01m0apv042ccy7j3edyf2vrjzp)) - Note: Nixon's central claim — asserted as "validated by extensive research" without citation. Load-bearing for the whole essay. - Tags: atom/literature/h1 - > > "Nothing starts without a founder, but here's the great paradox: to grow a collective endeavour, it can't just be about the founder. We have to decentralise, yet at the same time, founders and their successors have a natural authorship and vital role to play in endeavours they start. A founder failing to show up well can be the undoing of everything, but get it right and a purposeful vision can come to life spectacularly." > > > ([View Highlight](https://read.readwise.io/read/01m0apv47w6nnjzsx03aaj8w7e)) - Note: The one place the essay names the founder-overreach risk directly — but doesn't resolve it. - Tags: atom/literature/h2 - "Well, the audience doesn't know what they want. The audience only knows what's come before." ([View Highlight](https://read.readwise.io/read/01m0apv7xfbhdrb63cdwzb55v5)) - Note: Rick Rubin, via Spinks — the essay's most reusable analogy, applicable well beyond music. - Tags: atom/literature/h2, aphorisms ## New Highlights added 2026-08-22 at 1:28 PM - In his book “Work With Source”, Tom Nixon shares a perspective that is bold, but validated by extensive research conducted by Peter Koenig: ([View Highlight](https://read.readwise.io/read/01m0n6r63wsy310cm0yhdeabjx)) - Note: Fallacy — appeal to unverified authority (¶3). "Validated by extensive research" with no method, sample, venue, or replication named; Koenig's source work is practitioner-derived consulting, not peer-reviewed. Fix: cite n/method/venue, or say "developed from decades of consulting practice." - Tags: fallacy/appeal-to-authority, atom/literature/h3, source-principle - *“Every human initiative – from projects to parties to entire businesses – starts with one single founder, the source. The source is the person who takes the first risk to realise an idea.”* ([View Highlight](https://read.readwise.io/read/01m0n6rf7798fagz8rxed9y646)) - Note: Fallacy — sweeping universal (¶4). One counterexample defeats it: WordPress had two founders in 2003 (Mullenweg and Little). The frame usually rescues itself by retroactively demoting a co-founder, which makes it unfalsifiable rather than true. Fix: state as a strong tendency. - Tags: source-principle, open-source-governance, fallacy/hasty-generalization - As a community creator, you are the source of the communities you create. Without you, the community doesn’t exist. Your presence, decisions, and actions allow for a specific community to emerge, one that could only emerge through you. ([View Highlight](https://read.readwise.io/read/01m0n6qcwegeffh3wqp9wk2j6y)) - Note: Thesis sentence (¶8). The organizer is not overhead — they are the constitutive act. Carry into WordPress Make-team and Meetup organizer framing. - Tags: founder-leadership, atom/literature/h1, community-building - Failing to take one’s seat as a leader is why so many communities fail to get off the ground, and most don’t last long. The reasons are plenty: We want to be “communal”. We want everyone to have an equal voice instead of trusting our intuition. We don’t want to be bossy. We don’t want to take up too much space. We avoid conflict and people-please. Essentially, we make ourselves and our visions smaller so that we don’t ruffle feathers. ([View Highlight](https://read.readwise.io/read/01m0n6rrg1f8vzdqbtcm5dhxak)) - Note: Fallacy — false dilemma (¶9). Two options only: assert your vision, or shrink from conflict. Omits deliberately chosen sociocratic/consent-based governance, and omits structural failure causes (funding, time, venue, burnout, discrimination). Fix: distinguish abdication from designed distribution. - Tags: fallacy/false-dilemma, atom/literature/h2, founder-leadership - Community isn’t a song, but it is art. And like good art, we can’t describe what it is we’re looking for. It’s only after we’re moved by the experience of it that we realize how much it means to us. ([View Highlight](https://read.readwise.io/read/01m0n6s0nhxmc75ty15k0kjd4v)) - Note: Fallacy — weak analogy / faulty transfer (¶17). An album's audience consumes a finished artifact; a community's members ARE the artifact. Rubin also refused to generalize his own method ("maybe for someone else it is") — a caveat the essay drops. Fix: confine the transfer to initial vision-setting. - Tags: atom/literature/h3, fallacy/weak-analogy, community-strategy - No one can tell you the exact kind of community they’re looking for. But you know. It’s within you. All of your lived experiences to this moment, and all that you are, make it an absolute certainty that there’s a form of community only you can offer. They may not know it yet, but people are waiting for it. ([View Highlight](https://read.readwise.io/read/01m0n6qw7qwecywncfcy2xgahr)) - Note: ¶18. Core motivational claim, but "absolute certainty" about an untestable proposition — nothing could count as evidence against it. Fix: reframe as a working stance, not a fact. - Tags: atom/literature/h2, fallacy/unfalsifiable-claim, source-principle - Over time, others will join and bring in their unique source. They’ll contribute to the vision as long as it aligns with their vision. They’ll also become the source of subcommunities, side quests, and the creation of entirely new communities. Source leads to source. ([View Highlight](https://read.readwise.io/read/01m0n6qm97ag8d2fb2d3zrcztk)) - Note: ¶20 — the succession claim, and the most testable proposition in the essay. Spin-off generation is measurable in a bounded ecosystem (Meetups seeding WordCamps). - Tags: community-building, atom/zettel/z1, source-principle