But anyways.

Not only have I built a lot of community launch decks, but I’ve sat through probably 50x as many community decks from platform vendors, other communities, and more. And more than a small handful have a similar slide: a stunning landing page, a big ol’ friendly button that invites users to join, and someone excitedly explaining onboarding functionality like it’s the only way anyone will ever arrive. One door. One hallway. One version of hello.

That was never fully true, but it’s now catastrophically untrue. Someone finds your community through a Google search that dumps them straight into a three year old thread about a bug that was fixed two releases ago. Someone else asks an AI assistant a question and gets a paraphrased answer with a link buried at the bottom, if they get a link at all. A third person hears about you at a conference bar because a colleague name dropped your forum while complaining about something unrelated. Three people, three completely different rooms, and you designed a reception for… well… none of them.

I gave a talk last year about how architectural principles shape human experience across physical and digital environments, and I keep coming back to it because it maps onto this almost too cleanly.

A front door isn’t just an opening in a wall. It’s a invitation. You walk in, there’s a reception, maybe some much needed information, and a beat where your eyes adjust and your nervous system registers I am allowed to be here. Then you’re guided toward wherever you’re actually going via hallways, corridors, walls, signage, and more. And that’s truly just grand if you need that experience.

Now let’s say you already know this place and you know exactly where you want to go. You know there’s a side door that takes you right to where you want to be. Also truly grand.

But both of those are very intentional behaviors. You entered the space with a desired outcome; the first with exploration and the second with direction.

So now let’s say you didn’t see the front door, grabbed the handle of the side door. And the side door just skipped all of that ‘truly grand’ stuff from above. It drops you straight into the kitchen mid dinner party; no reception, no adjustment beat, just you and a room full of context you don’t have.

Uh… am I allowed to be here?

Search and AI summaries are side doors. They don’t route people through your front door and to reception. They drop them into a specific room, mid conversation, and expect that room to make sense on its own. So does it?

Most communities have spent a decade perfecting the front door and completely ignoring what happens at the side entrances.

That’s the thesis, and it’s worth sitting with, because it explains a specific kind of failure you’ve probably felt but not named: the sense that your community’s best content, the stuff that actually converts curiosity into belonging, gets buried three clicks deep, while a half baked thread with a so-so title is quietly doing the work of your entire acquisition funnel.

So what does it actually mean to design for three doors instead of one.

Your reception content (the landing page, the welcome thread, the about page) still matters, but it’s no longer your primary entrance. Its job shifts from persuasion to orientation: helping someone who’s already inside find their bearings, not convincing a stranger to walk through the wall.

Your side door content, the stuff that gets surfaced by search or scraped into an AI answer, has to work as a complete room. No hallway, no reception, no assumed context. A piece of knowledge that can’t stand alone and still be true, still be useful to someone who has never heard of your community, is not going to survive being extracted. Write for the person who arrives with zero reception.

Word of mouth is its own kind of door, and it’s the one most people forget is architectural at all. Someone vouched for you before the visitor ever showed up, which means the visitor is walking in with trust already extended on your behalf. Over explaining insults that trust. Under delivering breaks it. The room needs to be exactly as good as the person who recommended it implied it would be: no more theatrical, no less substantial.

The part that’s genuinely uncomfortable if you’ve spent years optimizing a single funnel: you don’t get to choose which door most people use anymore. The AI summary door is only going to get busier. The side entrances outnumber the front one now, probably permanently, which means the room by room experience of your community matters more than the building’s facade ever did.

I still love a good reception. First impressions matter and that the welcome experience deserves real design attention. But if every door except the front one drops a stranger into an unfurnished room with no context and no signage, the reception as entry point never mattered. It was just the door you happened to be standing at when you built the place.

Go check your side doors. I promise you’ll find at least one room with the lights off and nobody there to make sense of the chaos.

The ones who are quietly dismantling their communities because AI is going to make them obsolete anyway.

The ones who are carrying on like it’s 2019 and nothing fundamental has shifted.

And then there’s a smaller, quieter group. We’re a mix of deeply understanding what’s happening and adapting accordingly… or those just getting on with it because why the heck not?

This article is for that third group. But the other two are welcome to stay. Maybe we’ll convert you to the dark side.

But first, we’re going to need you to accept a really harsh reality: AI didn’t change what good community knowledge looks like. It just made it impossible to pretend that bad knowledge architecture was fine.

Do you know the move I’m talking about? Someone posts a question your community has definitely answered before, and instead of pointing to a crisp, documented resource, someone types: “Oh, great question, you should ask Jillian, she handled this exact thing last quarter.” And Jillian answers, because Jillian is generous and competent and has the institutional memory of a small government agency. Crisis averted. Thread resolved. Nobody notices that the actual answer lives entirely inside Jillian’s head.

That worked. Until it didn’t.

The communities that are panicking about AI right now were always one Jillian-on-PTO away from collapse.

Think about what “ask Jillian” actually means. It means your knowledge was never really in your community. It was in a person, and that person happened to be reachable. The member who joined six months ago and doesn’t know Jillian yet? They either figured it out themselves, gave up, or got lucky. That’s not community knowledge. That’s a single point of failure with good vibes.

And yes yes - we know the retort: “But but but… AI!”

AI didn’t create this problem. It removed the social scaffolding that let us ignore it.

Here’s where I’d gently push back on a story we tell ourselves about human cognition: we like to think we navigate knowledge relationally, that we’re fundamentally different from machines because we connect ideas through people and context and lived experience. And sure, there’s something to that. But mostly? We know where things are because we have context. We remember that the onboarding doc lives in the folder that so-and-so reorganized last spring. We know the workaround for that integration bug because we were in the Slack thread when it happened. That’s context. Not magic. Not some ineffable (how great is that word?) human quality that machines can never touch.

The gap between how humans find knowledge and how AI finds knowledge is narrower than we’d like to admit. (I know, I know. Uncomfortable. Stay with me.)

Which means the communities that will hold up, the ones that serve members well regardless of whether those members arrive having already asked ChatGPT something, run it through their company’s AI tool, or just typed a search query like it’s 2011, are the ones that were already doing knowledge architecture right. Clear, contextual, findable, not dependent on any single person’s availability or generosity.

This is not about making your community “AI-ready,” a phrase I’d actually be gloriously happy to retire. Communities serve humans. Full stop. But humans now move through information differently. They come in with partial answers. They paste things into tools and come back with follow-up questions. They expect to find what they’re looking for without having to know who to ask or which part of your site to go to. That’s not a new expectation, actually. It’s just newly consequential when it goes unmet.

So what does this mean practically? It means documentation that stands alone, with enough surrounding context that a reader (human or otherwise) doesn’t need backstory to make use of it. It means tagging and titling that reflects how people ask questions, not how the internal team thinks about categories (I’m glaring at you personas). It means periodically asking: if Jillian left tomorrow, what would actually be findable? What would disappear with her? (Not much actually; Jillian knows to document her brain on the regular but Jillian is weird.)

It also means letting go of the fantasy that relational knowledge transfer scales. It doesn’t. It never did. Jillian has been subsidizing your knowledge architecture for years, and she deserves a vacation. Italy or France will do.

The communities worth building, right now, are the ones that work when nobody knows anybody. They’re also the ones that become richer when people do connect, when Jillian’s expertise gets documented and built upon rather than just tapped and forgotten.

And y’all… that’s not an AI story. That’s just a community worth having.

Go give Jillian some time off.

A former boss of mine (Rachel Happe: LinkedIn | Engaged Organizations | Control is for Amateurs) used to gleefully and mischievously say “Control is for amateurs”; so much so that she made us t-shirts. She’d just drop it into conversation, totally unprompted, like it was obvious. It took me an embarrassingly long time to understand what she meant.

I kept waiting for the second half of the sentence. The “so instead, do THIS” part. The framework. The playbook. The three steps to structured freedom or whatever. It never came. Because that was the point. The people who feel compelled to reach for control, to define the outcomes, to spell out exactly what participation looks like and what it’s for… those are the amateurs. The masters are doing something sneakier (and sneaky she was - still IS!). And more interesting.

Here’s the thing we tell ourselves in community work: clarity drives participation. Make the ask specific. Show people exactly where their contribution lands. “Your answer helped 42 people this month.” “Your post was the top resource in Q3.” Explicit impact, explicit prompt, explicit result. Tight loop, measurable, reportable to stakeholders. Clean.

And it’s not wrong… exactly. It works. People respond to it. But it’s also a ceiling.

