{"id":16828,"date":"2026-03-21T08:00:00","date_gmt":"2026-03-21T01:00:00","guid":{"rendered":"https:\/\/beup.space\/?p=16828"},"modified":"2026-04-07T12:47:51","modified_gmt":"2026-04-07T05:47:51","slug":"thiet-ke-knowledge-management","status":"publish","type":"post","link":"https:\/\/beup.space\/en\/thiet-ke-knowledge-management\/","title":{"rendered":"Designing knowledge management for small businesses"},"content":{"rendered":"

\u23f1 8 min read<\/p>\n

A 7-person furniture company in Binh Duong lost its sales manager after three years. The new hire, experienced and qualified \u2014 but after two months still didn't know which supplier to order raw materials from.<\/p>\n

He couldn't grasp the pricing history with each partner. He also didn't understand why client A always requested invoices on the 25th instead of the end of the month.<\/p>\n

None of that information was in any file. It was all in the head of the person who left. This is the problem that business knowledge management needs to solve.<\/p>\n

This is not uncommon. Research from HR Daily Advisor indicates that, on average, 42% of the knowledge required to perform a role<\/strong> exists only in the head of the person holding that position.<\/p>\n

When they leave, colleagues cannot perform nearly half of the work. Furthermore, the replacement takes nearly 200 hours<\/strong> \u2014 equivalent to 5 weeks of work \u2014 just to rediscover what the previous person already knew.<\/p>\n

The problem isn't hiring the wrong people. The problem is never having a system. designed for knowledge management<\/strong> to retain knowledge as personnel changes.<\/p>\n

\n

Table of Contents<\/p>\n

    \n
  1. V\u00ec sao m\u1ea5t nh\u00e2n s\u1ef1 gi\u1ecfi l\u1ea1i g\u00e2y thi\u1ec7t h\u1ea1i l\u1edbn \u0111\u1ebfn v\u1eady?<\/a><\/li>\n
  2. C\u00f3 nh\u1eefng lo\u1ea1i tri th\u1ee9c doanh nghi\u1ec7p n\u00e0o?<\/a><\/li>\n
  3. Documentation isn't knowledge management \u2014 much like taking photos isn't filmmaking.<\/a><\/li>\n
  4. Start with one question: if this person leaves tomorrow, who knows how to do that job?<\/a><\/li>\n
  5. Thi\u1ebft k\u1ebf kho tri th\u1ee9c doanh nghi\u1ec7p c\u1ea7n g\u00ec?<\/a><\/li>\n<\/ol>\n<\/div>\n

    <\/p>\n

    \n

    When the best person leaves, you lose more than one employee<\/h2>\n

    In the software industry, there's a concept called bus factor<\/strong>. It represents the minimum number of individuals whose departure would lead to the complete paralysis of a system or process.<\/p>\n

    Should a single individual's departure render the entire team unable to proceed, the bus factor is 1 \u2014 the most critical level. Specifically, research indicates that 65% of systems have a bus factor of 2 or less<\/strong>Operations can be disrupted if just two people leave.<\/p>\n

    For small businesses, the problem is even more severe. When a team consists of only 5\u20137 people, each individual often juggles multiple roles \u2014 from sales and customer care to operational management. Knowledge isn't evenly distributed; it's concentrated in one or two key individuals.<\/p>\n

    When those individuals leave \u2014 whether due to resignation, extended leave, or moving to another position \u2014 the team doesn't just lose an employee. They lose customer relationships, specific ways of handling situations, and operational “tricks” that no one ever documented.<\/p>\n

    However, 47% of businesses confirm that losing internal knowledge is the biggest challenge when an employee leaves. It's not about hiring a replacement, nor about handing over tasks \u2014 it's about the knowledge disappearing with the person.<\/p>\n

    <\/p>\n

    \n

    Knowledge exists in two forms \u2014 and the most critical type often remains undocumented.<\/h2>\n

    Ikujiro Nonaka and Hirotaka Takeuchi \u2014 two Japanese researchers, authors of the book The Knowledge-Creating Company<\/em> \u2014 distinguish between two types of knowledge within organizations.<\/p>\n

    Explicit Knowledge<\/strong> (explicit knowledge) is what has been recorded: processes, price lists, contract templates, software user manuals.<\/p>\n

    Tacit Knowledge<\/strong> (tacit knowledge) is what lies within the experience, intuition, and habits of each individual. For example, how to handle customer complaints, knowing which supplier is reliable when urgently needed, or understanding why a process is designed a certain way.<\/p>\n

    \n

    Explicit Knowledge<\/strong> \u2014 can be immediately read, copied, and transferred: documents, spreadsheets, recorded procedures.<\/p>\n

    Tacit Knowledge<\/strong> \u2014 can only be acquired through experience: relationships, situational judgment, and decision-making context. This is the 42% that organizations lose when key personnel depart.<\/p>\n<\/div>\n

    Externalization \u2014 transforming tacit knowledge into organizational assets<\/h3>\n

    Nonaka and Takeuchi call the process of transforming tacit knowledge into explicit knowledge externalization<\/strong>. This is the core of every effective knowledge management system.<\/p>\n

    In reality, most small businesses in Vietnam operate entirely within the realm of tacit knowledge. Everything is passed down orally, learning happens through observation, and situations are handled based on personal experience.<\/p>\n

    That model works \u2014 until the experienced person leaves. At that point, the organization discovers that what they thought “everyone knew” was actually only known by one person.<\/p>\n

    <\/p>\n

    \n

    Documentation isn't knowledge management \u2014 much like taking photos isn't filmmaking.<\/h2>\n

    Many small teams think they have “knowledge management” because they have Google Drive with documents or a Zalo group for file sharing. Some have a few note pages on Notion. But personal notes and knowledge management are fundamentally different.<\/p>\n

    Note-taking is for oneself \u2014 arbitrary structure, found by memory, understood by no one but the writer. Knowledge management is for the organization \u2014 categorized, structured. Anyone in the team can find the necessary information without asking anyone.<\/p>\n

    Tiago Forte \u2014 author of Building a Second Brain<\/em> \u2014 proposes the structure PARA<\/strong>. This method is currently being applied at Toyota, Genentech, and by over 500,000 people worldwide. PARA consists of Projects (ongoing projects), Areas (areas of responsibility), Resources (reference materials), and Archive (archived items).<\/p>\n

    This structure is immediately applicable to both individuals and organizations. More importantly, it answers the question that most note-taking systems fail to address: where do I find this information?<\/em><\/p>\n

    \n

    “It is about optimizing a system outside of yourself \u2014 so your mind is free for creativity, not storage.”<\/p>\n

    \u2014 Tiago Forte, Building a Second Brain<\/em><\/p>\n<\/div>\n

    Three factors determining an effective knowledge repository<\/h3>\n

    A good knowledge base operates like a library: it has clear classification (taxonomy) and navigation. Anyone can find the information they need without asking a librarian.<\/p>\n

    Therefore, research from MatrixFlows on over 500 knowledge base systems reveals three decisive factors. First, classification with no more than 5\u20137 main categories. Second, each page has a single and clear topic. Third, content is cross-linked for users to explore related information.<\/p>\n

    <\/p>\n

    \n

    Start with one question: if this person leaves tomorrow, who knows how to do that job?<\/h2>\n

    Before thinking about tools or software, the first step in designing knowledge management is a simple test. List the ten most important processes or pieces of knowledge within the team.<\/p>\n

    For example, from handling customer complaints to the raw material ordering process, from salary calculation to product pricing logic. For each item, answer two questions: how many people in the team know how to do this?<\/em> and if the main person leaves tomorrow, who can immediately take over?<\/em><\/p>\n

    Tasks solely understood by one individual \u2014 those with a bus factor of 1 \u2014 should be prioritized for externalization. There's no need to document everything concurrently. Documenting the three most critical processes within two weeks has demonstrably reduced organizational risk.<\/p>\n

    What does each documentation page need?<\/h3>\n

    Each documentation page only needs to answer four things: the purpose of the process, the steps to follow in order, common pitfalls new users often miss, and who to contact when encountering issues.<\/p>\n

    Therefore, this approach does not require special software \u2014 a Notion page, a Google Doc, or even an Excel file will work. The important thing is that knowledge must leave one person's head and reach a place accessible to the entire team.<\/p>\n

    \n

    PRACTICAL TOOLS<\/p>\n

    Practical Knowledge Base \u2014 A Comprehensive Guide with Notion<\/p>\n

    Free 14-chapter course \u2014 a step-by-step guide to building a knowledge base on Notion, applying 4 practical methods (LATCH, DIKW, PARA, Zettelkasten). From knowledge audit to classification structure, from individual to organization.<\/p>\n

    View Free Course \u2192<\/a>\n<\/div>\n

    <\/p>\n

    \n

    A knowledge repository doesn't require vast content \u2014 it demands the correct structure.<\/h2>\n

    The most common mistake when starting to build a knowledge base is trying to record everything at once. The result is often a pile of documents that no one can find, no one updates, and after a few months, they are forgotten.<\/p>\n

    This is exactly the “dead processes” Michael Gerber describes in The E-Myth Revisited<\/em>. An effective knowledge base for a small team needs the right structure more than a lot of content.<\/p>\n

    Three principles for designing a knowledge base<\/h3>\n

    The first design principle: categorize by functional area (sales, operations, finance, HR), not by person. When knowledge is tied to an individual's name, it disappears with that individual. When knowledge is tied to a functional area, it belongs to the organization.<\/p>\n

    The second principle: each page contains only one process or one piece of knowledge. That page needs an assigned owner and the last updated date \u2014 so anyone knows if the information is still accurate.<\/p>\n

    The third principle: review quarterly \u2014 delete what's no longer correct, update what has changed, and add what's missing.<\/p>\n

    In summary, these three principles \u2014 categorizing by functional area, one topic per page, and regular reviews \u2014 are sufficient to operate a knowledge base for a team of under 10 people. No expensive software or external consulting is needed.<\/p>\n

    You only need an afternoon to set it up, and the discipline to update it whenever there's a change.<\/p>\n

    \n

    OPERATING SYSTEM<\/p>\n

    Small Team OS Lite \u2014 Operating Small Teams for Free<\/p>\n

    If your team needs a broader system \u2014 for project management, task assignment, KPIs, and a knowledge base \u2014 Small Team OS Lite is an 11-database framework on Notion for teams of 2\u201310 people.<\/p>\n

    Download Free \u2192<\/a>\n<\/div>\n

    <\/p>\n

    \n
    \n

    \ud83d\udccc Key Takeaways<\/p>\n