On any given day, my job touches a CRM, an accounting base, a resourcing tool, three chat apps and a stack of automations stitched between them. Each one holds a piece of how the company works. None of them holds the why: why a field maps the way it does, why we made an exception for one client, why a process has that odd extra step.
That context usually lives in one place — the ops lead's head. That works until you're on vacation, you hire someone, or an investor asks how a number was calculated. Then it becomes the single biggest risk in the business.
So I started moving that context into Obsidian. Here's why I think every operations leader should consider doing the same.
What Obsidian actually is
Obsidian is a note-taking app built on plain Markdown files that live in a folder on your computer. That folder is called a vault.
The magic is in the links. Type [[Month-end close]] inside any note and it becomes a connection. Obsidian tracks every connection in both directions, so each page shows what it links to and what links back to it. Over time, your notes stop being a pile of documents and start behaving like a map of your company.
You don't need to write code to use it. If you can write a bullet list, you can run an ops vault.
Six reasons it works for ops leaders
1. It captures the "why" your systems can't
Your CRM knows a deal closed. Your accounting base knows an invoice went out. Neither knows that the deal type was split into two products last quarter, or that one client is billed on a custom schedule. In Obsidian, that context gets its own page, linked to every process and system it touches. When something looks wrong in a report, you have somewhere to check before you start guessing.
2. Links mirror how operations actually work
Operations is a web, not a folder tree. A single client connects to a contract, a billing rule, an automation, an owner and a Slack channel. Folders force you to pick one home for each note. Links let a note live everywhere it matters. The graph view even shows you which processes are tangled together — useful when you're about to change one of them.
3. SOPs and runbooks that people actually open
Most SOPs die in a shared drive. In a vault, a runbook sits one click from the system it describes, the person who owns it, and the last time it broke. Templates make new ones fast to write, and plain Markdown makes them easy to edit, so they stay current.
4. A decision log that saves you from relitigating
Ops leaders make dozens of small calls a week: which tool owns which field, when an exception is allowed, who approves what. Write each one down as a short dated note — the decision, the reason, who agreed. Six months later, when someone asks "why do we do it this way?", you send a link instead of rebuilding the argument from memory.
5. You own your data
Your vault is a folder of text files on your machine. No vendor lock-in, no per-seat pricing surprises, no export button that loses half your formatting. If Obsidian disappeared tomorrow, every note would still open in any text editor. For the person responsible for business continuity, that matters.
6. It's the best format for working with AI
This is the benefit I didn't expect. Plain Markdown files are exactly what AI assistants read and write best. I now have Claude maintain parts of my vault: it ingests meeting notes and Slack threads, updates the relevant pages, and flags contradictions. I browse and edit the result in Obsidian. The vault becomes a shared memory between me and my tools, instead of another inbox to process.
How I set up my ops vault
I keep the structure simple: four areas, each linked to the others.
- Systems — one page per tool (CRM, accounting base, automations), covering what it owns, key fields, and known quirks.
- Processes and SOPs — how work moves between systems, step by step, with an owner on each.
- Decision log — short dated notes on every call that shapes how we operate.
- Clients and people — who owns what, plus client-specific exceptions.
My first focus was the flow from sales to accounting — deals created in the CRM that need to land correctly in our finance base. It's the process where one wrong field causes the most downstream pain, so it was the one most worth documenting. Once that section existed, reconciling a mismatch went from "ask around" to "open the page."
New context arrives from Slack threads, meeting notes, our internal knowledge base and a simple inbox folder where I drop anything worth keeping. An AI assistant folds it into the right pages; I review and edit in Obsidian.
Where Obsidian isn't the answer
Obsidian is a thinking and documentation tool, not a system of record. A few honest limits:
- It's not a database. Deal values, invoices and allocations belong in your CRM and finance tools. The vault explains them; it doesn't replace them.
- Real-time collaboration is limited. It's built for one person or a small group. If your whole team co-edits docs daily, a shared wiki may fit better — or use Obsidian as the ops lead's source and publish selected pages out.
- Structure is on you. There's no default setup. Without a few conventions (naming, templates, where decisions go), a vault gets messy fast.
- Sync costs a little effort. Use Obsidian's paid Sync, or a cloud folder you already trust. Decide once and move on.
Start in a week
Don't try to document the whole company. Pick the one process that breaks most often and start there.
- Day 1: Install Obsidian and create a vault with four folders: Systems, Processes, Decisions, People.
- Day 2: Write one page per system that process touches. Keep each to what it owns and what usually goes wrong.
- Day 3: Write the process itself, step by step, linking every system and owner with [[ ]].
- Day 4: Log the last five decisions that shaped it, one short note each.
- Day 5: Add a simple template for new decisions and SOPs.
- Days 6–7: Use it. Next time someone asks a question about that process, answer with a link.
If you already work with an AI assistant, point it at the vault in week two and let it help keep pages current.
The real payoff
The best ops leaders aren't the ones who know everything. They're the ones whose knowledge survives when they're not in the room. A good vault turns what you know into something your team, your successor and your tools can use. Mine has become the most valuable system I run — and it's just a folder of text files.
Tatiana is Head of Operations at Cantina, where she builds the systems that connect sales, finance and delivery.
That's the standard I hold myself to at Cantina: building operations that are the best in the business, and that keep getting better no matter who's in the room.