Almost every business owner has said some version of the same line: "I explain it, and everyone still does it their own way." It usually reads as a lack of commitment. It almost never is.
In industrial engineering this has a name, and the name isn't communication. It's variation.
A process with variation produces different results every time it runs, even when the input is the same and even when the people are good. And the discipline for reducing it doesn't start with motivating the team. It starts with admitting that if the result depends on who did it, what's missing is a definition.
A familiar case
An operation that produces documents for clients ends up with three people doing the same work. The three deliverables come out different. Not in one small detail: in everything.
Different from the moment the request comes in. Different in what counts as enough to call something finished. Different in the order of the information. Different in the format that reaches the client's hands.
None of the three is doing a bad job. Each one has a reasonable standard, built out of their own experience. The problem is that the standard lives inside each person's head and nowhere else.
And when the deliverable is the product, that stops being a question of style. If two people hand back different results from the same input, the client can't trust either one of them.
What doesn't work
The first thing anyone tries is asking that things get done "the same way." Explain it better, insist more, check in more often.
It doesn't work, because "the same way" means nothing if nobody wrote down what it looks like. Everyone keeps their own version of correct, and the conversation turns into an argument about standards, which on top of it all wears down people who are doing good work.
What does unlock it
Three things, and the order matters.
Documenting each client's requirement. Before defining how something gets done, you have to know what the person asking for it expects to receive. Not in general terms: client by client, with what they need and what is of no use to them. That part looks obvious and it tends to be the part that's missing.
Standardizing the whole process, not just the deliverable. From how the request comes in to how the document goes out. It's tempting to fix only the part the client sees, but if the intake of information varies, the result will vary no matter how clean the final format looks.
Leaning on artificial intelligence tools to hold it in place. Not to have them write for anyone, but so the standard gets applied evenly: checking that every delivery follows the defined structure, reviewing consistency, flagging what's missing. The tool doesn't set the standard, it holds it up when there's volume and time pressure.
The result isn't that everyone writes alike. It's that the client receives the same thing no matter who produced it, and that someone new can come in without repeating years of learning.
What this looks like in other businesses
The example comes from desk work, but the shape is the same in any operation with more than one person.
"Get the room ready" produces a different result depending on who hears it. "Take good care of the group" does too. "Send it out when it's done" does too.
None of those instructions is wrong. All of them are incomplete, because they leave the standard to whoever receives them. And when each person sets the standard, the result varies.
Where to start if this sounds familiar
There's no need to redesign the whole operation. It's enough to take the task that comes out different most often and ask it three questions.
What exactly the person requesting it receives, in their own words and not in yours. What steps it has from the start and not just from the visible end. And how you check that it came out right, without depending on someone remembering to look.
Once that's written down, most of the errors that looked like attitude stop happening.
What it costs to leave it alone
Variation doesn't show up on the income statement under its own name. It shows up spread around: in the work that gets redone, in the client who complains about something that was fine last time, in the owner's hours spent resolving what had already been explained, and in how long it takes someone new to become useful.
All of that gets paid for. It just arrives without a label.
At Kiin Hub we're putting together a biweekly table to work through this kind of thing: someone comes in, lays out their situation, and whoever is at the table weighs in from their own field. Accounting, tax, compliance, sustainability, processes. No cost and no pitch. If you'd like us to let you know about the first one, send us a message.
Share this article