Process Optimisation: 8 Methods Compared in Practice

Many project service providers only start looking at their processes once things have already become expensive. Billing takes two weeks instead of two days. Quotes sit in approval loops for days. Project managers rebuild the same reports by hand every month. Each of these frictions costs billable hours and depresses the margin without ever showing up in a metric.

Process optimisation starts exactly here. It makes visible where time drains away and provides a structured approach to improving workflows measurably. Choosing the right method determines both effort and impact. A Six Sigma programme takes months, a 5 Whys analysis takes an afternoon. This overview places 8 proven methods in context, each with a practical example from the project business and an honest assessment of effort and benefit.

The key points at a glance:

• 8 methods cover different situations: from quick root cause analysis (5 Whys) to structural redesign (BPM).
• The effort to introduce them ranges from a single workshop to multi-year programmes. The comparison table below places all 8 methods.
• Every method needs reliable data on working hours and project effort. Without that basis, optimisation stays guesswork.
• For project service providers, portfolio analysis is the best starting point: it settles which process gets optimised first.

What is process optimisation?

Process optimisation is the systematic analysis and improvement of business processes with the aim of increasing efficiency, quality and profitability. It is the operational part of the broader discipline of process management: while process management designs and steers workflows, process optimisation improves individual processes in a targeted way.

In the project business this has a direct commercial dimension. A consultancy with 50 employees, where each specialist loses just two hours a week to avoidable routine tasks, loses around 5,000 hours over the year. At an hourly rate of €120, that equals €600,000 in revenue potential. Process optimisation is therefore not a housekeeping task. It is margin management.

The foundation of every method is reliable data. Only once working hours and project effort are properly recorded via project time tracking can you measure which process ties up how much time and whether an improvement actually works.

8 methods for process optimisation

Which method fits depends on three questions: how big is the problem? How much time and budget are available for the rollout? And should a single process or the entire organisation be improved? The following 8 methods cover that spectrum.

1. The Six Sigma method

Six Sigma minimises variation and errors in processes on the basis of statistical data. At its core is the DMAIC cycle (define, measure, analyse, improve, control), which defines, measures, analyses, fixes and permanently controls problems using data:

Practical example: an IT consultancy finds that around 15 per cent of client invoices are disputed. In the measure phase, an analysis of time entries shows that service descriptions are inconsistent and clients cannot trace individual line items. The improve measure is a binding set of booking standards per project. Within two quarters the dispute rate falls below 5 per cent.

Effort and benefit: the rollout effort is high. Six Sigma needs trained owners and a clean data basis over several months. The typical effect is measurably fewer errors in high-volume processes such as billing and reporting. For companies with fewer than 20 employees, the method is usually oversized.

2. Continuous improvement (Kaizen)

Kaizen is a Japanese work philosophy of continuous improvement in small steps. Instead of large redesign projects, each team continuously improves its own day-to-day work. Kaizen distinguishes three types of waste:

• Muda (waste): activities that consume resources but create no value.
• Mura (unevenness): uneven workload, such as idle time in one team alongside overload on the neighbouring project.
• Muri (overburden): sustained overstretching of people or systems.

Practical example: an engineering firm introduces a weekly 15-minute retrospective per project team. After three weeks, something stands out: two status reports contain the same information for different recipients. One is dropped, saving each project manager around two hours a week. A small improvement with a lasting effect.

Effort and benefit: the rollout effort is low; Kaizen starts with a single team meeting. The effect comes from accumulation: many small improvements add up over months into noticeable capacity gains. The prerequisite is commitment. Without a fixed rhythm, the process fizzles out within weeks.

3. The 5 Whys method

The 5 Whys method identifies the actual root cause of a problem. Those involved repeatedly ask "why?" until they reach the root of the issue. Five iterations are usually enough.

Practical example: at a consultancy, project billing is delayed by several days every month.

"Why is billing delayed?" Because project hours are incomplete at month-end.

"Why are the hours incomplete?" Because many consultants only enter their hours at month-end.

"Why do they only enter them at month-end?" Because recording is cumbersome and runs in a separate tool.

"Why does it run in a separate tool?" Because time tracking and project management were never brought together.

"Why were they never brought together?" Because nobody owns the process from time entry to invoice.

The cause is a systems decision, not a question of discipline. Data from project controlling makes such analyses robust, because it shows where time and budget deviations actually arise.

Effort and benefit: the effort is minimal; a facilitated workshop of one to two hours is enough. The benefit depends on follow-through: 5 Whys delivers the diagnosis, the fix needs one of the other methods.

4. Total quality management (TQM)

Total quality management puts quality from the customer's perspective at the centre and embeds continuous improvement across the whole organisation. The method relies on performance metrics and data-based decisions, from the quoting phase through to project handover.

Practical example: a management consultancy with long-standing framework agreements measures two metrics per delivery phase: the number of review loops per deliverable and the share of non-billable rework. After a year, rework falls from 8 to 3 per cent of project hours. The more important effect shows up in follow-on business: clients extend more often because delivery dates and quality have become predictable.

Effort and benefit: the rollout effort is high, because TQM is a cultural topic and involves every level. The time horizon is one to three years. The typical effect is stable quality, less rework and stronger client retention. TQM pays off above all for service providers with recurring client relationships.

5. The PDCA cycle

The PDCA cycle (plan, do, check, act) is an iterative strategy for testing changes with low risk and only rolling them out once success is proven. It comprises four steps:

