How Claude and Obsidian run my working week
A case study: building an AI-assisted operating system from plain-text notes and a scheduled assistant.
+
How Claude and Obsidian run my working week
A case study: building an AI-assisted operating system from plain-text notes and a scheduled assistant.
Draft adapted from Katie's case study. Replace with the full write-up.
The problem
My role is deliberately broad: operations, technology, vendors, facilities, whatever needs a structure. The cost of breadth is that everything competes for the same attention, and the failure mode is quiet. Nothing dramatic goes wrong; things just slip.
What I built
The foundation is plain-text notes in Obsidian: a daily note, a commitments register, and a file for each initiative I'm running. On top of that sits a scheduled AI assistant. Each morning it builds my daily note: the decisions I need to make, the delegations to chase, and a short prioritised plan. Each evening it reconciles the day against my commitments register, updates the initiative files, and writes a debrief.
Why plain text
Because it holds. Plain-text files don't depend on a vendor, a subscription or an export tool. The AI does the moving parts; the notes stay simple enough that the whole system is legible to me at a glance.
What happened
Nothing falls through the cracks any more, and the time I used to spend reconstructing my week now goes into the work itself. The strongest signal it works: I'm now replicating the system for our finance team.