Digitising knowledge: what replaces shared folder structures in a mid-sized company?
How do you protect process knowledge from staff turnover with knowledge management software? With a named owner per type of knowledge, a searchable repository and a handover that starts before the notice. What replaces shared folders and why usually no new licence is needed.
In a mid-sized company, shared folder structures are best replaced by a knowledge repository with a named owner for each type of knowledge, a searchable interface and clear permissions. In most businesses this can be built in the existing Microsoft 365 environment, without an additional licence. More important than the tool is the question of who maintains which knowledge, because that decides whether process knowledge survives a change of staff. PASSION4IT builds this structure as part of Digital Work.
What you’ll take away:
- How to secure process knowledge before someone leaves the company
- Why a folder on a network drive doesn’t know which version is still valid
- Four types of knowledge that belong in different places in a business
- Which software is an option, from Microsoft 365 to the knowledge base in a service tool
- A five-step switch in which not every folder is migrated
- Why AI only pays off in a business once knowledge is in order
- What getting started costs and how long the first implementation stage takes
How do you protect valuable process knowledge from staff turnover with knowledge management software?
By making sure the knowledge sits in a searchable repository before the person leaves, and that someone else is responsible for keeping it current. The software provides search, versions and permissions, but what actually protects the knowledge is a fixed owner for each type of knowledge.
Process knowledge is lost in a change of staff for two reasons. Either it was never written down because the experienced colleague kept it in her head, or it exists in five places in five versions and nobody knows which one applies. The same sequence helps against both:
- Name the critical processes. Which workflows depend on a single person? That list is the starting point, not the entire network drive.
- Write knowledge down during normal operations. Work instructions and checklists are created while the person is still there, ideally together with the person who will share the workflow in future.
- One valid version in one place. The instruction lives in the knowledge repository with a version history, not as a copy in an email attachment.
- Hand over ownership. Every type of knowledge has a responsible person who is not the one leaving.
- Hand over before the last day. When someone resigns or retires, the open processes are walked through using the list from step 1, not from memory.
In most businesses Microsoft 365 with SharePoint is enough for this, more on that below. What matters is that staff know where new knowledge belongs, otherwise after three months it lands in the nearest folder again.
Why are shared folder structures no longer enough?
Because a folder only knows where a file is. Whether it is still valid, it doesn’t show. After a few years the same work instruction sits on the network drive in three versions, a fourth in an email attachment and a fifth locally on a laptop. New staff therefore ask the colleague who has been there for twenty years, and that knowledge retires with her.
Folders also have exactly one sort order. A guide to the complaints process sits either under “Quality” or under “Sales”, and half the people looking search in the wrong folder. A knowledge repository with search and tagging solves that.
Which types of knowledge should a business distinguish?
Four, because they go out of date at different speeds and are maintained by different people.
| Type of knowledge | Example | Where it belongs | Who maintains it |
|---|---|---|---|
| Process knowledge | work instruction, checklist, onboarding | central knowledge repository with search | process owners per department |
| Project knowledge | minutes, decisions, interim status | in the project team, archived after completion | project lead |
| Customer knowledge | contacts, agreements, history | in the CRM | sales and back office |
| Service knowledge | solutions to recurring enquiries | knowledge base in the service tool | customer service |
Putting all four into one repository recreates the old problem in a more modern interface. Customer knowledge belongs in the CRM, because there it is linked to the transaction. Project knowledge loses relevance after completion and must not clutter the search for valid instructions.
Which knowledge management software suits a mid-sized company?
The software the workforce already works in, as long as it offers search, permissions and a page structure. For most businesses that is Microsoft 365 with SharePoint as the repository and knowledge pages, because the licence is already included in Business Standard or Business Premium and people use Teams every day anyway.
A separate knowledge management tool pays off if knowledge has to be available across many sites or to external partners, or if the business doesn’t run on Microsoft 365. For service knowledge, the helpdesk or service tool usually brings its own knowledge base, and it is better kept there than in a central repository, because the solution sits right on the ticket.
Anyone who has to select a new system should decide on real use cases. What that looks like for small teams is described in Which software suits a small team without an IT department?. For bigger decisions there is Smart Software Selection.
How does a business switch from folders to a knowledge repository?
In five steps, and the second is the most important.
- Take stock. Which folders are still opened, and which haven’t been for years?
- Sort out before migrating. Only valid knowledge moves. The rest is archived read-only and stays findable, but doesn’t land in the new search.
- Define types of knowledge and their places. The table above is the template.
- Name owners. Each type of knowledge gets a person responsible for keeping it current and reviewing pages with an expiry date.
- Train the rules. Anyone who doesn’t know where new knowledge belongs will put it back in the nearest folder.
At PASSION4IT the first implementation stage with filing structure, permissions and binding standards takes 8 to 16 weeks depending on size. Training runs in parallel. The PASSION4IT Academy provides the Digital Work module for €39 per user and year, with no classroom dates, licensed per user.
What does knowledge management have to do with AI?
Everything, as soon as an AI assistant is supposed to answer questions about your own business. An assistant with access to a network drive holding five versions of the same instruction may well return the outdated one. AI only pays off in a business once documents, data and processes rest on a clean foundation.
The order is therefore the same as for any other introduction: tidy up first, automate afterwards. More on this in AI in the enterprise: why knowledge management decides success or failure.
What does the switch cost?
At PASSION4IT the entry point is the Digital Check at a fixed price of €3,950 plus travel costs, two to four weeks of analysis with a prioritised roadmap. It shows how many areas are affected and how much structure already exists, and only then can the implementation be priced seriously. With BAFA funding the own share in the western German federal states drops to €2,200, if the application is approved before the consulting starts.
Frequently asked questions (FAQ)
How can I use knowledge management software to protect valuable process knowledge from staff turnover?
By naming critical processes, documenting them while the experienced person is still in the company, and storing the documents as the single valid version in a searchable knowledge repository such as SharePoint. Every type of knowledge gets a responsible person who is not the one leaving. The software delivers search and versions, but only that ownership actually protects the knowledge.
What should I do when a long-serving employee resigns or retires?
Walk through the workflows that depend on that person using a list, and document them together with the successor before the last working day. The earlier this starts, the less depends on memory. Ideally documentation runs alongside daily work anyway, not only once someone hands in their notice.
Which knowledge management software is a good alternative to shared folder structures?
For most mid-sized businesses, the existing Microsoft 365 environment with SharePoint as a searchable knowledge repository, because no additional licence is needed and the workforce already uses Teams. A separate knowledge management tool pays off with many sites, external users or without Microsoft 365. PASSION4IT advises on this vendor-independently.
Do I need a new licence for knowledge management?
In most cases no. What a knowledge repository needs is already included in Microsoft 365 Business Standard or Business Premium and often just hasn’t been set up. The assessment clarifies whether buying more makes sense.
Should all old folders move into the new system?
No. Only knowledge that is still valid moves. Everything else is archived read-only, stays findable and doesn’t weigh down the new search.
Who maintains the knowledge after the switch?
One named person per type of knowledge: process owners for work instructions, the project lead for project knowledge, sales and back office for customer knowledge in the CRM, customer service for service knowledge. Without this ownership even the best repository goes out of date quickly.
How long does the switch take?
The analysis in the Digital Check takes two to four weeks. The first implementation stage with filing structure, permissions and standards takes 8 to 16 weeks depending on size.
Does an AI assistant help with knowledge management?
Yes, if the knowledge is in order. An assistant finds answers faster than any folder search, but it also returns outdated versions if they are still in the repository. That is why tidying up comes before AI.