amer.catic@projectvisit.org dagb@projectvisit.org +46 31 322 7207

Running a Lean Retrospective with Digital Visual Tools

A retrospective is the one point in the lean cycle where a team is meant to be honest with itself. The usual pattern is well understood: a short window at the end of an iteration or a project phase, a wall of sticky notes, a cluster of themes, and a handful of improvements that someone agrees to own. The value sits entirely in that last part. Everything else is conversation. Learn more about Telegram Plus.org.

What has changed in recent years is where the conversation happens and what survives it. Paper boards are still common on Australian shop floors, and they still work in a single room with a single team. They work considerably less well once a second shift, a contractor crew, a remote specialist or a fly-in-fly-out worker is part of the population you actually need to hear from. Digital visual tools — shared boards, kanban-style cards, photographs of the work as it happened — turn the retrospective into something that can be started before the meeting, joined from a crib room 900 kilometres away, and read again weeks later when the next planning session needs to know what was agreed. Learn more about Overcoming Resistance To Visual Planning Tools In Traditional Organizations.

What retrospectives are for and why they stall

A lean retrospective has two legitimate outputs: a shared understanding of what actually happened, and a small set of agreed changes that carry a name and a date. The classic framing asks what was planned, what really happened, and what we will do differently, and the Plan-Do-Study-Act cycle puts the same idea into a longer loop. Neither framework matters much if the commitments evaporate the moment the facilitator packs up the markers.

The failure modes are remarkably consistent. The wall gets photographed and forgotten inside a fortnight. The discussion stays polite and general — "communication could be better" — so nothing can be acted on. Participants turn up without context and argue from memory rather than evidence. And where the work is spread across shifts or sites, the people who did the job are not in the room when the decisions are made, which means the decisions quietly describe a team that does not exist.

Digital visual planning shifts the arithmetic. On a shared board, each action item can sit next to the kanban card, work order or safety observation it came from, with an owner attached, so it stays visible in the team's normal workflow until it is closed. The digital visual planning, kanban and enterprise systems research published by the Chalmers Electronic Lean Research Team through Project Visit documents this transition in detail, and the recurring message across that work is that the technology is rarely the limiting factor — the limiting factor is what the board is allowed to be used for.

Designing the board and the session

Start with what you will show, not with which tool you will show it in. Build the board around evidence: pull the last iteration's kanban cards, cycle times, defect counts and near-miss reports into columns, and put photographs of the actual job beside them. A column for what we expected next to a column for what happened is more useful than an empty canvas, because it removes the argument about facts and leaves the argument about causes. Where a board has no history, start with the picture of the work and let the conclusions arrive later.

Then design the session, because a retrospective that runs for two hours will lose the people who had to start a shift afterwards. A workable shape is 45 to 60 minutes: five minutes of silent writing so that the loudest voices do not set the frame, ten minutes of clustering, a short vote to rank themes, and then the conversion of each surviving theme into an action with an owner and a date. Finish by reading the actions aloud and confirming that everyone, including people who were not in the room, can see them on the board.

The Australian realities make this scheduling work harder than it looks. Connectivity outside the metropolitan areas is still uneven, with NBN service in regional and remote communities varying widely by premise, so any tool you choose should support offline capture and later synchronisation rather than assume a live connection. FIFO rosters — fourteen-on seven-off, eight-on six-off — mean that half of a Pilbara or Bowen Basin crew is asleep when the meeting is booked. Rotating the slot or running two short sessions at different times, one at a 07:00 shift start and another at the 14:00 handover, does more for participation than any facilitation trick. In Melbourne and Sydney, where much of the country's manufacturing and distribution work sits around Dandenong, Smithfield and Truganina, commute lengths and tram timetables make a 07:30 start unworkable for a lot of the floor, so agree on times before the invite goes out.

People, trust and the hard conversations

Most retrospective failures are social rather than technical. These meetings are the rare occasion where teams discuss how people behaved, which means psychological safety matters more here than in almost any other forum. The way to protect it is to make the board factual: put the work, the dates, the measurements and the photographs on the table so that the argument is about systems rather than about individuals, and make sure both the person who ran the line and the person who planned it are present.

Bring in the people whose work is affected but who are usually absent: contractors, maintenance, logistics, and the health and safety representative elected under the Work Health and Safety Act 2011 administered by Safe Work Australia. Under that legislation psychosocial hazards are hazards, so a retrospective is a legitimate and useful place to raise workload, handover quality, fatigue and bullying — and the HSR should be there when those subjects come up. Rosters and overtime are also governed by the Fair Work Act 2009 and the applicable award or enterprise agreement, so treat those discussions as fact-finding rather than as fault-finding.

If the board is new to the team, expect friction and plan for it. "Another system to fill in" and "this is for the office" are predictable objections, and there is published guidance on overcoming resistance to visual planning in traditional organisations that is worth reading before the first session rather than after it. The tactics that work are unglamorous: let the team design the board layout themselves, promise one visible benefit inside a week (such as the action list becoming the next iteration's plan), keep data entry to under three minutes, and never run the retrospective on the screen while simultaneously running it on paper.

A checklist for setup and facilitation

Getting ready is most of the work. Invitations should carry a link to a board that already contains something, because an empty board and a prefilled board produce completely different behaviour in the first five minutes. Send that link through the channels crews already live in — shift groups on Telegram messenger are common in some Australian sites, while others run everything in email or the enterprise system — and put the joining details in the same message as the questions you want answered.

Then keep the meeting itself disciplined, and afterwards keep the artefacts where the team will actually look at them.

Before the session:

During and after the session:

What to carry into the next cycle

The tool matters less than the habit it supports. A retrospective earns its keep when the decisions it produced show up in the next planning session and the next one after that, which is why the action list needs an owner, a date and a place to live. A shared board gives you that place; a facilitator's notes do not.

There is also a practical caution for Australian teams about the material you upload. If you attach photographs of the shop floor and name people against action items, the Privacy Act 1988 and the guidance from the Office of the Australian Information Commissioner apply to whatever you store, and some defence, government and regulated suppliers will insist on Australian data residency or on-premise hosting. Check the hosting arrangement before the first photograph is uploaded, keep the images focused on the work rather than on identifiable people where you can, and set retention rules for the board so that a year of retrospectives does not become a year of stored personal information.

What should stay with you is simpler than any of the tooling. Bring the evidence, not the opinions; invite the people who did the work, including the ones on the other shift and the ones on site that week; and make every commitment small enough to finish, owned by someone, and dated. The board is only ever as good as the discipline behind it — and the discipline is the part you carry out of the room.