Document the process before you hire: why growing firms stall at the same point
Adding people to an undocumented process adds confusion faster than capacity. What to write down first, how much is enough, and how it turns into roles and responsibilities.
A business grows, the founder is stretched, and the answer seems obvious: hire. Six months later there are five more people, the founder is busier than before, and mistakes that never used to happen are now routine.
The cause is usually the same. The process existed only in the heads of two or three early employees. New people were told to "learn from Ramesh". Ramesh was too busy to teach, so each new person worked out their own version.
What goes wrong without documentation
- Roles cannot be assigned. You cannot give someone responsibility for a step that has never been defined. Work is handed out by habit, and gaps appear between people.
- Nobody knows who approves what. Small decisions go up to the owner because no limit was ever set.
- Training depends on one person. When that person leaves, the method leaves too.
- Errors cannot be traced. If there is no agreed way to do a task, there is no way to say where it went wrong.
What to write down first
You do not need a manual for the whole business. Start with the cycles that move money:
- Order to cash: from customer order to money in the bank.
- Procurement and payments: from purchase request to vendor payment.
- Payroll: from attendance to salary credit and statutory deposits.
- Month-end close: the entries, reconciliations and reports produced each month.
For each one, record five things: the steps in order, who does each step, what document or system entry it produces, who checks or approves it, and by when.
How much is enough
A useful test: could a competent new joiner follow the document and complete the task correctly in the first week, asking only a few questions? If so, it is detailed enough. Two or three pages and a one-page flowchart per process is normal for a small business. A thick manual that nobody opens is worse than a short one that is used.
From process to roles
Once the steps are listed, roles follow almost mechanically. Mark each step with who is responsible, who approves, who must be consulted and who is informed. This is a RACI chart. Three things show up immediately:
- steps with nobody responsible
- steps where the same person both does and approves the work, which is a control weakness
- people whose name appears on nearly every line, which is the real bottleneck
Job descriptions written from this chart are specific. "Accounts executive" becomes "raises invoices within two days of delivery, reconciles customer ledgers monthly, follows up on dues up to 60 days".
Keeping it alive
Documentation fails when it is written once and filed. Give each process an owner, review it once a year or when the system changes, and use it for onboarding. If new employees are trained from the document, people will keep it current, because they notice quickly when it is wrong.
The order matters
Hiring first and documenting later means paying salaries while people find their own way. Documenting first takes a few weeks and shows how many people are needed and for what. Sometimes the answer is fewer than expected, because half the pressure was coming from rework.
This article is general information as on the date of publication. Law and practice change, and the facts of each business differ, so please take professional advice before acting on it.