Information isn't just a part of the community. It IS the community.
We are living through a quiet redefinition of what it means to belong somewhere. The town square has moved. The water cooler conversation has migrated to Slack threads, Twitter spaces, and Discord servers that never sleep.
What I find fascinating is how much of this is shaped by design: the decisions we make about information architecture, notification patterns, and feed algorithms. These aren't neutral choices. They are choices about community.
The Infrastructure of Belonging
Every community tool makes assumptions about how people want to relate to each other. Twitter assumes you want to broadcast. Discord assumes you want to belong to multiple rooms at once. Substack assumes the relationship between writer and reader is closer to mentorship than conversation.
These assumptions shape behavior more than any community guideline ever could.
I've been thinking about this a lot while building Lena. A health app isn.t just a tool. It is a space where people come to feel less alone with something that scares them. The information architecture of that space either creates community or kills it.
What Gets Lost in Translation
The thing about digital communities is that they're extraordinarily good at scale and extraordinarily bad at depth. You can reach a thousand people instantly. Getting those thousand people to actually know each other is a different problem entirely.
The communities I've seen work (really work, in the way that changes how people think and act) share a common characteristic: they organize around a shared practice, not a shared identity.
Identity-based communities ask "who are you?" Practice-based communities ask "what are you doing?"
The first collapses into in-group signaling. The second collapses into a craft.
The Role of Information
Here's the thing I keep coming back to: information, in the context of community, isn't content. It's currency. It's the thing you trade when you want to build trust.
When someone shares something that matters to them (a struggle, a discovery, a question they.re embarrassed to ask elsewhere), they.re not distributing data. They're extending trust.
The design of the space around that act either honors the trust or betrays it.
Designing for the Trade
If information is currency, then the design job is closer to designing a market than designing a feed.
Markets need a few things to function. People have to be able to tell what something is worth. They have to believe the rules will not change under them. And there has to be some cost to bad behavior, or the whole thing floods with noise.
Most social products get the first one wrong immediately. They measure worth by reach, because reach is easy to count. So the thing that travels furthest becomes the thing that looks most valuable, regardless of whether it was true, careful, or costly to say. The currency inflates. Trust is what gets devalued.
The communities that hold their value do the opposite. They make the expensive contribution visible: the long answer, the correction, the admission that something did not work. Not because they moralize about it, but because their design surfaces it. Reputation accrues to the person who was useful, not the person who was loud.
That is an information architecture decision before it is a moderation policy.
Why This Keeps Mattering
I keep returning to this because the products I care about are all, quietly, community problems wearing other clothes.
A health app is a place where people bring a question they are afraid to say out loud. A learning platform is a place where people admit they do not know something. A professional network is a place where people risk being seen trying.
In every case the design either makes that risk feel survivable or it does not. And nobody reads the community guidelines. They read the interface.
The interface is the guideline.
FAQ
What makes an online community actually work?
Shared practice, not shared identity. Identity-based groups collapse into in-group signaling. Practice-based groups collapse into a craft, which is where the value was all along.
Can you design trust into a community product?
You can design for it or against it, but not neutrally. Trust accrues when the expensive contribution (the long answer, the correction, the admission that something did not work) is what the interface makes visible. Measuring worth by reach does the opposite.
Do community guidelines change behavior?
Far less than the interface does. Nobody reads the guidelines; everyone reads the layout, the notifications, and what gets rewarded. Information architecture is a moderation decision before any policy is written.
