The five-week leader presentations are baseline once, then deltas forever - show me what you changed to move the number, not the same dashboard

August 19, 2026 at 8:27 PMoperationalmedium

Situation

Closing the Engineering Weekly Sync on 2026-08-18, Peter defined what the recurring per-report presentations are for now that nearly every direct report has completed one iteration. He said he is deliberately giving little feedback on the first round because its only job is to set a baseline for each team. From the second round on he wants the conversation to be about what changes the leader is making to drive improvement in the metrics they report, what they are changing when those changes do not produce the expected movement, and whether the metrics themselves should still be the metrics. He explicitly said he does not expect the org to be tracking the same metrics a year from now and that this is fine.

Reasoning

Peter set up this cadence to see how each leader thinks about their team, and he had noticed the variation across reports was in what people track rather than in how they manage. Left alone the presentations would converge into a recurring dashboard read - a compliance ritual that produces no information. So rather than criticise anyone first round, he defined the purpose of the artifact out loud and told everyone what the second round has to contain. He also pre-authorised the metrics themselves to change, which removes the incentive to keep a stale metric alive just because it was in the last deck.

Additional Context

Delivered in the same closing block as his do-fewer-things-all-the-way message. He asked Make sense and got explicit yeses from Wolford and Wallace. This is the cadence he instituted on 2026-07-24 as a rotating per-team deep dive anchored on empirically measurable metrics co-designed in the room.

Observed Evidence

Direct quote above. Peter prefaced it with an observation that you are seeing pretty big variation in terms of how people manage teams, in terms of what people track. He closed with Now that pretty much everybody has gone through one iteration. Make sense? Wolford: Yep. Wallace: Cool.

Matching Patterns

80%
Demonstrate the Standard, Then Collect It(2 keyword matches, involves Nathan Blackham and Steve Wallace, same category (operational))
45%
Purpose Is the Decision Procedure(involves Nathan Blackham and Steve Wallace, same category (operational))
40%
Metrics Must Follow Strategy(metrics may change over time by design)

Confidence Breakdown

34/35
Evidence
28/30
Pattern
20/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:The presentation is an instrument for observing how a leader thinks, not a status report. Withholding first-round feedback was itself the signal - silence meant baseline, not approval.
Who Affected:All six direct reports, and by extension every team whose metrics get chosen or retired. Also the program people, who consume whatever the leaders decide to track.
Precedent:Any recurring artifact Peter institutes comes with an explicit statement of what it is for, and permission for its contents to change. It also sets that a metric can be retired without that being a failure.
Consequences:Real - from the next round a leader who brings the same dashboard with no delta story has not met the bar. Peter said the deltas are what he is most interested in talking about.
Timing:Now specifically because everybody has completed one iteration, so the baseline round is over and the second round starts against a stated standard rather than a discovered one.

Source

reflection

AI Confidence

88%

Related Context

🎥
Engineering Weekly Sync 2026-08-18

fathom

What I want out of this process is not the same presentation from everybody every five weeks. What I want to understand is how the way you think about your team is evolving, how you are driving the metrics and driving improvement in the metrics that you are reporting. So for the first iteration of these presentations, I just want to set a baseline for each team. That is why you are not seeing a lot of feedback from me about what should change. But then in subsequent ones I do not want just a presentation of the same dashboards. I want the conversation to be about what changes you are making to drive improvement in the numbers that you are presenting. And if that is not giving you the changes that you expect to see, what you are changing, and then how you are thinking about the actual metrics and whether the metrics should be changing over time. I do not expect that a year from now we will be tracking the same metrics that we are tracking today. And that is fine, but it is those deltas and the first order change that I am most interested in.

Outcome

No outcome recorded yet.

Decision ID: 1d7dd407-7690-4749-90f6-cc5588ecca0a