A job sheet that keeps missing the serial number. A van that leaves the yard without the right fittings. A quote that takes three days because the pricing sits in one person’s head. Each is small, and each tends to come back unless someone changes how the work is done. Continuous improvement is the ongoing improvement of products, services or processes through small changes made over time and larger changes made all at once.
In a contracting business, those changes can show up in fewer return visits, shorter waits for parts, quicker invoicing and less rework. The rest of this guide explains how continuous improvement works, how it relates to Lean, and how it can run week to week in a business without a dedicated improvement team.
What is continuous improvement?
Continuous improvement, as ASQ, the American Society for Quality, defines it, is the ongoing improvement of products, services or processes through incremental and breakthrough improvements. The improvements can be small or large; what makes them continuous is that they keep coming.
Adding a photo of the finished installation to the job completion step is continuous improvement. So is changing the order in which jobs are booked so engineers spend less time driving between them. The habit is what counts: problems are noticed, fixed at the cause, and then the next one is picked up.
ASQ notes that “continuous” and “continual” improvement are often used interchangeably. Where a difference is drawn, continual improvement is the broader term preferred by W. Edwards Deming, and continuous improvement is a subset of it focused on steady, incremental change. For a business owner the distinction rarely matters; what matters is whether improvement happens as a habit or only when something goes badly wrong.
Continuous improvement is one part of the wider subject of business improvement, which also covers one-off projects, strategy and structure.
How is continuous improvement different from Lean?
Lean is a way of thinking about creating the value a customer needs with fewer resources and less waste, while continuous improvement is the habit of improving the work again and again. The Lean Enterprise Institute describes Lean as “a way of thinking about creating needed value with fewer resources and less waste”. Lean gives the lens for spotting waste; continuous improvement gives the rhythm for removing it.
Lean grew out of the Toyota Production System. Toyota describes a system in which “all employees implement daily incremental kaizen”. Kaizen is the Japanese term for this kind of continuous, small-step improvement.
Five Lean principles, first set out by James Womack and Daniel Jones and summarised by the Lean Enterprise Institute, are value, value stream, flow, pull and perfection. In a contracting business they read like this:
- Value. Define what the customer is paying for: a working system, installed safely, first time, with the paperwork they need.
- Value stream. List every step from enquiry to paid invoice, and mark which steps add value the customer would recognise.
- Flow. Make the value-adding steps follow each other without waiting, such as parts arriving before the engineer does.
- Pull. Start work when the next step is ready for it, so surveys are not stacked up waiting for a designer, or jobs waiting for materials.
- Perfection. Repeat the cycle. There is no finish line, because each round shows the next problem.
What does waste look like in a contracting business?
Waste in a contracting business is any activity that uses time, materials or money without adding value the customer pays for. Lean calls it “muda”. Much of it is not dramatic: it is the return visit, the hour spent waiting for a part, and the job details typed in twice. Where that waiting builds up between enquiry and invoice, and how to measure it, is covered in how workflow efficiency is measured and improved.
Lean’s traditional categories of waste, such as waiting, transport, inventory and defects, translate into six forms in installation and maintenance work: return visits, waiting, rework, re-keying, travel and stock problems.
- Return visits. A second trip because the right part, access or information was missing on the first.
- Waiting. Engineers waiting for materials, sign-off or a site to be ready; customers waiting for a quote.
- Rework. Work redone because it did not meet the specification or the customer’s expectation.
- Re-keying. The same job details entered into the quote, the job system and the invoice by hand.
- Travel. Time on the road caused by how jobs are booked rather than where customers are.
- Stock problems. Too much of some items on vans and in stores, and not enough of the ones that matter.
The cost of getting things wrong adds up across the sector. The Get It Right Initiative, an industry body focused on construction error, reports that international studies put the direct cost of avoidable error at around 5% of project value, and that, once unrecorded process waste, latent defects and indirect costs are included, estimates of the total cost range from 10% to 25% of project cost, or £10–25 billion a year across UK construction. Those are industry-wide figures rather than figures for any one trade, but they show why removing rework and return visits is worth the effort.
Value stream mapping is a practical way to find where waste sits: it draws each step in order, with the time each takes and the time work waits between them.
What is the difference between incremental and breakthrough improvement?
Incremental improvement makes small changes over time, while breakthrough improvement makes a larger change all at once. ASQ uses the same distinction. A business can use both: steady small fixes to keep the work running well, and occasional bigger changes when the current way of working has reached its limit.
| Incremental improvement | Breakthrough improvement | |
|---|---|---|
| Size of change | Small, one step at a time | Large, several steps at once |
| How often | Weekly or as problems appear | Occasionally, as a planned project |
| Who leads it | The people doing the work | Management, with the team involved |
| Risk | Low, easy to reverse | Higher, needs planning and testing |
| Contracting example | Adding a parts check to the day-before call | Moving to a new job management system |
When breakthrough changes start reshaping several parts of the business at once, such as structure, decision rights and systems, the work has moved beyond improvement into business transformation.
How does the PDCA cycle keep improvements working?
The PDCA cycle keeps improvements working by testing each change on a small scale, checking the result with data, and only then rolling it out. PDCA stands for Plan, Do, Check, Act, and ASQ describes it as a four-step quality assurance method.
- Plan. Name the problem and the change to try. For example: too many visits end with no access, so the office will call each customer the day before.
- Do. Try the change on a small scale, such as one engineer’s diary for four weeks.
- Check. Compare the no-access rate before and during the test.
- Act. If it worked, make the call part of the standard booking process for everyone. If not, adjust the idea and run the cycle again.
PDCA sits alongside other methods such as DMAIC and the wider Lean toolkit; a comparison is set out in what a business improvement framework is and how the approaches differ.
How does continuous improvement run week to week in a contracting business?
Continuous improvement runs week to week through a short, fixed review of a few measures and a visible list of improvements, each with an owner and a date. It does not need an improvement department. It needs a place to record problems, a time to look at them, and a rule that changes are written down once they work.
Five elements make up a simple weekly rhythm: a problem list, a few measures, a short review, an owner and date for each improvement, and a written standard.
- A problem list. One shared place where anyone can record a problem the moment it happens: a whiteboard, a shared sheet or a column on the job board.
- A few measures. Three to five numbers that show whether the work is getting better, such as first-time fix rate, return visits, days from completion to invoice, and quote conversion.
- A short review. Fifteen to thirty minutes at the same time each week to look at the measures and pick the next problems to fix.
- An owner and a date. Every improvement in progress has one named person and a date for the next check.
- A written standard. Once a change works, it goes into the procedure, checklist or template the team already uses. A Kanban board is one simple way to make the list and its progress visible.
In Rostone Operating Partners’ work with contracting businesses, the improvements that last are the ones built into the job sheet, checklist or booking routine the team already uses, rather than agreed in a meeting and left to memory. The weekly review then checks that the new way is still being followed, not only whether the numbers moved.
Why does continuous improvement matter for productivity and business value?
Continuous improvement matters because the Office for National Statistics measures it as one of the management practices associated with higher productivity in UK firms with 10 or more employees. It also sits alongside the people practices, such as training and staff involvement, that make up high performance work systems.
The ONS bulletin Management practices in the UK: 2016 to 2023 measures continuous improvement, meaning how businesses respond to problems, as part of its management practices score, and reports that better management practices are associated with higher productivity and resilience.
The ONS presents its own figures as a correlation between management scores and labour productivity, so they show the two move together rather than proving that one causes the other. Even so, the practices it measures, such as responding to problems, using key performance indicators and setting targets, are the same building blocks a weekly improvement rhythm puts in place. How targets themselves can be set and reviewed is explained in how goal setting frameworks such as SMART goals and OKRs work.
Rostone looks at continuous improvement through the four GRAX options: Grow, Raise, Acquire and Exit. To grow, it can free capacity so more jobs are done with the same team. To raise finance, it can produce steadier numbers for a lender or investor to look at. To acquire, it can give a tested way of bringing another business’s processes into line. To exit, it can help show a buyer that the business runs on agreed methods rather than on the owner fixing problems personally. How these changes show up in a valuation is covered in how operational improvements increase business valuation.
How can a contracting business start with continuous improvement?
A contracting business can start with continuous improvement by choosing one measure that matters, finding the biggest cause of waste behind it, testing one change, and writing the change down once it works. Starting with one problem keeps the effort small enough to keep going alongside paid work.
Five steps make a simple start: pick one measure, find the main cause, test one change, write it down and review weekly.
- Pick one measure. Choose a number the team already cares about, such as return visits or days to invoice, and record where it stands today.
- Find the main cause. Look at the last ten or twenty examples and group the causes. Asking “why” several times, the “5 Whys” technique, helps get past the symptom to a cause.
- Test one change. Run a small PDCA test on one team, one van or one job type.
- Write it down. Update the checklist, template or procedure so the change survives holidays and new starters.
- Review weekly. Keep the measure on the weekly review and pick the next problem once the first is under control.
More approaches to improving how work flows are set out in seven business process improvement strategies.
The Business Improvement service runs Diagnose, Design and Deliver with a management team, starting from a written diagnostic and then working in 90-day turns.
Frequently asked questions
Kaizen is the Japanese term used for small, continuous improvements made by everyone in a business. It is a core idea of the Toyota Production System, where the people doing the work are expected to look for and make improvements every day.
Examples include a standard van stock list for each job type, a pricing sheet that lets more than one person produce a quote, and a set list of completion photos. Each is small, tested on a few jobs, and then written into how the work is done.
Lean focuses on removing waste so work flows to the customer with fewer delays and less effort. Six Sigma focuses on reducing defects and variation, usually through the Define, Measure, Analyse, Improve, Control (DMAIC) steps. Lean Six Sigma combines the two.
Each improvement can have one named owner, with a member of the management team leading the weekly review. The people doing the work are often closest to the problems, so the problem list is open to everyone.
There is no fixed timescale. A single small change can show in the numbers within a few weeks, while the habit of improving takes longer to settle. Tracking one or two measures from the start shows whether the changes are working.
Sources
ASQ: What is continuous improvement?
Lean Enterprise Institute: What is Lean?; Lean thinking and practice
Toyota: Toyota Production System
Get It Right Initiative: Cost of error in construction
Office for National Statistics: Management practices in the UK: 2016 to 2023
Last updated: 13 November 2026




