All articles

Governance

Daily Management Board: Keeping an Improvement Alive Months After Handover

A daily management board turns a finished project into a daily habit of looking, asking and acting. This guide walks through a four section accounts payable board, the result the tool calculates, and the early signals that the discipline is slipping.

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

What the tool is for and when to use it

The Daily Management Board tool helps you define the board structure that drives operational discipline and fast issue resolution. You list the sections of the board, what each section shows, the measure or target it tracks, who owns it and how often it is updated. The tool then summarises that structure so you can see whether it holds together.

You use it in the Sustain phase of RDMAICS. Control gives you the response plan and the charts. Sustain asks a harder question. Will anyone still look at those charts in six months when the project team has moved on and the person who ran the pilot has changed roles.

A daily management board answers that question by making the looking visible. The board sits where the work happens. People stand in front of it. Numbers get written on it by the people who own them. Problems get raised the same day they occur rather than being discovered in a monthly report.

Build the board before handover, not after. If the board only appears once performance has already drifted, you are not sustaining anything. You are starting a new project.

The worked example: an accounts payable board

Everything in this guide is built on the sample data that loads with the tool. It describes an accounts payable team that has just finished an improvement project. The case is fictional. It exists to show the shape of a good board, not to report a real result.

The board has four sections. Safety and Quality tracks incidents and errors against a target of zero critical. SQDCP Delivery tracks invoices processed with an on time target of at least 97 per cent. Performance tracks cycle time and DPMO against targets of four hours or less and 80,000 DPMO or less. Improvement tracks action items and kaizen, with the measure being actions closed.

Three owners carry the four sections. The AP Manager owns two, the AP Clerk owns one and the Green Belt owns one. Every section is updated daily.

That is a small board. It fits on one surface and it can be walked in a short huddle. Small is the point. A board with twenty sections gets read by nobody.

Setting up the data

The input table asks for six things per row. Board section, content, metric or target, owner, update frequency and a row number. Four of those fields are marked required. Section, metric or target, owner and update frequency. The tool is telling you something with that choice. A section without a measure is a poster. A section without an owner is nobody's job. A section without an update rhythm will be updated when somebody feels like it, which means never.

Write the content column in the language the team already uses. The sample data says incidents, errors and invoices processed. Those are plain words. They describe what the team does. If you need a glossary to read your own board, rewrite it.

Make the metric column specific enough to settle an argument. On time at or above 97 per cent settles an argument. Good service does not. Cycle time of four hours or less settles an argument. Faster does not.

Note the Improvement row. Its measure is actions closed rather than a numeric threshold. That is deliberate. The improvement section is not there to hit a number. It is there to prove that the problems raised at the board actually get fixed and shut.

  • One owner per section, named by role so the board survives staff changes.
  • A measure that can be marked pass or fail by looking at it.
  • Content described in words the team already says out loud.
  • An update frequency that matches how fast the process can go wrong.
The input table with the four accounts payable sections. Notice that every row carries both a measure and a named owner before the result is generated.
The input table with the four accounts payable sections. Notice that every row carries both a measure and a named owner before the result is generated.

Reading the result

The calculated output gives you four headline counts. Four board sections. Four of four with a metric or target. Three owners. Four of four updated daily. It then names the ownership split as AP Manager 2, AP Clerk 1 and Green Belt 1, and states that every section is updated daily.

Read those counts as coverage tests rather than as a score. Four of four with a metric means no section is decorative. Four of four updated daily means there is no section that quietly runs on a different clock and gets skipped in the huddle. Three owners across four sections means the load is shared but not scattered.

Below the summary, each section is rendered as its own card showing content, metric or target and update frequency. The cards show Not set where an optional field has been left blank. That is not a fault. It is the tool being honest about what you have actually filled in.

The tool also offers an AI review that explains the result in narrative form. Use it as a second reading, not as the decision.

The calculated output showing four sections, four of four with a metric, three owners and four of four updated daily.
The calculated output showing four sections, four of four with a metric, three owners and four of four updated daily.

The decisions the board supports

The structure decides what gets talked about every day. With this board, the AP Manager opens on Safety and Quality against zero critical. If the answer is not zero, the huddle stops there and the problem gets an owner and a date. That ordering is not accidental. Safety and quality before delivery before performance before improvement.

The AP Clerk then reports invoices processed against on time at or above 97 per cent. The AP Manager covers cycle time and DPMO against four hours or less and 80,000 DPMO or less. The Green Belt closes with action items and kaizen, confirming which actions have been closed since yesterday.

That sequence supports three decisions. Does anything need escalating today. Does any miss need a containment action right now. Is the backlog of open actions growing or shrinking. None of those decisions need a report. They need five minutes and a pen.

The board also supports a handover decision. When the Green Belt leaves, the Improvement section needs a new owner. The tool shows you that one of your four sections is owned by a role that is temporary by design. Plan for that before it happens.

The full screen from inputs through to the section cards. Use this view to check the board end to end before you print it.
The full screen from inputs through to the section cards. Use this view to check the board end to end before you print it.

What tells you the board is slipping

Boards rarely fail loudly. They fade. The signals are structural and you can see most of them in the tool itself before you see them in performance.

The first signal is update frequency drifting away from daily. If a section quietly moves to weekly, it has stopped being a daily management item. Re run the tool. If updated daily drops below four of four, ask why.

The second signal is a measure going blank. A section with Not set where a target used to be is a section that has become commentary. The tool counts metrics for exactly this reason.

The third signal is ownership collapsing onto one person. The sample board has three owners. If all four sections end up owned by the AP Manager, the board has become a manager reporting to a wall rather than a team managing itself.

The fourth signal is the Improvement section. Its measure is actions closed. If actions are raised and never closed, the board has become a complaints list. That is the clearest early warning you will get.

  • Updated daily falls below four of four.
  • A metric or target reverts to Not set.
  • Owner count shrinks and one role absorbs everything.
  • Actions accumulate without closure.
  • Sections get added until the huddle no longer fits in the time allowed.

Common mistakes

The most common mistake is building the board for the audit rather than the team. A board designed to impress a visitor is dense, laminated and static. A board designed for the team is sparse, handwritten and changes every day. Choose the second.

The second mistake is targets without ownership. It is easy to write on time at or above 97 per cent. It is harder to write a name next to it. The tool makes owner a required field so you cannot skip the hard part.

The third mistake is mixing frequencies without saying so. If three sections are daily and one is monthly, the monthly one will be ignored in the daily huddle and forgotten in between. Either make it daily or move it to a different board at a different tier.

The fourth mistake is treating the board as the whole of Sustain. The board is the daily habit. You still need the control plan, the standard work and the audit rhythm behind it.

What this tool will not do

The tool defines structure. It does not run the huddle. It cannot tell you whether anyone turned up, whether the conversation was honest, or whether a miss led to action. Four of four updated daily describes an intention, not a behaviour.

It does not validate your targets. It accepts zero critical, on time at or above 97 per cent, four hours or less and 80,000 DPMO or less without judging whether those numbers are achievable or whether they match the control plan. You have to check that yourself.

It does not hold any performance data. There are no trends here, no run charts and no history. The tool tells you what the board should contain. The board itself carries the numbers.

It does not know your organisation chart. Three owners looks balanced on screen. Whether the AP Clerk has the authority to stop work when delivery slips is a question the tool cannot answer.

Use it for what it is. A fast, honest check that your board has sections, measures, owners and a rhythm before you hand the improvement back to the people who have to live with it.

daily management boardsustain phase RDMAICSSQDCP boardvisual managementdaily accountability processcontinuous improvement sustainmenttiered huddle board

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