Jishuken: Toyota's Self-Study Improvement Workshops
By Mahasys Multi Zenith · Manufacturing software for Indonesian plants · Last updated June 2026
Jishuken (自主研, from jishu kenkyūkai — "autonomous study group") is an intensive, hands-on kaizen workshop format developed within the Toyota group. A cross-functional team spends focused days on one shop-floor area, measures the actual condition in detail, and implements improvements on the spot. Its deeper purpose is not the improvement itself — it is training people to see waste.
Where jishuken comes from
In the 1960s and 70s, as Toyota extended the Toyota Production System beyond its own walls, it faced a teaching problem: TPS cannot be learned from a manual. The thinking behind it — seeing waste, questioning every motion, improving with your own hands — only transfers through guided practice on a real shop floor.
Toyota's Operations Management Consulting Division (OMCD), established under Taiichi Ohno, organized supplier companies into study groups. Each group would descend on one member's plant for an intensive improvement activity, guided by a Toyota sensei. The host plant got the improvement; every participant got the education. Then the group moved to the next member's plant. This rotating, mutual-development format became known as jishuken, and it remains one of the main channels through which TPS capability spreads through the supplier base — including supplier associations in Indonesia.
How a supplier jishuken typically runs
- Theme selection. A specific area with a specific problem — e.g. "reduce changeover time on stamping line 2" or "cut WIP between welding and assembly by half." Vague themes produce vague results.
- Grasp the current condition. The team spends the first days measuring reality: cycle times by stopwatch, operator movement diagrams (spaghetti charts), downtime records, WIP counts, defect data. Opinions are banned; observation is everything.
- Identify waste against the ideal. The team compares current condition to takt time and standard work, and lists gaps in the seven-wastes framework (overproduction, waiting, transport, overprocessing, inventory, motion, defects).
- Improve immediately. This is the jishuken signature: changes happen during the event. Relocate a rack tonight, rebalance the line tomorrow morning, re-measure after lunch. Not a report with recommendations — a changed process.
- Standardize and present. New standard work is documented, results are quantified against the baseline, and the team presents to management — including what they learned, not just what they changed.
Why data quality decides jishuken quality
Step 2 — grasping the current condition — is where most of a jishuken's time goes, and where weak plants struggle. If downtime is recorded as free-text guesses in a paper logbook, the team spends its first three days reconstructing reality instead of improving it. If cycle times exist only as engineering standards from two years ago, every discussion starts with an argument about the baseline.
Plants with reliable production data flip this equation:
- An MES provides actual cycle times, downtime Pareto, and OEE per machine — the baseline is ready before the team arrives.
- Digital checksheets give defect data by station and shift, searchable in minutes.
- Dashboards let the team watch the effect of a change in the next hour, not the next month.
The improvement philosophy is Toyota's; the measurement infrastructure is yours. Good data doesn't replace going to the floor and watching — nothing does — but it multiplies what a week of jishuken can accomplish.
Jishuken vs kaizen event vs Lean Six Sigma project
| Aspect | Jishuken | Kaizen event / blitz | Lean Six Sigma project |
|---|---|---|---|
| Primary goal | Develop people's ability to see and solve | Fix a specific problem fast | Reduce variation in a measured process |
| Duration | Days to weeks, often recurring | 3–5 days | 3–6 months (DMAIC) |
| Participants | Cross-company / cross-plant + sensei | Internal team | Belt-certified project team |
| Method | Direct observation + immediate change | Structured workshop | Statistical analysis (DMAIC) |
| Output | Changed process + trained people | Changed process | Validated, controlled improvement |
These are complements, not competitors. Many Indonesian suppliers run all three: jishuken with their OEM or supplier association, internal kaizen events monthly, and Lean Six Sigma projects for chronic variation problems.
Frequently asked questions
What does jishuken mean? +
Jishuken (自主研, short for jishu kenkyūkai — "autonomous study group") is an intensive, hands-on kaizen workshop format developed within the Toyota group. A cross-functional team spends focused days on one shop-floor area and implements improvements immediately rather than producing recommendations for later.
How is jishuken different from a normal kaizen event? +
Depth, participants, and learning intent. Jishuken runs deeper and longer; it deliberately mixes people from different plants or companies, often with an OEM sensei; and its primary goal is developing problem-solving ability — the improvement itself is the training exercise.
Apa itu jishuken bagi supplier otomotif di Indonesia? +
Aktivitas improvement intensif yang difasilitasi tim OEM atau asosiasi supplier — tim gabungan turun ke satu area produksi, mengukur kondisi aktual, dan mengimplementasikan perbaikan dalam hitungan hari. Supplier yang datanya rapi mendapat hasil jauh lebih besar dari aktivitas ini.
How should a supplier plant prepare for jishuken? +
Accurate baseline data (real cycle times, downtime, OEE), stable standard work documentation, operators briefed that the activity targets the process rather than people, and management committed to implementing changes during the event. Real-time production data lets the team quantify improvements immediately.
Further reading
- Jeffrey Liker, The Toyota Way (2004) — chapter on developing suppliers and jishuken's role in Toyota's supplier network.
- Steven Spear & H. Kent Bowen, "Decoding the DNA of the Toyota Production System," Harvard Business Review (1999) — why TPS transfers through practice, not documents.
- The Toyota kanban system explained — the pull system jishuken activities often target.
- Just-In-Time explained — the philosophy jishuken exists to teach.
- Lean Six Sigma — the complementary variation-reduction methodology.