Anyone setting out to systematise their business almost always arrives at the same picture: at the end there is a folder with a written procedure for everything. That picture is the reason most systematisation projects fall asleep in month three. It is not too ambitious; it aims at the wrong quantity.

Fully documented is not the same as independent

A business can have every activity described and still be exactly as dependent as before. That happens whenever what got documented was what was easy to write down rather than what actually hangs on the owner. Invoicing runs are quickly captured. The question of who may approve an exception still sits nowhere afterwards.

So the productive question is not “which processes do we have?” but “which processes carry dependency today?”. In an owner-led business those are typically decision paths, approvals, client handovers and the knowledge that lives in one head. The rest usually runs anyway.

Four checks before any documentation

Frequency: is it needed more than three times?
Transferability: can someone else run it afterwards?
Time value: does the description save more than two hours?
Describability: can it be captured at all without the description growing longer than the task?

What the evidence says

That structured management practices work is not merely plausible, it has been tested experimentally. Bloom, Eifert, Mahajan, McKenzie and Roberts published a randomised field experiment in the Quarterly Journal of Economics in 2013: introducing documented procedures and performance monitoring raised productivity by roughly 17 per cent within a year. The finding that matters more here sits next to it: measurable delegation to plant managers followed. Structure produced handover, not just order.

The limit of that figure belongs with it: the measurement took place in Indian textile firms. The direction holds; the 17 per cent is not a commitment for a DACH consulting business.

The uncomfortable rule

From all of this follows a rule that sells badly and works well: as little systematisation as possible, as much as necessary. Standards are set where they reduce dependency — not across the board. A business with twelve well-chosen descriptions where approvals run without the owner is further along than one with a hundred documents and an unchanged constraint.