How to Conduct a Kaizen Event Using Digital Visual Boards

A Kaizen event is a focused improvement workshop in which people who do the work examine a problem, identify its causes, test changes and agree on a better operating method. A digital visual board gives that process a shared workspace. It can display the current state, capture observations, assign experiments and preserve decisions after the workshop ends.

For Australian organisations, the format is especially useful when teams are spread across factories, offices, warehouses, mines or customer sites. A team in Melbourne may be working with colleagues in Brisbane and Perth, while a maintenance specialist is on a FIFO roster. A well-designed board keeps the improvement effort visible across locations without turning the event into another series of disconnected meetings.

Set The Improvement Focus

Begin with a specific business problem rather than a broad ambition such as “improve productivity”. A useful Kaizen theme might be reducing the time from a customer order to dispatch, cutting changeover delays on a production line, improving first-time quality or making an approval process easier to follow. Define the boundary of the process, the people involved and the measure that will show whether the change worked.

Write a short problem statement on the digital board. Include the current performance, the desired condition, the period being studied and any restrictions. For example, an Australian food manufacturer might examine a packing process that regularly misses the afternoon carrier collection. The team should know whether it is investigating labour allocation, material availability, equipment reliability, batch sequencing or all of these factors.

Choose a facilitator who can protect the method and keep discussion grounded in evidence. That person does not need to be the most senior manager. They need to prepare the board, explain the working agreements, manage time and prevent the loudest voice from becoming the default answer. Facilitator development resources, such as practical lean training, can help organisations build this capability rather than relying on enthusiasm alone.

Invite people with direct process knowledge, including operators, planners, supervisors, quality staff, maintenance and relevant support functions. If the event affects a unionised workplace, include appropriate consultation early. A clear scope makes it easier to respect workplace agreements and focus the group on process improvement rather than personal performance.

Design A Board That Shows Flow

A digital visual board should make the work understandable within seconds. Use columns that match the improvement cycle, such as “problem”, “evidence”, “cause”, “countermeasure”, “owner”, “test” and “result”. Cards should contain concise information, with links to documents, photographs, process data or meeting notes where more detail is needed.

Do not reproduce every field from an enterprise system. The board is a thinking and coordination space, not a second database. A card might record an observed delay, its location, the relevant shift, the person collecting evidence and the next action. Keep the language concrete. “Waiting for QA release at line 3 for 22 minutes” is more useful than “quality bottleneck”.

Visual cues need consistent meanings. Colours can distinguish risk, status, work type or urgency, but too many colours create noise. The psychology of colour coding is relevant here: a colour should carry one agreed meaning, and that meaning should be documented in the board legend. Use accessible contrast and do not rely on colour alone, especially when the board is viewed on mobile devices or shared in a dim control room.

Set work-in-progress limits for the investigation itself. If the team has twelve untested ideas, it has probably started collecting solutions before understanding the problem. A limit of two or three active experiments encourages the group to finish learning cycles. Kanban principles are valuable here because they expose stalled work and make hand-offs visible.

Access and security also matter. Australian organisations may be managing commercially sensitive information, personal data or operational details related to critical infrastructure. Use role-based permissions, single sign-on where appropriate and a clear retention policy. The board should be easy to access on a factory tablet, laptop or phone, while sensitive attachments remain protected.

Run The Event Around Direct Evidence

A short preparation period improves the quality of the workshop. Gather baseline measures, map the current workflow and identify the people who perform each step. Ask participants to bring examples from different shifts, product types and operating conditions. A process that looks stable during a weekday day shift may behave differently on a weekend or overnight roster.

Start the event by reviewing the purpose, scope and board rules. Then walk through the process as it actually happens. In a warehouse near Port Botany, that may mean tracing an order from release through picking, replenishment, packing and carrier handover. In a regional Queensland operation, it may involve considering long replenishment lead times, contractor availability and weather-related interruptions. The digital board should record what the team sees, not what the procedure says should happen.

Use a simple sequence: observe, describe, investigate, test and review. Ask for facts before explanations. Record waiting, rework, interruptions, searching, movement and unclear decisions. A virtual or hybrid team can contribute photographs, timestamps and short notes, but remote participants should be given a deliberate role. Otherwise, people in the room will dominate the discussion while colleagues in Western Australia or another site struggle to enter the conversation.

