FreeNo sign-upYour notes stay on your computer
Kaizen Tracker
Log every improvement suggestion from the people doing the work, see which are still waiting past a week, and track the defect rate every month to see whether errors keep falling.
This tool also runs as a stage in a playbook, which takes you through several tools in order:
- Reduce errors and defects Stage 6 of 6: how do errors keep falling after the project ends? Start at stage 1
Not following the playbook?
The rhythm
Every suggestion, with the date raised and the date answered
Leave the answer date empty while it waits. Reopen your progress file each week to add the new ones.
Your notes never leave your browser
Suggestions, names and counts stay on your computer and in your progress file. To write the diagnosis, only counts and dates worked out as days are sent to our server. How it works
The defect rate each month
Count the same way every month, with the same definitions, so the months compare.
Chances to go wrong in each unit
Each month
The suggestions
Highlighted: waiting more than a week for an answer.
The defect rate, month by month
Save your progress
Download your progress file to continue from this point any time, on any computer: choose it under "Coming back?" at the start of the tool. Each new file includes everything so far, including the earlier stages when they are connected, so keep the latest one. Your work stays in this browser only until you close it.
Not saved yet.
Take your results with you
A PDF of the suggestions and how fast each was answered, the defect rate month by month, and the diagnosis. Inside the playbook, it holds every stage's diagnosis.
About the tool
Why it exists
Errors keep falling only if improvement keeps going
A project ends; the errors come back unless the people doing the work keep finding small fixes. Kaizen is that habit: small changes from everyone, designed where the work is done, usually through a short daily meeting and a board for suggestions, with every suggestion answered within a week. Unanswered suggestions stop people suggesting. This tool logs each suggestion with its dates, shows which are still waiting, and tracks the defect rate every month with the same definitions.
It works on its own, and as the last stage of our playbook for reducing errors and defects, where it picks up the chances per unit from stage 1 and the owner and measure from stage 5, and puts every stage's diagnosis in one report.
The method
How the tool works
The suggestions. What was suggested, by whom, the date raised, the date answered, and what came of it: tried and kept, tried then used everywhere, tried and not kept, or not done and told why.
Within a week. Any suggestion waiting more than seven days stops the tool. The median days to an answer, and how many were tried, show whether the habit is working.
The rate each month. Units, defects and how many customers found, with the chances per unit fixed. The tool works out DPMO each month, the fall since the first month, and the share of errors customers find.
When it stops falling. If the last three months are no lower than the best month before them, the easy fixes are done: run stages 2 and 3 again to find where errors start now.
What leaves your computer. Suggestions and names stay in your browser and progress file. To write the diagnosis, the page sends counts and days only, and the server keeps nothing.