Someone on your team takes a week off, and that same week the quality of the work drops. Your customers notice too, even if they never say so.
That means the work has not become a system yet. Most people assume having a system means good software and a few written procedures, but the real test is something else.
What is a system?
A system is a defined path from an input to an output. An order comes in, a few things get done to it, and a properly packed parcel goes out to the customer. But every task in every business looks like that, so the definition on its own does not tell you which work has become a system and which has not.
What separates a system from an ordinary task is that its output is predictable. The same input comes in and roughly the same output comes out at the same quality, regardless of who was behind it or what kind of day they were having.
There is a simple test for it. If someone else does this job tomorrow instead of the usual person, will the customer notice the difference? If the answer is yes, the work is not a system yet. It only lives in one person’s head and hands.
Tidiness, procedures and software are still not systems
Three things get confused with systems, and that confusion is what makes you think you have one.
- Being tidy. Files and messages are where they should be and everything is easy to find, but none of that touches whether the output is consistent. A warehouse can be immaculate and still send a short order out every time.
- Written procedures. Writing them down is necessary but not sufficient. Until someone else has actually worked from the document and produced the same output, it is just a piece of text.
- Software. This is always the last step, never the first, because it only makes an already clear path faster and less error-prone. If you still do not know what the right path is, software just repeats your mess faster and at greater expense.
The real test is consistency, not freeing yourself up
Most of what gets said about systemization focuses on being able to go away on holiday while the business keeps running. That is true, but it is a side effect, not the goal itself.
What the customer actually feels is consistency. Every customer, every time they come to you, gets the same quality, regardless of who answered them or what day of the week it was. Once the result is consistent, you no longer have to stand over everything yourself. But if all you are chasing is getting yourself out of it, you hand the work over, the quality goes a different way every day, and customers leave without a word.
Consistency matters enough that an entire global standard is built around it. According to the International Organization for Standardization’s annual survey, there are close to one and a half million valid ISO 9001 certificates in the world, and at bottom the standard says only one thing: define your work so that its output is, every time, what you promised the customer. A small business does not need certificates and audits to get there, because the idea itself works just as well for a café with three staff.
The café example
Picture a small café with three baristas. The quality of the coffee depends entirely on who happens to be at the machine, because each of them judges the dose, the milk temperature and the extraction time by feel.
A customer who had an excellent latte on Tuesday gets a bitter, thin one on Thursday and concludes that this café is not consistent, with no idea that all that changed was the barista.
Now picture writing a specific recipe for each drink, with exact numbers for dose, temperature and time, and all three working from it. You get roughly the same cup every time, and the customer stops gambling on who is on shift today. In the first case quality is a property of the people, in the second it is a property of the café.
How to turn one task into a system
Take one of the repeating jobs in your business and put these five steps to it.
- Define the right output. Write down exactly what an acceptable result looks like, say an order shipped within twenty-four hours with the correct invoice. Until that is clear you cannot tell whether the work is consistent or not.
- Write the path down once. Put the job you currently do by feel and habit on paper, plainly, so that a newcomer could work straight from it.
- Turn judgment calls into rules. Anywhere a person decides by personal taste is the biggest source of inconsistency. For example, if a customer has not heard back within two days, an apology message with a small discount goes out.
- Test it with someone else. Hand the document to someone who has never done the job and see whether the same output comes out. That is the only way to find out.
- Give yourself one signal. A simple number, like how many orders went out late, that tells you whether the output is still where it should be or drifting away from it.
Next time you want to know whether a job has become a system, do not count your procedures. Ask yourself whether the customer would notice if the person behind it changed. The answer to that one question tells you whether you are still person-dependent or you genuinely have a system.