Guide
Method
A practitioner guide describing design requirements for institutional knowledge systems. It reports no adoption data and claims no rates.
Sample
Not applicable.
Key points
Knowledge systems fail on structure and ownership, not on software. A well-modelled system on modest tooling outlives an elegant platform with no taxonomy and no owner.
Where infrastructure must be minimal, a static, self-contained system with full-text search is frequently the correct answer, and it removes an entire category of operational risk.
Every content area needs a named owner with the time allocated. “The communications team” is not an owner. A person with a name, a review cadence and an escalation route is an owner.
Do not digitise or index what should be disposed of. The retention schedule and disposal authority are agreed before capture, not discovered afterwards during an audit.
Queries reveal what people cannot find. Reading the log monthly is the cheapest content audit available and it consistently outperforms the workshop where everyone says the system is fine.
Content model starter (PDF)
Taxonomy, metadata fields, ownership map and review cadence template.
Sent by email within one business day. No registration, no marketing sequence.
Book a Discovery Session
A structured session that produces a written problem statement, whether or not it leads to an engagement. If the problem is not one we should be paid to solve, we will say so.
Enquiries acknowledged within one business day, always.