Business process improvement works when it is owned as a permanent routine rather than purchased as a finite engagement. A project produces documents and a temporary lift. An owned routine produces a standing capability that keeps finding and removing friction long after the outside help leaves. Structure decides the outcome more reliably than the quality of the analysis.
A Project Buys a Snapshot, Not a Capability
Process work sold as a project has a defined start and a defined finish. The finish is a deliverable, usually a map of how work currently moves and a ranked list of changes worth making.
That deliverable is accurate on the day it is handed over. It describes a business staffed by the people who were present, serving the demand that happened to arrive during the interview weeks.
None of those conditions stay still. People leave, volume shifts, a supplier changes terms, one customer segment grows faster than the others. The map remains accurate about a company that no longer exists.
A capability behaves differently. It does not describe the business at a moment. It describes how the business notices friction and removes it whenever friction appears, which is continuously.
The distinction matters because buyers rarely think they are choosing between the two. They believe they are choosing a provider, a price, and a timeline. The choice underneath is whether improvement will live inside the company or visit it.
Decay Is the Default Condition
Improvements fade for reasons unrelated to the quality of the original analysis. Every process sits inside a system of people who protect their own workload before they optimise the whole.
A step that shields the finance team costs the sales team an afternoon. The sales team invents a workaround. The workaround becomes normal, and the documented process quietly stops describing reality.
This is not misconduct. It is how competent people behave when a rule obstructs work they are accountable for delivering. Nobody announces the deviation because nobody experiences it as one.
Half a year after a redesign, the observable process is a blend of the new design, the old habits, and the workarounds invented in between. No single person can see the blend. Each person only sees a portion of it.
By then the outside adviser is gone. The staff who lived through the redesign have moved on or moved up. What remains is a document nobody reads and a practice nobody examines.
Decay is not a sign that the work was poor. It is the expected behaviour of any process left without a maintainer, in the same way an unattended garden reverts regardless of how well it was planted.
Ownership Is the Structural Variable
The difference between an improvement that lasts and one that fades is rarely the sophistication of the method. It is whether a named person owns the process after the engagement closes.
Ownership here means something narrow. One person is accountable for the outcome the process produces, holds authority to change the steps, and reviews it on a fixed cadence whether or not anything looks broken.
Most businesses have none of the three. Processes are owned collectively, which means owned by nobody. Authority to change them sits above the people who can actually see the problems.
Review happens only after failure. A missed shipment or an angry customer triggers examination, which guarantees that examination is always defensive and always late.
Splitting accountability from authority is the most common version of this failure. A supervisor is measured on an outcome but cannot alter the steps that produce it. That arrangement generates escalation, not improvement.
A structured way of treating process improvement as a standing discipline rather than a one-time exercise puts ownership at the front of the design rather than at handover.
What Buying a Routine Looks Like
The purchasable version of a routine differs from the purchasable version of a project, and the difference is worth stating plainly.
A project engagement is scoped by deliverable. A routine engagement is scoped by transfer. Success is not measured by what the outside party produced, but by what the internal team can do unaided afterward.
That changes the sequence of the work. Rather than analysing everything and presenting findings, the work takes one process, runs the full loop on it, and puts an internal owner in charge immediately.
The loop itself is unglamorous. Define the outcome the process exists to produce. Observe how work actually moves rather than how it is supposed to move. Remove steps that produce no outcome. Set a review date. Repeat.
Running that loop once teaches nothing durable. Running it three times on three different processes teaches a team the pattern, and the pattern is the asset being bought.
Outside expertise is real and it is temporary by design. Its job is to compress the learning curve, not to become the permanent place where process knowledge lives.
A useful test exists for any proposal. Ask what the internal team will be able to do in six months that it cannot do today. Vague answers to that question predict a binder.
Why the Project Version Keeps Getting Bought
Businesses keep choosing the project because the project is easier to approve. It has a price, a duration, and a document at the end that justifies the spend to anyone who asks.
A routine has no natural stopping point, which makes it awkward to put in front of a board or a lender. Budgets are built around things that finish.
The project also protects the buyer from an uncomfortable premise. Owning a routine means accepting that the business generates its own friction and will keep generating it. That is harder to sit with than the idea that a specialist can arrive and fix things.
A quieter reason sits underneath. A project can be delegated downward and forgotten. A routine requires the person at the top to keep asking about it, which costs attention every month rather than money once.
Providers respond to what buyers approve. The market supplies projects because projects sell, and the resulting body of work reinforces the belief that improvement is something a business receives rather than something it does.
Working through what operations support actually costs and which businesses genuinely fit it tends to move the conversation from duration toward ownership, which is where it belongs.
Compounding, and How to Start
The case for the routine is not that it wins in the first quarter. In the first quarter the project usually looks better, because a project concentrates effort and produces visible artifacts quickly.
The case is what happens afterward. A project delivers a step change followed by a slow slide back toward the earlier condition. A routine delivers smaller steps that do not slide, because the mechanism producing them is still running.
Two years out the comparison is not close. The business that owns the routine has removed friction no adviser ever saw, in corners nobody thought to examine. The people doing the work now hold a method for examining it.
The business that bought the project has a binder, a memory of a productive quarter, and a growing suspicion that another engagement will be needed soon.
Compounding is the whole argument. Small improvements that persist beat large improvements that decay, and the crossover arrives earlier than most owners expect.
Nothing about the routine requires an outside party. The method is simple enough to begin internally, and beginning internally is often the better test of whether the business is ready for more.
Pick the process that generates the most complaints from customers, not the one that generates the most complaints from staff. Friction the customer can feel is the friction that costs money.
Name one owner. Give that person authority to change steps without assembling a committee. Set a monthly review that happens even when nothing seems wrong, because reviews triggered only by failure teach everyone that failure earns attention.
Write down what the process is meant to produce before writing down how it works. Most process documentation skips the purpose and goes straight to steps. That is why so much of it survives long after the purpose has changed.
Then run the same loop on a second process, with the first owner acting as coach rather than doer. Transferring the method is the entire point of the exercise.
Resist the urge to start with the largest process in the business. Large processes cross departments, involve competing incentives, and take months to change. A small process finished completely teaches more than a large one abandoned halfway.
The first cycle will feel slow and slightly awkward. That is normal, and it is also the cost of building something that does not need to be repurchased next year.
Process work carries a reputation problem it earned honestly. Too many owners have paid for analysis, watched the gains fade, and concluded the discipline does not work at their scale. The discipline works. The purchase structure was wrong. Improvement that belongs to someone inside the building outlasts improvement delivered to the building and left there. That difference is available to any owner willing to name a person and hold a review.
Frequently Asked Questions
How long before process improvement shows results?
Single-process changes usually show measurable relief within a month or two, because most friction sits in obvious handoffs. The durable gains take longer and arrive differently. They come from the second and third cycles, when the team starts finding problems without being prompted. Owners expecting one dramatic before-and-after are usually measuring the wrong thing.
Should you hire an outside adviser or build the capability internally?
Both, in that order, with a defined end to the outside part. An adviser compresses the learning curve and brings pattern recognition from other operating environments. What an adviser cannot do is stay long enough to own the routine, and any arrangement assuming otherwise creates dependence rather than capability. The real test is what remains six weeks after the engagement closes.
Which process should be improved first?
The one where customers feel the friction, not the one where staff complain loudest. Staff complaints tend to cluster around irregular, judgment-heavy tasks that resist standardisation. Customer-visible friction is repetitive, high in volume, and directly connected to revenue. Starting there also builds internal support, because the improvement is visible to people outside the team doing the work.
How do you stop a documented process from going stale?
By reviewing it on a schedule rather than after an incident. A short monthly review by the process owner catches drift while it is still small and cheap to correct. Documentation opened only during onboarding or after a failure will always lag actual practice. The review matters more than the document.
Is this worth doing in a business with a small team?
Smaller teams often gain more, because a single broken handoff consumes a larger share of total capacity. The method scales down cleanly, since fewer people means fewer stakeholders to align and faster decisions about changing steps. What smaller businesses lack is slack, so the work has to be sized to fit alongside operating duties. One process at a time is the realistic pace.
What is the most common reason improvement efforts fail?
No named owner once the work concludes. The analysis is usually sound and the recommendations are usually reasonable. What is missing is a person holding both accountability for the outcome and authority to change the steps. Without that pairing, the process reverts to whatever arrangement causes the least friction for the people executing it.
No comments:
Post a Comment