Reload, don't remember
Every document you own opens with the context needed to restart cold — what this is, where it stands, what's next. You are writing for yourself in three weeks, with nothing in your head.
adhdpm.com
Mine doesn't. These are the systems that work anyway — starting with a setup you can build this afternoon that keeps your project notes current without you having to remember to update them.
The whole walkthrough is on this page. Obsidian, Claude, about twenty minutes. Nothing gated, nothing to sign up for.
Read the setupObsidian is free. If you already use it, you're most of the way there.
This block is the first system on the site. Every document you own should open with one.
Every document you own opens with the context needed to restart cold — what this is, where it stands, what's next. You are writing for yourself in three weeks, with nothing in your head.
If the ticket isn't written during the meeting, it doesn't exist. The gap between the conversation and the artifact is where the work actually disappears.
Stakeholders don't lose confidence because you forgot — they lose it because they can't see the state. Visible state buys you the slack to forget.
The vault is not a note archive. It's a context store. Notes go in raw and unedited — that's the whole point, because any capture step with friction is a capture step that doesn't happen. The structure gets imposed later, by asking, not by filing.
Everyone has been told to take better notes. The claim here is narrower and more useful: stop organising, and make retrieval somebody else's job. Obsidian holds the notes as plain markdown on your disk. Claude reads them, answers from them, and keeps the project notes up to date when you ask it to.
The discipline is entirely in the first one.
inbox/projects/people/Every project note opens with the same four lines. Fill in what you know; Claude keeps the middle two current.
What this is — One sentence, for someone who has never seen it.
Where it stands — [date] One line, dated every time it changes.
Next decision — The single open question, and who owns it.
Blocked on — Names, not teams. "Nothing" is a valid answer.
This uses the filesystem route: Claude reads the vault as ordinary folders on disk. One config file, no plugin, and it works whether or not Obsidian is open.
Install the pieces. Obsidian, the Claude desktop app, and Node.js, which runs the bit that lets Claude see your files.
Make the vault. Create a folder — Vault in your home folder is fine — with inbox, projects and people inside it. Open it in Obsidian as a vault. Add one note per live project to projects, each starting with the four lines above.
Point Claude at it. In the Claude desktop app, open Settings → Developer → Edit Config. Paste this in, with your vault's full path in place of /Users/you/Vault:
{
"mcpServers": {
"vault": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/you/Vault"
]
}
}
}
If the file already has an mcpServers section, add the "vault" entry inside it rather than replacing the lot. On Windows the path looks like "C:\\Users\\you\\Vault", with the backslashes doubled.
Restart Claude and check. Quit the app fully and reopen it. Ask: "List the folders in my vault." It should name your three. If it doesn't, the official setup guide covers the usual problems.
Two other routes work. The Obsidian Local REST API plugin understands tags and backlinks, but Obsidian has to be running and it needs an API key — use version 4.1.3 or later, which fixes a path-traversal vulnerability. Or, if you're comfortable in a terminal, run Claude Code in the vault folder.
These are the point. Everything above is scaffolding to make them work.
The maintenance pass once a week
Read everything in inbox/ from the last week. For each note in projects/, update the Where it stands line with today's date and revise Next decision. Only use what's in the inbox files. If a project has no new information, say so and change nothing.
The cold reload before you pick something back up
Where does the connector work stand? Answer only from the vault, and tell me what you couldn't find.
The 1:1 prep ten minutes before
I have a 1:1 with Priya in ten minutes. What's open from last time, and what has she come up in since?
The "only from the vault" and "tell me what you couldn't find" clauses are load-bearing, not politeness. Without them the gaps get filled with plausible invention, which on a project status is worse than an admitted blank.
Once a month I write up one system that holds under pressure, with the template to go with it and the prompt that keeps it current in the vault you just set up. The state-reload doc, in-meeting capture, the 1:1 that works without memory. No archive to catch up on, no course at the end.
Principal product manager on a data platform team at a large enterprise software company; nearly fifteen years in product and engineering, most of it with ADHD and none of it with a system I inherited from anyone. Everything here is what I actually run, written up after it survived contact with a real roadmap.