On Monday, Tomek starts his holiday. Marta, who runs an 11-person design studio, is trying to work out why the client rejected the first version of the facade and where the signed contract is - only Tomek knows the answers. Knowledge management in a small business starts at exactly a moment like this: with recording decisions and documents where the team actually handles the matter.
Knowledge stays in people's heads, because saying is easier than writing down
A client calls Tomek with a comment about the facade, and right after the call, Tomek picks up another one. The agreement stays in his head, because writing it down requires a separate action and a separate place.
Fragmentation follows. One answer sits in an email, another on a private drive, a third is mentioned by the coffee machine. When someone asks Marta on Tuesday where the Nord project stands, she first has to work out who to ask. The next time someone's on holiday, the question comes back.
The idea of "let's make a wiki" sounds reasonable, until it needs updating alongside everyday work. It's better to start by recording things where the decision was actually made. We wrote more broadly about reducing scattered conversations in the article why teams lose track of agreements. This one is about the next step: what to keep so that knowledge survives a change of the person handling the matter.
Knowledge management in a small business starts with three types of records
You don't need to document every conversation. Start with the decision along with its reason, agreements with clients, and the course of any task the team repeats.
| What you record | Example | Where to keep it |
|---|---|---|
| The decision and its reason | "We're changing the facade material, because the client rejected the previous option" | The thread of the task related to the project |
| Agreement with the client | "Model by Thursday, by 12:00; dark background" | The task or chat thread |
| A recurring process | "How we prepare a quote: five steps" | A note shared with the people who prepare quotes |
The "why" note explains the most. Simply knowing that a new material was chosen won't help someone who'll be talking to the same client in six months. The reason lets them tell a deliberate decision apart from a random change.
That said, don't turn every agreement into an instruction. A one-off client request should stay with their matter; the way quotes are prepared for all clients makes sense in a note the team keeps coming back to. If you're unsure whether something belongs in a task or a conversation, the distinction described in where to record team agreements can help.
Record knowledge alongside the matter, not in a separate documentation project
Knowledge is easier to maintain when it's created alongside the work, not after it's finished. Agree on one simple approach with your team: each matter has its own place, the decision goes into the conversation, and the document goes to the same matter.
- Choose one place for the matter. For the Nord project, direct questions and agreements to its task or chat, instead of starting a new conversation for every topic.
- Record the decision as a full sentence. "We're choosing option B, because the client needs space for an extra entrance" says more than "B approved".
- After a meeting, note the outcome. It's enough to record what you agreed, who's responsible for the next step, and the deadline; the full discussion can stay in participants' memory.
- Keep the file with the matter. Whoever takes over the project should know which contract or model relates to a given decision.
- Revisit the exceptions. Once a quarter, ask the team what they still have to ask only one specific person about. Move any recurring answer into a shared note.
This is a way of working, not a feature tied to one piece of software, so you can start with your current tool. When choosing the next one, though, check whether the conversation, document and task can be linked without copying the same agreements into several places. You'll find a broader picture of such a setup in the article on a company's digital brain.
A task stores not just the outcome, but also the reason for the change
Record the reason for a decision as a message in the task thread - the changed description alone won't explain it. In Task Manager, the description, responsible people, due date and conversation all sit within the same task. The thread also logs system messages about changes to status, assigned people, due date, priority and name, so you can check who moved the deadline and from which date.
Picture a Thursday in Marta's office. She sets up a Workspace for the Nord client - a space that groups work together and defines access - and a task called "Elevation project". Tomek writes in the chat why the client rejected the previous version, and Marta adds a checklist to the description of things to check. Participants tick off items without opening the editor; a progress bar shows how far along things are, and each ticked item shows who completed it.
An important distinction: editing the description doesn't create a separate system message. A "(edited)" label appears next to the author's name, so it's better to record the reason behind an important decision as a message in the thread as well, rather than quietly swapping out the earlier description.
When Marta wants to point a colleague to the matter, she selects "Copy task link" from the ⋮ menu. The link opens the thread, but it doesn't override permissions - someone without access will see a "No access" message. Once the task is finished, it can be archived: it disappears from the main list, but its data remains. That's the practical difference between tidying up a list and deleting history.
You'll find more on what a task in Task Manager includes in the feature description.
A note comes in handy when a decision needs to be used again
Save a recurring instruction, checklist, or meeting summary in Notes. Don't treat them as automatically shared documentation, though: every note is private until you share it yourself.
On Friday, Marta writes "How we prepare an offer - five steps". She shares the note with three people on the team: two get "Can edit" access, one gets "View only". This way, people preparing offers can add an exception, while someone who only needs the instructions can't change it. The note's owner manages sharing; the app administrator doesn't see other people's unshared notes.
Assigning a note to a Workspace helps filter the list, but doesn't grant access to the whole team. Likewise, pinning it to a task's folder doesn't make it shared. This matters if a note is meant to be part of the knowledge another person can use once Marta is on leave: sharing has to be set up deliberately.
Notes save automatically, and the search tool looks through their names and content. An @ mention doesn't send a notification, so put the instruction "send the offer" in a task, not just in a paragraph of instructions.
In the Pro variant, a file can stay with the task
The Files module is available in the Pro variant. Every task and chat in a Workspace has its own folder there, where attachments from the thread end up, including images pasted into the text; it's a view of the same files, not separate copies.
If Tomek adds the corrected elevation to the conversation, Marta will find it in that task's folder. The paperclip icon in the thread header opens Files straight at the right spot. The directories visible in Notes and Files are shared, so there's no need to maintain two separate folder structures.
This is an easy place to get access wrong. A file dropped into a regular Workspace folder stays private; location alone doesn't share it with the team. You can share it via the "Whole workspace" row. A file uploaded directly to a task's or chat's folder works differently - participants in that thread can see it. Access to a note pinned alongside still requires separate sharing.
In Files you can preview PDFs and images, spreadsheets as a table, and DOCX as plain text. This helps you check which version of a document you're looking at, though you'll only see the full layout of a DOCX file once you download it.
Search first, then ask the AI Assistant
When you need a specific matter, start with search. In Task Manager, global search covers task and chat names, and in Notes and Files it also covers content - so don't assume it will find every sentence buried in a months-long conversation.
The AI Assistant is available in the Standard and Pro variants, but the app also works without AI. In Standard, you can manually point the Assistant to sources, such as a task, chat, note, or Workspace. A bar shows how much of the indicated knowledge fit in, and the Assistant tells you what it didn't take into account - not all the materials you point to are guaranteed to fit. It only sees material you have access to; it won't read someone else's unshared note.
In Pro, there's also an AI knowledge base, known as RAG. It's an index that helps the Assistant find information in the company's knowledge without you having to point to every source manually. It's built in the background once a day from summaries of tasks and chats, plus excerpts from notes and files; it doesn't cover Mail. If Marta asks on Monday about a decision recorded an hour earlier, she should point to the fresh thread manually - the new entry may not be in the index yet.
The Assistant can't read text from a PDF that's just a scan, because Task Manager has no OCR, meaning no text recognition within images. In that case, save the key points in a note or a message on the matter. AI runs on your own key with OpenAI, Google Gemini, Anthropic Claude, or xAI Grok: you pay the model provider directly, with no Task Manager margin added. The query, along with the needed context, is then sent to the chosen AI provider.
When someone leaves, shared knowledge needs a successor
Before an employee leaves, share the materials they'll need and grant their successor access to the relevant Workspace. Once an account is deactivated in Task Manager, the data remains and the licence seat is freed up. This doesn't mean, though, that the departing person's private notes automatically become accessible to the team - share important instructions with colleagues before they're needed.
The following Wednesday, after Thursday's decision being recorded and Friday's note being shared, Marta checks three things: whether the reason for the elevation being rejected was recorded on the Nord project, whether the signed contract was attached to the right matter, and whether the instructions for preparing offers have the right recipients. Whoever takes over the work doesn't have to guess which of these was missed. Access to the relevant Workspace still needs to be granted according to that person's role.
When you pass on company knowledge to a successor, where the data is stored matters too. In Task Manager, the application's data stays on your company's server; ordinary shared hosting is enough. The licence is perpetual and paid once for a number of seats, with no per-user subscription. It includes 12 months of updates; a yearly renewal afterwards is optional. The Standard variant costs 690 PLN for the Starter plan for up to 8 people, and 1,490 PLN for the Classic plan for up to 20 people. The Pro variant, with Files and the AI knowledge base, starts at 1,990 PLN for the Starter plan.
Tomorrow, pick one matter that only one person on the team is ever asked about. Write five sentences on the task: what was decided, why, where the document is, who's taking the next step, and by when. If you'd like to see what a place like this looks like in Task Manager, open the Demo.
Frequently asked questions
What is knowledge management in a small business, and where do you start?
It means recording decisions, agreements and recurring ways of working so the right people can return to them. Start with one matter: write down the decision with its reason, the next step, and where the document is kept.
Is a note assigned to a Workspace visible to the whole team?
No, assigning a note to a Workspace is only for filtering and doesn't share it with other people. The note stays private until the owner shares it themselves; even an administrator can't see it.
How do you find an agreement from six months ago in Task Manager?
Search for the task or chat name, or the content of Notes and Files. If you're using the Pro plan, you can also ask the AI Assistant about knowledge covered by the index, keeping in mind your access rights to the sources.
Do you need to enable AI for knowledge management?
No, Task Manager works without AI: you can record decisions in tasks, talk in chats and share Notes. AI is optional, and once enabled, it runs on your own key with your chosen model provider.
What happens to knowledge when an employee leaves?
Deactivating an account keeps the data and frees up the licensed seat, but it doesn't automatically share that person's private notes. So share any instructions the team needs beforehand, and record decisions about matters in their threads.
Sources
The Task Manager Team - we write about teamwork, AI in business and keeping tasks organised, using examples from Task Manager, software installed on your own server. Task Manager has been developed by Blue Creation Group (Piotr Łącz) since 2013 and is used by organisations including Neonet, the Military University of Technology and Polpharma - read customer reviews. We check our articles against the user guide and the latest version of the software.
