Every economic development office, city department, and school district has the same vulnerability, and almost none of them budget for it: institutional memory that lives in people instead of systems.
The grant narrative that finally got funded — written by a coordinator who left two years ago. The history of why a zoning conversation stalled in 2023. The contact at the regional council who actually returns calls. When the person who knows these things retires, resigns, or simply goes on vacation, the organization gets measurably slower. Onboarding a replacement takes months not because the work is hard, but because the context is gone.
Most organizations try to solve this with shared drives. Shared drives are where documents go to be stored, not found. A folder tree tells you where a file lives; it tells you nothing about how that file connects to the project, the stakeholder, or the decision it belonged to.
What we use instead
At the City of Elsa’s EDC, and across our consulting work at Rivera Educational Consulting, we run organizational memory on a tool called Obsidian. It deserves a serious look from institutional buyers for reasons that have nothing to do with productivity trends.
Obsidian is a free application that manages a “vault” — a folder of plain-text files on your own machine or your own network drive. Three properties make it a fit for government and education environments specifically:
Your files stay yours. Everything is plain text in a folder you control. There is no proprietary database, no required cloud account, no vendor who can raise the price or sunset the product and strand a decade of records. If Obsidian disappeared tomorrow, every note would still open in any text editor. For records-conscious organizations, that is not a small point.
Notes link like the work actually connects. A meeting note links to the project it belongs to. The project links to the businesses, partners, and funding sources involved. Click any stakeholder and see every interaction, commitment, and open thread attached to them. Structure emerges from how the work relates — not from guessing which folder a document should have gone in.
It costs nothing to pilot. No procurement cycle, no license negotiation, no IT integration project. One staff member can start a vault this afternoon.
How this looks in practice
Our working vault is organized into a handful of top-level areas: active projects, goals by department, people and organizations, and an operations library of SOPs and templates. When we ran our Digital Facade Program — scoring the online presence of more than 180 businesses in Elsa — every business visit, follow-up, and fix list flowed into that structure. Any team member can pick up any thread without a briefing meeting, because the briefing is already written down and linked to everything it touches.
The habit that makes it work is simple: if it matters, it gets a note, and the note gets linked. Meetings, decisions, phone calls, why-we-did-it-this-way explanations. Ten minutes of capture per day builds an asset that compounds for years.
The AI dividend
Here is the part institutional leaders should not overlook. In our AI training work, the pattern is consistent: when an organization’s information is scattered, AI produces generic output. When the context is structured, AI becomes genuinely useful. It stops guessing and starts assisting.
We call this framework Brain, Train, Execute — and the Brain comes first. An Obsidian vault is exactly the structured context base that makes AI tools work on your organization’s real problems: drafting board memos that reflect your actual project history, answering “what did we commit to this partner?” in seconds, preparing a new hire’s orientation from notes that already exist. Organizations that skip this step and jump straight to AI tools are prompting into the void. Organizations that build the brain first get the multiplier.
Where to start
Do not attempt an organization-wide rollout. Pick one department or one program. Create a vault with four folders — Projects, People, Meetings, Procedures — and require that every meeting for the next thirty days produces one linked note. At the end of the month, ask a simple question: could a new hire reconstruct what happened this month from the vault alone?
If the answer is yes, you have started building something most organizations never have — a memory that outlasts any single employee. If you would like help designing that system, or training staff to maintain it, that is precisely the work we do.