Here’s what social physics (yes, that’s a real field, and yes, it will make you feel like a puppet and a puppeteer simultaneously) keeps showing us: human behavior is not nearly as spontaneous as humans believe it to be. We are wildly, almost insultingly predictable. The conditions you set determine the behavior you get, far more than the individuals making choices inside those conditions. Which means the actual job of a community designer is not to control behavior. It’s to architect the conditions that make the behavior you want feel like the member’s own idea.

The best community design is invisible. Not because it’s subtle. Because it’s a theme park.

Think about how a theme park works. Every path, every sightline, every queue is engineered. The “spontaneous” detour through the gift shop? Planned. The feeling that you discovered that hidden churro cart? Designed. The mechanical box you never noticed because it was painted “Go Away Green” (no, really - it’s a thing)? You are being guided at every moment, and you are having the time of your life, and you will go home and tell people you just wandered around and it was magical. Disney didn’t hand you a map with the route highlighted and a timer. They built an environment where you couldn’t help but do exactly what they needed you to do, while feeling entirely free.

That is what mastery looks like in community design.

So what does this actually mean for how we work? A few things worth munching on.

First: Stop over-narrating impact. When you tell someone exactly what their contribution accomplished, you close the loop for them. You also close the door on their imagination, which is almost always more generous than your metrics. A member who wonders “I hope that helped someone” will carry that question into their next visit. A member who knows “that helped 12 people” has completed a transaction. Leave some darn room, willya?

Second: Watch what happens when you remove the explicit prompt. Most community programs are prompt-heavy: “Share your story,” “Answer this week’s question,” “React if you agree.” These work. They also train members to wait to be asked. The communities with the most durable contribution cultures tend to have softer structures, ones that create occasion without dictating behavior. There’s a difference between a room with assigned seats and a room with good acoustics. Both fill up. Only one feels alive.

Third: Trust the container more than the content. Your job is to build the walls, the lighting, the ambient conditions. What happens inside is, genuinely, up to the people in the room. The instinct to over-program, to fill every silence, to make sure every interaction has a clear purpose and a tracked outcome… that instinct is not serving your members. It’s serving your anxiety. (I say this as someone who has definitely built a spreadsheet tracking “spontaneous” member interactions. We contain multitudes.)

Fourth, and maybe the hardest: Get comfortable not knowing exactly what worked. Ambiguity in impact is not a measurement failure. It’s a sign that people are doing things you didn’t design for, which is the whole goal. The moment your community is perfectly legible is the moment it has stopped surprising you. And a community that can’t surprise you is one that your members have already outgrown.

My former boss was right. Control is for amateurs. The professionals build the theme park and then buy a ticket if for nothing else but the people watching.

And trust me, y’all are predictably entertaining.

But I’m going to suggest a uncomfortable swap, though. Well, uncomfortable for you. I got comfy with this a long time ago.

What if the lurker isn’t the edge case you’re tolerating? What if they’re the actual user, and the person posting is just... infrastructure?

Marinate in that for a second, because it changes everything downstream. Most community programs are built, measured, and pitched to leadership around the people who show up and talk. The 1% writing the posts, asking the questions, starting the threads, they’re treated as the community itself, the thing you’re trying to grow. Everyone else is a rounding error, or worse, a problem to be “activated.”

But think about how you actually use most communities you’re not active in. You search a Slack workspace for how someone else solved the bug you’re stuck on. You read three pages of a forum thread before deciding not to post. You scroll a subreddit for twenty minutes during lunch, contribute nothing, ever, and leave knowing something you didn’t before. None of that shows up in a dashboard. All of it is the thing working.

The 1% aren’t the community. They’re the maintenance crew for a building full of people they’ll never meet.

I don’t love writing that sentence as I am, after all, part of the 1% in most of the communities I belong to, and “maintenance crew” is not exactly the origin story I tell myself (I prefer “architect of chaos”). But if the lurker is the primary user, the people posting are providing a service to someone else, not building a thing for themselves. Bit of an inversion, eh?

So if we take that inversion seriously, a few things stop making sense the way they used to.

The whole vocabulary of “community” starts to wobble. Trust, reciprocity, belonging, a sense that other people are there with you, those words assume two-way contact. If your primary user never posts, never replies, never even creates an account, do they have any of that? Or do they get a version of it anyway: trusting the same FAQ a thousand other people trusted, absorbing the same norms by reading instead of participating, feeling like “people like me are here” because the archive proves it, just distributed across time instead of synced across people?

I genuinely don’t know. Some days it feels like community, evolved, quieter, asynchronous, but still very very real. Other days it feels like a ghost of community from the days gone by: a town that’s all storefronts and no residents, kept running by the handful of people who still show up to stock the shelves, while everyone else just... walks through, takes what they need, and leaves. Same buildings. Different town.

And maybe that’s the part worth not resolving. Because here’s what doesn’t change, regardless of which version you believe: if your strategy, your roadmap, and your metrics are all built around the 1%, you’re optimizing for the maintenance crew and ignoring the building’s actual occupancy.

That means the read experience needs as much design attention as the write experience, because for most of your users, reading is the entire interaction. It means “active member percentage” stops being a meaningful headline number (a concept I’ve thoroughly explore in other articles here), because it was never measuring your primary user in the first place, it was measuring your staff. It means onboarding has to account for someone who’s already had four useful visits before they ever consider creating an account, because by the time they show up in your numbers, they’ve already gotten most of what they came for. And it means the loud, visible, engaged minority deserves a different kind of recognition, not because they’re “the community,” but because they’re doing labor on behalf of people who will never know their names.

Whether that’s still community or something quieter wearing community’s name, I’m not sure it matters as much as we think it does. What matters is whether you’re building for the people who show up in your reports, or the people who show up, get what they need, and never appear in one at all.

Go ahead and thank the second group. They won’t see it. They’re not logged in.

What doesn’t make it into the onboarding deck is this really finicky little thing: the moment your first members walk in, you start making promises. Not in your guidelines. Not in your welcome post. In the design itself and your behavior. In who you let in first, how you responded to the first difficult thread, whether leadership showed up in the forums or stayed behind glass. In all of it.

By Year 3, those promises are big burly walls.

We (me included) talk a lot in this profession about community design like it’s a series of discrete decisions: category structure, membership tiers, moderation policy, gamification. And it is. But it’s also something harder to name. Every design choice in Year 1 sends a signal about what this space values, who it’s for, and how status works inside it. Members absorb those signals. They build their participation habits around them. And then, quietly, they build their identity around them too.

So therefore: your founding ethos isn’t what you wrote in the mission statement. It’s what your earliest members learned to expect.

This is the thing that makes Year 3 redesigns so much more treacherous than they look on paper. You’re not updating a category taxonomy or refreshing a recognition program. You’re renegotiating a social contract that your community didn’t know it had signed, with members who didn’t know they were signing it, but who will absolutely notice when you try to change the terms.

Take something as seemingly low-stakes as expert-to-novice knowledge flow. If your community launched with strong subject matter experts front and center, and your early moderation rewarded definitive answers over exploratory questions, you’ve done more than establish a posting norm. You’ve told your members what intelligence looks like here. You’ve created a hierarchy, and some people have climbed it. When you decide in Year 3 that you want more peer-to-peer conversation, more vulnerability, more “I don’t know, what do you think?” energy, you’re not just asking for different posts. You’re asking the experts who built their reputation on certainty to step down a rung. And you’re asking the community to redefine what it means to contribute well.

And while it feels like a content problem, it’s not. It’s an identity problem.

The same dynamic shows up in access and responsiveness. If your team was highly visible in Year 1, answering questions fast, showing up in threads, being genuinely present, members calibrated to that. It became the baseline. The expectation. When your team grows and bandwidth stretches thin, or when the strategy shifts toward member-led support, the community doesn’t read that as a natural evolution. They read it as withdrawal. Because from their perspective, something was offered and then taken away.

And yes, you can explain the change. You can announce it thoughtfully. But you’re still arguing with the founding ethos, and the founding ethos has three years of precedent on its side.

None of this means Year 1 decisions are irreversible. Communities do change, and some of them change well. But the ones that manage it tend to share a quality: they treat the redesign as a renegotiation, not a correction. They name the original ethos explicitly, honor what it built, and bring members into the conversation about what needs to shift and why. That’s slower and messier than a clean product update. But it also actually works.

The harder lesson, the one I’d have wanted someone to hand me early in my career, is that intentionality in Year 1 isn’t just about building something good. It’s about building something you can actually change later. Because you will need to change it. But will you be renegotiating or apologizing?

Choose your founding ethos on purpose. Your Year 3 self will be living inside it either way.

And so once again, we’re going to visit a metric I despise: monthly active members. Some community dashboards will give you daily actives. A few will break it down by post type, session length, time of day. You can slice your membership into cohorts and watch them drift in and out of your engagement funnel like tides.

