Do you start process improvement with the friction or with the process map?
Do you start process improvement with the friction or with a complete map from A to Z? Almost every business owner asks that question once the work stops running smoothly. The honest answer is both, but in a fixed order. Reverse that order and you lose months. Stop halfway and you fix the wrong thing.
You usually only notice once it has been going on for a while. Jobs sit around longer than they need to. A quote goes out and afterwards nobody knows who is doing the follow-up. Something falls between sales and delivery, and the customer rings three days later to ask how things stand. You can feel time leaking away, but you cannot point to exactly where. So you want to make it more efficient. You just do not know where to start.
At that point you see two reflexes. The first: map everything. You want to draw out every process in the business, from the first customer enquiry to the last invoice, so you have the complete picture. That feels thorough. In practice you are busy for months and nothing changes on the work floor in the meantime. Your team sees workshops being held and carries on working with the same frustrations.
The second reflex is the exact opposite. You see where it pinches and you fix that part straight away. An extra check, a new list, an automation. That feels decisive and sometimes delivers something in the first few weeks. But after a few months the same problem pops up somewhere else, in a different form. Then you have one more check and the problem still has not gone away. Both reflexes are understandable, but each one only solves half of it.
Where it hurts is rarely where it starts
The friction tells you which process to tackle first. Nothing more. Choose a process that takes a lot of time, that causes frustration, or that everyone in your team brings up immediately when you ask where things are not running well. That is where most of the gain lies. It is also where you win your people over fastest, because they have been complaining about that one thing for weeks. You do not need to convince them of anything.
After that you have to resist the reflex to start fixing straight away. That is where most businesses go wrong. The place where it hurts is often not the place where the problem starts. A complaint about slow delivery can start with an unclear intake two departments earlier. A pile of open questions in the accounts team can start at a step nobody feels responsible for.
With one client recently, it looked as though a process simply had far too many steps. The logical response was to start cutting. When we mapped the whole process, it turned out the problem was not the number of steps. There was one step that nobody owned. Every question that arrived there stayed put until someone else happened to pick it up. If you only look at the one bottleneck, you never see that. Had we cut those steps, the process would have been shorter and the same question would still have been left lying. Just faster.
So the order is simple. Let the friction decide which process you choose. Then map that one process completely, from A to Z. Only once you understand where it goes wrong do you start building. So in that first week, do not reach for a new tool, an extra check or a different list.
Five questions per step
Mapping sounds bigger than it is. You do not need special software or a thick process manual. A whiteboard or a large sheet of paper and an hour with the people who actually do the work is enough. The difference lies in what you ask at each step. Five questions take you a long way, and together they show exactly where the work gets stuck.
The framework: what, time, owner, waiting, needed
For each step you ask: what exactly happens here? How much time does it take? Who is the owner? Who are you waiting for? And what do you need to be able to move on? The first two questions describe the work. The last three show where it gets stuck. For most business owners with a team of ten to thirty people, it goes wrong at the owner or at the waiting, rarely in the work itself.
If you do that consistently, you suddenly see everything. You see steps nobody needs, that crept in at some point and were never removed. You see waiting times that are invisible on paper but cost days in practice. And you see people doing the same work, each in their own way. That happens more often than you think.
Do pay attention to who is at the table. If you map the process with managers only, you get how it should run, not how it does run. Bring in the people who carry out the steps every day. They know which email always arrives late and which form nobody fills in.
One process a week, not everything at once
The second thing that goes wrong is the scope. As soon as business owners see how much one map delivers, they want to do the whole business at once. Then you are busy for months and nothing changes in the meantime. Do one process at a time instead, for example one a week. The first version does not need to be perfect, it needs to show where it goes wrong. A map with gaps that you act on delivers more than a perfect map sitting in a drawer.
Do the sums. One process a week, kept up for a few months, and you have worked through all ten or twelve processes that really matter at least once. By then you are already much further than most businesses. Every process you solve makes the next one easier too, because your team now knows how it works and comes forward with bottlenecks themselves.
The friction shows where you start. The map from A to Z shows what is really going wrong. Only then do you start building. Business owners who stick to this order do not need to launch large improvement programmes. This week they pick one process the team complains about, map it with five questions per step and solve the real cause. Do you notice things pinching in your own business but do not know which process to start with? At Lead Innovation we are happy to make that first map together with you.