kaizen in practice · comparison

Kaizen Events vs Daily Teian Systems: Cadence, Roles, Results

D-KAI-08  |  First published 2026-07-18  |  Revised 2026-07-18  |  Primary sources: 7

Disclosure: Gemba Works Lab is supported by advertising. This page contains no affiliate links; if any are added in the future they will be clearly marked (per the FTC Endorsement Guides).

Every small manufacturer that decides to try kaizen faces the same fork within a month: run a concentrated improvement event, or stand up a daily suggestion routine. Vendors sell the first because it invoices cleanly. The Japanese record was built mostly on the second. The two are not rivals so much as different machines — one is a milling operation, the other is corrosion protection — but they compete for the same scarce resources in a small shop: supervisor hours and crew trust. This comparison puts the two side by side on cadence, roles, cost, and documented results, then gives the sequencing question a straight answer. The working question underneath it: which of the two failure modes — post-event decay or response silence — is your shop structurally more likely to commit?

The comparison, attribute by attribute

How to read the symbols: ◎ = documented in a primary source · ○ = partial or conditional · △ = weak — verify before relying on it · — = not applicable. Every symbol translates a sourced fact or a labeled estimate; bracketed numbers point to the reference list.

What the results columns actually say

Read the two "results" rows carefully, because they are not symmetrical kinds of evidence. Event results are point measurements: an MEP-network affiliate reports that 3–5 day events typically cut changeover times 50–70% and lead times 30–70%[4]. Those numbers are real and fast, and they are also exactly the numbers the sustainability fieldwork warns about: across 65 events in eight manufacturers, what predicted whether gains still existed months later was not the event-week result but the post-event mechanisms — management review, institutionalized follow-up[3]. The EPA module writes a whole third phase around the same point, with monthly meetings after the event week[1].

Teian results are trajectory measurements. Toyota's official program history shows the shape: 789 suggestions in the first year, roughly 20,000 by 1967, 168,000 in 1972 against a 120,000 target, 220,000 through early October 1973 from a workforce of about 43,000 — with the adoption rate climbing from 29% in 1956 to 76% in 1972[2]. Two decades of compounding, and the striking variable is not idea quality but the adoption rate: the system got better at saying yes. A documented single suggestion from 1972 — automatic piston-ring setting equipment — saved about ¥24 million (roughly $91,000) a year[2], but the design lesson for a 30-person shop is the ratio, not the jackpot: mature systems approve most of what comes in, quickly, and count what they implement[5].

Roles: the org-chart difference nobody prices in

An event needs a cast: a sponsor who owns the target, a facilitator who runs the week (hired at published rates of $1,500–$3,000 a day if not internal[6]), a 5–8 person team pulled off their jobs, and an auditor with a calendar date. Teian needs exactly one named role beyond the workforce itself: the supervisor who reads and answers, inside the deadline, every week including bad ones. This is why events feel easier to buy and teian feels easier to afford — and why each fails where it does. An event's cast disperses when the week ends, which is the decay mechanism[3]; teian's single role is invisible on any invoice, so it is the first thing sacrificed to a rush order, which is the silence mechanism. OSHA's worker-participation guidance describes the underlying law of both: people keep contributing to systems that visibly act on what they raise, and stop when the system goes quiet[7].

The sequencing answer

Start teian first — four weeks before any event. The reasons are practical, not philosophical. First, the suggestion flow generates the event target list: after a month you know which changeover, which cell, which recurring irritation deserves a concentrated week, instead of letting a facilitator's intake questionnaire guess. Second, teian establishes the response habit that event follow-up will depend on — a shop that cannot answer a suggestion in 72 hours will not hold a 30-day audit date either. Third, the costs stack sensibly: teian's sub-$1,000 start (estimate) risks almost nothing while the crew decides whether this attempt is real — a live question if a previous program died (D-KAI-05).

Then run events as punctuation, not as the program. Two to four a year is plenty for a shop under 200 people, each with its follow-up phase scheduled before the event is[1], each feeding its results back into standard work so the gain outlives the team — the capture step our video SOP method (D-SKT-04) makes cheap. The full calendar that interleaves both cadences — teian from week 3, first event in month two, monthly reviews from month three — is the 90-day plan in the pillar guide (D-KAI-P01), with the budget arithmetic at small scale in D-KAI-06 and the job-shop target translation in D-KAI-07.

The honest summary: events buy speed and proof; teian buys permanence and participation. A shop that runs only events rents its improvements. A shop that runs only teian improves slowly and may never crack its biggest bottleneck. The record — from the EPA's phase model to Toyota's twenty-year suggestion curve — belongs to shops that run the drumbeat and add the bursts[1][2].

Last updated: 2026-07-18 | Primary sources referenced: 7 | Every unlabeled figure links to a source; estimates and schematic figures are marked as such. Spotted an error? Tell us via the contact page.