Process First, Then Growth

Growth is supposed to be the good part. Then it arrives and the business gets louder. More clients means more scheduling, more chasing, more questions that only one person can answer, and a diary that stops having any gaps in it.

The instinct is to hire. It's often the right instinct. But bringing people into a business that hasn't written down how it works just means more people working from the same incomplete picture, all at once.

Process isn't what you do instead of growing. It's what makes growth survivable.

What a process actually buys you

A process is a decision you make once instead of every time. That's all. The value is boring and enormous.

• Consistency - the job comes out the same way whoever does it, so the standard doesn't depend on who was rostered
• Speed - the steps are already decided, so starting doesn't require thinking
• Capacity - work that used to need your attention can run without it
• Quality - errors get caught by the process, not by a client
• Cover - when someone's away, the work continues instead of pausing

The last one is the one people undervalue until someone resigns.

Why the process usually doesn't exist

It isn't neglect. At small scale, memory is a genuinely good system - fast, flexible, zero setup cost. The trouble is that nothing ever triggers the upgrade. There's no meeting where someone says the business has outgrown remembering, because each day's increase is too small to notice.

So the business grows on a foundation built for its smaller self, and the first sign of trouble is usually a mistake in front of a client.

How to build it so it actually holds

This maps to the Systems Architecture, Implementation & Integration and Sustained Performance phases of our Operational Excellence Framework.

1. 1

   Start with the processes that hurt. Don't document everything. Find the three or four that cause the most rework, interruption or missed dates, and start there. Everything else can wait.

2. 2

   Watch the work being done. Never ask someone to describe their job from memory. Sit alongside them and watch it happen. The steps they'd forget to mention are usually the ones that matter.

3. 3

   Write it for the person doing it. Short, numbered, verb-first, with screenshots where a system is involved. If it runs longer than two pages, it's two processes.

4. 4

   Put it next to the task. Attach the process to the recurring task where the work is scheduled. If someone has to go and find the procedure, they won't.

5. 5

   Give it an owner and a review date. Every process needs one named person responsible for keeping it current, and a date that forces the check. Processes drift; only ownership stops that.

6. 6

   Test it by handing it over. Next time the task comes around, someone else runs it with the original owner on standby. Gaps surface immediately and you fix them on the spot.

What this looks like in practice

An Australian services business we work with had grown to the point where the founder was still the routing layer for everything. Quotes, scheduling, client questions, invoicing - all of it passed through her, and the team had learned to wait rather than decide.

We didn't reorganise anyone. We documented the handful of processes that ran through her, moved each one's steps onto the recurring tasks in their system, and gave each an owner who wasn't her. The visible change was that quotes went out the same week. The less visible one was that decisions started getting made without her, correctly.

Quick self-check

If you answer "no" to more than one, your growth is currently capped by your diary rather than by your market.

Your task for this week

Name the one process that, if it stopped working, would cost you the most. Then sit with whoever does it and watch it done once. You'll find two or three steps nobody knew were missing.