What none of them will show you is the conversation, conversion, or behavioral shift that happened because of your community, somewhere else entirely.

Your member who lurked for six months before pulling a thread on customer onboarding and sharing it in her company’s internal Slack. The practitioner who cited a three-year-old discussion in a presentation to his leadership team. The person who never posted once but quietly absorbed enough that they stopped making a particular mistake. That value left your platform. It’s living somewhere you’ll never see. And it’s been happening since the first community went online. And it’s probably the best thing your community will ever do and keep on doing.

This is not new behavior. Communities have always been leaky by design, in the best possible way. We learn things and we take them with us. That’s the whole point. A community that produced knowledge people hoarded inside it would be a pretty useless community.

But alas… The problem isn’t that value escapes the platform. The problem is that we built dashboards that can only see inside it and expectations only aligned to what we can see.

Think about a library. A library doesn’t know that you recommended a book to your sister, or that you spent three hours with a resource and it changed how you approached a problem, or that the idea you found in the stacks eventually ended up in a report that influenced a decision at your organization. It knows you checked out the book. Maybe it knows how many people checked out that same book. The rest is invisible, which doesn’t make it any less real.

Community platforms work the same way. We instrument what happens inside the walls because that’s what we can count. Logins, posts, replies, reactions. Useful signals, all of them. But they’re not the whole picture, and for a long time we let the measurable crowd out the acknowledgment that something larger was happening beyond it.

We designed for re-entry when we should have been designing for portability.

That means asking different questions about what we build. Is your best content accessible to someone who hasn’t logged in recently, or is it locked behind a gate that requires fresh authentication? Are your templates, frameworks, and resources structured so members can actually take them somewhere? Is your community producing the kind of distilled, usable knowledge that travels well, or is it mostly in-the-moment conversation that loses context the moment it leaves? These aren’t arguments against a logged-in experience, but they are arguments for being intentional (and realistic) about what you’re making and where it’s going to end up.

But why is this feeling really uncomfortable right now? Why are you squirming reading this going ‘oh, I feel seen and I don’t like it’?

A lot of us are confronting this belatedly because our new AI overlords have made the invisible visible. Language models trained on forums, help communities, and practitioner discussions surfaced, at scale, the knowledge our communities had been producing for years. The value was indexed… outside our communities. It was findable… outside our communities. It turned out our members’ collective intelligence was genuinely useful and widely usable… outside our communities.

However, we didn’t measure that. We didn’t build for it. We were watching active member percentages while something else entirely was happening with the content we’d spent years cultivating.

There’s something both validating and humbling about that moment. Validating because it confirmed what community builders have always believed: this work produces real, lasting value that’s so good that WE are the ones feeding AI the valuable stuff. Humbling because the entity that made that legible wasn’t our analytics platform. It was someone else’s model.

So here we are. The behavior was always there. The knowledge was always escaping the walls and making its way into the work. We just finally have a mirror big enough to see it.

A little too late, but better late than never.

So am I alone in this? Or is this a thing?

The reality is that just one bad review can outweigh five good ones. Not because people are irrational, but because recency and specificity do something to our brains that aggregate ratings can’t undo. A glowing 4.8 with 200 reviews means nothing if the most recent entry says “got food poisoning, still not over it.” You close the app. You pick somewhere else. (Reminds me to go leave a review on the place that gave me food poisoning last weekend…)

I think about that a lot when I’m looking at community spaces.

We spend a lot of time in this profession talking about what our best interactions look like: the member who got a thoughtful response, the feedback thread that turned into a product feature, the support question that became a knowledge base article. We curate those wins. We screenshot them for our quarterly reviews. And none of that is wrong, exactly. But it might be obscuring the more important question which is: what did the worst interaction in your community teach every lurker who watched it?

Because someone is always watching.

The psychological cost of participating publicly in a community, whether to ask for help or critique a product, isn’t fixed. It fluctuates based on what people have already seen happen to others. Before anyone posts, they do a quick, mostly unconscious threat assessment. They scroll back. They read a few threads. They’re not looking for the average experience. They’re looking for evidence of the worst case.

This is why support and feedback feel like the same problem even though they’re not quite the same risk. When someone is considering posting a support request, the vulnerability on the line is competence. What if I’m the only one who doesn’t understand this? What if someone tells me to read the docs in a way that makes me feel stupid? When someone is considering posting product feedback, the vulnerability is credibility. What if I suggest something that’s already been rejected a hundred times? What if the response makes me look uninformed? Different fears, same mechanism. They’re both scanning for evidence of how this goes when it goes badly.

The floor of your community sets the ceiling for participation.

This is the thing we underinvest in. We optimize for making great interactions great, and we let the bad ones quietly do their damage. A cold, dismissive response to a frustrated user doesn’t just affect that user. It’s a public record. It sits there, searchable, permanent, training every future reader on what this space does with vulnerability.

So what do you do with that?

First: your worst public moments deserve the same strategic attention as your best ones. Most community teams have a plan for amplifying wins. Very few have a plan for actively rehabilitating bad threads. That doesn’t mean deleting them (almost never the right call). It means going back, adding context, following up, making sure the public record reflects that the community course-corrected. A thread that starts badly and ends well tells a better story than a thread that starts well and gets abandoned.

Second: if you’re designing for participation, you’re designing for the lurker. The person considering whether to post is your real audience. They outnumber active posters by a lot (honestly, by a lot… most community benchmarks suggest somewhere between 80 and 95 percent of community members never post at all). They’re not going to tell you what scared them off. They’re just going to stay quiet, or leave, or pursue a 1:1 avenue instead. So when you’re thinking about how to respond to a tricky feedback post or a frustrated support thread, think past the person in front of you. Think about who’s reading.

Third: response quality to difficult posts is a brand decision, not a support task. I know that framing makes some people uncomfortable, because it sounds like it’s adding pressure to already-pressured community managers. But consider the alternative framing: every response to a hard post is an opportunity to publicly demonstrate what this community is for. The member who posts “I’ve been asking for this feature for two years and nothing has happened” is handing you a moment. What you do with it is up to you.

The floor matters more than the ceiling. Your community’s best thread is a nice thing to have. Your community’s worst thread is what people make decisions based on.

Next time you’re reading back through your space, try to find the one that makes you wince a little (or a lot). The one where the response was curt, or the feedback got dismissed, or the frustrated member never got a real reply. It’s still there, doing its quiet work. That’s the one worth fixing first.

Right?

Not really. The problem is that by the time your content looks stale, the decay happened a long time ago. You’re working from a lagging record, not a live one. Knowledge decay isn’t just a content problem. It’s a participation problem that eventually shows up in your content. The content is just where it becomes visible.

Outside of all things nerd related these days, I’m working on trying to get the last few details figured out for a new home build. And of all freaking things - water tables and aquifers are very much on my mind.

So we’re gonna run with that analogy.

Think about an aquifer. The water table underneath a region can drop for months, sometimes years, before anyone notices the wells running low. On the surface, everything looks fine. The tap still works. You don’t know the recharge stopped until you’re already in trouble (arguably well into trouble). Community knowledge works the same way. The knowledge base can look intact, even active, while the conditions that keep it alive are quietly disappearing underneath.

And therefore… the leading indicators of knowledge decay aren’t in your content. They’re in your participation patterns.

The first thing to watch is expert withdrawal. Every community has people who actually know things, not just people who post a lot. When those people start going quiet, the knowledge base has lost its primary source of new deposits. The existing content doesn’t change overnight. But the system that generates and validates knowledge has already started shutting down. If your subject matter experts are still showing up in your metrics but only reacting, not responding, that’s worth noticing.

The second signal is question deflection. Pay attention to where hard questions go. When community members stop expecting good answers from the community itself and start saying “DM so-and-so directly” or “ask in the Slack channel,” that’s a participation pattern telling you something. The community is no longer the authoritative source. People still show up, but they route around it for anything that actually matters.

Third, watch where correct answers come from. This one takes some active monitoring, but it’s worth it. Are your best answers coming from community members drawing on lived experience and collective memory? Or are they increasingly citations to external docs, support tickets, and search results? A community that answers its own questions is a recharging aquifer. A community that outsources its answers is running on reserves.

The last one is the hardest to catch because it looks like humility. Watch for hedging in responses. When declarative answers (”here’s how you do this”) start giving way to qualified ones (”I think this used to work, but I’m not sure if it’s changed”), you’re watching knowledge confidence erode in real time. Nobody decided to stop knowing things. The community just stopped being the place where knowing things gets reinforced and updated.

What do you do with this? The honest answer is that recharging a depleted aquifer is much harder than maintaining one that’s healthy. But you can’t fix what you can’t see, and most community managers are watching the wrong layer. Start tracking expert participation rates separately from general participation. Map where complex questions get answered, not just whether they get answered. Notice when your answer quality shifts in register.

