Skip to content
KatafactsBeta

Visual management

Visual management audit

Visual management audit is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).

Customise with AISkill file ↓

1 · What it is

What it is

A visual board designed once and never checked tends to go stale exactly where it matters. This audit is the sustainment audit's exact shape, applied to a visual board: restate what the board was supposed to keep current, get a checklist of specific zones and practices to verify, and see honestly which are still holding.

2 · When to use it

When to use it — and when not to

Use it when

  • A visual board has been in place long enough to check whether its zones are actually being kept current.
  • You want to catch a zone that's gone stale, or one whose update ownership never got assigned, before the board loses the team's trust.
  • You want to verify the team is genuinely using the board, not just walking past it.

Not when

  • The board was just designed — give it real time to settle into use before auditing it.

3 · How to fill it in

How to fill it in

Original objective
What was the visual board supposed to keep current?
Sustainment checks
Drafted from what the board was supposed to show — verify what's actually still holding.
Narrative
Drafted from the checklist actually built.

4 · What good looks like

What good looks like

The example below audits the tier-7 visual board thirty-five days after it was designed — including whether the escalation-matrix zone's originally-unassigned update owner has since been named.

Same example, as a downloadable xlsx workbook.

Download .xlsx

Sustainment audit

35-day audit — renewal-risk queue visual board

Auditing: Renewal-risk queue visual board

Dana Whitfield · 2026-11-12 · 35 days since event

Original objective

Keep the KPI tree summary, escalation matrix reference, and ILUO snapshot zones all current enough that the team can trust the board at a glance.

Sustainment checks

3 of 4 holding (75%)

  • KPI tree summary zone is updated before each huddle, not stale
  • Escalation matrix reference zone has an assigned owner now (it didn't at launch)
  • ILUO snapshot zone reflects this week's actual training levels
  • Team actually references the board during the huddle, not just walks past it

At risk: Escalation matrix reference zone has an assigned owner now (it didn't at launch)

Narrative

Three of four practices are holding well — the KPI summary and ILUO snapshot stay current, and the team genuinely uses the board in the huddle. The escalation matrix reference still has no owner keeping it current, the exact gap flagged when the board was first designed — worth closing now that it's been over a month.

5 · Common mistakes

Common mistakes

  • Auditing a board that's never actually been used by the team.

    There's nothing to check if the board was designed but never adopted — that's a rollout problem, not a sustainment one.

  • Treating a stale zone as a minor issue rather than raising it.

    A board with even one stale zone starts losing the team's trust in all of it — small gaps are worth closing quickly.

6 · What it connects to

What it connects to

upstream

  • Visual board design guide

    The board's own zone specifications and update owners are exactly what this audit checks against reality.

downstream

    7 · Where AI helps

    Where AI helps

    Judgement — stays yours

    • Deciding how much time to give a board before auditing it
    • Deciding what to do about a zone that's flagged at risk

    Analysis — AI helps

    • Drafting specific, verifiable checks from a description of what the board was supposed to keep current
    • Drafting the narrative from the checklist actually built

    Drudgery — automated

    • Tallying how many practices are still holding
    • Identifying which zones are at risk
    • Exporting to xlsx in the house format

    9 · Rate this kata

    Rate this kata