The Kaizen Roadmap
A practical guide to turning Toyota’s philosophy of continuous improvement into a working system. Five chapters, four case studies, a self-assessment, and links to the source essays.
The stairway to perfection
Toyota’s philosophy of continuous improvement is not a programme, a project, or a passing management fad. It is a system of four tools operating inside a culture that took decades to build.
Kaizen, the Japanese concept of continuous improvement, has been praised for half a century as the foundation of Toyota’s rise from postwar obscurity to global quality benchmark. Yet most organisations that attempt to adopt it fail. They announce an initiative, expect measurable results within a fiscal year, and declare the experiment over when the numbers do not cooperate.
The philosophy itself is rarely the problem. Kaizen works because it assumes three things that sound unremarkable until an organisation tries to live them: that the people closest to a problem understand it best, that small improvements compound over time, and that mistakes are opportunities for learning rather than grounds for punishment. What undermines most adopters is the belief that Kaizen is a single tool or a short-term programme. It is neither. It is a system of four tools operating inside a supportive culture, sustained over decades.
When Toyota began exporting cars in the early 1950s, “Made in Japan” was not yet a mark of quality. It took roughly forty years to change that entirely. The climb was not dramatic. It was the cumulative effect of millions of tiny improvements, each one unremarkable on its own.
That is the central paradox. Kaizen is the pursuit of perfection, and perfection is by definition unattainable. That is the point. Each small improvement is one step on a stairway that never ends. The stairway is what keeps people climbing.
At Toyota, four tools make up the system: PDCA (Plan-Do-Check-Act), which provides project discipline; Horenso (報連相), which ensures 360-degree communication; the 5-Whys, which identifies root causes; and Mieruka (見える化), which makes the state of work visible at a glance. Together, these allow Kaizen to move from abstraction to something grounded in fact and operational reality.
Around them sit two supporting principles: Genchi Genbutsu (go and see for yourself) and 5S (workplace organisation), the latter of which requires significant adaptation for service industries.
5S: Workplace organisation
In manufacturing, 5S is straightforward: tools go in marked locations, floors are clean, shelves are labelled. In service industries, the application is less obvious. The “workplace” may be a shared drive, an intranet, or a set of procedures that exist only in people’s heads. Adapting 5S to this context requires thinking about what “Sort” and “Set in order” mean when the materials are digital and the processes are knowledge-based. A case study later in this briefing illustrates both how this adaptation can go wrong and how it can be recovered.
Service industry focus
Virtually all existing literature on Kaizen is biased towards manufacturing, because that is where the concept originated. The focus of this briefing is on service industries. Whether the setting is a law firm, a consultancy, a bank, a hospital, or a travel agency, value can be added using Kaizen. The concepts travel. Only the implementation must be reinvented.
Like many quality management approaches, Kaizen is not a quick fix. Quantifiable improvements may not be significant in the short term, but the positive effects steadily snowball into long-term gains in quality, efficiency, and retention. A company needs to be married to Kaizen for it to succeed.
The five-stage cycle
Every Kaizen improvement follows the same sequence. Five stages, infinitely repeated, powered by four tools. Each stage is small. The effect compounds.
1. Identify the problem and use PDCA for project management
Kaizen begins with the identification of a real problem or an opportunity for improvement within a process. Once identified, the work moves to the centre of the system: Plan-Do-Check-Act, popularised by the statistician Edwards Deming.
Plan. Formulate a detailed plan for the improvement. Identify goals, delegate work, and set a clear action plan with milestones. Document everything, because the documentation feeds the analysis stages that follow.
Do. Execute the plan. As no plan is ever completely perfect, keep a running list of problems encountered during execution, and how the team responded to them.
Check. Once the work is complete, compile the list of problems and solutions. Share them across the team so that everyone understands what happened and why. For each problem, identify the root cause using the 5-Whys. This is where surface fixes are distinguished from structural ones.
Act. With root causes identified, formulate countermeasures to prevent recurrence. The goal is to make the improvement permanent so that past problems do not reassert themselves. Standardise the new approach through documentation and share the knowledge through team meetings.
Then start again. PDCA is a never-ending cycle.
Most people operate in what Toyota calls the Do-Do-Do-Do cycle, applying fixes without first examining the root cause. PDCA provides precision. Consider a party where catering arrives two hours late. The obvious reaction is to blame the supplier. A team running the full PDCA cycle would instead ask why the purchase order was issued only three days before the event, discover there was no checklist for time-critical tasks, and fix the missing process rather than changing the caterer. Fixing problems at their root cause is like pulling weeds out entirely. Fixing them at the surface is like cutting weeds; they grow back.
The discipline of PDCA also enforces incrementalism. If a massive project reaches the Check stage, the volume of issues to analyse becomes overwhelming. Small, focused cycles produce manageable problems and visible progress. The effect accumulates over time.
2. Use Horenso for 360-degree communication
Horenso (報連相) is a compound of three Japanese abbreviations: Hokoku (report), Renraku (update), and Sodan (consult). The original concept was developed for manufacturing and assumed a hierarchical structure where information flowed in one direction: upward from the factory floor to management.
The adapted model for service industries operates in three directions:
Report (Hokoku): Communicate status and seek guidance from supervisors or project leaders.
Update (Renraku): Keep team members informed so they can take action and work in parallel.
Consult (Sodan): Engage stakeholders, clients, and those impacted by the project to validate direction and identify improvements.
The point is not to share everything with everyone. It is to make the choices about who knows what an explicit, deliberate discipline rather than an accident of office proximity. Horenso operates throughout the entire PDCA cycle. It is the connective tissue that holds the other tools together.
3. Use the 5-Whys to identify root causes
Problems encountered during implementation need to be analysed for their root cause. Without this step, solutions tend to address symptoms rather than what is actually driving the issue. The method is straightforward: state the problem, then ask “why did this happen?” Note the answer. Ask “why did that happen?” about the answer. Repeat five times.
In Toyota’s methodology, five iterations are considered sufficient to reach a root cause. In practice, three or four sometimes suffice; complex problems may require seven or eight. Too few indicates insufficient depth. Too many indicates over-analysis and fatigue without proportional benefit.
The critical qualifier: only those with firsthand knowledge of the problem should perform the analysis. In Toyota, the 5-Whys is almost always conducted by the subject-matter expert on the ground. It is not possible for someone without direct exposure to the issue to understand the contributing details. Analysis conducted at a distance will produce educated guesses, and countermeasures based on inaccurate root causes will fail. The problem will re-emerge.
The tool has known weaknesses. Since it is qualitative, conclusions depend on the analyst’s perspective and experience. Bias can skew results. The remedy is group work: form a team of subject-matter experts, each producing their own analysis independently before presenting findings for rigorous discussion. The group prioritises the fixable root causes collectively.
4. Use Mieruka to make improvements visible and permanent
Mieruka (見える化) is a critical tool in Toyota’s system. Its purpose is to visualise and condense information so that it is immediately understandable at a glance, while still providing everything needed to act.
In a Toyota factory, examples appear everywhere: whiteboards showing progress, signs classifying sections, coloured lines on floors indicating how products should be stacked, metal clipboards containing information needed at fingertips. Three rules govern effective visuals:
Make it easy to understand. Distil information to its essential core, so that anyone can immediately grasp the current situation. The emphasis is on speed and simplicity.
Make it big and physically visible. Place visuals in high-traffic areas where they are impossible to miss. Toyota uses freestanding whiteboards and entire walls dedicated to visual communication.
Make it interactive and easy to change. Visuals must be kept current. Magnetic stickers that can be rearranged, hand-written whiteboard notes, colour-coded Post-its. Toyota uses whiteboards rather than computer dashboards because they offer more reliability and ease of modification.
Visuals fall into four types, classified as 3I1P:
| Type | Purpose | Examples |
|---|---|---|
| Identification | Tells what something is | Labels, colour-coded stickers, QR codes, shelf tags |
| Informative | Shares the current situation | Wall charts, defect statistics, staff location boards |
| Instructional | Tells how to perform a task | Step-by-step procedures, floor markings, colour-coded zones |
| Planning | Shows the plan and its progress | Gantt charts on whiteboards, magnetic strips, schedules |
The principle running through all four types: visuals do not need to be complex or flashy. They need to be clear.
5. Start again
Once all four tools have been used in conjunction and an improvement has been implemented, one cycle of Kaizen is complete. The next cycle begins immediately, on the next problem worth solving. Kaizen has no finish line. Toyota’s forty years of improvement were forty years of this repetition.
Many projects fail because they are overambitious, attempting to fix too many problems simultaneously. The discipline is to keep each cycle small, focused, and completable. Mastery of Kaizen depends on mastery of the four tools and the patience to apply them repeatedly.
Within the methodology, checklists are among the most basic visual control tools, used to formalise processes so that procedures are repeated consistently and knowledge is retained. Toyota’s A3 report is itself a formalised checklist: one sheet of paper containing the problem statement, root-cause analysis, countermeasures, and follow-up plan. The discipline of fitting everything onto a single page forces clarity of thought.
When it goes wrong
Most Kaizen initiatives fail for six predictable reasons. Each is a mirror image of the cultural conditions under which the philosophy succeeds.
From experience working inside the Toyota system, organisations with one or more of the following characteristics will struggle to implement Kaizen without first addressing them.
1. Kaizen is treated as a short-term project. The emphasis in Kaizen is on long-term improvement. The concept is simple to understand but difficult to master, and it takes time before it is fully absorbed across an organisation. The recurring problem: companies expect a quick turnaround and visibility in KPIs within a year, and when that does not materialise, they write Kaizen off as a failure. When Toyota began exporting cars, “Made in Japan” was not a mark of quality. It took forty years to change that entirely.
2. Over-emphasis on tying Kaizen to KPIs. While connecting Kaizen to measurable outcomes matters, over-emphasis ignores the incremental nature of improvement. The effects accumulate gradually, like a snowball rolling down a gentle slope. It gathers size and momentum as it goes.
3. Implementation in an organisation resistant to change. Kaizen will not survive in an environment dominated by rigid procedures and an unwillingness to question how things are done. Where change is formally or socially punished, any incentive to improve is eliminated before it can take hold.
4. Management pays lip service. At one university, a suggestion box was installed and called Kaizen. No training was provided on root-cause analysis or any of the associated tools. Suggestions were rarely reviewed, and on the occasions they were, management ridiculed the contents. Feedback dried up almost immediately.
5. Insufficient training. Kaizen will not work if people are expected to use its tools without proper instruction. Staff who have never performed a 5-Whys analysis will produce a list of grievances rather than a structured identification of root causes.
6. Management does not lead by example. It is essential that leaders do not merely endorse Kaizen but visibly practise it. They need to demonstrate that they themselves are continually looking for improvements. If the most senior people in the room do not share their own mistakes or conduct their own root-cause analysis, nobody else will either.
Kaizen is about everyone improving everything, not a designated group doing all the work.
The seven foundations
Four stories, four lessons
The abstract arguments take their shape from specific incidents. Three are drawn from Toyota itself. One is from a software firm that got 5S badly wrong before getting it right.
The power of the Toyota system is not in its abstractions. It is in what happens when people facing real problems pick up the tools and use them.
How Toyota Tsusho won a multi-million dollar contract
Toyota Tsusho, the trading arm of the Toyota Group, had a good relationship with the Malaysian government, which was looking for a new supplier of noise-absorbing highway walls. The team assembled a proposal offering the best, highest-quality wall at a competitive price.
The proposal was rejected in committee as too expensive. The working team was surprised. They conducted several rounds of 5-Whys analysis but none led to the root cause.
The Chief Operating Officer was due to fly into Kuala Lumpur shortly afterwards. When he landed and the driver asked whether to take him to the office, he replied: “No, let’s go for a drive around the city.”
A few hours later, he arrived at the office and asked to see the proposal. “Here’s the problem,” he said, pointing to the model they had offered. “This is the best in the market and although we use this in Japan, Malaysia isn’t ready for it. Have you noticed that Malaysian highways all use a much older, but cheaper version? They can’t afford this yet. Economic reality is the reality that we live with.”
The team revised and resubmitted. A few weeks later, they had won the contract.
LessonThe 5-Whys had failed because nobody running it had actually looked at the competition on the ground. Data alone could not surface what a single afternoon driving around a foreign city revealed. This is Genchi Genbutsu: go to the source to find the facts.
Yuji Yokoya and the 85,000-kilometre minivan
In the early 2000s, Toyota engineer Yuji Yokoya was given responsibility for redesigning the Sienna minivan for the North American market. Toyota had historically ceded this segment to American manufacturers, and the previous Sienna had done little to change that. Instead of relying on customer focus groups and reports, Yokoya decided he needed to experience driving through Canada, Mexico, and the United States himself.
Over two years he drove more than 85,000 kilometres, encountering every condition the continent could offer: icy windswept highways, dense urban centres, and places where roads barely existed. He became the customer.
Crossing the Mississippi River, he noted that crosswind stability needed improvement. On gravel roads in Alaska he observed excessive steering drift. In Santa Fe he needed a tighter turning radius. In Glacier National Park the handling felt imprecise. He made all-wheel drive a priority, along with more interior space and cargo flexibility. He decided the new Sienna would have to be a minivan that families could live in for extended periods: upgraded seat quality, a roll-down window for second-row passengers, an optional DVD entertainment centre, and a conversation mirror so parents could monitor the back seat.
When the revamped Sienna launched in 2004, sales were up 60% compared to the same period in 2003, significantly closing the gap on American manufacturers who had traditionally dominated the segment.
LessonA focus group in Tokyo, however well-run, could not have produced these insights. Genchi Genbutsu is the discipline of not trusting second-hand information when first-hand information is available. Toyota’s own translation: “go to the source to find the facts to make correct decisions, build consensus and achieve goals at our best speed.”
The software firm that disinfected its desks
A software company attempted to implement 5S, the workplace-organisation discipline that Toyota pioneered in its factories. The 5S methodology was initially developed to facilitate just-in-time production, ensuring that the right tools are available when needed in a clean, ordered environment.
Management concluded that 5S meant an hour each week for all engineers to clean their desks, including wiping them down with disinfectant. This was redundant: a clean-desk policy already existed. And because the work was entirely digital, there were almost no physical tools to sort or set in order. Germ-free desks were achieved. Measurable output did not change. An hour of productive engineering time disappeared every week, and the credibility of the entire lean initiative took a knock.
The firm actually relied on a sprawling web of documentation scattered across unstandardised intranet locations. A corporate wiki was available but underutilised. Most knowledge resided in disparate Word and Excel files, with different teams using different directory structures. This was where 5S could add genuine value: not on desks, but on information.
The team agreed on a standard directory structure, documentation templates, and naming conventions. Knowledge was migrated to the wiki where it could be searched by keyword. The desk disinfecting was quietly de-emphasised.
LessonTPS concepts must be implemented in a way that makes sense for the organisation. Keeping the physical work area clean and organised makes sense in a car factory. It may add nothing in a software company. The concepts travel; the implementation must be reinvented.
Alencia and the anatomy of a root-cause analysis
Alencia, an outsourced executive recruitment firm, had a problem most companies would envy. Demand had boomed. But capacity had remained flat. Job requests were piling up, clients were growing impatient, and candidates were drifting to more responsive competitors. A previous attempt to introduce a computerised system had collapsed when staff pushed back. Knowledge about how work got done lived inside people’s heads rather than in any documented procedure.
Mio, the manager assigned to fix the problem, did not buy new software. She did not reorganise the team. She sat down with her colleagues and ran a 5-Whys analysis using the table method.
She started with the core question: why is the company unable to keep up with demand?
Two branches emerged. First, there was no computerised system to handle the volume of applications. Second, there were no formal procedures for the manual process, meaning each person handled work differently with no standardisation.
Pursuing the first branch: why was there no system? Because a previous implementation had been abandoned after staff resisted it. Why had staff resisted? Because nobody had explained the benefits of the system, nobody had addressed their concerns about being made redundant, and nobody had provided training on how to use it.
Pursuing the second branch: why were there no procedures? Because the company had grown so quickly that there had never been time to document how work was done. Why had nobody found the time? Because management was entirely consumed by day-to-day operational demands.
Both branches, followed to their conclusion, converged on the same root cause: a leadership capacity gap. Management had no bandwidth for strategic work. They could not plan, communicate, or train because they were permanently absorbed in operational firefighting.
| Why | Observed cause | What it revealed |
|---|---|---|
| 1 | Processing of applications is delayed. | Two branches: no computerised system, and no formal procedures. |
| 2 | System abandoned due to staff resistance; procedures exist only in heads. | A people problem, not a technology problem. |
| 3 | Staff feared redundancy; company grew too fast to document. | Both branches converge on a communication failure. |
| 4 | Benefits never explained. Change management absent. | A leadership gap, not a staff gap. |
| 5 | Management too busy firefighting to think strategically. | Root cause reached. |
| Root cause | Countermeasure |
|---|---|
| Benefits of the new system were never communicated; job security fears were never addressed. | Build a communication plan. Explain what the system does and does not replace. Reassure staff about their roles. |
| No culture of change. Staff felt insecure about altering how they worked. | Include formal change management in any rollout. Provide comprehensive training before deployment. |
| Management absorbed in operational firefighting, unable to plan strategically. | Redistribute operational work. Hire if necessary. Free leadership to think beyond the next week. |
The countermeasures followed from this diagnosis. First, build a communication plan explaining what a computerised system would and would not replace, directly addressing job security concerns. Second, include formal change management in any future technology rollout, with training provided before deployment rather than after. Third, redistribute operational work so that leadership has genuine capacity for strategic planning, hiring additional support if necessary.
The instinct to simply purchase better software would have repeated the same failure. The 5-Whys revealed what needed to be in place first: communication, training, and leadership capacity to see it through. The software was still part of the solution. It just was not the root cause of the problem.
The limits of continuous improvement
Kaizen excels at making what exists better. It does not create what comes next. An organisation that relies on it exclusively will refine itself into irrelevance.
Kaizen is a rearward-facing discipline. Its fundamental question – how can we improve what we are already doing? – assumes that the thing being done is worth continuing. That assumption is safe most of the time. It is catastrophically wrong when the market shifts beneath an organisation’s feet.
The mechanism is subtle. Continuous improvement rewards conservatism. Each small gain reinforces the existing direction. Over time, the culture becomes inward-looking: teams optimise processes, reduce defects, shave costs. The work feels productive. It often is. But it produces no capacity to see that the game itself is changing, because the discipline is designed to improve the current game, not to question whether it is the right one.
In the 1960s and 1970s, Japanese consumer electronics firms took existing technologies (the transistor radio, the portable television, the cassette recorder) and refined them through continuous improvement until they dominated global markets. Sony perfected this approach. The Walkman was not Sony’s invention; it was Sony’s refinement of existing portable audio technology, iterated to the point of market dominance.
By the end of the millennium, the market was shifting towards digital music in the form of compressed audio files. Sony responded as its culture demanded: it produced slimmer, more colourful portable CD players with improved battery life. It enhanced its MiniDisc system to support file transfers and greater storage capacity. Each improvement was genuine. None of them mattered. Apple’s iPod redefined the category entirely, and no amount of incremental refinement of optical disc technology could respond to that kind of disruption.
The lesson is not that Kaizen failed Sony. It is that Kaizen was the wrong tool for the problem Sony faced. Continuous improvement cannot produce a discontinuous leap. It cannot generate the creative risk that a new market category demands. It can only make the existing category better, which is worthless if the category is dying.
Toyota itself understood this distinction. When the company decided to develop the Prius hybrid, executives deliberately chose an engineer who had never headed a vehicle development programme. His background was in technical research rather than product design, and that was precisely the point: they needed someone untainted by the incremental assumptions of existing car development. The Prius required a fresh perspective, not a refined one. Less Kaizen, not more, was the strategy that produced Toyota’s most significant product innovation in decades.
The implication for any organisation adopting the system described in this briefing is straightforward. Kaizen must be a rule, but it must not be the rule. It is the tool for making existing operations excellent. It is not the tool for deciding whether those operations should exist at all. An organisation needs both: a culture of continuous improvement for its current work, and a parallel capacity for strategic disruption that operates outside the improvement cycle entirely.
The two capabilities require different people, different incentives, and different tolerance for failure. Kaizen penalises waste. Innovation requires it. Holding both simultaneously is the real discipline, harder than either one alone.
Why paper still wins
For the world’s largest car manufacturer, the continued use of paper is not an accident. It is a considered choice, and it holds the key to the whole system.
Walk into any Toyota factory today and there is a significant amount of paper in use. The famous A3 reports, for example, remain rooted in paper. For a company that developed the know-how to create the hybrid car and operates some of the most sophisticated manufacturing lines on earth, this can look odd. It is not conservatism.
Toyota will adopt new technology when the case is clear. But the company does not believe in using technology for the sake of being new. A solution needs to be justified and demonstrate that it adds value without depreciating the benefits of what it replaces.
A piece of paper can be marked up with a pen by anyone who picks it up. It can be passed around a room. It can be stuck on a wall during a standup. It keeps working in a power cut. It costs almost nothing. A tablet adds hardware, software licences, support contracts, charging infrastructure, and training overhead. It subtracts the ability to hand the report to someone and have them annotate it immediately.
The same logic runs through the Mieruka principles discussed earlier. Whiteboards are preferred to dashboards because they are easier to change. Checklists on clipboards are preferred to form-filling software because they are easier to carry. The pattern is consistent: use technology where it clearly helps, and resist it where it does not.
This is perhaps the most counter-intuitive lesson in the Toyota Production System for a modern service organisation. The default assumption in most workplaces today is that any problem can be addressed by installing new software. Toyota’s record suggests a different starting point: begin with the cheapest, most flexible, most visible tool available. Move up the technology stack only when a specific task cannot be done any other way.
If it ain’t broke, don’t fix it. For seventy years Toyota has operated on that principle. It has also, in that time, become the largest car manufacturer in the world.
Which returns to the opening argument. Kaizen is not a programme. It is not a project. It is not a suite of software tools with a licence fee. It is a set of habits, a culture of small corrections, and a willingness to ask honestly why things are not working before the obvious fix becomes the standard one. The tools described in this briefing are well understood, inexpensive, and available to anyone. The culture required to make them work is harder to build, but not impossible.
An organisation that wants to adopt Kaizen should probably not start by declaring a Kaizen initiative. It should start by picking a real problem, forming a small team to address it, running one PDCA cycle properly, and banking the result. Then another. Then another. If, in forty years, the organisation looks back and sees a stairway, the climb will have been worthwhile.
PDCA Tracker
A simple Kanban board for tracking your Kaizen projects through the four PDCA stages. Data is saved in your browser.
Your PDCA Projects
Self-Assessment
Twelve questions drawn from the six failure modes and the seven cultural foundations. How ready is your team?
Am I doing Kaizen right?
Select the option closest to the truth for your team today.
Frequently asked questions
What is Kaizen?
Kaizen is the Japanese philosophy of continuous improvement. Rather than a single tool or a programme with a start and end date, it is a system of four tools (PDCA, Horenso, 5-Whys, and Mieruka) operating inside a supportive culture. The philosophy assumes that workers closest to a problem understand it best, that small improvements compound over time, and that mistakes are opportunities for learning.
What is the PDCA cycle?
PDCA stands for Plan-Do-Check-Act. It is a four-step project management cycle popularised by the statistician W. Edwards Deming and adopted by Toyota as its core discipline. Plan the improvement, execute it, check what went wrong by identifying root causes, then act to prevent recurrence. The cycle then repeats indefinitely.
What is Horenso?
Horenso (報連相) is a Japanese communication framework combining three elements: Hokoku (report to supervisors), Renraku (update team members), and Sodan (consult stakeholders). Adapted for service industries, it ensures 360-degree communication so that everyone who should know about a project’s progress does know.
What is the 5-Whys method?
The 5-Whys is a root-cause analysis technique. State the problem, then ask “why did this happen?” five times in succession. Each answer becomes the subject of the next question. Five iterations typically reach the structural root cause rather than surface symptoms. The method must be performed by people with firsthand knowledge of the problem.
What is Mieruka?
Mieruka (見える化) means “making things visible.” It is Toyota’s system of visual controls that condense information so it is immediately understandable at a glance. Visuals fall into four types (3I1P): Identification, Informative, Instructional, and Planning. Toyota prefers whiteboards and physical displays over digital dashboards.
What is Genchi Genbutsu?
Genchi Genbutsu means “go to the source to find the facts.” It is Toyota’s principle of not relying on second-hand information when first-hand observation is possible. Toyota’s own translation: “go to the source to find the facts to make correct decisions, build consensus and achieve goals at our best speed.”
Why does Kaizen implementation fail?
Kaizen fails for six main reasons: treating it as a short-term project rather than a permanent commitment, over-emphasising quarterly KPIs, implementing in a change-resistant culture, management paying lip service without practising it, insufficient training on the tools, and leaders who do not lead by example.
Can Kaizen stifle innovation?
Yes. Kaizen focuses on improving what already exists. It cannot produce discontinuous innovation or respond to disruptive market shifts. An organisation that relies solely on continuous improvement will refine its existing products while competitors redefine the category entirely. The solution is to make Kaizen a rule but not the rule.
Sources & Downloads
All articles at bulsuk.com. The full 33-article series is available online.
Kaizen · the philosophy
PDCA
Horenso
5-Whys
Mieruka · visual control
Genchi Genbutsu
5S & Toyota thoughts
Full series index
Downloads & Templates
PDCA Wall Chart
A3 printable wall chart for tracking project status with colour-coded Post-its.
Horenso Visual Chart
Blank spreadsheet for tracking 360-degree communication across Report, Update and Consult.
5-Whys Excel Template
Blank 12-column spreadsheet for branching root-cause analysis using the table method.
5-Whys Example · Alencia
The worked example from this briefing. Complete analysis from problem through root causes to countermeasures.
Comments