- 19
- February
Every organization has faced this situation — a long-time employee suddenly resigns, and you realize that all work processes were stored in that person's head alone. No manuals, no SOPs, and no one knows what to do next. The systems configured by the former employee remain untouched because everyone is afraid of breaking them.
Real Situations That Happen in Many Organizations
Consider these scenarios:
- An accountant who worked for 10 years resigns — no one knows how to close the books, and no one understands the Excel formulas used for tax calculations
- The inventory officer managing the warehouse resigns — no one knows where items are stored, as the storage system exists only in handwritten notebooks
- The company's sole IT person resigns — no one knows the server passwords, and the custom systems they built have no documentation
- The procurement staff who dealt with all vendors resigns — special terms, discounts, and agreements were all stored in their head, never recorded anywhere
These problems are not uncommon — they happen repeatedly, especially in organizations that lack a Knowledge Management system and still rely on "people" rather than "systems"
The Aftermath — When New Employees Come In
After the experienced employee leaves, new hires face these challenges:
1. Not Knowing What to Do or How to Do It
No manuals, no SOPs, no checklists — work procedures were never written down. Everything existed in the "habits" of the former employee. Asking colleagues yields no answers because everyone focused on their own tasks.
2. Systems Configured by the Former Employee That No One Dares to Modify
Excel files with 5 layers of complex formulas, custom-written Macros, custom-configured systems — no one knows why they were set up that way or what changing one element would affect. New employees are afraid to touch them for fear of breaking everything.
3. Critical Information Disappears with the Person
Vendor agreements, special conditions, previously encountered problem solutions, key contacts — all of this lived in Line chats, personal notebooks, or memory. None of it was ever recorded in the organization's systems.
4. Having to Relearn Everything from Scratch
What the former employee spent 10 years accumulating, the new hire must "guess" and "trial-and-error" on their own, taking 3-6 months before they can work normally. And what if the new hire also resigns? The same cycle repeats.
Simulated Example: The Case of Khun Malee
Khun Malee was a senior accountant who had worked for 15 years. She knew everything about the company's accounting system — from how to close the books and calculate taxes to how to manage each vendor.
When Khun Malee resigned, she left behind 47 Excel files on her computer. Each file contained complex formulas, hidden sheets, and custom-written Macros, with no documentation explaining what each file was used for.
Her replacement opened the files and couldn't understand the formulas in even a single file, having to trace each cell to figure out where data came from, what was being calculated, and why it linked to other files.
Result: Financial closing was delayed by 2 months. External consultants had to be hired, costing hundreds of thousands of baht in additional expenses.
Why ERP Can Solve This Problem
The core of the problem is that "knowledge resides in people's heads, not in the system." An ERP system solves this by "transferring" knowledge from people's heads into the system:
1. Processes Live in the System, Not in People's Heads
Every work procedure — from purchase requisitions and approvals to goods receipt and payments — is defined as a Workflow in the system. Whoever takes over follows the same flow without asking anyone or guessing.
2. Clear Workflows — Who Does What, When, and Who Approves
Every step has clearly assigned responsibility with an Approval Chain defined in the system. It's not "go ask Khun Malee who needs to sign" — the system automatically routes to the appropriate approver.
3. SOPs Live in the System, Not in Filing Cabinets
Standard Operating Procedures are not just A4 documents stored in folders — they are embedded in the ERP system. Every time a transaction is processed, the system enforces SOP compliance. Skip a step, and the system won't allow it.
4. New Employees Can Follow the Flow Immediately
New employees don't need to spend 3-6 months learning. Simply log into the system, and it tells them what to do next — with a Dashboard showing pending tasks, flows to follow, and historical data to review.
What Organizations Should Do Starting Today
Don't wait until someone resigns to fix the problem. Organizations can prepare now:
1. Document Work Procedures for Every Position
Every position must have SOP documentation that explains work procedures from start to finish — not just "roles and responsibilities" but a step-by-step guide that new employees can read and follow.
2. Use an ERP System Instead of Excel
Stop relying on Excel files where formulas live in one person's head. Move everything to an ERP system with Standard Processes for everyone to follow. Data lives in a central database, not on any individual's computer.
3. Cross-Training — Training Across Positions
Don't let any single person become a "Single Point of Failure." There should be at least 2 people who know the work for each position. If one leaves, the other can fill in.
4. Audit Trail — Recording Every Change
Every transaction must be recorded in the system — who did what, when, who approved it, and what changed from before. This data helps new employees understand the work history and review how things were done in the past.
How Saeree ERP Prevents Knowledge Loss
| Feature | Details |
|---|---|
| Standard Workflow | Every process has a standard Workflow — from purchase requisition, approval, goods receipt, to payment. No need to memorize; the system guides you to the next step. |
| Role-based Access | Permissions are assigned by role. New replacements see the exact same menus and screens as their predecessors, ready to work immediately. |
| Audit Trail | Records every change — who did what and when. New employees can review what their predecessors did and learn from actual data. |
| Training Mode | A Sandbox system for training. New employees can practice real transactions in a test environment without affecting live data. |
| SOP Integration | Attach SOP documents and work manuals within the system. Access them anytime from the relevant screen without searching through filing cabinets. |
Saeree ERP — Organizational Knowledge Must Live in the System, Not in One Person's Head
Saeree ERP is designed to ensure all work processes are recorded and stored in the system. Regardless of who resigns, transfers, or retires, the organization continues operating smoothly because Workflows, SOPs, Audit Trails, and all data remain in the system — ready for new employees to step in immediately.
Summary
The problem of "when key employees leave, the system collapses" isn't about not finding replacements — it's because organizational knowledge lives in one person's head, not in the system. If you still rely on Excel with formulas in someone's head, on "habits" instead of SOPs, and have no Audit Trail — this problem will recur every time someone resigns.
Organizations using an ERP system like Saeree ERP won't face this problem because all processes are in the system. Regardless of who comes or goes, the organization keeps moving forward. This is true Business Continuity.
