Require every five-week org review to show the delta against the prior review and what was done to move it - not a fresh static report

August 13, 2026 at 10:44 PMoperationalmedium

Situation

Peter gave Nathan and Steve the same instruction on Aug 13. The first round of five-week presentations is a level-set; from the second round onward he does not want to see the same presentation again. Each leader picks their own metrics - Max supplied a candidate list but Peter explicitly allowed rejecting any of them - and then must show how those numbers changed since the last review, what they did to change them, which metrics they dropped, which are new, and why. He named the intended side effect directly: so that you are feeling some pressure during the intervening five weeks to know that I am going to have to report against these metrics, what am I doing. Nathan is standing the metrics up as a self-service dashboard app rather than a slide, so the org can see them without him.

Reasoning

Peter is not after the metrics themselves - he was indifferent about which ones. He is after making improvement legible and continuous. A static report answers how are we doing; a delta plus an intervention answers how are you improving your team, which is the thing he actually wants to evaluate his directs on. Letting each leader choose the metric is what makes the pressure real rather than compliance-shaped: you cannot dismiss a number you selected. The five-week interval is the mechanism - it is short enough that a leader carries the next review with them while doing the work.

Additional Context

Runs alongside the leveling and comp work. Both are attempts to replace subjective assessment of leaders with something a leader can be held to on a cadence. Nathan is building the dashboard with Butler and asking IT for a host so it becomes an org asset rather than a personal tool.

Observed Evidence

Peter to Nathan: it does not have to be those metrics from Max, it can be whatever. But understanding what you want to start reporting against there, so that you are feeling some pressure during the intervening five weeks. And: the second order thinking that I want you to be able to talk about with that org is how are you thinking about improving.

Matching Patterns

71%
Metrics Must Follow Strategy(pairs a cadence with explicit metric expectations, forceful about the team being driven toward the numbers)
58%
Purpose Is the Decision Procedure(restates what the five-week review is FOR rather than critiquing its contents)
47%
Protect Engineering Focus Through Process(same category, creates a regular cadence that gives engineering a structured voice)

Confidence Breakdown

34/35
Evidence
25/30
Pattern
19/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:Recasts the five-week review from a status ritual into a performance surface for the leader presenting, not the team being described.
Who Affected:All direct reports presenting on the cadence, plus Max whose metric list is now advisory rather than mandated, and the wider org once Nathan dashboard is self-service.
Precedent:Establishes leader-chosen metrics with mandatory deltas as the standing format - which also makes it hard to quietly drop an unflattering metric, since drops must be explained.
Consequences:Real. A leader who shows the same slide twice will be visibly failing the format.
Timing:Now because the first level-set round is completing, so the format for round two has to be set before anyone starts preparing it.

Source

reflection

AI Confidence

90%

Related Context

🎥
Nathan <> Peter Weekly 1:1

fathom

I do not want to see the same presentation. ... this is how they have changed, this is the delta from five weeks ago, this is what you are going to drive this delta ... use it every time as an opportunity for you to talk about, here is how you are thinking about improving your team.

🎥
Steve <> Peter Weekly 1:1

fathom

Future 5-week metric reviews must show a delta from the prior period and explain what actions were taken to improve the numbers.

Outcome

Operating as intended. Wallace shared an ops scorecard with his team and reports it already changing behaviour and cleaning up Jira, with Norm giving useful feedback; Nathan runs a live metric set and volunteered to add the why to the dashboard unprompted.

Rating: 4/5

Decision ID: b5117a7a-8af6-4ff1-bac6-706d023a0806