Design the client folder and naming taxonomy
Proposes a reusable workspace structure and naming convention for client notes, outputs, and shared docs — fitted to the chosen platform and the advisor's actual retrieval habits.
In / outPlatform constraints + advisor's retrieval habits → folder structure and naming convention design
You might say…
“I'd find the same note in three different places and lose the one that mattered because I'd never decided where things lived.”
What it does
Proposes a reusable workspace/folder structure and naming convention for client notes, session outputs, and shared docs, fitted to the chosen home (Notion, Drive, Obsidian) and the advisor's retrieval habits. Used when first setting up the file system.
Trigger: Use when first setting up the file system — before you have clients in it — so the structure reflects how you retrieve information, not just how you file it.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation