A Kaizen Board in Japan, and a Manager Who Answered Every Sheet

The kaizen board held a couple dozen sheets. Each one numbered, each one stamped “jisshi-zumi” — already done. A board full of carried-out improvements is a strong sign in any factory, in any country.

But that wasn't the part that caught me. What caught me was the handwriting at the bottom of every single sheet.

I saw this on Katie Anderson's Japan Leadership Experience in 2024, at one of the manufacturing companies we visited. The board itself was straightforward: a problem written at the top of each sheet, the change made in the middle, the result at the bottom, and a photo or two taped alongside. These weren't ideas sitting in a queue, waiting for a committee to approve them. They were problems people saw, fixed, and then wrote up. The submission dates ran from July through September of that year. And I visited in November. A few ordinary months, not a highlight reel.

A note on how I read it. I don't read Japanese — my vocabulary runs out somewhere after “arigato.” So I photographed the sheets and had Claude translate them for me. The translations seem solid, though I can't vouch for every character. The titles and the handwritten notes I'm fairly confident about. The fine print in the boxes, less so. Treat the specifics below as my best reading, not a court transcript.

A different comment on every sheet

The remarks line at the bottom is called the “biko.” On every sheet, a manager whose signature reads Hayashi had written something there and signed it. Not a checkmark. Not initials. A sentence — a different one on each sheet.

On a sheet about adding price and item labels to a cardboard storage rack, Hayashi wrote something close to “This is the basics of the basics.” On one where the team swapped a stainless-steel machine sign for a laminated one and mounted it on the motor cover so product bags would stop knocking it loose, he wrote: “This is risk management too.” On a fix that cut a cleaning task from about 30 minutes down to 15 — by switching from a water wash to taking the part apart and using an air wash, which the team had cleared with quality assurance first — the note reads “Grateful to QA.” On a sheet where someone stopped a recurring paperwork mix-up by adding a machine's ID number to a form, he wrote, roughly, “Yep, that's a classic one.”

Not every note is a small sermon. Plenty of them just say “OK.” One reads “good observation.” The point isn't that each comment is profound. It's that someone bothered to write a real one.

Here's why that seems important to me. You can rubber-stamp a stack of forms in about the time it takes to finish a coffee. You cannot write 24 different, specific reactions unless you have actually read all 24. The variety is the proof. Hayashi read what each person did, and he responded to the person.

Most suggestion systems do the opposite

I've written before about why the suggestion box is dead. The classic version fails in a predictable way. Ideas sit for weeks. Most of them get rejected or quietly ignored. The whole thing lands on a busy manager's desk as one more task, and the person who had the idea rarely gets to see it through.

Norman Bodek pointed out something I keep returning to: a suggestion is something you, pointing at someone else, should do for me. A kaizen idea is something I can do, often for myself and my team. There is an “I” in idea. This board is what the second version looks like once it's running. People found the problem, made the change, and someone in authority took thirty seconds to say, in writing, “I saw what you did, and here's what I think of it.”

That gap between the two approaches is wider than it looks. Every ignored idea quietly teaches someone that noticing problems is a waste of their time.

What ends up on a kaizen board

The second thing the board shows is the subject matter. A good share of these are about safety and the basic difficulty of the work, not cost or throughput.

One sheet marks a set fork height on a pallet jack, because moving a load with the forks raised risked dropping it on someone. Another adds a chain to keep people out of a pinch point near a machine. Another secures a wash hose that people kept tripping over. And one repositions the sensor on a metal detector so that rejected product — bags weighing around 20 kilograms, about 44 pounds — wouldn't have to be lifted and rerun three separate times by hand. The sheet notes, plainly, that the lifting was hard on the operators doing it.

That's a compelling reason for a kaizen improvement — making work safer and easier.

Then there's the small stuff. Someone replaced a stiff carabiner with an S-hook because the original was a daily irritation. The writeup actually records the frustration. Hayashi's comment on that one is just “OK.” A stiff hook is not a crisis. But it was making someone's day slightly worse, every day, and now it doesn't.

None of these will show up in a cost-savings report with an impressive number attached. That's sort of the point. When the people doing the work choose what to fix, a lot of what they fix is the stuff that was making the job harder, or more dangerous, than it needed to be. A culture that only celebrates the big-dollar idea tends not to hear about the hose on the floor.

Whose names are on the sheets

The last thing I noticed was who else shows up in the writeups.

One sheet about a month-end inventory count credits a colleague by name for building the one-button calculation that replaced a slow manual process in a spreadsheet. The sheet about that wash hose notes that the team did the installation themselves, and Hayashi's comment reads something like “you did this yourselves.” Another thanks the quality assurance group for confirming that a change wouldn't hurt product quality.

These are small things to write down. Easy to leave off. The fact that they made it onto the form tells me that credit travels sideways here, to the colleague who helped and the department that checked the work. It doesn't only travel up to whoever signs the bottom.

I keep wondering what the equivalent of that biko line would be in most of the organizations I visit. Not the software, not the form, not the metric on the wall. Just the plain question of whether anyone in charge would take thirty seconds to read what you did and write back. If your improvements went up on a board this week, what do you think the comment would say — and would there be one at all?