Practical example: an IT consulting firm suspects that same-day time entry speeds up billing. Instead of announcing a rule for everyone, one team tests it for four weeks (do). The comparison shows that hours are complete on the first of the month and invoicing starts five days earlier (check). Only then is the rule adopted for all teams (act).

Effort and benefit: the effort is low to medium, and a cycle typically takes weeks. The benefit lies in the low risk: bad decisions stay confined to the pilot. PDCA suits practically any process change and can be repeated as often as needed.

6. Lean manufacturing

Lean manufacturing minimises waste and maximises value for the customer. The principles come from production but work just as well in service processes. The central lever is value stream mapping: every process step is examined to see whether it creates value or produces waiting time.

Practical example: an engineering service provider maps its quoting process as a value stream. The result: of ten days' lead time, six are waiting time between costing, technical review and management approval. After introducing clear approval thresholds (quotes below €25,000 are approved by the division head), lead time falls to four days. The company responds faster than its competitors.

Effort and benefit: the rollout effort is medium. A value stream analysis per process takes a few days, implementation a few months. The typical effect is significantly shorter lead times in processes with many handovers, such as quoting and billing.

7. Business process management (BPM) principles

BPM analyses and optimises business processes end to end, with the aim of eliminating inefficiencies and automating manual tasks. The approach follows five steps:

1. Analysis: document the current process from start to finish (process modelling).
2. Modelling: design an improved version of the process.
3. Implementation: put the model into practice and define success metrics.
4. Monitoring: track the process against those metrics.
5. Optimisation: continuously look for further improvements.

Practical example: a consultancy models its core process from quote to invoice and finds four manual handovers across five systems. Hours are exported, checked in Excel and transferred by hand into the invoicing software. Consolidating onto a shared data basis eliminates three of the four handovers. The article on ending tool sprawl shows how to take that step. Subsequent process automation takes over the remaining routine steps.

Effort and benefit: the effort is medium to high, because BPM cuts across departmental boundaries and often triggers systems decisions. In return, the effect is structural and lasting: fewer handovers, fewer errors, continuous data.

8. Portfolio analysis

Every company runs many processes in parallel, often interdependent. Optimising them all at once is neither possible nor sensible. Portfolio analysis sets priorities: it assesses processes in a matrix against two criteria.

• Strategic importance: how strongly does the process contribute to achieving company goals?
• Improvement potential: how large is the realistic lever, measured by the nature, scope and feasibility of possible measures?

Practical example: an IT service provider with 80 employees assesses twelve core processes in a half-day workshop. The billing process lands in the critical quadrant: high strategic importance, because it directly affects liquidity and margin, and high potential, because it runs across three systems. It becomes the first optimisation project; the overhaul of holiday administration can wait.

Effort and benefit: the effort is low; a workshop with the process owners is enough. The benefit is indirect and nonetheless substantial: portfolio analysis prevents months being invested in processes that barely move the commercial needle.

The 8 methods compared

The methods differ less in their goal than in their scope: some solve a single problem in days, others reshape the organisation over years. The table places all 8 methods for your selection.

In practice a combination works well: portfolio analysis for selection, 5 Whys for diagnosis, PDCA for testing the solution. The large programmes only follow as experience grows.

The benefits of process optimisation

Systematic process optimisation reduces broken handovers, improves data quality and strengthens competitiveness. In the project business, five effects feed directly into steering.

Greater efficiency

Optimised processes eliminate activities that consume time without contributing value. Every hour freed up for a specialist can flow into billable project work. For project service providers, efficiency therefore works twice over: as a cost reduction and as a revenue lever.

Lower costs

Fewer manual handovers mean less correction work. Keeping hours, project status and billing data on one data basis saves the hours that otherwise go into reconciliation and rework every month.

Better quality

Continuous process monitoring catches errors early, before they reach the client. That stabilises delivery dates and reduces complaints, in billing just as much as in technical delivery.

Flexibility and adaptability

Documented, lean processes can be adjusted faster when requirements or team sizes change. Processes that work with 20 employees collapse at 60 without structure.

Employee satisfaction

Efficient processes remove the friction that frustrates specialists most in daily work: duplicate data entry, unclear responsibilities, time spent searching. That creates room for the professional work people were hired to do.

Increasingly, artificial intelligence supports these effects too, for instance in analysing project data and detecting deviations early. The article on AI in project controlling shows where the lever actually sits.

How ZEP supports the implementation of all 8 methods

All 8 methods share one prerequisite: reliable data on where working time actually goes. ZEP provides that basis by connecting project time tracking, project controlling and resource planning on one data basis. Analysis and impact measurement therefore work without manual exports.

For the diagnosis phase (5 Whys, portfolio analysis), the reports in ZEP Compact show which projects and activities tie up the most time. For testing and control (PDCA, Six Sigma, Kaizen), the before-and-after comparison of recorded hours makes the effect of each measure measurable. The ZEP Assistant answers questions about project hours and utilisation directly in conversation, without anyone having to assemble reports.

For structural redesign (BPM, lean), the platform reduces the handovers themselves: in ZEP Professional the process runs end to end in one system, from quote through time entry to invoice. The manual interfaces that show up in many process analyses as the biggest source of error are structurally removed.

{{blog-cta}}

Conclusion

Start small and data-driven. Three steps are enough to begin: assess your core processes in a workshop using portfolio analysis. Analyse the prioritised process with the 5 Whys method. Then test the solution via PDCA in one team before rolling it out.

In parallel, it is worth looking at your data basis. If working hours, project status and utilisation sit in separate systems, every method lacks its foundation. Clean project time tracking is therefore not a side issue. It is the first optimisation step that makes all the others measurable.