adilallo
8.9 KiB
title, description, author, date, related, thumbnail, background
| title | description | author | date | related | thumbnail | background | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Knowledge Management and Institutional Amnesia | Preserving what we learn without surveillance infrastructure | Author name | 2025-08-20 |
|
|
|
Someone leaves the group and takes three years of operational knowledge with them. Not because they're selfish, but because that knowledge lived in their head and in message threads that have already disappeared. The new person trying to figure out how intake works has to reconstruct the process from fragments and half-remembered explanations. Six months later, someone else leaves and the cycle repeats.
This is the tax encrypted organizing pays. Signal, Matrix, and similar tools protect vulnerable people from surveillance. The ephemerality is the point. But groups need institutional memory to function. You can't rediscover how to verify requests or coordinate emergency response every time your membership turns over. The energy cost is unsustainable.
This isn't a personal failure. It's what happens when the tools we use for privacy conflict with the requirements of institutional memory. The question isn't whether to use encrypted messaging, it's how to preserve knowledge without compromising security.
Signal's disappearing messages and lack of cloud storage are features, not bugs. They protect people. But cooperatives and organizing groups need to document procedures: how intake works, how resources get distributed, how conflicts get resolved, what to do in emergencies. The solution isn't abandoning encrypted tools. It's building complementary systems that respect both privacy and sustainability.
The most effective approach separates operational communication from institutional documentation. Signal, Matrix, or whatever encrypted tool you use stays as the primary channel for real-time coordination, personal information, and sensitive discussions. Meanwhile, procedural knowledge that doesn't contain identifying information lives somewhere more permanent.
For documentation, use password-protected wikis, encrypted cloud documents like those provided by Nextcloud cooperatives, or collaborative platforms like CryptPad that prioritize privacy. The commercial option is Notion, though it's surveillance infrastructure pretending to be helpful. Better to support cooperative alternatives when possible.
Essential documentation includes onboarding guides for new volunteers explaining roles and expectations. Step-by-step protocols for common tasks like intake, verification, and distribution. Decision-making processes and governance structures so people understand how choices actually get made. Contact trees and escalation procedures for when things go wrong. Templates for common messages or forms so people aren't reinventing basic communications. Retrospectives on what worked and what didn't during major operations.
This last one matters more than groups realize. After a big action or crisis response, you know what succeeded and what failed. Six months later, that knowledge has evaporated. Document it while it's fresh. Future members will thank you for not making them learn through the same painful trial and error.
Knowledge management requires ongoing attention, which means it needs to be someone's responsibility. Designate a rotating documentation coordinator. Not a permanent position, because that creates the same knowledge hoarding problem you're trying to solve. Rotate every few months. The coordinator's job is capturing new procedures as they emerge and making sure documentation stays current.
After significant operations or when processes change, hold brief documentation sessions. Thirty minutes where participants help update guides while details are still clear. This isn't bureaucracy, it's preventing the loss of hard-won understanding.
Worker cooperatives face similar challenges. Member composition changes over time. If operational knowledge lives only in people's heads or in vanished message threads, every transition becomes a crisis. Documenting procedures isn't about control, it's about continuity. It's ensuring that the person who developed the accounting workflow or the member intake process doesn't become a single point of failure.
The hardest part isn't technical, it's cultural. Groups that move fast and prioritize immediate needs often see documentation as bureaucracy. This is backwards. Documentation is care work. You're caring for future volunteers and the sustainability of your mission. When exhausted members can find clear procedures instead of piecing together information from scattered message threads, everyone benefits.
Frame it as preparation for growth, not paranoia about decline. If your group succeeds, you'll need to onboard new people efficiently. If your project gains users, you'll need documentation they can actually use. If your cooperative expands, new members need to understand how things work. The alternative is that your most knowledgeable people become bottlenecks, explaining the same things over and over until they burn out.
Consider what gets lost when documentation doesn't exist. The person who set up your verification process leaves. No one remembers exactly how it worked or why certain steps matter. You reinvent something inferior. The coop member who negotiated your supplier relationships retires. No one documented those connections or the reasoning behind vendor choices. You start from scratch. The developer who built a critical feature disappears. No one understands the architecture decisions. The technical debt accumulates.
This pattern repeats endlessly in groups that don't take knowledge management seriously. It's not dramatic, it's grinding. Constant small losses of understanding that accumulate into major dysfunction.
Tools matter here. CryptPad offers encrypted collaborative documents without corporate surveillance. Nextcloud can be run by cooperative hosting providers, keeping your data under collective control rather than corporate ownership. BookStack provides wiki functionality with granular permissions. Zulip offers persistent, threaded communication that's more searchable than Signal while still being open source.
The point isn't specific tools, it's the principle: use encrypted ephemeral channels for sensitive operational communication, use persistent documentation systems for procedural knowledge, and make sure those systems align with your values around surveillance and ownership.
Stop treating institutional memory as a luxury you'll get to when things calm down. Things won't calm down. The crisis is permanent under capitalism. Either you build systems that preserve knowledge despite constant turbulence, or you accept endless cycles of reinvention that exhaust everyone involved.
Documentation isn't about bureaucracy. It's about refusing to let hard-won knowledge disappear when it could help the next person trying to do the work. It's about building organizations that can outlast any individual member. It's about sustainability in the ruins.
The critical distinction: these repositories contain procedures, not personal data. Document the how of your work without including identifying information. How to verify requests, how to coordinate pickups, how to handle disputes. The process, not the people.
Build redundancy into your system. Multiple members should have access to documentation repositories. Critical information should exist in at least two forms. If the wiki goes down or someone loses the password, you need backup. Consider quarterly reviews where coordinators check that documentation remains current and accessible.
Not everything needs the same security level. Public-facing resources like volunteer signup information can live openly. Internal procedures might use password protection. Only information that could directly harm community members requires encryption. Create clear guidelines about what stays in encrypted channels versus what moves to documentation.
Case-specific details stay in Signal. Personal information stays in Signal. Real-time sensitive coordination stays in Signal. General procedures, lessons learned, organizational structures can move to documentation. The line is whether the information could identify or harm specific people. If yes, it stays ephemeral. If no, it gets preserved.
The open source model offers useful parallels here. Successful projects separate community discussion, which happens in ephemeral channels, from documentation, which lives in wikis and readme files. They have contribution guidelines, architecture decisions, and troubleshooting guides that persist. The knowledge exists independently of any individual contributor. When someone leaves, their specific conversations may disappear, but their contributions to understanding how the system works remain.