How to Share Information in a Community: Living Maps
Every community that works runs on the same invisible asset: everyone roughly knows who knows what. The ones that fail built a wiki instead.
The most durable way to share information in a community is to map minds, not archive documents: maintain a living directory of who knows what, share through voice and story in the channels people already use, and write down only the few things that must outlive their holders. Communities remember collectively, by knowing whom to ask, and that web of overlapping personal knowledge graphs degrades gracefully where central archives go silent. Reserve writing for safety-critical facts, agreements, and anything that has to survive a generation change.
The most durable way to share information in a community is to map minds, not archive documents. A community is a set of overlapping personal knowledge graphs, each member a First Brain holding a different region of what the group collectively knows, and information flows when everyone can answer one question fast: who knows this? So the working method has three parts: keep a living who-knows-what directory, move daily knowledge through voice and story in the channels people already use, and reserve writing for the few things that must outlive their holders. Communities that start with a shared drive get a graveyard; communities that start with the map get answers.
Why do community wikis and shared drives go silent?
Because they store answers while members carry questions, and nothing connects the two. The pattern repeats everywhere from neighborhood associations to open-source projects: an enthusiastic setup week, forty documents, then silence, until the next newcomer asks in the group chat anyway. Knowledge-management research has named the missing layer for decades: the knowledge that matters most is tacit, carried in experienced heads as judgment and context, and it does not survive being flattened into a document nobody can find.
An archive also fails socially before it fails technically. Documents are written once, by whoever had energy that month, then drift out of date with no owner, and a community member who follows a stale instruction once stops trusting the whole archive. The group chat keeps winning not because people are lazy but because a question asked there reaches living minds whose knowledge is current by definition.
The archive is the backup, not the home. Getting that order right is most of the method.
What does a community knowledge graph actually look like?
People as nodes, who-knows-what as the edges. Maria holds the permits process, Kwame holds the supplier history, the retired electrician on the corner holds thirty years of why-the-power-fails. Psychologists call this transactive memory: groups remember collectively by encoding not the information itself but its location in other minds. A community with a sharp who-knows-what map can answer almost anything in two hops, and the knowledge stays where it is best maintained, in the head that uses it daily.
The practical artifact is almost embarrassingly simple: a maintained list, pinned wherever the community already talks, of fifteen to forty lines in the form “ask X about Y.” It is one screen of text, it costs minutes a month, and it outperforms most wikis because it routes questions to living graphs instead of dead pages. Overlap is the resilience feature: when two or three people share each region, the map survives anyone moving away, which is why mapping should favor redundancy over neat single ownership, the same decentralized pattern that makes the informal economies of the Global South so hard to break.
| Sharing model | Where it shines | Where it breaks down |
|---|---|---|
| Living who-knows-what directory | Daily questions, tacit knowledge, fast routing | Needs a steward; fades if never refreshed |
| Central archive (wiki, shared drive) | Documents that must outlive people; reference facts | Unowned pages rot; tacit knowledge never enters |
| Broadcast channel (newsletter, announcements) | One-to-many urgency, events, decisions | One-way; accumulates no searchable memory |
| Apprenticeship pairing | Deep skills, judgment, the unwritable craft | Slow, one-to-one, depends on patient seniors |
How does sharing work day to day, especially mobile-first?
Through the channels the community already opens fifty times a day, in formats that match how people actually talk. Across emerging economies the practical infrastructure is the messaging app: Pew’s research across eleven emerging economies found smartphones and social platforms woven into daily life even where laptops never arrived, which means the community’s knowledge system should live in a chat thread, not behind a login nobody remembers. A pinned directory message, topic threads, and voice notes cover most of what a knowledge base pretends to do, the architecture I unpacked in the WhatsApp exocortex.
Voice deserves particular respect. A sixty-second voice note carries tone, caveats, and emphasis that a typed summary strips out, and for communities with strong oral registers it is the native format of tacit knowledge, audio is how the informal economy already maps its nodes. Stories work the same way at longer range: a well-told account of the flood year, retold at gatherings, transmits judgment that no laminated emergency checklist achieves, because narrative is the one format every mind stores without effort.
One rhythm holds it together: a weekly question thread. One prompt, “what did someone ask you this week that others should hear?”, surfaces the knowledge that is actually in demand, and the answers update the map for free.
Who maintains the commons, and what stops freeloading?
Shared knowledge is a commons, and commons survive under known conditions. Elinor Ostrom won the Nobel in economic sciences for documenting how real communities govern shared resources without markets or central states: clear boundaries on who belongs, rules fitted to local conditions, monitoring by the members themselves, and graduated consequences for abuse. A knowledge commons needs the same small constitution: membership someone can name, a norm that answering this month earns asking next month, and a steward, rotating is fine, whose only job is keeping the directory current and the threads findable.
The communities-of-practice tradition adds the engagement half. Wenger-Trayner’s framework describes thriving knowledge communities as three interlocking pieces: a domain people genuinely care about, relationships dense enough that asking feels safe, and a shared practice that accumulates, vocabulary, shortcuts, war stories. Tools never substitute for any of the three. A half-empty spreadsheet inside a community that trusts itself beats polished software inside one that does not.
When does writing things down still matter?
When the knowledge must outlive its holders or carry legal and safety weight. Gas-line locations, medication protocols at the community clinic, the terms of the land agreement, the treasurer’s handover notes: these belong in writing, in two places, with a named owner and a yearly review, no exceptions for being boring. The test is simple: if the person who knows this left tomorrow and the knowledge died with them, would someone get hurt or cheated? Write those down; let conversation carry the rest.
This division of labor is also the honest limit of the minds-first method. A community that documents nothing is one funeral away from losing its constitution, and a community that tries to document everything exhausts its volunteers producing pages nobody reads. Strong communities run both layers in proportion, roughly: a living map for the daily ninety percent, durable documents for the critical ten. Members who want to deepen their own region of the shared graph are doing the individual half of the same project, the one Building Your First Brain (free for the first 1,000 readers) covers, and communities that skipped the wiki era entirely may be better positioned than the ones still maintaining graveyards, an advantage I explored in leapfrogging the Second Brain era.
Key takeaways: sharing information in a community
Map minds first: a pinned who-knows-what directory routes questions to living knowledge faster than any archive, and overlapping coverage makes the map survive departures. Move daily knowledge through voice, story, and the chat the community already uses; run one weekly question thread to keep the map honest. Govern it like a commons, clear membership, reciprocity norms, a rotating steward, and reserve writing for what must outlive people: safety facts, agreements, handovers. The balance is roughly ninety percent living conversation, ten percent durable documents, and getting that ratio backwards is how communities end up with silent wikis and overloaded elders.
Frequently asked questions
How do you share information in a community?
Start with a living map of who knows what, pinned in the channel the community already uses, and route questions to people rather than pages. Share daily knowledge through voice notes, stories, and topic threads; run a weekly question thread to surface what people actually need; and write down only safety-critical facts, agreements, and handover knowledge. Mapping the community’s overlapping First Brains beats building an archive, because answers stay where they are maintained: in living heads.
Why do community wikis usually fail?
Because they store answers without connecting them to questions. Pages are written once by whoever had energy, drift out of date with no owner, and lose trust the first time someone follows stale instructions. Meanwhile the group chat keeps winning: a question asked there reaches current, living knowledge. Wikis work only for the small core of stable, critical content that has a named owner and a review rhythm.
What is transactive memory?
The way groups remember collectively: instead of everyone storing everything, members encode who knows what, and retrieve by asking. A couple, a kitchen crew, or a village runs on it daily. Strengthening it is cheap, keep a visible directory of expertise, introduce members around what they know, maintain overlap so no region depends on one person, and it is usually worth more than any new tool.
How do you keep a few people from carrying the whole load?
Treat the knowledge commons the way Ostrom’s research says communities sustain any commons: clear membership, reciprocity as an explicit norm (answering earns asking), light monitoring, and a rotating steward role so maintenance is a duty that circulates rather than a personality trait. Public thanks matters more than it sounds; the fastest way to lose your most generous elder is to let their answering stay invisible.
When should a community rely on documents instead of people?
When losing the knowledge would cause harm or disputes: safety procedures, medical protocols, financial records, land and rental agreements, handover notes for every official role. Those need a written home in two places, a named owner, and a yearly review. Everything else, the daily how-to, the supplier gossip, the craft, travels better through conversation, voice, and retold stories, refreshed by use instead of by audits.
Dive deeper in
How to Synthesize Voice Notes Into Mental Models
How to synthesize voice notes: a daily 15-minute metabolize pass. Extract each note's one claim, wire it to what you know, delete the audio, repeat.
How to Work With Slow Internet (and Think Better)
Batch your connectivity, go offline-first, and let the constraint filter your inputs. A slow connection blocks hoarding and forces high-intent thinking.
How to Scale a Small Business With AI
AI does not scale hustle, it scales structure. Learn how to turn a small business into a system AI can run, the mobile-first way founders are doing it now.