Important knowledge can exist and still be unusable
Expertise may be concentrated in a founder or a few senior people. Documentation may be scattered, outdated or written around steps while the decisions and exceptions remain implicit. A knowledge base may contain a lot and still fail at the moment someone needs an answer.
The goal is not more documentation by default. It is a usable knowledge system that reduces avoidable dependence, supports consistent work and preserves the reasoning people need to make good decisions.
The practical outcome
The knowledge that matters is easier to find, understand and apply. Roles and ownership are clearer. Critical expertise is less dependent on one person, and documentation is connected to the workflow rather than stored as a parallel universe.
What I actually do
- Map the knowledge, decisions, dependencies and friction that affect performance.
- Identify which expertise is critical, at risk, repeated or difficult to transfer.
- Interview experts and analyze source material to capture process, reasoning, judgment and exceptions.
- Design a usable information architecture and content model.
- Create or improve knowledge resources, SOPs, decision guides, templates and supporting assets.
- Connect the system to roles, workflows, tools, ownership, review and real moments of need.
An example of the work in practice
A founder-led agency may have a documented delivery process but still route difficult decisions through the founder. The useful work is not simply rewriting the SOP. It is mapping where judgment enters, extracting how experts read the situation, designing guidance for the recurring decisions and integrating that guidance into the workflow, onboarding and review system.
How METIS shapes the engagement
Knowledge and documentation projects usually emphasize Map, Extract and Integrate. Map identifies what knowledge drives performance and where it breaks down. Extract captures the process, reasoning and exceptions behind expert work. Integrate puts the resulting knowledge into the tools, roles and moments where it can support execution.
Transfer and Scale can become more important when the project includes onboarding, practice, adoption or a wider effort to reduce dependence and improve consistency.
Adoption is part of the design
A knowledge base is only useful when people know when to use it, can navigate it quickly, trust what they find and have a way to improve it. The engagement can therefore include ownership, workflow placement, templates, handover, training, feedback and review, not only the production of documents.
What counts as evidence
Evidence may be an operating manual that captures an entire service, a clearer knowledge architecture, fewer gaps between process and judgment, resources that answer recurring questions or a team that can deliver more consistently without routing every decision through one person.