All articles

Governance

Visual Management Board: Keep the Gain Visible Long After Handover

A Visual Management Board names the few things a team must see every day to hold a process gain. This guide walks through a worked accounts payable example with four board elements, four owners and daily updates, and shows the early signs that a board is slipping.

Ci Flow editorial team 13 October 2026 8 min read
Visual Management Board, Sustain phase tool guide from Ci Flow

What the tool is for and when to use it

The Visual Management Board tool asks you to specify the visual management board elements that make process status and issues visible at a glance. That is the whole job. You list each element, say what it is for, say how it is shown, say where it lives, name an owner and set an update frequency.

You use it in the Sustain phase of RDMAICS, after the controls from the Control phase are agreed and the project is handing back to the line. Control decides what gets measured and what the limits are. Sustain decides how the team will see that information without asking anyone for a report.

The reason to be formal about this is simple. A gain fades when nobody can see it move. If the only evidence of performance sits in a monthly pack, the team learns about a problem four weeks late. A board shortens that gap to a day. The tool forces you to be explicit about the few things on the board, not the many things you could put there.

Build the board before handover, not after. The board is part of the handover, in the same way a work instruction is. If you leave it until the project team has moved on, nobody owns the first update.

The worked case: an accounts payable area

The example here is the sample data built into the tool. It is fictional. It describes an accounts payable area that has just finished an improvement project and is moving into Sustain.

The board has four elements. KPI tiles show key metrics on a digital display. An exception board highlights open issues on a physical board. An action tracker tracks improvement actions on a kanban board. SPC charts show process stability on a digital display.

All four sit in the AP area. That matters. The board is where the work happens, not in a manager's office or a shared drive. Owners are the AP Manager for the KPI tiles, the AP Clerk for the exception board, and the Green Belt for both the action tracker and the SPC charts. Every element is updated daily.

Four elements is a deliberate number. It covers performance, problems, actions and stability. Read in order, those four answer the questions a daily huddle actually asks. How are we going. What is stuck. What are we doing about it. Is the process behaving the way we expect.

Setting up the data

The table has seven columns. Three are required: the board element, the owner and the update frequency. The tool marks those with an asterisk because a board without an owner and a rhythm is a poster.

Purpose is the column people skip. Do not skip it. Writing "Show key metrics" or "Highlight open issues" is a test of whether the element earns its space. If you cannot write a short purpose, take the element off the board.

Visual tool records the medium. In this case the mix is two digital displays, one physical board and one kanban board. Mixing media is normal. A digital display suits charts that refresh themselves. A physical board suits issues the team writes up by hand in the moment.

Location is a single field but it drives behaviour. All four elements are in the AP area, so the board is one stop rather than four. Update frequency is the commitment. Daily for all four here, which matches a team that meets every day.

  • Name the element plainly, the way the team will refer to it
  • Write the purpose in one short line
  • Record the medium, including whether it is physical or digital
  • Put the location where the work is done
  • Name a person or role that keeps it current, and the cadence they commit to
The four sample elements with purpose, visual tool, location, owner and update frequency filled in. Notice that every row has an owner and a frequency, not just a name.
The four sample elements with purpose, visual tool, location, owner and update frequency filled in. Notice that every row has an owner and a frequency, not just a name.

Reading the result

The tool counts the board and reports back. The calculated output here reads: 4 board elements, 4 of 4 with an owner, 3 owners, 4 of 4 updated daily, 1 location. The summary adds the breakdown of visual tools as digital display 2, physical board 1 and kanban board 1, and the owner split as Green Belt 2, AP Manager 1 and AP Clerk 1.

Read the ratios first. Four of four with an owner means no orphan elements. Four of four updated daily means one rhythm, not a mix of daily and weekly that the team has to remember. One location means one walk.

Then read the owner count. Three owners across four elements is a sign of shared load rather than a single hero. The Green Belt holds two elements, which is worth noting for a reason covered below. The AP Manager and the AP Clerk each hold one, so the line is already carrying part of the board.

Each element is then shown as its own card with purpose, visual tool and update frequency repeated, the owner named, and the location shown as evidence. The status field on each card reads "Not set" in the sample data, which is a reminder that the tool records your design and leaves the judgement to you. The tool also offers an AI review that explains the result.

