What columns should a kaizen newspaper have?

The classic columns are an item number, the type of waste being attacked, the problem and root cause, the countermeasure, the owner (one named person), the due date, and the status, often tracked through the PDCA cycle. Owner and due date are the two most important and the two most often fudged; both must be specific for the tool to work.

How is a kaizen newspaper different from a regular action item list?

It is a specific, visible, disciplined form of action list built for improvement work. What sets it apart is that it is posted publicly where the team stands, updated as items move, reviewed on a fixed cadence, and it insists on a single named owner and a real date for every item. The visibility and the discipline are what make it effective where ordinary meeting minutes fail.

When do you use a kaizen newspaper?

During and after a kaizen event or blitz, to track the actions the team could not finish on the spot. It is a core part of the sustain plan, carrying open commitments across the boundary from the event to normal operations. Teams also use a running version for ongoing daily improvement, capturing small actions and tracking them to done.

Who owns items on a kaizen newspaper?

Each item is owned by a single named person, even if a group helps do the work. A task assigned to a department or 'the team' is effectively owned by no one and tends to stay open. Naming one owner per item, alongside a real due date, is the core discipline that makes the newspaper drive follow-through.

Why do kaizen newspapers stop working?

Usually because they go stale. A paper chart is only as current as the last person who updated it, and in a busy plant it can drift into fiction within a week, marked 'in progress' after work has stopped. Reviewing on a fixed cadence keeps it honest, and running it as a live shared log updated at the point of work makes it much harder to let slide.

The Kaizen Newspaper (Action Log)

Q: How does the kaizen newspaper relate to standard work?

Many newspaper items end in a change to how a job is done, and that change is only real once it is written into standard work and trained out. The newspaper tracks the change to done, and the updated standard is where the gain gets locked in. An item that closes without updating the affected standard has not truly finished; it has just stopped being watched.

A visible who-does-what-by-when list that keeps improvement commitments from dying the Monday after the event ends.

A kaizen newspaper is a visible action log for an improvement effort: a running list where each item is recorded as who does what by when, along with the problem, the countermeasure, and a status. It is posted where the team can see it, and its whole purpose is to keep open action items alive after the excitement of the event fades.

Every kaizen event, every improvement week, every good huddle ends the same way, with a handful of things the team agreed to do but could not finish on the spot. Move the rack. Update the form. Add the fixture. Untracked, those items are where improvement quietly dies: everyone remembers agreeing, nobody remembers who owns it, and three weeks later the process has slid back because the follow-through never happened. The kaizen newspaper is the low-tech, high-discipline tool that fixes this. It is one of the humblest instruments in lean manufacturing and one of the most decisive, because it is the difference between an event that changed the process and an event that produced a slide deck.

What is a kaizen newspaper?

A kaizen newspaper is a chart, on paper or a board or a shared sheet, that lists improvement actions and tracks each one to completion. The name is a translation of a Japanese term for the running list posted during improvement work; it is also called a kaizen action log, kaizen to-do list, or simply the newspaper. The format is deliberately plain, usually a table with one row per action item, posted in a spot everyone passes so status is public and unmissable.

What makes it a newspaper rather than a private task list is the visibility. It hangs where the team stands, updated as items move, so anyone can see at a glance what is open, who owns it, and whether it is on time. That public quality is not decoration; it is the mechanism. An action that lives on a posted board with your name next to it and a date behind it gets done in a way that the same action buried in meeting minutes never does. It is a specific, focused application of visual management aimed at one thing: commitments.

What columns go in a kaizen newspaper?

A kaizen newspaper carries just enough structure to make an item actionable and trackable, and no more. The classic columns are:

Column	What it captures
Item #	A simple sequential number so items can be referenced in the huddle
Type of waste	Which of the wastes this attacks (motion, waiting, defects, overprocessing, and so on)
Problem & root cause	The problem in one line, and the cause if it is known
Countermeasure	The specific action to take, stated concretely, not "improve flow"
Owner (who)	One named person, even if a group helps. Not a department, a person
Due (when)	A real date, not "ASAP" or "ongoing"
Status	Where the item stands, often tracked through the PDCA cycle: plan, do, check, act

Two columns do most of the work and are the two most often fudged: owner and due date. "Who" must be a single name. A task owned by "maintenance" or "the team" is owned by no one, and it will still be open at the next review. "When" must be a specific date. "Ongoing" is not a date, and items marked ongoing are items on their way to being forgotten. If you cannot name an owner and a date for an item, it is not ready to be on the newspaper; it is a topic, not an action.

