What is a Kamishibai audit and how are the cards prepared?
In brief
Kamishibai checks with short cards, at regular intervals, whether a standard is being followed on the floor. The structure of a card, the layers, good and bad question examples and the path of a red card.
7 November 2026 · 5 min read
Sample company · demo dataKamishibai card
Kamishibai is Japanese for storytelling with picture cards; in manufacturing it has become the name of a method for checking regularly, with short cards, whether standards are being followed. The Lean Enterprise Institute lexicon defines standardised work as the current best method for each operator; Kamishibai is the routine that asks whether that method is alive on the floor. The card is not an audit form but an excuse for a visit: it takes the manager to a specific standard every day and makes them ask a question there.
How a card works
Each card carries one standard and a few questions: work sequence, a safety point, a quality check, 5S order.
Cards sit on a board; the auditor draws the next card, goes to the floor and answers.
If every answer is compliant, the card returns to the board green side up; if one answer is not, it returns red side up and an action is opened.
At the end of the period the board also shows which cards were not drawn; an undrawn card is a finding too.
Layers
The strength of Kamishibai lies in its layers. The team leader draws their cell's cards every day; the area owner draws a few of the same cards once a week, the plant manager once a month. Each layer looks at the same standard with a different question: the team leader asks “is it followed today”, the area owner “was it followed all week”, the plant manager “is this still the right standard”. The upper layer's card is not there to audit the lower layer but to see whether the lower layer's findings were answered.
How to prepare a card
Start from the standard, not from the card: a standard without a card can exist, a card without a standard cannot.
At most five questions per card; answered in five minutes.
Questions are answered by observation, not by interrogation: “did the operator measure at the checkpoint” is a good question; “does the operator know the standard” is a bad one.
Every question ends in yes or no; there is no “partly”.
The card shows the standard's name, its version and when the card was last updated; when the standard changes, so does the card.
The card asks about the process, not the person; the operator's name is not written in the answer.
Good and bad question examples
Good: “Is the screw torque checked with a torque wrench on every part?” Bad: “Are the screws tightened properly?”
Good: “Is red-tagged material in the designated area?” Bad: “Is 5S in good shape?”
Good: “Is the area in front of the emergency stop clear?” Bad: “Are safety rules followed?”
The path of a red card
A red card is information, not a penalty, and it says one of two things: either the standard is not being followed, or the standard cannot be followed that day. The second is at least as common as the first: the material came in differently, the fixture is broken, takt has changed. So the first question of a red card must be “why?”, and the answer usually corrects the standard itself. A red card does not close without an action; the action closes with evidence, and at the next draw the same question is asked again. A card that stays red draw after draw says that standard is a Kaizen topic.
Choosing the first cards
Look at the last six months of incident, non-conformity and customer complaint records; the three most repeated standards are the first cards.
Start with at most five cards per cell; the number of cards is what the floor can carry, not what the board can hold.
Write the card with the person who wrote the standard; try the question with the operator on the floor and change any question that is not understood.
Run only the team leader layer in the first month; upper layers are added once the routine has settled.
A fictional example
In a welding cell the card “is the torque wrench used on every part” came back red three days in a row. On the first day the team leader warned the operator; on the second day he got the same result, and on the third he asked why. The answer was simple: the cell had one torque wrench and shared it with the neighbouring cell; while the wrench was there, the operator tightened by hand. The action was to buy a second wrench; the card turned green the following week. The red card had shown not the operator's negligence but a missing condition in the standard.
Sample company · demo dataKamishibai layers
How it is done in Gemy
Cards, layers and frequencies are company settings; which layer draws which card and how often is defined.
In the field view the auditor opens the next card on a phone, answers the questions on the floor and opens an action with a photo if needed.
The board view shows every card's status by colour; cards not drawn in the period are visible too.
A red card does not close without an action; the finding lands on the single action list and goes to its owner with a due date and the evidence rule.
Kamishibai is a module the company switches on if it wishes; the standard itself is kept separately as a work instruction or a document.
In short
Kamishibai asks, with short cards and at regular intervals, whether a standard is alive on the floor. A card carries one standard, at most five observation questions and a yes or no answer. Layers look at the same standard at different frequencies with different questions. A red card is information rather than a penalty; its first question is “why?” and it usually corrects the standard. An undrawn card is a finding too.
Takt time is the customer's pace; Yamazumi stacks each station's load against that pace. Calculating takt, reading the chart, the balancing sequence and how to explain balancing to the operator.
Autonomous maintenance means the person who knows the machine best, the operator, takes over its daily care. The content of the first three steps, the abnormality tag, the CIL standard and the division of work between operator and maintenance.
5 Whys follows a single chain of a problem that has already happened; FMEA looks for failures that have not yet happened at the start of a design or process. When to use which, and where the two meet.
7 November 2026 · 5 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.