Concepts, not folders: how a knowledge base earns its keep over time
Folders make sense when you're filing. Concepts make sense when you're thinking. A knowledge base for consultants needs the second.
The team behind Pith Lab
Why folders rot
Folder structures are decisions made on day one that get worse every day after. The categories that made sense in 2023 don't fit the engagements of 2026. The folder labelled digital-transformation now contains five different things; nobody renames it because that means deciding which thing wins.
This is the structural failure of every shared drive in every consultancy. It's not a tooling problem; it's a categorisation paradox. The categories you'd want only become clear after you've done the reading.
What concepts give you instead
A concept page is the inverse: it doesn't exist until enough material accumulates to justify it. Save 15 passages about retrieval-augmented generation across six engagements? A concept page emerges automatically — RAG patterns observed in client work — with all 15 passages cited inline.
This works because concepts are retrospective, not prospective. You're not deciding what categories should exist. You're reading the structure of what does exist.
The right structure for a consulting library is the structure that emerges from how the team actually reads.
Why this is hard to fake with tags
Tags look like a solution but aren't. They require the saver to decide the structure at the moment of saving — exactly when they have the least information. Six months later, the tag taxonomy has 200 entries, half overlapping, none load-bearing.
Concepts move that decision to the right time: after enough reading to know what's load-bearing. The system proposes; the human confirms or merges. The taxonomy grows from evidence, not anticipation.
What this changes operationally
When the structure is concept-based, several things shift. Search becomes useful — concepts are precise enough to land on. Briefings get sharper — they cite concept pages, not raw articles. New team members onboard faster — they read concept pages, not folders. And the library gets better with use, instead of decaying.
A folder structure is a bet on the future. A concept structure is a memory of the past. For a consulting library, memory is the asset.
FAQ
Do I still need tags?
Yes, but for client-scoping, not topic. Tags answer 'whose project is this for'. Concepts answer 'what's actually in this'.
How do concepts get created?
From clusters of saved passages — the system surfaces a recurring pattern across bookmarks and proposes a concept page with citations. You confirm or rename.