The calculated output with counts, the visual tool mix and the per element cards. Notice the status on each card reads Not set, so the tool is describing your design rather than grading it.
The calculated output with counts, the visual tool mix and the per element cards. Notice the status on each card reads Not set, so the tool is describing your design rather than grading it.

The decisions this supports

The first decision is scope. Four elements and one location is a board a team can actually maintain. If your count climbs past that, you are deciding to spend more of the team's morning on the board than on the work. Use the counts to argue that case with evidence.

The second decision is ownership transfer. In the sample, the Green Belt owns two of the four elements. That is normal at handover and a problem six months later. The board tells you exactly which two elements need a new owner before the project team leaves, and it tells you the AP Manager and AP Clerk are already carrying one each.

The third decision is cadence. Every element is daily. If a metric only moves monthly, a daily slot on the board trains the team to ignore it. Review frequency against how fast the underlying number actually changes.

The fourth decision is media. Two digital displays carry the KPI tiles and the SPC charts. If a screen goes dark, half the board disappears and nobody notices for a week. Knowing the split tells you where to plan a fallback.

The whole tool screen, inputs through to result. Use this view when you walk the board design through with the receiving manager at handover.
The whole tool screen, inputs through to result. Use this view when you walk the board design through with the receiving manager at handover.

Signs the board is slipping

A board rarely fails loudly. It fades. These are the signals worth watching in the months after handover, and most of them are visible in the board's own fields.

The clearest one is the owner column. If the Green Belt still owns the action tracker and the SPC charts a year on, the improvement never transferred. It is being propped up by a project resource.

The second is frequency drift. The sample commits every element to daily. If the exception board has the same three issues written on it that it had a fortnight ago, the stated frequency and the real frequency have parted ways.

The third is the action tracker emptying out. An action tracker with nothing on it does not mean the process is perfect. It usually means nobody is raising anything. Treat an empty tracker and a silent exception board as the same warning.

  • One owner holding most of the elements, especially an improvement role rather than a line role
  • Stale content on a physical board while the digital tiles keep refreshing themselves
  • A dark screen that nobody has reported
  • No new entries on the action tracker or the exception board
  • The daily huddle moving away from the board, or shortening to a notice read out

Common mistakes

The most common mistake is putting everything on the board. Teams add every metric they have ever reported, then stop looking at any of them. The sample stays at four elements for a reason. Each one answers a different question.

The second mistake is leaving the owner as a team name. "AP" is not an owner. The sample names the AP Manager, the AP Clerk and the Green Belt. A role can be held accountable at a huddle. A department cannot.

The third mistake is putting the board where the work is not. All four sample elements sit in the AP area. A board in a meeting room becomes a meeting artefact and stops being a working tool.

The fourth mistake is setting a frequency nobody agreed to. Daily means someone touches four elements every working day. Confirm with the named owners that the cadence fits the shift pattern before you write it down. Writing daily and delivering weekly is worse than writing weekly, because the team stops trusting the board.

What this tool will not do for you

The tool records a design. It counts elements, owners, frequencies and locations, and it shows the visual tool mix. It does not check whether any of it is true. In the sample, the status on each element card reads "Not set". Nothing in the output confirms the KPI tiles were updated this morning.

It does not judge whether you chose the right metrics. It will accept any purpose you type. Deciding that key metrics, open issues, improvement actions and process stability are the four things worth seeing is your judgement, taken from the Control phase, not an output of this tool.

It does not audit. There is no count of missed updates, no history of who refreshed what, no trend of board health over time. If you want that, you need a separate check, usually a short walk by a manager who looks at the board and asks the owner one question.

It does not create the behaviour. A board makes status visible. People make it matter. The daily huddle, the manager who stops at the board, the clerk who writes up an exception instead of working around it. The tool gives you the structure and the counts. Holding the gain for months after handover is still a choice the team makes every day.

visual management boardsustain phase toolsRDMAICS sustainprocess visual controlsdaily management boardKPI tiles and exception boardcontinuous improvement handover

Run this method inside Ci Flow

RDMAICS, A3, Just Do It and Kaizen projects with the full Lean Six Sigma toolset, AI interpretation and tollgate presentations built from your real evidence.

Keep reading

Ci Flow

Ci Flow connects improvement methodologies, guided tools, project evidence, AI support, collaboration and tollgate presentations in one operational-excellence workspace.

RDMAICS · A3 · Just Do It · Kaizen

© 2026 Ci Flow. All rights reserved.

Built for evidence-led continuous improvement