Process Optimization Without Permanent Project
7 Min. reading time
When a process in the mid-market gets stuck, the same sentence often follows almost reflexively: Let’s turn this into a project. Steering circle, milestone plan, external consulting. Six months later, the process is often just as sluggish as before, only more expensively documented. However, most bottlenecks in purchasing, sales, and back office can be solved with small levers that no one needs to inflate into a program.
Key Takeaways
- The project reflex costs more than it brings. According to McKinsey, large transformation programs miss their targets in around 70 percent of cases. The small, immediately measurable lever outperforms the program in almost every mid-market case.
- The levers are visibly available. Duplicate data entry in purchasing, delayed offers in sales, approval backlog in back office. Each of these points can be adjusted within two to four weeks.
- A short cycle outperforms the big plan. Observe, choose a lever, test for two weeks, measure, keep or discard. Whoever makes this a habit doesn’t need a permanent project.
Related:Productivity instead of savings program / When AI collaborates instead of assists
Why the project reflex is expensive
What is process optimization? Process optimization refers to the targeted improvement of workflows to make them faster, less error-prone, or more cost-effective. It ranges from the small adjustment of a single step to the complete redesign of a department. This range is often overlooked in the mid-market.
I’ve seen enough transformation programs from the inside to recognize a pattern. A process is annoying, someone names the problem, and the next step is a project. With a project comes structure: an assignment, a budget, a steering circle. That feels serious. But it’s also the moment when improvement slows down.
A project generates its own effort. Status reports, coordination rounds, a communication line. This is worthwhile for a genuine realignment. For a stuck approval step, however, the effort is out of proportion to the benefit. The improvement then disappears between two steering circle meetings, and after half a year, no one remembers the original pain point.
This quota has been stable for years and is no argument against change. It’s an argument against the size of the vehicle. Whoever ties an improvement to a program couples its success to the success rate of programs. Whoever keeps it small decouples it from that.
Three Places for Small Levers: Purchasing, Sales, Back Office
The most productive levers are rarely found where the organizational chart suggests complexity. They are located at the handover points where work is passed from one hand to another. Three examples from real mid-sized companies, anonymized.
Purchasing: double entry. In a mechanical engineering company, the purchasing department entered order data first into a supplier portal and then again into their own system. No one had ever decided on this, it had evolved over the years. The lever was a simple export-import comparison, set up once in a week. The purchasers gained almost an hour per day without a single steering committee meeting.
Sales: the quote that gets stuck. A trading company took an average of four days from customer request to quote. The actual calculation took twenty minutes. The rest was waiting time because the quote required approval from the department head, even for standard goods. The lever was a value limit: below a defined amount, approval is waived. The throughput time fell from four days to one.
Back office: the approval backlog. In the administration of a service provider, every invoice went through three signatures. The third was almost always a formality because the first two had already checked the content. The lever was to switch the third stage to random sampling. The invoices went through faster and the checked substance remained the same.
None of these three levers are intellectually demanding. The reason they were overlooked is banal: no one was responsible for finding them. This gap is exactly what a short cycle closes.
An Improvement Cycle in Four Weeks
Instead of a project plan, a repeatable rhythm helps. Four weeks, four steps, then start again. The cycle is deliberately short so it fits into everyday life without a special committee.
The crucial part is week four. A long-term project rarely knows a clean “no” because too much has been invested to abandon something. A four-week cycle is allowed to fail. This is what makes it honest. Discarded levers are no loss, they are the cheapest form of insight.
What makes the small lever tick and what holds it back
Even a small lever can fizzle out. Over the years, several conditions have emerged that regularly make the difference.
What holds it back
- Handling multiple levers simultaneously, making it impossible to attribute any effect clearly
- No predefined success metric, causing the test to end in a feeling rather than a number
- The lever affects one department, but was decided by another
- The improvement is not documented and is lost again after the next personnel change
What makes it tick
- Exactly one lever per cycle, with clear responsibility for implementation
- A single key figure that is agreed upon before the test and read honestly after the test
- The people who carry out the process daily are also involved in choosing the lever
- A brief entry in a shared list, ensuring the change survives the next changeover
The left column rarely has to do with ability. It has to do with discipline. One lever, one number, one responsibility. This sounds unspectacular, and it is. What’s spectacular is how reliably these three points determine success.
How individual levers become a habit
A single four-week cycle improves a process. It becomes interesting when the cycle doesn’t stop. After the first cycle comes the second, then the third. An action becomes a routine, and the routine no longer needs a project name.
For this to work, a clear, small framework is needed. A person who moderates the cycle without owning it. A fixed 30-minute appointment at the beginning of the month, where the last lever is evaluated and the next one is chosen. A visible list of previous levers, so progress isn’t lost in individual memories.
This is the actual difference to a permanent project. A project ends, often without effect. A habit continues, in small, verifiable steps. Medium-sized businesses rarely have a problem with understanding their processes. They have a format problem. The four-week cycle is a format that fits into everyday life.
If you want to improve something in the next quarter, you don’t need a program mandate. It’s enough to take a close look next week, see where work is waiting, and choose a single lever. The rest is repetition.
Frequently Asked Questions
When does a real project make more sense than a small lever?
When the change affects multiple departments structurally, introduces a new core system, or impacts the business model. Such projects require a mandate, budget, and steering. The mistake is not the project itself, but the project for a single bottleneck that could be resolved in two weeks.
How do you determine which lever to tackle first?
For one week, the parties involved note where work is waiting, duplicated, or backlogged. From this list, the point with the best ratio of effort to visible impact is chosen. Quick impact takes precedence over the absolute ranking of the problem.
Which metric is suitable for measuring success?
The simplest one that matches the bottleneck. Processing time for a task, number of returns, processing minutes per case. It’s essential that the number is agreed upon before the test and can be collected without significant effort. A rough, honest number beats a precise one that no one maintains.
Does the improvement cycle require external consulting?
Usually not. The people who execute a process daily know its weaknesses better than any external consultant. Consulting can help establish the rhythm in the first cycle. After that, the cycle should run on its own; otherwise, it’s just another project.
What happens to levers that don’t work in the test?
They are discarded, and that’s explicitly allowed. A discarded lever has shown in four weeks that it doesn’t deliver. This insight comes at a low cost and prevents the permanent dragging of an ineffective change. This clean “no” option is precisely what’s missing from most ongoing projects.
Editor’s Reading Recommendations
- AI in Accounting: 78 Percent Dark Entries in Medium-Sized Businesses
- Cloud Costs are a CEO’s Concern: When CFO and CIO No Longer Plan in Tandem
- M&A Rarely Fails Due to Price: 180 Days Make All the Difference
More from the MBF Media Network
Title Image: AI-Generated (May 2026)
