Make metric design the single biggest ask of Max - 10 auto-reported metrics spanning Justin and Nathan, delivered by Thursday

July 27, 2026 at 11:56 PMoperationalhigh

Situation

In the Max 1:1 Peter redirected Max away from personally fixing NARF reporting bugs and toward crafting the metrics that Nathan and Justin will present against at the engineering all-hands and the Tuesday meeting. Peter framed it as if I have a single biggest ask of you, it is help craft that. Max committed to writing a list of the ten most interesting metrics he would want reported automatically in a dashboard anyone can look at any time, spanning both Justin and Nathan, by their Thursday 1:1. Peter stated he will work Nathan on the people-management side but wants to do it through the lens of achieving those metrics.

Reasoning

Peter has two levers on the Linux org and is deliberately choosing which to lead with. He named the people-management lever explicitly and unattractively - take Jason Rodriguez and fire him in front of everybody - and set it aside in favour of instrumenting what good looks like. His stated object is velocity, not in-the-moment delivery: I need the people in that space to understand that the thing I care about is velocity, not in the moment delivery, in the moment delivery I will get if you give me velocity. Metrics are the mechanism for making that legible, because the behaviour he wants - stop and fix the tool instead of working around it - looks like a delay under a delivery metric and like progress under a velocity metric. Assigning it to Max rather than owning it himself is a competence routing call: Peter said he understands Wolfords world because it is the world he comes from, and Linux is the area where he lacks visibility and needs help most.

Additional Context

This continues the 7/24 decision instituting a rotating per-team deep dive at the Tuesday staff meeting anchored on empirically measurable metrics. This session names the owner and sets a date. Peter said Linux is the biggest area he is worried about not getting visibility into, in contrast to Ryan and Fuzzball where he is getting traction. Max linked it back to a prior airport conversation about choosing the valuable correct metrics.

Observed Evidence

Direct quote naming it the single biggest ask, plus Max accepting a dated commitment in the same exchange.

Matching Patterns

30%
Protect Engineering Focus Through Process(same category (operational))
30%
Lead by Example with New Tools(same category (operational))

Confidence Breakdown

33/35
Evidence
26/30
Pattern
19/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:The Linux org will be steered by publicly argued metrics before it is steered by personnel action - measurement first, accountability second.
Who Affected:Nathan and Justin have to present against metrics they did not author; Max gets a staff-level charter that spans two orgs he does not manage.
Precedent:Establishes that the Chief of Staff can define the measurement frame for peer orgs. Also establishes velocity, not delivery, as the metric family engineering is judged on.
Consequences:Real - Max has a dated deliverable and the metrics will drive the all-hands presentations.
Timing:Now because the engineering all-hands is the next day with Wolford presenting, and Nathan and Justin are queued behind him.

Source

reflection

AI Confidence

84%

Related Context

🎥
Max <> Peter Weekly 1:1

fathom

Where I could use help is on the crafting of the metrics that we want them talking to in this meeting. If I have a single biggest ask of you, it is help craft that. ... I will work with Nathan on the people management side of things, but then I can do it in through the lens of achieving those metrics.

🎥
Max <> Peter Weekly 1:1 (Max commitment)

fathom

I will commit to you by Thursday, I can write up a list of the 10 most interesting metrics I would like to see reported on automatically in a dashboard, where I can just look at it, anyone can look at it, anytime they want. Spanning Justin and Nathan.

Outcome

Doc delivered and deliberately simple, which Peter accepted. But the handoff did not happen - I had wanted to feed Nathan, here are the metrics I want you to start tracking against. We did not.

Rating: 3/5

Decision ID: 997a5c29-3c8a-4f06-818b-0696bc9a885d