Takt or Cadence Board¶

Coordination artifact — instantiates Tempo-Matched Response Governance

Puts both clocks on one board — the rhythm the work is running at and the rhythm the environment demands — so tempo mismatches and their bottlenecks are seen at a glance before they bite.

A tempo mismatch is easy to miss when the two clocks live in different heads and different reports. Takt or Cadence Board is the shared display that puts them on one surface: the actual rhythm each part of the work is running at, laid against the target rhythm the environment demands, with deviations flagged and bottlenecks visible. Its defining property is that it is descriptive, not directive — it decides nothing and stops nothing; its whole value is making a mismatch common knowledge, early and cheaply, so that some rule, gate, or person acts on it. Where other mechanisms in the archetype change the tempo, the board is what lets a team see that the tempo needs changing.

Example¶

An assembly line has to match customer demand. Available production time divided by demand gives a takt time of, say, 90 seconds per unit — the rhythm the environment is asking for. The Takt or Cadence Board shows each station's actual cycle time against that 90-second line: stations 1–3 run comfortably under it in green, but station 4 runs 105 seconds and shows red — it is over takt, the bottleneck that will let work-in-progress pile up in front of it and starve the stations after it. Nobody has to reconcile spreadsheets to notice; the mismatch is on the wall at the morning standup, where the team can rebalance work off station 4 before the pile-up forms. The board changed nothing by itself — it made the one number that mattered impossible to overlook.

How it works¶

What distinguishes it from a status dashboard is the deliberate juxtaposition of the two clocks and its role as a trigger for shared attention:

Co-locate the clocks. The demand-set target rhythm and the actual operating rhythm sit on the same surface, so the gap between them — not either number alone — is the thing on display.
Inventory the cycles. Each response cycle or station is shown with its current rhythm, so the board reveals where in the flow the rhythm breaks, not just that it does.
Flag the breach. Deviation past a set tolerance is highlighted, turning a subtle drift into a visible signal that pulls the team's eye.

Tuning parameters¶

Target choice — which clock is drawn as the target line (customer demand, an upstream cadence, a forecast). Get the target wrong and every reading is measured against the wrong rhythm.
Deviation-highlight threshold — how large a gap turns red. This is the tempo-fit tolerance made visible: tight highlighting catches drift early but cries wolf; loose highlighting is calmer but late.
Refresh frequency — live versus periodic. A live board catches drift immediately but demands constant attention; a daily board is calmer but can miss a fast excursion.
Granularity — per-station versus whole-line rollup, trading diagnostic precision against clutter.
Ritual coupling — the standup or review cadence built around reading it, which is what converts seeing into acting.

When it helps, and when it misleads¶

Its strength is turning tempo mismatch into common knowledge — cheap, early warning that everyone shares, so the response isn't gated on one person happening to notice.^[1] A visible bottleneck gets addressed; an invisible one metastasizes.

Its failures are the failures of any information radiator. It can become wallpaper — so familiar that no one reads it — or it can be gamed, with numbers massaged to keep the board green while the real rhythm drifts. And a tidy green board invites the deeper trap: mistaking visibility for control, treating "the board looks fine" as proof the tempo is matched when in fact the target line itself has gone stale. The disciplines are to couple the board to a ritual that forces a response to red, and to re-baseline the target rhythm as demand changes rather than leaving yesterday's takt line up while today's demand has moved.

How it implements the components¶

Takt or Cadence Board fills the make-it-visible subset — the shared picture of the two clocks and the gap between them:

response_cycle_inventory — the board displays each response cycle with its current rhythm and where the flow is bottlenecked.
tempo_fit_threshold — it draws the target rhythm and the tolerance band, and highlights the breach when actual drifts outside it.

It does not re-estimate the target when demand shifts (environmental_clock_profile, cadence_adaptation_rule — Rolling Forecast Resynchronization), stop a release (readiness_and_expiry_window_register, deliberate_wait_gate — Readiness Gate), or meter one out (absorptive_capacity_monitor, action_lead_time_map — Slow-Release or Phased Absorption Plan). It shows the mismatch; the acting mechanisms respond to it.

Instantiates: Tempo-Matched Response Governance — the board is the shared surface on which a tempo mismatch becomes visible.
Consumes: Rolling Forecast Resynchronization — supplies the current target rhythm; Decision Latency Scorecard supplies the cycle-time readings it displays.
Sibling mechanisms: Rolling Forecast Resynchronization · Decision Latency Scorecard · Readiness Gate · Slow-Release or Phased Absorption Plan · Queue-Jump Authority · Environmental Time-Constant Estimate · Event-Triggered Escalation Rule · Freshness Timer or Timestamp Badge · Hold-and-Revalidate Protocol · Lead-Time Decomposition Map · Preapproved Response Playbook

Notes¶

The board is descriptive, not a governor: it changes nothing on its own. Its entire contribution is making a mismatch visible so that a rule, a gate, or a person acts — which is exactly why the standing trap is to treat a green board as evidence the tempo is matched. A board is only as honest as its target line; re-baseline that line as the environment's demand moves, or the display will reassure you against the wrong clock.

References¶

[1] Takt time — available production time divided by customer demand — is the real Lean/Toyota Production System concept for the demand-set rhythm work should run at. A takt board is the practice of posting actual cycle times against that rhythm so deviations are seen on the floor. ↩