You don’t fill an aquifer by updating your FAQ. You fill it by creating the conditions that make expert participation worth sustained investment, and catching early enough when those conditions are starting to fail.

The tap still works. For now.

I’d like to yeet that into the sun.

It treated like a pulse check. If it’s going up, the community is healthy. If it’s going down, something is wrong and you need to fix it.

But hear me out: That number is going to go down no matter what you do, and that this is mostly fine.

Not “fine” in the way we say things are fine when they’re not. Fine in the way that radioactive decay is fine - predictable, measurable, and not actually a crisis once you understand the physics.

When someone joins a consumer community - a fandom, a hobby forum, a subreddit for people who love their air fryers - they’re there because the thing is inherently interesting to them. The participation is the point. There’s no asymptote. They’ll never effectively reach 100%.

But B2B communities (which is my bread and butter) work differently. Your members joined because they needed something: help getting started, answers to configuration questions, workarounds for edge cases, someone to tell them they’re not the only one confused by the onboarding flow. The community is instrumental. It’s a means to competence (which is 100%), not an end in itself.

The moment a member achieves competence, their relationship to the community fundamentally and wildly changes. They stop asking questions because they know the answers. They stop searching the knowledge base because they’ve internalized it. They can troubleshoot solo. They don’t need the community anymore, and in the absence of need, participation drops. Not because you failed them. Because you succeeded. Pat yourself on the back. Buy yourself a cake. YOU DID IT!

(Uh, great. What did I do? Do you have a fork for this cake?)

The half-life of a B2B community member is determined by the length of their learning curve, not the quality of your content calendar.

Every member enters at peak engagement potential - lots of questions, lots of unknowns, lots of reasons to show up. Over time, that potential converts into competence and their active participation drops. Some become lurkers. Most eventually go inactive. And in a growing community, new members are continuously entering at the top of their curve while older members slide toward the asymptote. The denominator keeps growing. The numerator can’t keep pace (unless your company is experiencing wild growth).

If you’re reporting % active members to leadership as a health metric, you’re setting yourself up to spend a lot of time explaining a phenomenon that isn’t a problem.

What’s more interesting to track is engagement density during the learning window. Are new members getting value while the community is most useful to them? Are questions getting answered? Is the knowledge base covering the actual gaps people hit? Is time-to-competence improving? That’s the community doing its job. Raw active percentage is the community aging.

Extending the half-life for members who’ve cleared the learning curve is possible, but it requires genuinely different work. Change logs that surface the right information to the right users. Feature feedback loops that give mature members a reason to show up; not to ask, but to influence. Early access programs. Beta cohorts. The value proposition has to shift from “get help” to “have a voice,” and that shift doesn’t happen through a monthly newsletter blast to your entire member base.

The community doesn’t fail when members graduate. It fails when members arrive and can’t find what they need, when questions go unanswered, when the same confusion cycles through every six months because no one captured the answer the first time.

So the next time someone asks why your active member percentage is declining: the community is working. Members are learning. The curve is doing what curves do.

Then maybe quietly suggest you all agree on a better metric.

You already know what was in it: posts per week, active members, monthly content volume, some variation of “how much stuff is happening in here.” Every single line was about quantity. Not one of them touched quality or consumption.

And y’all know how I feel about those metrics. (See The Metrics We Measure Because We Can)

I’ve been working to change that since the moment my eyeballs landed on it, because this is the thing I keep coming back to: volume tells you that activity happened. It tells you almost nothing about whether any of it mattered.

We’ve built a whole professional reflex around visible participation. Partly because visible participation is what our platforms surface easily. Partly because a graph that goes up is easier to explain than a nuanced story about member satisfaction. And in the earliest days of a community, volume genuinely can be a useful proxy for health. You need to know that anyone is showing up at all.

But communities don’t stay early-stage forever (in fact, early stage is a far shorter phase than you might think). Yet, our metrics often stay stuck in that early-stage phase… for a looooooong time.

Here’s what community maturity actually looks like: members stop asking beginner questions because they already know the answers. They get value from reading, not posting. They show up when something specific prompts them. Conversations get fewer but deeper. Response times slow down because the people responding actually think before they type. (Wild, eh?)

To a volume-first dashboard, this looks like decline. A failure. A proper catasrophe. To someone who understands community dynamics, it can look like exactly the opposite.

A healthy community can be a quiet community, and confusing the two is one of the most expensive mistakes we make.

Think about the neighborhoods you’ve actually wanted to live in. Not the ones where everyone is outside all the time, performing neighborliness, hosting block events every weekend. The ones where you know your neighbors well enough to borrow something without asking twice. Where the group chat is mostly quiet but lights up reliably when someone needs help. That’s not an inactive neighborhood. That’s a neighborhood with trust baked into the infrastructure.

Online communities work the same way. The noisiest ones aren’t always the most valuable. Sometimes they’re the most anxious, the most algorithmically gamed, the most dependent on manufactured prompts to keep the feed moving. What gets mistaken for vibrancy is sometimes just churn.

So what do you do with this practically?

Start with the diagnosis. Before you panic about a dip in posting volume, look at what kind of posting dropped. Fewer people asking for help might mean the knowledge base got better, or members are finding answers without posting at all (which is something I love). Fewer introductions might mean the community skews toward longer-tenured members rather than constant churn. Context changes the story completely, and volume gives you none of it.

Then there’s the leadership conversation. Volume metrics feel safe to report because they’re legible. But you can build the case for quieter indicators without abandoning the dashboard entirely. Member retention, time-to-first-value for new members, the ratio of questions that get answered versus questions that go dark: these tell a more honest story, and most of them can still be graphed. You’re not asking leadership to trust vibes. You’re asking them to trust a better set of numbers.

The harder shift is structural. A community program built around publishing cadences and weekly prompts designed to keep the feed alive is optimizing for volume in ways that actively work against depth. Every low-effort prompt posted to “spark engagement” is also training your members that this is what participation looks like here. That’s a ceiling you set, and it’s genuinely hard to raise later.

And then: get comfortable not knowing and living in the perpetual squishiness. Some of the value your community generates is invisible by design. Members who read a thread and make a better decision at work. Members who avoid a costly mistake because someone posted about it six months ago. Members who feel less alone in a hard job because they know this place exists, even on weeks they don’t log in. You will never fully measure that. Your job is to argue for its existence anyway.

The next time someone pulls up that volume chart looking worried, you don’t have to pretend the number is fine. You can say something more interesting: let’s talk about what the quiet is actually telling us.

That’s not a dodge. That’s the work.

It’s a content strategy we all know super well. So what’s the problem?

The problem is that everyone figured it out at roughly the same time. And now we’re all swimming in correct, (mostly) useful, thoroughly optimized content that says approximately the same things in approximately the same order. Your search results. Your LinkedIn feed. Your newsletter inbox. A sea of answers, and almost no one willing to have an original thought about them.

But you want to know what’s actually scarce? Perspective. Not information. Not even insight, really. Genuine, specific, shaped-by-someone’s-actual-experience point of view. The kind that makes you think “I’ve never heard it put that way” or, more usefully, “I completely disagree with that.”

Which is a problem, because perspective is also kind of terrifying to produce.

Think about the last time you had a hot take at work. Not in your head, not vented to a trusted colleague over Slack, but actually said out loud in a meeting or written down somewhere with your name on it. There’s a particular kind of vulnerability in that moment. You’re not just sharing information. You’re making a claim about how you see the world, and inviting other people to tell you you’re wrong. Most of us have learned, through one too many bruising experiences, to hedge. To qualify. To present “considerations” rather than conclusions.

When the cost of having a public opinion feels high, people stop having them publicly. And what’s left is a lot of very careful content that doesn’t actually say a darn thing.

This is where community comes in, and not in the soft, feel-good way people usually mean when they say “community is important.” I mean structurally. Mechanically. Communities lower the personal cost of having a take.

When you post a question or a half-formed opinion in a community of peers, something specific happens. You get responses. Some of them agree and extend your thinking. Some of them push back and sharpen it. Some of them are wrong in ways that make your original point clearer. The opinion doesn’t just sit there in the void, waiting to be judged. It enters into a conversation. It becomes a contribution rather than a declaration.

That changes the mathematics entirely. It’s the difference between standing up at a podium alone and saying something in a room full of people who are actually present also trying to figure it out. The social context doesn’t just make it more comfortable. It makes it more useful. Your perspective gets tested, refined, and returned to you in better shape than it left.

