In brief: Kaizen means continuous improvement. For an SME, it is a practical way to identify a real operating problem, test a manageable change, check the result and make the better method part of normal work. It works best as a repeated problem-solving habit, not a one-off cost-cutting campaign.
What is Kaizen?
Kaizen is a Japanese term commonly translated as continuous improvement. The Lean Enterprise Institute describes it as small, incremental improvement to processes and systems, supported by the Plan-Do-Check-Act cycle.
The idea is closely associated with lean management and the Toyota Production System, but it is not limited to manufacturing. The same discipline can be applied to administration, customer service, sales handovers, stock control, onboarding, project delivery and other repeatable work. Toyota describes Kaizen as a philosophy of continuous improvement that supports quality, waste reduction and efficiency in equipment and working procedures.
For a small business, the useful question is not whether it can copy a large production system. It is whether the team can make problems visible, learn from controlled changes and retain what works.
What are the main Kaizen principles?
Different books and organisations group Kaizen principles in different ways, so there is no single universal list that every practitioner uses. The following principles provide a practical SME interpretation without presenting one framework as the only correct version.
1. Start with the actual work
Observe how the process currently operates rather than relying only on how it is supposed to work. Record delays, errors, repeated questions, duplicate entry, unclear approvals and workarounds. A specific current condition provides a baseline for improvement.
2. Involve the people closest to the process
The people doing the work often see friction that is invisible in a management report. Ask them where information is missing, which exceptions cause disruption and what customers or colleagues repeatedly need clarified. Their involvement also helps test whether a proposed change is workable.
3. Improve through manageable experiments
A Kaizen change should have a defined problem, owner, test period and expected outcome. Where possible, start small enough to learn without exposing the whole business to an untested change. A test might simplify a handover, remove duplicate data entry or introduce a clearer checklist.
4. Use evidence, not assumption
Measure the current position before changing it, then use the same measures after the test. Combine speed or cost with quality and customer impact. A change that saves five minutes but creates more errors has moved the problem rather than solved it.
5. Standardise what works
When a change produces a dependable improvement, update the process, template, system, training or responsibility so the new method becomes normal work. A successful experiment that is never embedded will usually fade as people return to the previous habit.
6. Repeat the cycle
Kaizen is not completed by one workshop. The improved method becomes the next baseline. The team then identifies the next important gap, tests another change and learns again.
Are there four main Kaizen principles?
Searches for four Kaizen principles often refer to the four stages of Plan-Do-Check-Act (PDCA). PDCA is better understood as an improvement cycle than as a definitive list of Kaizen values. The Lean Enterprise Institute PDCA guide describes it as the foundation of continuous improvement:
- Plan: define the problem, current condition, intended result, measure and proposed change.
- Do: run the change on an appropriate scale and record what happens.
- Check: compare the result with the baseline and look for unintended effects.
- Act: standardise a successful change, adapt it or stop it, then begin the next cycle.
This distinction matters because merely listing values does not improve a process. PDCA turns the intention to improve into a testable working method.
How can an SME apply Kaizen?
Choose one meaningful operating problem
Start with a recurring issue that affects customers, cash, capacity, quality or staff time. Examples might include slow quotation turnaround, missing information at onboarding, repeated invoice queries or unclear job handovers. Avoid a vague instruction to become more efficient.
Describe the current condition
Map the main steps and collect a small amount of relevant evidence. Record how frequently the problem occurs, how long the work takes, where it waits, who is affected and what rework follows. Use enough information to guide the test without turning diagnosis into an endless project.
Set a narrow target
State what should be different and by when. The target should be meaningful to the business and measurable using information the team can obtain reliably. Avoid promising an outcome before the test has produced evidence.
Find the cause before choosing the fix
Ask why the problem occurs and check the answer against the work. The visible symptom may have several causes. For example, a late handover could reflect missing customer information, unclear ownership, conflicting deadlines or a system that hides the next action.
Test one controlled change
Give the experiment an owner, start date, review date and stop condition. Record what changed so the result can be interpreted. Changing several parts of the process at once makes it harder to know what helped.
Review the complete result
Check whether the target improved and whether another measure became worse. Ask the people using the process and, where relevant, review customer feedback. The result may justify adoption, adaptation, another test or no further action.
Embed and document the better method
Update the source of truth, remove obsolete instructions and tell affected people what has changed. If the process depends on a form, template, system field or recurring meeting, update that control as part of the change.
A simple Kaizen example for a small business
Consider a hypothetical service business where project work starts before the delivery team has complete customer information. The problem creates follow-up emails and delays.
- Plan: record how often information is missing, identify the essential fields and agree a complete-handover measure.
- Do: test one shared handover checklist for a small number of suitable projects.
- Check: compare completeness, start delay, rework and team feedback with the previous position.
- Act: if the test improves the overall result, update the standard handover process and remove the old version. If it does not, review the cause and test a different response.
The example is illustrative, not a case study or reported outcome. The correct change and measures depend on the business and the risk of the process.
What should a small business measure?
Choose a small set of measures linked to the problem. Depending on the process, these could include:
- Elapsed time and waiting time.
- Errors, defects, complaints or rework.
- First-time completion or right-first-time rate.
- Work in progress or outstanding items.
- Customer response or resolution time.
- Staff time, process capacity or avoidable cost.
- Safety, compliance or service-quality indicators.
Do not optimise one measure in isolation. Faster work is not an improvement if quality, safety, compliance or customer experience deteriorates.
Common Kaizen mistakes
- Treating suggestions as the outcome: ideas need owners, tests, measures and decisions.
- Blaming individuals for system problems: this discourages people from exposing useful evidence.
- Starting too many improvements: an overloaded action list weakens ownership and follow-through.
- Skipping the baseline: without a current measure, success becomes a matter of opinion.
- Failing to standardise: improvements disappear when templates, systems and training remain unchanged.
- Using Kaizen for every problem: a failing business model, major strategic choice, legal issue or unsafe process may require immediate specialist action rather than a small experiment.
Kaizen, projects and business strategy
Kaizen is strongest when improving repeatable work. A larger transformation may need a defined project, investment decision or strategic change. The approaches can support each other: strategy identifies the outcome and priorities, projects deliver substantial changes, and Kaizen helps teams improve the recurring processes around them.
For related practical guidance, see how to streamline a team workflow and how to run projects without a dedicated project manager. Those articles focus on workflow and project delivery; this guide remains the owner for Kaizen definitions, principles and the PDCA improvement method.
Turn improvement ideas into accountable action
If the business has several competing problems and needs an objective view of which matter most, G&G’s Business Review can help identify and prioritise operational risks and opportunities. Where the problem is day-to-day coordination, records or repeatable process ownership, explore Business Administration Support.
