In short: Robert Nikic's guide to writing a small business operations manual: what to document first, a simple one-page template and how to keep it current.
Take two weeks off. Not as a reward. As a test.
If the business stalls, drifts or calls you every day while you're gone, you don't have a company yet. You have a job with employees.
I've watched a lot of founders build something real and then get trapped inside it. Every decision routes through them. Every new hire learns by watching them. Every problem waits until they're back. They're not controlling on purpose. They just never wrote anything down.
An operations manual fixes that. It doesn't have to be fancy, and it doesn't have to be finished. It has to exist.
What an operations manual actually is
Forget the image of a thick binder nobody opens. A good operations manual is a set of short documents, one per process, that let a reasonable person do a task right without asking you.
That's the whole standard: someone new can follow it and get the result you'd expect.
Step 1: List what would break if you disappeared
Sit down with a blank page and list every task that would stop, slow down or go wrong if you weren't there for a month.
Common ones I see:
- Sending quotes and setting prices
- Onboarding a new customer
- Paying suppliers and running payroll
- Handling a complaint or a refund
- Hiring and training someone new
- Ordering inventory
- Closing the books at month end
Don't try to document everything. Circle the ten that would hurt most. Start there.
Step 2: Record yourself doing it
The fastest way to write a process is to stop trying to remember it. The next time you do the task, record your screen or have someone take notes while you talk through each step out loud.
You'll be surprised how many steps you do automatically. Those invisible steps are exactly what new people miss.
Step 3: Write it on one page
Every process gets one page. If it needs more, it's probably two processes.
Use the same format every time, so people always know where to look:
Process: Onboarding a new customer Owner: The person responsible for keeping this page accurate Starts when: The signed contract arrives Steps: Numbered, short, one action per line Done looks like: What a finished result looks like, specifically Watch out for: The two or three mistakes people usually make Last checked: The date someone last confirmed this still works
The "done looks like" line matters more than people think. Most mistakes I've seen aren't from skipping steps. They're from different people having different ideas of what finished means.
Step 4: Have the newest person test it
Hand the page to the person on your team with the least experience doing that task. Ask them to follow it exactly, with no help.
Wherever they get stuck, the page is wrong, not them. Fix it on the spot. Repeat until someone new can get it right on the first try.
Step 5: Put it where the work happens
A manual nobody can find is the same as no manual. Keep everything in one shared place your team already uses, organized by area: sales, customers, money, people, operations.
Link to the right page from wherever the task starts. If refunds are handled in your help desk, the refund process should be one click away from it.
Step 6: Give every page an owner
Processes change. Software updates, prices move, people find better ways. A page with no owner goes stale, and a stale page is worse than none because people trust it.
Every page gets one name. That person updates it when the process changes and checks it on a regular schedule.
Step 7: Update it every time a mistake repeats
Here's the rule I like best. The first time a mistake happens, it's a mistake. The second time, it's a missing line in the manual.
Every repeated error should end with someone updating a page. Over time, the manual becomes a record of everything the company has learned the hard way, so nobody has to learn it twice.
A simple operations manual template
Use the same layout for every page:
- Task: what the page covers
- Owner: the one person responsible for keeping it current
- When it happens: the trigger or schedule
- Tools: the software and materials needed. Keep passwords in a secure password manager, never in the manual
- Steps: numbered, one action each
- What good looks like: the result someone should see when it's done right
- Common mistakes: the errors that have happened before and how to avoid them
- Last updated: the date and who changed it
Keep each page to one screen. Group the pages by area, such as sales, delivery, finance, hiring and customer service, so people find them fast.
Quick answers
How do you write an operations manual for a small business?
Start with the tasks that would break if you disappeared, record yourself doing each one, write it up as one page with numbered steps, then have your newest team member test it. Fix every point where they get stuck.
What should a small business operations manual include?
One page per recurring task, each with an owner, the trigger, the tools, numbered steps, what a good result looks like and the common mistakes. Group the pages by area so they're easy to find.
What is Robert Nikic's advice on operations manuals?
Robert Nikic's advice is to start small and write down the work only the founder knows how to do. A short manual people actually use beats a thick binder nobody opens.
What changes when you do this
The founders I've seen do this well describe the same things:
- New hires get productive faster, because they're not waiting for someone to show them.
- Quality gets more consistent, because everyone works from the same page.
- The founder gets time back, because questions get answered by the document instead of a meeting.
- The company is worth more, because it can run without one person holding it up.
That last one matters more than most founders realize. A business that depends on one person is a risk to everyone who works there, buys from it or might buy it someday.
Start small
You don't need to write all of it this week. Write one page. Test it. Then write the next.
Ten good pages will change how your company runs more than a hundred you never finish.
If it only lives in your head, it isn't a process. It's a single point of failure.
Related reading
- Stop apologizing for your price
- Investing in people first
Robert Nikic is an entrepreneur, TEDx speaker and advisor on innovation and economic growth. He writes about what he has seen build and break companies, and about the rules that decide whether small businesses get a fair shot. Read his writing on Medium, the Open Doors newsletter on LinkedIn and daily posts on X.