This is the thing communities offer that no amount of content can replicate. A blog post, a newsletter, an AI-generated summary: they can deliver information efficiently. What they can’t do is witness your specific perspective and respond to it. They can’t tell you where you’re right and where you’re missing something. They can’t turn your half-formed take into a real argument.

For community builders, this reframes the job in ways worth sitting with. If one of the core functions of your community is to give members a low-stakes place to think out loud, then the design question isn’t just “how do we drive more content?” It’s “how do we make it safe enough to say the uncomfortable thing?” That’s a very different problem. It requires different moderation norms, different conversation starters, different tolerance for disagreement. It means occasionally letting a spicy thread run instead of smoothing it over. (I know. That one’s hard. But gosh… I adore spicy threads.)

It also means the communities that will hold value as content gets cheaper to produce aren’t necessarily the ones with the most resources or the most members. They’re the ones where people are actually willing to say what they think. Where the culture has built enough trust that someone will post the thing they’d never put on LinkedIn. Where dissent is treated as a contribution rather than a disruption.

Infinite content raises the floor on information. It makes “here’s what the research says” essentially free. What it can’t touch is “here’s what I actually think about what the research says, and here’s where I think it’s wrong.”

That’s yours. And the communities where people feel safe enough to share it? Those are going to matter more, not less.

Go build the room where someone can say the uncomfortable thing.

The optimistic answer is that it would thrive (said with jazz hands and sparkles). That members would self-organize, hold each other accountable, and the community would demonstrate exactly the kind of organic health that makes leadership teams feel good about the budget line. The pessimistic answer is that it would devolve into chaos within a week (followed by an evil villain laugh). Both of these answers miss the actual answer.

It would still be moderated. Just not by anyone you appointed.

We talk a lot in this industry about “self-governing communities” as if that’s a thing that spontaneously happens when you get the right people in a room and step back gracefully. It doesn’t. Not really. What actually happens when formal moderation disappears is that informal moderation creeps and slithers in to fill the space. Someone sets the tone. Someone decides which questions are worth engaging and which ones get the cold shoulder. Someone’s interpretation of the rules becomes the interpretation, not because they were given that authority, but because they showed up consistently and had the time and inclination to assert it.

Power doesn’t leave when moderators do. It just stops being legible in the way you knew it.

When moderation goes underground, it doesn’t become democratic. It becomes a function of availability and appetite.

Think about what that actually looks like in practice. The member who’s online at 11pm every night and has Opinions about how things should go. The long-tenured member whose contributions are genuinely valuable, but who has also quietly accumulated enormous social influence over what’s acceptable and what isn’t based on their perspective. The person who doesn’t technically break any rules but whose presence shapes what other people feel comfortable saying. These folks exist in almost every community, moderated or not. The difference is whether you’ve thought about them.

Formal moderation structures, for all their messiness and overhead (and yes, there is a lot of both), do one thing that informal power cannot: they make accountability visible. You know who to go to when something goes wrong. You know whose job it is to make a call. You know, at least in theory, what the decision-making process looks like. Remove that structure and you don’t get a flat community. You get a community with a hidden org chart and a concept of guidelines.

This matters for how we think about distributed governance models, member-led spaces, and the general trend toward “lighter touch” community management. None of those things are bad ideas. But they require more intentional design, not less. If you’re going to distribute moderation authority across a member base, you have to think hard about who ends up holding it and why. You have to make the informal org chart legible. You have to build in ways for power to be contested, transferred, and held accountable, because if you don’t, you’re not creating a self-governing community. You’re just outsourcing the governance to whoever wants it most.

Which, to be clear, is sometimes fine. Organic community leaders emerge for good reasons. But “see, it worked out” is not a governance model.

The moderator-free thought experiment is useful precisely because it surfaces what we usually don’t want to look at: the informal power structures that already exist in our communities, right now, running alongside the formal ones. Who in your community is already doing de facto moderation without the title? Whose approval does a new member implicitly need before they feel like they belong? Whose disapproval quietly ends threads?

If you can’t answer those questions, you don’t actually have a picture of how your community governs itself. You have a picture of the part you built intentionally, which is probably not the whole picture.

So needless to say, the goal was never fewer moderators. It was accountability that doesn’t depend on any one person showing up. That’s a much harder design problem, and it doesn’t get easier by pretending the power isn’t there.

It’s just quieter.

It’ll turn into a disaster. What if people say mean things about us or to us? And: We don’t have the bandwidth to manage it.

Both fears are understandable. Both are also, in most cases, solving for the wrong problem.

Let’s start with hostility, because it tends to be the scarier one. This is the:

“Your product sucks and I’m going to let everyone know.”

“Do you people even think before releasing this junk? I’m demanding a refund.”

And so on.

There’s a persistent assumption in organizations that online communities are inherently volatile, that if you give people a space to talk, the worst voices will fill it. And yes, that happens. But it doesn’t happen randomly. It happens by design, even when nobody intended to design it that way.

Hostile communities are almost always communities where hostility works. Where the person who posts the most inflammatory take gets the most replies. Where complaining loudly is the fastest path to getting your problem solved. Where drama generates visibility and visibility generates status. If your community rewards bad behavior with the thing bad actors want most (attention, validation, answers, reputation), you will get more bad behavior. That’s not a community problem. That’s a feedback loop problem, and it starts with the environment you built.

And if this is sounding familiar already - you either have this in your community or you read When Your Community Turns Into a Stage.

So tl;dr… Hostility isn’t a community’s default state. It’s a community’s response to its incentive structure.

This is actually good news, because incentive structures are something you can design. It means thinking carefully about what behaviors your platform surfaces and amplifies. It means not rushing to answer the loudest complaint in the room while quieter, constructive voices go unacknowledged. It means having a communication plan for the moments you know are coming: the product changes, the pricing updates, the industry news that’s going to hit your members’ feeds before it hits your forum. Proactive communication doesn’t eliminate negative sentiment, but it takes away the conditions in which panic and speculation become the loudest voices in the room.

The second fear, the resource question, is where it gets interesting.

Leaders imagine moderation as a full-time job requiring a dedicated team, a ticketing system, and probably a therapist on retainer. (Fair, honestly.) And for some communities… at some moments… that’s true.

But here’s what tends to happen in communities with generally healthy cultures and satisfied members: the members don’t want the ruckus either.

This is the neighborhood watch model, and it’s more common than we talk about. In communities where people have co-built something they value, they show up to protect it. Not because a community manager asked them to. Not because they have a “trusted member” badge. Because they live there, and they care what it feels like. They reply to the off-tone newcomer before the mod team even sees the post. They downvote the bad-faith question into obscurity. They tell someone directly, and often more effectively than any official warning, that this isn’t how things work here.

And honestly: this is such a fun thing to watch (both because it’s behavioral modeling in action… and also watching users say what you can’t say).

But alas, I want to be careful here: I’m not arguing for turning moderation entirely over to the community. That’s a different kind of chaos. Moderation accountability has to live somewhere official, with people who have both the authority and the responsibility to make hard calls or call in backup (security, legal, etc.). But in a healthy community, that team isn’t carrying the weight alone. They’re supported by members who have internalized the culture deeply enough to act as an informal first line of response.

The organizations that figure this out spend less time playing defense. They also tend to have communities that are more durable, because the culture isn’t dependent on any single moderator or policy update. It’s distributed.

Here’s the thing the two fears have in common: both are solved by the same underlying work. Building a community where members are satisfied, where good behavior gets rewarded and bad behavior doesn’t find footing, where the culture is legible enough that people understand what they’re protecting. You don’t get the self-sustaining neighborhood watch without first building a neighborhood worth watching.

That’s the part that requires real investment: not an army of moderators… not a panic response every time someone posts something spicy. It’s the upfront work of being intentional about culture, incentives, and communication.

So next time a leader in your organization raises the hostility fear or the resource fear, here’s your reframe: those aren’t arguments against building a community. They’re arguments for building one carefully. The neighborhood takes care of itself, once you’ve built something the neighbors actually want to protect.

They mean it kindly. They are beaming at you. And somewhere behind your professional smile, a small part of you is screaming. For multiple reasons.

One because we’re terrible at taking compliments.

Two… because you know what runs itself: a rock. A parking lot. A PDF. Communities do not run themselves. They run because someone is running them, and that someone has spent years getting good enough at the job that it no longer looks like a job. Congratulations. You have achieved professional invisibility.

This is not a metrics problem, exactly. We’ve been told for years that the solution is better measurement: track response times, post volume, engagement rates, NPS scores. And look, metrics matter. But dashboards haven’t solved the core issue, because the core issue was never about data. It’s alwways been translation.

The invisibility of community labor isn’t a measurement problem. It’s a legibility problem. The solution isn’t more dashboards; it’s learning to speak your organization’s language instead of asking your organization to learn yours.

