Set a six-month horizon on migrating low-value work off Damens plate - naming it the one change he requires from Justin, while refusing the headcount answer until the work is concretely scoped

August 11, 2026 at 3:06 PMpeoplemedium

Situation

Following back-to-back 1:1s with Joseph and then Damen - the second scheduled entirely because of what Joseph said, which Peter confirmed unprompted as 100 percent of it - Peter reported one yellow flag. Damens interrupt load splits into two buckets: stuff that is worth his time and stuff that is a complete waste of someone with his brains time. His judgment: he is fine right now, but if he is still carrying that percentage in six months, I do not think he will be fine. So it is figuring out how we get stupid off of Damens plate. But that is it. That was the only significant takeaway for me of a change that I need to ensure happens. And it does not have to happen today. It is just, it is a migration. When Justin floated hiring college students, Peter declined the shape while keeping the door open: I do not want to bring in three college students just because, but if you can stare at something and go, one relatively smart kid could hold the reins on these things and free Damen up, yeah, I am happy to have that conversation - I am going to want to have a conversation in a concrete manner around what you want this person or persons doing. He tested the AI substitute first and rejected it for a specific reason: can AI do the stupid work in front of Damen, and when Justin said that is what he uses it for, Peter pushed back - that is what he uses it for, but it is still him driving it, somebody has still got to drive it.

Reasoning

This manages an attrition risk that has not materialised. Damen told Justin the same thing and reports enjoying the interrupts, so nothing is wrong today, which is precisely why Peter named a horizon rather than an action - it does not have to happen today, it is a migration makes it a trajectory Justin owns rather than a fire to fight. He would not accept the headcount answer as posed because hire three college students is a shape, not a scope, and converting a retention risk into a req before the work is defined produces a hire nobody can direct. He tested the AI answer first and found the specific insufficiency - somebody still has to drive the agents - which is the same distinction he drew at the AI Committee that same afternoon: AI does the work, a human owns the mechanism. And disclosing that Josephs comment was the entire reason he took Damens 1:1 is a deliberate transparency, telling Justin that skip-level comments have a live channel into the CTOs calendar.

Additional Context

Delivered in the same 1:1 that opened with Justin diagnosing Nathans visible frustration and Peter recasting it as growth-with-headcount. Damen separately turns out to see himself as closer to a developer advocate role, which Justin described him as being both excited about and very good at - so the low-value work is displacing something the company also wants. No action item was opened at Peters direction; the horizon is too far out to carry one now.

Observed Evidence

Direct transcript quotes across a three-minute stretch of the Jul 31 1:1, including the six-month framing, the refusal of the intern shape, the AI-substitute test, and Peters unprompted confirmation that Josephs comment was 100 percent of why the Damen 1:1 happened.

Matching Patterns

40%
Three-Lever Talent Management(retain-first lever applied pre-emptively to someone with no current complaint, data-driven read from paired 1:1s)
35%
Route Non-Differentiating FTE Classes to Partners(same who-should-carry-this-class-of-work question, applied to one persons plate rather than a team)
25%
Constrain the Mechanism, Not the Access(same AI-does-the-work-but-a-human-drives-the-mechanism distinction, applied to headcount rather than data access)

Confidence Breakdown

33/35
Evidence
21/30
Pattern
19/20
Source
7/15
Corroboration

Reasoning Depth Analysis

Org Signal:That high-value engineers get protected on a six-month horizon rather than after they complain - and that a skip-level comment will put a 1:1 on the CTOs calendar, which Justin now knows explicitly.
Who Affected:Joseph, whose comment triggered the whole thread. Justin, who owns an undated migration. Whoever eventually absorbs the low-value work, whether that is a junior hire or an agent someone has to drive.
Precedent:Sets that he is fine now does not close a role-fit conversation, and that a retention risk gets a horizon and an owner rather than an immediate req. Also sets that a headcount request must arrive with a concrete account of the work before Peter will engage it.
Consequences:Real but soft-edged and deliberately so - Justin owns a six-month migration with no deadline and no defined destination, and no action item was opened on Peters side because the horizon is too distant to track now.
Timing:Immediately after the paired 1:1s while the read was fresh, and coupled to a headcount conversation left deliberately open rather than closed.

Source

reflection

AI Confidence

80%

Related Context

🎥
Justin <> Peter Weekly 1:1 - 2026-07-31

fathom

He is fine right now. But if he is still carrying the percentage of stupid work in six months, I do not think he will be fine. So it is figuring out how we get stupid off of Damens plate. But that is it. ... And it does not have to happen today. It is just, it is a migration.

🎥
Justin <> Peter Weekly 1:1 - 2026-07-31

fathom

I do not want to bring in three college students just because, but if you can stare at something and go, you know what, one relatively smart kid could hold the reins on these things and free Damen up, yeah, I am happy to have that conversation. I am going to want to have a conversation sort of in a concrete manner around what you want this person or persons doing.

🎥
Justin <> Peter Weekly 1:1 - 2026-07-31

fathom

That is what he uses it for, but it is still him driving it, driving the AI. So it cannot do all of it. Somebody is still got to drive it?

Outcome

No outcome recorded yet.

Decision ID: b61f0528-091c-4432-b429-48ea6d2ed508