Write It Down Once: SOPs That Free a Founder From Daily Firefighting
If every problem still reaches your phone, the business runs on your memory. Simple SOPs move that memory onto paper so the team can work without you.

There is a kind of tiredness that only founders know. It is not the tiredness of hard work. It is the tiredness of answering the same question for the fifth time this month — how to pack the fragile order, what to say when a customer asks for a refund, which courier to use for outside Dhaka.
Each question is small. Together they fill the day. By evening you have solved twenty problems and moved the business forward by none.
Most founders call this "being busy". I call it running a company on one person's memory. As long as the knowledge of how things are done lives only in your head, every decision has to pass through you. The fix is not working harder or hiring a smarter manager. The fix is to write the work down, once, in a way people can follow.
Why the same fires keep starting
In a small company, the founder does almost everything at least once. That is how the business learns. The problem starts when the company grows and the learning never leaves the founder.
A new packer joins and learns from whoever is sitting next to him. A new page moderator copies the replies of the person before her, including the mistakes. Two people on the same team do the same job in two different ways, and both believe theirs is correct. When something goes wrong, nobody can say what "correct" was, because it was never written.
So the problem comes back to you. You decide, the fire goes out, and next week the same fire starts in a different corner. This is not a people problem. It is a missing system. In my experience, most repeated mistakes in a growing business are not caused by careless staff. They are caused by unclear instructions that each person fills in with their own guess.
What an SOP really is (and what it is not)
A standard operating procedure sounds like something from a large factory with thick binders on a shelf. That picture puts many founders off. They imagine weeks of writing documents nobody will read.
A useful SOP for a growing company is much simpler. It is a short, written answer to one question: how do we do this task here, every time? It names the task, who does it, when it starts, the steps in order, and what "done" looks like.
It is not:
- a policy manual full of rules about behaviour,
- a job description that lists responsibilities but no steps,
- a perfect document that covers every rare exception.
A good SOP fits on one or two pages. A new person can follow it on their second day without asking anyone. If it needs a training session to explain, it is too complicated.
Choosing what to write first
You cannot write everything at once, and you should not try. Start where the pain is. I use three simple filters to pick the first processes:
1. It happens often. Daily or weekly tasks — order confirmation, packing, customer replies, courier booking, daily cash count.
2. Mistakes are expensive. A wrong address, a wrong price quoted on the page, a payment recorded twice.
3. It still reaches you. If people keep asking you how to do it, that question is your first SOP.
Write down every task that passes all three filters. For most small companies the first list is ten to fifteen processes. That list is your plan for the next two or three months — one or two SOPs a week, not all of them in one weekend.
How to write an SOP your team will actually follow
The biggest mistake is the founder sitting alone and writing how the work should be done. The result is often neat and wrong. The better way is to write it with the person who does the job.
Here is a simple method that works in a shop, a factory floor or an online sales team:
1. Watch the work once. Sit with the person who does the task best. Let them do it normally while you note each step.
2. Write the steps in plain words. One action per line, in the order it happens. Use the words your team uses, in the language they think in. If your packers think in Bangla, write it in Bangla.
3. Add the checks. Where can it go wrong? Add a line: "Before sealing, match the item with the invoice." Checks are where an SOP earns its value.
4. Show, do not only tell. A photo of a correctly packed box or a screenshot of the right courier screen saves a paragraph of explanation.
5. Test it on someone new. Give the draft to a person who has never done the task. Every question they ask is a gap in the document. Fix it.
6. Name an owner. One person is responsible for keeping that SOP up to date. Not "the team" — one name.
A simple layout I like for every SOP:
- Task: what this covers
- Owner: who keeps it current
- When: what starts the task
- Steps: numbered, one action each
- Checks: what to confirm before moving on
- Done means: the result we expect
- If something goes wrong: who to call, and what to do first
Keep them all in one place everyone can open on a phone — a shared folder, a simple internal page, or a printed sheet on the wall where the work happens. An SOP nobody can find does not exist.
Making SOPs part of how the company works
Writing the document is the easy half. The hard half is making it the normal way of working. A few habits make the difference.
Train from the SOP, not from memory. When someone new joins, the SOP is the training. The senior person walks through it with them, step by step. This also tests the document again.
When something goes wrong, look at the SOP first. Ask two questions: was the SOP followed, and is the SOP right? If it was not followed, that is a coaching conversation. If it was followed and the result was still wrong, the document needs fixing. Either way, the fire becomes a lesson that is written down, instead of a lesson that lives in one person's head.
Review on a rhythm. Once a quarter, each owner reads their SOPs and updates what has changed — a new courier, a new price list, a new software screen. Old instructions are worse than none, because people trust them.
Let the team improve them. The person who does the task every day will see better ways before you do. Make it normal for them to suggest a change. When a suggestion is accepted, say so in front of the team. People follow rules they helped write.
What changes for the founder
When the first ten SOPs are written and followed, something quiet happens. The phone rings less. Questions that used to come to you are answered by a page. New people become useful faster. Managers can hold their teams to a clear standard instead of to "what the boss would want".
And you get your attention back. That is the real return. A founder's time is the most limited resource in a growing company. Every hour you spend answering the same question is an hour not spent on customers, partners, new products or the next business. SOPs do not make a company rigid. They make it calm enough for you to think.
This is also the first step to delegation that actually holds. You cannot hand over a job you have never described. Once the work is written down, handing it over becomes a decision, not a gamble. For help mapping and fixing the core processes in your company, see my business consulting work.
What to do this week
- Keep a list for five working days of every question your team brings to you about how to do something.
- Circle the three that come up most often or cost the most when done wrong.
- Pick one. Sit with the person who does it best and write the steps together — one page, plain words, with checks.
- Give that page to someone new and fix every point where they get stuck.
- Name an owner for it, put it where the team can open it on a phone, and tell everyone this is now the way.
Next week, do the second one. In three months, the business will run on paper instead of on your memory.
If you want a second pair of eyes on this for your business, book a free strategy call.