Think about the building superintendent. In a well-run building, you never think about the super. The heat works. The pipes don’t rattle. The lobby is clean. The super is invisible by design, because the super is doing their job. But the moment the boiler breaks, suddenly everyone knows exactly who they are and what they do and why it matters.

Community managers are the super. Except we don’t usually have to deal with heating, cooling, or rattling pipes literally and unless things really go sideways leadership doesn’t always fully register that someone is down there running it. The better you perform, the more you disappear. It is a genuinely perverse incentive structure and I think about it more than is probably healthy.

So what do you do with that?

First, stop documenting only what happened and start additionally documenting what didn’t. A post count tells your leadership how many conversations occurred. It says nothing about the conflict that got quietly defused before it became a thread, the new member who almost churned after an awkward first post but didn’t, the question that got answered in four minutes instead of four days. Near-misses are data. Start treating them that way.

Second: stop asking leadership to learn community vocabulary. They won’t. Not because they’re incapable, but because they already have a vocabulary that works fine for them. If your organization is obsessed with churn, your community work is a retention play. If they care about pipeline, your users are warm leads. If they track support ticket deflection, your peer-to-peer answer threads are saving someone real money. The translation is your job. I know that’s annoying. But alas… it’s also true.

Third, make your labor visible before you need it to be. The worst time to explain what community management actually involves is during a budget review or, worse, a reduction in force. By then you’re playing defense. The case for your work - and YOU - should be ambient, woven into regular reporting, mentioned casually in team meetings, present in the room before anyone thinks to question whether you should be.

Here’s the part that’s hardest to say: a lot of us were trained, explicitly or culturally, to make hard work look effortless. To handle the crisis gracefully, clean up quietly, and never let them see you sweat. That norm made us better at the job and worse at keeping it. The community that “runs itself” is also the community that leadership looks at and thinks, hm, do we really need a full-time person or team for this?

The answer is yes. Obviously yes. But invisible labor doesn’t argue for itself. Don’t hide in the boiler room. Go introduce yourself. Tell someone what’s down there.

Well, as most of us know by now we (or I) didn’t do anything. It was just our AI overlords moving in… noisily, clumsily, and without much warning. Not much we could do about that, and so we moved on with life and they moved on with their hallucinations.

But then… then we starting noticing the problems.

Us humans love quick dopamine hits and nothing hits quite like smugly thinking you’ve solved your problem super fast with a few key words and smashing the enter key. And man did Google’s AI Overviews seem to deliver initially.

In reality, LLMs are kind of just glorified search engines except they’re dialed in to sort of make educated guesses on what words likely surround the word in question. We talked about this in Your Community Isn’t Messy. It’s Training Data.

And all of that is well and good as the internet has many words to consume and frankly us humans could use a hand there. However, my team and I starting noticing that Google’s AI Overviews were surfacing subtly wrong answers about our product. And lucky for us, we didn’t panic. We got curious.

The pattern was interesting: a customer would search something reasonable - like whether they could book multiple appointments in a single session - and the AI Overview at the top of the results page would respond with a confident, slightly off answer. Not a hallucination exactly. More like the model had found a thread with 21 replies, half of them contradicting each other, and landed on the most cautious interpretation it could find. I mean… AI… same. I get it.

That gave us a hypothesis: If community content is what these models are pulling from, but community content is inherently conversational and messy, then the fix isn’t to produce less community content. It’s to give the models something better to work with as a sort of hub model.

So we ran an experiment.

The Setup

We audited our highest-traffic content (top-viewed threads, most common queries, biggest search drivers, highest impressions) and looked at what Google was actually surfacing and what AI Overviews were doing with it. The failure mode turned out to be pretty consistent. Someone posts “can’t do this yet, but it will soon”. A human reads that and understands timing, context, and subtle nuance. A model reads it and files it under “can’t do this” because it craves binary inputs and outputs. Multiply that across hundreds of pieces of user-generated content (UGC) and you’ve accidentally given Google’s AI a reason to be confidently wrong about your product.

LLMs aren’t great with grey area. When content is ambiguous, model confidence drops. When confidence drops, answers get worse. We wanted to see if we could fix that upstream.

We chose to focus on Google Search and AI Overviews specifically because the data is accessible (hello, Google Search Console), the surface is one we knew our users were actually hitting, and it was feasible to test and measure in a reasonable timeframe. It doesn’t capture everything - other search engines, direct LLM queries in tools like Claude, ChatGPT, or Gemini are a different problem - but it was a smart, practical place to start. And honestly, it’s probably a smart place for other community teams to start too.

The Build

We did something a little meta: we asked AI what kind of content it actually wanted to consume. Clear titles. Direct answers. Step-by-step formats. Headers. FAQs. Links to authoritative sources. Then we built a template around exactly that and created an AI agent workflow to do the heavy lifting. It would read the original UGC thread (from URL), cross-reference our help center, apply the template, and output a clean document ready for human-in-the-loop review before publication.

The result is what we’re calling “Asked + Answered” articles: structured Q&A with clear solutions and resolution summaries, purpose-built to become the preferred ingestion target for AI Overviews and public models. We published them into a dedicated, low-profile forum inside our community; not actively promoted, but indexable, findable, and fully controlled by us. And most importantly: still human friendly.

And the original user generated content (UGC)? The original UGC stays and serves in a few ways. It still powers discovery. Customers find us through those threads constantly. But now when Google goes looking for what we can and can’t do, it has a better source to pull from. And, it augments the AI optimized answer, which builds confidence and additional context.

UGC as discovery engine. Optimized content as ingestion target. Both doing their jobs.

What We Found

The hypothesis held… and then some.

More than 50 optimized articles are now fully ingested by public AI systems. Google impressions for community grew roughly 37% from before the initiative to after, and about 90% year-over-year, well above our historical average. We hit the largest month ever for page views, unique visitors, and impressions in the history of the community… while new topic creation actually declined. We theorize the growth is coming from better discovery and utilization of existing content, not just more volume.

The traffic pattern tells a clear story: UGC continues to drive topic discovery. Optimized content improves ingestion and answer accuracy in the AI Overviews that prospects and customers are landing on every day.

The Bigger Opportunity

AI models and search algorithms generally tend to rank community pages above static help center content. That means community teams are sitting on a strategic asset that most organizations aren’t fully leveraging yet. The opportunity isn’t just “write better content.” It’s “write content that makes models confident enough to repeat it correctly while continuing to serve your human audience” - and then verify that they actually do… both.

If you’re thinking about what this looks like for your own community: start with Google. The data is there, the surface is familiar, and the wins are measurable. It starts with an audit, a template, and a willingness to publish content that’s more structured than your usual style. The Asked + Answered articles don’t read like traditional community. They read like reference or help docs. That’s the point.

But the payoff is that when someone searches a question about your product, they get an answer you’d actually stand behind. Your community becomes the authoritative source, not the ambiguous one. And that makes you - the steward of both humans and AI knowledge - pretty darn valuable.

That’s a pretty good place to land.

PS: Big thanks to my colleague David Hartman who ran with this pilot, operationalized it, and continues to ensure Calendly Community is at the right place at the right time with the right answer every single day. He’s becoming quite the AI pro. Watch out world!

It’s not moderation. It’s not event planning. It’s not advocacy stuff. It’s the person who goes first. The one who posts before anyone else has a chance to, who asks the question everyone’s thinking but nobody wants to be caught asking, who walks onto the empty dance floor and starts jamming while the rest of the room pretends to check their phone.

In community work, I call this “being first weirdo”. And it is quietly one of the most important things we do.

Let me allow these shirtless dudes below to demonstrate (things I didn’t think I’d write, but alas).

Watch what happens in that clip (not my video; cannot find original for credit either). One guy, shirtless, in a largely empty stadium section, decides to have fun with it. He waves his shirt. He commits. And then, slowly and then all at once, other dudes join. Not because anyone told them to. Not because it was safe. Because some dude made it safe by going first and surviving. And, actually having fun with it which seems like a great outcome.

And yeah, that’s the job. That’s what I do.

THE END. (kidding, please keep reading)

But here’s the dealio: The first weirdo isn’t performing bravery. They’re performing permission.

When you post the first reply in a brand new forum, you’re not just adding content. You’re telling everyone watching that it’s okay to exist here, that participation won’t be met with silence or worse. You’re saying that the room is inhabited by someone who seems normal enough - or ahem… even stranger than them! You’re absorbing the social risk of going first so everyone else’s activation energy drops just enough for them to follow.

This is a structural intervention dressed up as a personality quirk. The industry tends to celebrate it as a character trait, something about being “willing to be vulnerable” or “authentically engaging” but that framing obscures what’s actually happening. Someone has to go first. You’re deciding it’s going to be you. That’s not a vibe. That’s a deliberate act with real stakes.

