Why informal processes stop working

Every business starts with shortcuts. Someone orders the packaging, someone else raises the invoices, and the whole thing runs on memory, goodwill and a few shared spreadsheets. It works — until it doesn't. Somewhere around the point you take on your fifth or tenth employee, the cracks appear. An order sits unprocessed because the person who usually handles it is on holiday. A new starter spends their first fortnight asking colleagues the same questions. A customer chases an invoice that nobody realised hadn't been sent.

None of this means you have hired badly or that the business is failing. It means your operation has outgrown the informal system that carried it this far. The fix isn't a costly overhaul. It's deliberate tidying: writing down what you already do, deciding who owns each piece, and removing the places where work piles up.

Map what actually happens, not what should happen

Before you change a single thing, get the truth on paper. Sit with the people doing the work and walk through a real example, start to finish. Pick three of your most frequent journeys: taking and fulfilling an order, invoicing and chasing payment, and bringing a new client or team member on board.

For each one, note every step, every handover and every tool involved. You will usually find a few predictable things:

• The same information is typed into two or three different systems.
• A step exists only because someone once asked for it and nobody has questioned it since.
• Two people are quietly doing overlapping work, or nobody is doing a step at all.
• Everything depends on one person's inbox.

Capture this as a simple numbered list, not a diagram in specialist software. A shared document anyone can edit beats a beautiful flowchart nobody updates.

Document the tasks that carry the most weight

You don't need a manual. You need a short, plain-English process note for the eight to twelve tasks that cause the most pain when they go wrong. Think quotes and proposals, taking payment, ordering stock, onboarding a new client, month-end bookkeeping, handling complaints, and the weekly report your biggest customer expects.

Each note can fit on a single page. Include:

• A trigger — what starts things off, such as a signed order landing in the inbox.
• The steps, in order, with the actual screen names or file locations people need.
• The owner — the one person accountable for the process running properly.
• What good looks like — the deadline, the standard, the checks that must happen before something is called done.
• Common failures — the two or three things that most often go wrong, and what to do about them.
• Escalation — who to ask when something unusual happens.

Write them with the person who does the job, not for them. A note written by someone who has never processed a refund will miss the details that matter.

Give every process a named owner

Shared responsibility sounds generous and behaves badly. If three people are responsible for credit control, the likelihood is that nobody is. Every documented process needs one named owner whose job it is to keep it working, train new people on it and flag when it breaks.

Being the owner doesn't mean doing every step. It means being the person who notices. Distinguish clearly between the owner and the doers, and make sure someone else can cover each critical step during holiday, sickness or a busy spell. Test that cover occasionally — ask a colleague to run the process while the usual person watches. You will learn more in an hour than in a week of planning.

Find the bottlenecks, then fix one at a time

Bottlenecks cluster in predictable places: approvals that wait for a founder, work that batches up until Friday, and any step requiring information to be re-entered by hand. Measure a couple of simple things for a month — how long an order takes from confirmation to invoice, how many handovers it passes through, and how often work comes back to be redone.

Those three numbers will point you at the problem far faster than instinct will. A process with nine handovers and no waiting time is fine; a process with two handovers and a two-day queue at one of them is not. Fix the single worst bottleneck, give it a fortnight to settle, then look again. Trying to fix everything at once is how improvement projects quietly die.

Keep it alive with a light rhythm

Documentation rots the moment it stops being used. Protect it with a small, regular habit rather than a grand annual tidy-up. A 45-minute operations review once a month, with the people who own the key processes in the room, is enough. Ask three questions: what broke since we last met, what change would stop it breaking again, and who owns that change by when.

Keep every process note in one obvious place, link it from your onboarding checklist, and update it whenever something changes — a new system, a new customer requirement, a new team member. When someone leaves, their process note is the difference between a smooth handover and three weeks of confusion.

None of this is glamorous. But a growing company that writes down how it works, names an owner for each piece and reviews the awkward bits is a company that can add people, customers and volume without everything creaking. Start with the process that irritates you most this week, and write one page about it today.