Time-box analysis so that the event does not become an endless mapping exercise. Five Whys, cause-and-effect diagrams, Pareto charts and simple tally sheets can help the team move from symptoms to likely causes. Treat each cause as a hypothesis until the process provides evidence. “The system is slow” may turn out to mean that a required approval is hidden in an inbox, a barcode is frequently unreadable or a replenishment signal is misunderstood.

Plan around operational reality. A team in Sydney may need to work across daylight-saving changes with a partner in Queensland, while Perth colleagues are several hours behind eastern states. Put the session times, board links and decision deadlines in one visible place. If staff use terms such as “arvo”, “ute” or “tradie” in everyday conversation, retain familiar language in local notes where it helps, but use precise labels for measures, owners and controls.

Convert Ideas Into Controlled Experiments

A Kaizen event should finish with tested countermeasures, not a wall of attractive suggestions. Each proposed change needs an owner, a start date, a defined trial period, a measure and a condition for review. A card might state: “Move label verification before packing; trial on afternoon shift for five working days; measure mislabels per 1,000 units and packing time.”

Select experiments that are small enough to run safely and meaningful enough to reveal something. If the suspected cause is an unclear handover, trial a standard digital checklist at one work cell before changing the entire site. If the issue is a long approval queue, test a threshold-based escalation rule with the relevant manager. Small experiments reduce resistance because people can evaluate the change without committing the whole operation.

Include the people affected by the change in its design. An improvement that saves office time but adds awkward steps for operators will not last. Consider training, ergonomics, safety, workload, industrial obligations and customer impact. In Australia, a shift pattern, heat exposure, remote travel or reliance on labour hire may alter how a solution works in practice. The best countermeasure is one that fits the real operating environment.

Use the board to distinguish assumptions from results. A hypothesis card might be linked to the original observation, while an experiment card records the method and a result card shows the measured outcome. This creates a traceable improvement story. It also prevents a popular idea from being declared successful simply because the workshop ended with agreement.

Review results at an agreed cadence. Daily checks may suit a short production trial; weekly reviews may suit procurement or service processes. Compare performance with the baseline and record side effects. If output improves but rework rises, the experiment has produced useful learning rather than a simple success. Move unresolved items back to analysis, adjust the countermeasure or close them with a reason.

Make The New Method Visible And Durable

When an experiment proves effective, convert the learning into a clear standard. Update the relevant work instruction, visual control, checklist, training material or system configuration. Link the final standard to the board card so a future team can see why the change was introduced. A board that records only tasks, without decisions and rationale, loses much of its value.

Assign ownership at two levels. The process owner is responsible for maintaining the improved method, while a board owner keeps the digital workspace accurate and useful. These roles may belong to different people. Without them, completed cards accumulate, outdated measures remain on display and staff stop trusting the board.

Connect the Kaizen board with existing enterprise systems only where the connection helps flow. A link to a maintenance ticket, quality record or resource plan can remove duplicate entry. Automatic feeds may show performance trends, but they should not replace conversation at the workplace. Digital visual management works when data supports observation and decision-making, not when people spend the event formatting dashboards.

Make the board available after the event as a living record of improvement. Teams can use a small backlog for follow-up actions, a results area for confirmed changes and a parking area for issues outside the current scope. Periodic reviews should remove stale cards and check whether the new process is still being followed.

Project Visit’s research and project updates offer useful context for organisations exploring digital visual planning, Kanban and lean process management. Research-informed practice can help teams ask whether a tool is improving coordination, learning and transparency rather than simply adding another screen.

Practical Rules For The Pilot

• Start with one process, one team and one measurable problem.
• Give every active card an owner, due date and next observable step.
• Use colour sparingly and publish a short legend beside the board.
• Record evidence from different shifts, sites and operating conditions.
• Limit active experiments so the team can complete each learning cycle.
• Agree how sensitive information, photographs and personal data will be handled.
• Review the board after 30 days and remove anything that no longer supports decisions.

A strong digital Kaizen event combines disciplined observation with visible coordination. The board should help people see the work, understand the cause of a problem, test a practical change and retain the learning. It is most effective when operators, managers and support teams can contribute in the same place, whether they are in a Melbourne plant, a Perth project office or a remote site on a different roster.

The essential point is simple: use the digital visual board to make improvement work observable and testable, then let evidence—not the board itself—guide the next decision.