And sometimes… you misread the room entirely.

Sometimes you wave your shirt and the section stays empty. You’ve posted into the void, modeled a behavior nobody wanted to replicate, started a thread that got two replies including your own and your moms (hi mom! why haven’t you been liking my substack posts!?!). You’ve danced alone to music nobody else heard. This is also part of the job, and the community management industry is hilariously bad at talking about it, because it doesn’t make for a great case study.

However - good news: misreading the room is data. When nobody joins, you’ve learned something real about what this particular group of people won’t do in public yet, or maybe ever. That’s not nothing. It’s just emotionally expensive nothing. (I’m still working on reframing that one in the moment, for what it’s worth. I am an introvert who needs significant wine in her system to be the first on the literal dance floor.)

The wry truth is that going first means occasionally (read: often) going alone. You budget for it. You shake it off. You go first again next time and the next time and the time after that, because that’s what the role requires.

What the stadium clip captures, though, is the other outcome. The one that reminds you why you keep doing this even when you spent some time creating multiple profiles on your community just to not look like a lunatic talking to yourself. It’s not just that the section fills up. It’s the speed of it. It’s watching the logic of “this looks fun” spread faster than any announcement or nudge or carefully crafted call-to-action ever could. It’s the moment when the thing you started stops being yours and becomes theirs.

That transfer of ownership is the whole point. You go first not to lead forever but to make leading unnecessary. A community that still needs you to be the first weirdo two years in isn’t a community that’s grown, it’s a community that’s waiting. The goal is to go first often enough, and model it openly enough, that other people start to see themselves as someone who could do it too.

And eventually, someone does. They post first. They beat you to the dance floor. They ask the weird question. They walk onto the empty floor and they freaking own it.

And maybe it’s weirdos recognizing other weirds, but you’ll recognize them immediately. They’re doing the thing you taught them without knowing you taught them. They didn’t need a workshop or a framework. They just needed to see someone survive going first.

So here’s the challenge: find your empty section. It doesn’t have to be dramatic (you can keep your literal shirt on). It doesn’t have to work. Post the thing you’ve been waiting for someone else to post. Start the thread. Ask the question. Wave the metaphorical shirt.

Someone’s watching. They just need to see you survive it first.

But do you? Like community manager to community manager… do you?

We’ve been measuring community engagement the same way since the forum era, and honestly, most of it made sense then… when the platform was the community, when showing up to post was the whole point, when activity volume was a reasonable proxy for value. That world still exists in some corners. But for a lot of us, the community has quietly grown into something more complex than a post count can hold. We chatted about this earlier in From Destination to Infrastructure.

So here’s the uncomfortable question: What if I forced you to strip out every default metric your platform hands you - the ones you didn’t choose, you just inherited, or some leader insisted that’s how it was done - and had to build your measurement framework from scratch? What would you actually want to know?

The most honest answer to that question is also the most useful thing you can do for your community strategy.

Historically, what we’ve reached for is traffic, membership, and engagement. How many people showed up, how many joined, how many did something while they were there. These made sense as a starting framework. They’re super visible, they’re easily trackable, and in the early days of community-building they gave you a reasonable read on momentum. A growing member count meant you were doing something right. A spike in posts meant the conversation was alive. Direct traffic told you people were coming back on purpose, not just stumbling in from a search.

The problem isn’t that these metrics are wrong. It’s that they’re incomplete in ways we’ve mostly agreed not to talk about. Membership counts don’t tell you if the right people joined or if they ever found what they came for. Engagement volume doesn’t distinguish between a genuinely helpful conversation and a three-page thread that went nowhere useful. And direct traffic… well, direct traffic just means someone knew your URL. It doesn’t mean anything worked. In fact in the day and age of AI, it might signal that the right information isn’t being ingested.

So what would actually work?

Chances are you didn’t come here to read empty musings. At least I think not. You came here for some real world nerd perspective.

And while I don’t have all the answers, nor can I claim to have absolutely perfected an even near answer - I’ve been working on an approach I call ACE: Audience, Consumption, Engagement. It may be a bit biased towards the support communities I tend to run, but it has elements applicable to all communities.

Audience isn’t about how many members you have. (I retroactively apologize for the ferocious eye rolls I’ve given that metric when asked and the violent eye rolls I’ll continue to give it.) It’s about whether the people who need your collective knowledge can actually find it. Discovery is the metric. Can someone land on your community from a search - internal or external - and reach something useful without already knowing exactly what to look for? If your answer is “our content is all in there somewhere,” that’s not a measurement strategy. That’s a hope, a prayer, a concept of a plan.

Consumption is where things get interesting - or at least I think things get interesting (says the nerd delighted by CSV files). Did the knowledge seeker find it, and did it actually land? Did it change what they did next? The behavioral signal matters more than the view count. Someone reading a solution and then immediately raising a support ticket anyway or not following through on the intended product action is not a consumption success. And that’s a gap you need to know about. The goal shouldn’t be traffic to your content; it’s your content doing the job it was created to do.

And engagement… man, this one requires the most honesty. It should be a measure of necessity, not volume. In a well-functioning support community, engagement is what happens when the existing knowledge base doesn’t cover it. If you’re seeing high engagement, that’s not automatically a health signal. It might mean you have redundant flows, a lack of necessary knowledge, or friction that’s pushing people into creating new threads when the answer already exists three pages back. Engagement when necessary is a feature. Engagement as a substitute for findability is a bug.

None of this means you should torch your existing dashboards tomorrow. Traffic, membership, and engagement volume still tell you something useful for operational health checks. They’re just not the whole story, and we’ve spent a decade letting them stand in for one. The gap between what you’re currently measuring and what you actually care about is where your strategy is quietly leaking brain juice.

You probably won’t rebuild your entire measurement framework this quarter (unless you’re a bonafide data nerd or have one kicking around). But you could start with one honest audit: review each metric on your current dashboard and ask what decision it actually informs. If you can’t answer that cleanly, you already know what to do.

Go find out if your community is doing its job… not just whether people showed up.

The business promise was simple: if we show people exactly what they care about, they’ll feel more at home and therefore happier (read: more spendy, more loyal, etc.) customer.

And honestly? It works. Up to a point.

If you were to ask me what a community is, I’d say something like “It’s a group of individuals with shared values, behaviors, and artifacts.” Cool cool. (Also thanks to The Community Roundtable for drilling that definition into my head.)

But here’s the problem: personalization is also the fastest way to accidentally build a community where nobody shares the same experience. And where the thing that was supposed to make people feel seen quietly makes it impossible for them to find each other.

There’s a useful distinction hiding inside the word “belonging.” Belonging-as-recognition is the feeling that I am seen, known, welcomed. Belonging-as-connection is the feeling that we are in this together. Both matter. But they pull in different directions the moment a personalization algorithm gets involved.

When we personalize for recognition - think tailored onboarding, relevant topic suggestions, the right content at the right time - we’re often doing our best work. New members especially need to find their footing fast, and a well-timed “based on your interests, you might like this thread” can be the thing that converts a lurker into a contributor. That kind of personalization is generous. It reduces the tax of figuring out where you belong.

But personalization-as-connection is trickier, and most platforms haven’t cracked it in a scalable sustainable way. Because connection requires shared reference points. It requires the experience of the same thing happening to all of us at once.

Maybe it’s a spicy and rather aggressive take, but here is what I think: Personalization optimized purely for individual relevance will corrode the commons over time.

Think about what it felt like when your community had a moment. Maybe it was a thread everyone was reading, a debate that split the room, an announcement that landed differently depending on who you were. Those moments aren’t just engagement metrics. They’re the connective tissue. They’re what people refer back to six months later. They’re how inside jokes get born. Remove them, or fragment them by routing different content to different members, and you end up with a lot of people who feel personally served but have nothing to talk about together.

So where does that leave us, practically?

First: protect your shared spaces. Whatever your version of the town square is whether it be the main feed, the weekly digest, the all-community thread, be deliberate about what you do and don’t personalize there. If everything is filtered, there’s no shared ground. Even if some content feels less relevant to some members, relevance isn’t the only value. Shared experience is a value too, but it rarely shows up in your analytics.

Second: personalize the path in, not the experience of being there. Onboarding, topic discovery and first-week nudges are great candidates for personalization. The goal is to get people oriented so they can participate in the commons, not to build them a private commons of their own. The difference matters.

Third: watch for the fragmentation signal. It shows up when members start struggling to reference shared events. You’ll know it’s happening when someone says “wait, that was posted? I never saw that.” It shows up when subgroups stop being able to talk to each other because they’ve been optimized into parallel universes. It’s subtle at first. By the time it’s obvious, you’ve got a cohesion problem that’s hard to reverse.

