All guides
Guide · Measurement and operating cadence

An operations review meeting agenda built around decisions, not dashboards

Start the review from the decisions it must support, read a small set of measures in time order, and spend the meeting on decisions and owners rather than on reporting. Measurement systems usually fail the same ways: too many measures, measures not tied to strategy, and measures nobody reviews or retires.

Published · Updated

Start from the decisions

Performance-measurement systems often fail because they collect too many measures, are not linked to strategy, and are not reviewed or updated. Measurement also costs something: data collection, attention and distorted behaviour. More measurement is not automatically better, and the right number of measures depends on context.

Financial measures alone are lagging indicators and can distort behaviour. Adding customer, internal-process and learning perspectives lets managers see the drivers of future performance, not only its financial result. Scorecards can still turn bureaucratic and be gamed, so ownership and a regular audit matter.

Read the data in time order

A run chart plots a measure in time order and uses the median, runs and shifts to separate signal from noise. It is deliberately simpler than a control chart and makes the effect of a change visible without waiting for an aggregate before-and-after comparison. It is less sensitive than a control chart and does not establish cause on its own.

A short, regular huddle can help, with caveats

A scoping review of 158 empirical studies of frontline huddles found that 67.7% reported positive team-process outcomes and 44.3% reported positive clinical-care outcomes. The evidence is heterogeneous, mostly non-randomised, from healthcare, and positive findings may be over-represented, so it supports trying a short regular huddle, not a particular format or frequency.

Run it as a decision forum

People do not optimise over every alternative; they simplify and search until an option meets an aspiration level. A review that expects perfect analysis will stall, so frame each item as a decision with an owner and a date. Different situations also call for different approaches: simple ones suit established practice, complicated ones need analysis, complex ones call for small safe-to-fail tests. Applying one mode everywhere produces predictable failure.

A working agenda

This agenda is Portolan's, built from the playbook steps; it is not a standard. One: decisions due before the next review. Two: the few chosen measures, each as a run chart with its owner. Three: what moved, and whether it is signal or noise. Four: decisions made, with an owner and a date for each. Five: one measure to fix or retire, because a measure that is never reviewed or retired is how a system fills with noise.

The path, step by step

These steps come from the Measurement and operating cadence playbook. Each has a checkpoint you can observe.

  1. Start from decisions, not dashboards

    List the recurring decisions the operation needs to make and who makes them. For each, name the measure that would change the decision and the cadence at which it needs to arrive.

    CheckpointA decision-to-measure map, with an owner and cadence for each decision.

    Common failureAdding every available metric to a dashboard and calling it visibility.

  2. Choose a small balanced set with owners

    Select a handful of measures across financial, customer, process and capability outcomes. Give each a definition, a baseline, a target and one owner.

    CheckpointA one-page scorecard with definitions, baselines, targets and named owners.

    Common failureMeasuring twelve things and owning none of them.

  3. Review time-ordered data in a short cadence

    Run a short, frequent review of the few measures that change weekly. Plot them over time, annotate interventions, and discuss the trend rather than a single snapshot.

    CheckpointA weekly chart with annotations, and a short review that starts from the trend.

    Common failureHolding a monthly meeting to review annual data.

  4. Run the review as a decision forum

    Use a fixed agenda: what changed, what it means, what we will decide, who owns it and when. Separate information sharing from decision-making, and record the decision.

    CheckpointA decision log with owner, date and the measure that will show whether it worked.

    Common failureEnding the meeting with 'let's keep an eye on it' and no owner.

What this guide does not settle

Most sources are methods papers, frameworks and a scoping review of mostly observational healthcare studies. None shows that a particular agenda, length or frequency improves results in an operation like yours, so treat the agenda as something to test and revise after a few cycles.

Each finding below is quoted from Portolan's research library, with the limits the library records for it. Applying a result from another setting, such as a hospital or a factory, to yours is an analogy, not a proof.

Neely · 1999Established

The Performance Measurement Revolution: Why Now and What Next?

Performance-measurement systems often fail because they collect too many measures, are not linked to strategy, and are not reviewed or updated. Measurement also has real costs—data collection, attention and distorted behaviour—so more measurement is not automatically better.

Where it stops. The article is a review of measurement practice and research rather than a controlled test; the 'right' number of measures is context-dependent.

Kaplan & Norton · 1992Applied

The Balanced Scorecard: Measures That Drive Performance

Financial measures are lagging indicators and can distort behaviour when used alone. The balanced scorecard adds customer, internal-process and learning-and-growth perspectives so managers can see the drivers of future performance, not just its financial residue.

Where it stops. The framework's causal claims are often assumed rather than tested; scorecards can become bureaucratic and are vulnerable to gaming.

Perla et al. · 2011Applied

The run chart: A simple analytical tool for learning from variation in healthcare processes

A run chart plots a measure in time order and uses the median, runs and shifts to distinguish signal from noise. It is deliberately simpler than a control chart and makes the effect of an intervention visible without waiting for an aggregate before-and-after comparison.

Where it stops. A methods paper, not evidence that run charts improve outcomes. Run charts are less sensitive than control charts and do not establish causality on their own.

Pimentel et al. · 2021Applied

Huddles and their effectiveness at the frontlines of clinical care: A scoping review

Across 158 empirical studies, 67.7% reported positive team-process outcomes and 44.3% reported positive clinical-care outcomes from frontline huddles. The evidence is heterogeneous, often non-randomised, and the huddle formats varied widely.

Where it stops. A scoping review of mostly observational studies. Positive findings may be overrepresented, and the review cannot identify the best huddle frequency or format.

Simon · 1955Established

A Behavioral Model of Rational Choice

People do not optimise over all possible alternatives; they simplify the problem and search until they find an option that meets an aspiration level—satisficing. Bounded rationality is a description of how decisions are actually made under limited information and attention, not a failure to be corrected by simply trying harder.

Where it stops. The model is a foundational theoretical account, not a prescriptive recipe; aspiration levels can adapt in ways that make decisions inconsistent.

Snowden & Boone · 2007Applied

A Leader's Framework for Decision Making

Different situations call for different decision approaches: simple contexts suit best practice, complicated contexts require expertise and analysis, complex contexts call for safe-to-fail probes and sense-making, and chaotic contexts need decisive action to stabilise. Applying one mode everywhere produces predictable failure.

Where it stops. Cynefin is a conceptual framework with limited empirical validation; the categories can blur in practice and should not be used as rigid labels.