The newspaper is a plain table with an outsized job: one row, one owner, one date, tracked to done.

How do you run a kaizen newspaper?

You run it by populating it during the work, assigning every item hard, and reviewing it on a fixed cadence until the list is empty. The mechanics are simple, and the discipline is everything:

Capture items as they surface. During a kaizen event or blitz, every idea that cannot be finished on the spot goes straight onto the newspaper rather than into someone's notebook. Capture beats memory; the point is that nothing agreed-to escapes the list.
Assign one owner and one date per item. Before an item is considered logged, it has a single named owner and a real due date. If the team cannot name either, the item is not ready and needs to be broken down or clarified first.
Post it where the team stands. Hang the newspaper on the area's board, not in a shared drive nobody opens. Visibility is the enforcement mechanism, and a newspaper filed away is a newspaper ignored.
Review on a fixed cadence. Walk the list in the daily huddle or a standing weekly review. Each open item gets ten seconds: on track, blocked, or done. Blocked items get help; done items get closed and celebrated briefly.
Close items visibly and keep going. Mark finished items done in front of the team, and keep the review running until every item is closed, then retire the sheet. The newspaper is finished when the work is finished, not when the event ends.

Keep the items small. A newspaper works best with actions sized in hours or a few days, not month-long projects; anything bigger should be broken into steps that each get their own row. And keep the review honest: an item that has been "in progress" for three reviews running is not in progress, it is stuck, and the review's job is to surface that, not paper over it.

What are the common mistakes with a kaizen newspaper?

Most failures trace back to breaking one of the tool's few rules. The recurring ones are worth naming so you can catch them in your own reviews:

Group ownership. Items assigned to "maintenance" or "the team" stay open. Assign one name, always, even when several people do the work.
Fuzzy dates. "ASAP" and "ongoing" are not dates and become permanent. Every item gets a specific day.
Items too big. A month-long project on a single row never visibly moves and demoralizes the review. Break big items into hour-sized or day-sized steps that each close.
No cadence. A newspaper nobody walks on a schedule is just a poster. The review is the engine; without it the chart is decoration.
Closing without standardizing. Marking an item done without writing the change into the standard means it will reopen itself in a month when the floor drifts back.

None of these are exotic. They are the ordinary ways discipline erodes under production pressure, and a good facilitator spends most of their review energy guarding against exactly this handful.

How does the kaizen newspaper relate to the event and to standard work?

The newspaper is the bridge between the event's energy and the plant's daily reality. A kaizen blitz generates changes fast, but always more than a week can finish; the newspaper is where the unfinished remainder lives so it does not evaporate when the team disperses. In that sense the newspaper is a core part of the sustain plan: it is the concrete, visible instrument that carries open commitments across the boundary from event to normal operations.

It also feeds back into standard work. Many newspaper items end in a change to how the job is done, and that change is only real once it is written into the standard and trained out. So the newspaper and the standard work an area maintains are two ends of the same loop: the newspaper tracks the change to done, and the updated standard is where done gets locked in. A newspaper item that closes without updating the affected standard has not actually finished; it has just stopped being watched.

The same ten open items go one of two ways. The newspaper is what decides which.

Why does a kaizen newspaper keep commitments from dying?

Because it makes forgetting impossible and ownership public, which are the two conditions under which follow-through actually happens. The kaizen event tradition is honest about the problem it solves: gains fade not because the ideas were wrong but because the follow-up never happened, and the follow-up never happened because nobody owned it and nothing kept it in view. The EPA's lean guidance notes that kaizen events run anywhere from one to seven days (EPA, Lean Thinking and Methods: Kaizen), which is simply not long enough to finish everything a good event uncovers, so a mechanism for the remainder is not optional. The newspaper is that mechanism, and the discipline of naming an owner and a date is what makes it work.

The place newspapers fail in practice is staleness. A paper chart on a board is only as current as the last person who updated it, and in a busy plant it can drift into fiction within a week, marked "in progress" long after work stopped. This is where the tool is moving off the wall. Plants increasingly run the kaizen newspaper as a live shared log, updated by owners from a tablet at the point of work, with overdue items flagged automatically, so the review works from reality instead of from a chart someone forgot to update. That live status, visible to the team and the supervisor the same shift, is the same real-time-visibility principle Harmony brings to production data generally, and it is the shift CLS made when it moved off paper. The newspaper only holds commitments if it stays true, and a live log is far harder to let go stale than a marker board. Pair it with a disciplined shift handover so open items cross shifts, and the follow-through that kills most events stops being a matter of memory.