Fourth: think about what your community needs to remember together. Memory is underrated as a community mechanic. Shared history - the thing that happened, the conversation that changed something, the moment the community showed up for itself - is what turns a platform into a place. Personalization can help individuals find their people, but it can’t manufacture collective memory. That has to be built in the open, where everyone can see it.

None of this means personalization is the enemy. It’s one of the best tools we have for reducing the friction that keeps people from ever finding their footing in the first place. I’d rather have a thoughtful, context-aware onboarding flow than throw a new member into the deep end and hope for the best.

And therefore, the question isn’t whether to personalize. It’s where and for what purpose.

Personalize to help people find the community. Don’t personalize the community itself out of existence.

Supposedly, at least. And if they do show up, they’ll do something (play baseball!?!). Ask questions, share wins, argue about the right way to onboard a new hire, post the occasional meme that somehow perfectly captures a Tuesday.

Participation is the whole darn point. It’s what separates a community from a mailing list. But what happens when participation becomes the input we automate rather than the output we cultivate?

Answer: We get communities that look busy and feel empty.

You’ve almost certainly seen it on LinkedIn. Maybe you’ve stopped posting there because of it (I flirt with the idea weekly). Our feeds have a particular slimy texture now - a dude in a tech bro uniform sharing a “hot take” that is aggressively tepid, followed by seventeen replies that all say some version of “this is so important, thanks for sharing.” Nobody is actually talking to each other. They’re performing engagement at each other. The replies don’t reference the post in any meaningful way. The post doesn’t respond to the replies. It’s participation as theater, automated or half-automated, optimized for the appearance of a thriving network all for the sake of reach and influence.

Reddit has a different flavor of the same problem. There are entire subreddits now seeded with AI-generated “stories” - first-person confessionals, AITA posts, dramatic workplace sagas - written not because someone had an experience worth sharing, but because the content generates upvotes and therefore karma farming and therefore reach. The karma system, originally designed to surface quality, has become the thing being gamed. You end up with a front page full of structurally perfect content that nobody actually lived.

It almost makes me miss the good ol’ days of social media. (Of course one could argue the 2009-2010 Farmville craze on Facebook was also not actually lived, unless y’all are farmers and I didn’t know about it.)

So what is actually bothering us community minded folks so fiercely? Well, simply put: The failure mode isn’t fake content. It’s the erosion of legible signal.

What dies first isn’t authenticity in some abstract sense. It’s usefulness. When you can’t tell if the ten replies praising your question are written by people who’ve actually wrestled with the problem, you stop trusting the answers. When the top post in a community is there because it was optimized to be there rather than because it resonated, you lose the ability to read the room. The crowd stops telling you anything. Even worse is when YOU are throwing content into the ether… and don’t care about trust, usefulness, or reading the room.

And this matters for community practitioners because the behavior doesn’t stay on LinkedIn and Reddit. It migrates and normalizes like a bad highly contagious virus (this is a good example of when a behavior has RO > 1… and we don’t want it to).

But why? If we don’t want to see it ourselves, why the heck are we emulating it?

First, because the people who are members of your community are already living in these environments. They’re learning - unconsciously, habitually - that participation can be low-effort, performative, and consequence-free. They’re importing those norms. Your thoughtfully structured discussion forum starts getting replies that are the community equivalent of a thumbs-up emoji rendered as a paragraph.

Second, because automation tools are getting better and cheaper, and community platforms are not immune. AI writing assistants can help members “respond faster”. The gap between “a tool that helps me articulate my thought” and “a tool that posts on my behalf while I do something else” is smaller than we’d like to pretend. (I say this as someone who has absolutely let an AI tool smooth out a reply I was too tired to write well. I’m not outside this problem.)

Third - and this is the one I think about most - automated participation creates a specific kind of ghost town: one that still has lights on. Vanity metrics stay healthy. Post counts, reply counts, maybe even DAUs look fine. But the qualitative signal - you know, the sense of whether people are actually in it - quietly degrades. By the time the metrics catch up, the community has already hollowed out.

What does this mean for how you manage?

It means presence detection matters more than participation counting. Are people responding to each other, or just posting into the void? Threaded conversation depth, direct replies, members who appear in someone else’s post rather than only their own… these tell you more than total reply volume.

It means friction (in the right places) is protective. A small barrier to posting such as a format requirement, a prompt that asks for specificity, a norm that replies should reference what they’re replying to filters out the low-effort automated churn without suppressing genuine participation. Not all friction is bad friction.

And it means you should probably get more deliberate about modeling what good participation looks like. Not as a policy document. As behavior… yours, your team’s, your community champions’. Humans still imitate humans. For now, anyway.

LinkedIn and Reddit aren’t cautionary tales about them. They’re early readings on a trend that’s coming for every community that touches the internet, which is all of them.

The crowd hasn’t disappeared. But you’re going to need to get better at knowing when it’s actually there.

But there’s another kind of failure that’s a heck of a lot quieter, more expensive, and honestly more embarrassing: the community that was loved to death. Engineered and orchestrated within an inch of its life. So carefully constructed that the humans inside it never quite had room to breathe.

But we don’t talk about that one as much. Probably because it requires admitting that we - the architects, the builders, the strategists, the people who genuinely care - can also be the problem.

Think of it this way. Imagine a dinner party.

Under-design looks like: no host, no food, a group chat that just says “my place, 7ish.” Some people show up. Nobody’s sure where to sit. The conversation is either great or excruciating, and there’s no in-between. A few people have a transformative night (mostly because they found the host’s dog and have had some quality canine time); most quietly slip out before 9 (with the excuse of needing to feed their dog).

Over-design looks like: assigned seating, a printed agenda, a Slack channel for pre-dinner conversation organized by topic, and a facilitated icebreaker where everyone shares one professional win and one personal growth area. The food is excellent. By 8pm, everyone is behaving beautifully… but feeling vaguely suffocated and as if their dinner jacket is a straight jacket.

The failure mode isn’t too much or too little effort. It’s effort applied without understanding what the community actually needs to feel alive.

In the end, both parties fail spectacularly… just differently. The under-designed one can’t retain anyone. The over-designed one can’t keep anyone real.

So what does this mean in practice, for those of us who spend our days thinking about this stuff?

The under-designed community fails at the threshold. People arrive and can’t find a foothold. No clear reason to post, no sense of who else is here or why, no signal that their participation matters. The intervention needed is structural: better onboarding, clearer purpose, a visible core of active members who model what “being here” looks like. This is the kind of failure community folks are trained to fix, which is why it gets most of the airtime. In fact, it’s so talked about that this paragraph is literally all I’m going to say about it.

But the over-designed community?

The over-designed community fails further in, and that delay is what makes it dangerous. Engagement metrics often look fine (if not fantastic) for a while. Members are completing the onboarding flow. They’re posting in the right channels. They’re responding to the prompts. And then, gradually, a kind of managed listlessness sets in. The community becomes a place where people perform participation rather than actually participate. You’ll notice it when the posts start to feel like press releases. When no one says anything surprising. When you realize you haven’t seen a genuine argument or original thought in months. (A community with no constructive dissent is not a thriving community.)

This is where you have to resist the instinct to add more structure as the fix. More programming, more content calendars, more themed weeks. If over-design is the disease, more design is not the cure. It would actually be a death sentence.

The harder question (and admittedly I’m still working on perfecting this one myself) is how to create enough structure that people can find each other and orient themselves, while leaving enough genuine openness that something unexpected can happen. That unexpected thing is the whole point. It’s what makes a community different from a newsletter or a course or a very organized Slack workspace.

There’s also a power dynamic worth naming here. Over-designed communities often reflect the anxieties of their builders more than the needs of their members. We fill the space because we’re afraid of what the silence means. We add a feature because we want to demonstrate value to our stakeholders. We launch another initiative because last quarter’s numbers were flat. The community becomes a canvas for our own professional discomfort, dressed up as member benefit.

And I know that’s not a comfortable thing to sit with. But it’s worth sitting with.

The practical upshot is this: when a community is struggling, the first diagnosis should not be “we need more.” It should be a genuine inquiry into which kind of failure you’re looking at. Is the space too sparse to be habitable? Or is it so curated that real humans have stopped showing up, even if their login activity says otherwise?

You can usually tell by asking one question: When’s the last time something happened here that surprised you?

If the answer is “never… things are very predictable,” you’ve got one problem. If the answer is “I have no idea, I don’t think anyone’s in there,” you’ve got a different one.

Both are solvable. But not with the same solution.

So, go leave some space in your community this week. See what fills it.