Why project knowledge gets lost
How to set up a market entry strategy, which questions are decisive in a due diligence, which measures really work in a restructuring: this methodological knowledge sits mainly with experienced consultants, and when they leave the firm, it leaves with them. What is documented is scattered: presentations on SharePoint, Excel models on personal drives, insights in emails and chat histories.
Then there is day-to-day project work. After the project is before the project, lessons-learned sessions are postponed and documentation is left undone. The result: proposals, analyses and slides are created from scratch again and again, although the firm has long had good templates and experience.
What it costs
Duplicated work costs hours that directly reduce the margin on fixed-fee projects. When everyone works with their own method, quality varies with the project team. New consultants take a long time to learn how the firm works, and a few experienced people become a bottleneck because everyone brings their questions to them. In the long run, even the value of the firm declines: in a succession or sale, a firm is worth more if its knowledge lives in the firm and not only in the partners’ heads.
Which knowledge should be secured
| Type of knowledge | Where it usually sits today | How it is secured |
|---|---|---|
| Methodological knowledge | In the heads of experienced consultants | As fixed workflows (playbooks) for the whole team |
| Industry and market knowledge | In old analyses and presentations | Searchable knowledge base, without confidential details |
| Templates and deliverables | On various drives | Centrally in corporate design, directly in the workflow |
| Proposal knowledge | In old proposals and emails | Make building blocks from won proposals reusable |
| Experience from projects | Nowhere, except in conversations | Capture insights while working |
Why classic approaches rarely work
Wikis and intranets go out of date quickly because nobody has time to maintain them. Lessons-learned workshops are unpopular and rarely produce results that are really used in the next project. Template libraries only help if you know they exist and if they are up to date. The common problem: knowledge management happens alongside the actual work and costs extra time.
What works: securing knowledge in the flow of work
Knowledge management only becomes effective when it is not an additional task. When proven approaches are stored as playbooks, everyone uses them automatically, and the methodological knowledge of senior consultants becomes the standard of the whole team. Research, analyses and results land directly in a shared knowledge base while work is going on. AI-assisted search finds relevant content even when you do not know the exact term or location, and every insight stays linked to its origin.
Confidentiality matters here. Client data is often subject to confidentiality agreements, so you need strict separation between engagements and access rights that follow existing permissions. What gets reused are methods and general insights, not confidential client data.
Checklist: knowledge management in five steps
- Name the 3–5 most frequent project types and define fixed workflows for them.
- Define one central place for insights and deliverables.
- Capture knowledge in the flow of work instead of documenting afterwards.
- Set rules for confidentiality: what may be used across projects?
- Measure usage: how often is knowledge reused, how much faster do proposals and analyses become?
Conclusion
A consulting firm’s knowledge is its most important capital and at the same time the worst secured. Wikis and workshops rarely solve the problem because they mean additional work. With AI, knowledge can for the first time be secured where it arises: in the project itself. Every engagement makes the firm a little better, and the knowledge stays in the firm even when people leave.
