A weekly operating review that ends with a decision

Run the weekly operating review around a decision the team can make now, using comparable evidence and a bounded next step with an owner and checkpoint.

A review loses its purpose when each function narrates a dashboard and the meeting ends with “keep monitoring.” The alternative is a short preparation discipline: identify what changed, establish what the comparison means and choose the smallest justified commitment. Use the worksheet below to turn that discipline into a repeatable review.

Establish the baseline before explaining the movement

Write down the measure, its definition, the period and the population. Compare actual performance with the agreed plan and, where useful, a comparable prior period. Label each comparison. Missing plan, changed definition and incomplete reporting are different limitations; none should disappear into a single red status.

Check whether both periods contain the same number of working days, a similar customer mix and a consistent cutoff. For pipeline conversion, specify the stage being entered, the stage being reached and how much time each cohort has had to progress. A weekly snapshot can mix fresh opportunities with mature ones.

The HEART research from Google, presented at CHI 2010, connects product goals with meaningful measures. The application here is our own: choose the signal because it informs the decision, then check whether the way it is measured supports that use.

Separate the symptom from the explanation

“Revenue is below plan” describes a symptom. “The new sales process is failing” proposes a cause. Between the two sit questions about volume, conversion, deal value, timing and recognition. List the plausible explanations before choosing the one that fits the loudest anecdote.

Ask each functional lead for evidence that could weaken their preferred explanation. A sales team blaming lead quality might examine comparable leads handled by different teams. An operations team blaming staffing might check whether rework or queue policy changed first. These checks guide investigation; they do not automatically establish causation.

Decide which uncertainty matters for the next commitment. The team may lack a complete explanation yet still be justified in correcting an identified reporting error. Conversely, an expensive change in commercial strategy may need more evidence than the next review can supply.

Use one compact worksheet

Fill this in before the meeting. Keep source detail in a supporting note that the reviewer is authorized to access.

Review field	What to write
Decision needed	The choice, decision owner and latest useful decision date
Signal and baseline	Measure, denominator, period, actual and comparison
Comparability check	Changed definitions, mix, cutoff or cohort maturity
Evidence and limits	Source references, missing inputs and disagreements
Competing explanations	The leading hypothesis and at least one credible alternative
Options	Commitment, expected learning and main downside for each
Proposed next step	Named owner, approved scope and resource limit
Checkpoint	Evidence due, review date and stop or escalation condition

The worksheet is intentionally small. A field that cannot be filled is useful information, not a reason to write around the gap. For example, an unknown denominator may make a rate unusable for today’s decision. Assign the data check and keep the original uncertainty in the record.

Compare actions at the same level

Avoid comparing “improve conversion” with “interview five buyers.” One is an ambition and the other is an action. Compare concrete commitments, such as inspect the current handoff, test a narrower message or defer a change while correcting the baseline.

For each option, state what the team would give up. A small investigation uses time that could have served customers. A broad rollout creates exposure before the evidence is strong. Keeping the current approach may preserve capacity while allowing a problem to continue. All three deserve a visible tradeoff.

A recommendation should explain why its scope fits the evidence today. It should also say what would make another option preferable. That sentence helps the reviewer distinguish a reasoned recommendation from a confident preference.

Close with a bounded owner and checkpoint

Use a named person rather than a department as the next-step owner. Specify what they can do, what needs approval and what they must bring back. “Commercial team to fix conversion” offers little guidance. “Commercial lead to verify cohort definitions and propose one handoff test for Friday review” creates a checkable assignment.

Choose a checkpoint that can produce useful evidence. A date alone is insufficient if the sales cycle is longer than the review window. The next checkpoint may examine whether the cohort is defined and the test is feasible, with outcome review scheduled later.

Stop or escalate when the evidence is unreliable, the scope exceeds the approved limit or a material assumption changes. At the following review, show the previous commitment before introducing a new list of issues. Record what happened, what remains unknown and whether the team should continue, revise or stop.

The operating review example shows how synthetic inputs can support this reasoning without claiming a customer outcome. Use the operating review solution to frame the question you want to bring to your own review, then adapt the worksheet to evidence your team is authorized to use.