The engineering re-leveling lands as a conversation with each direct report, not a directive - and Wallaces org is over-titled but not over-paid

Situation

Peter settled how the engineering leveling and compensation review will be delivered. The artifact is a spreadsheet comparing each orgs leveling and compensation against all of engineering, and he will walk it through individually with each direct report next week. He pre-emptively stripped it of authority in both 1:1s where it came up. To Ryan: it is going to be the spreadsheet I am putting together is the beginning of a conversation with each of my direct reports to say, here is how your org is structured from a leveling perspective, here is how all of engineering is structured, here is how your org is compensated, here is how all of engineering is compensated. I am not going to shove it down your throat. To Steve, twice: it is not something I am going to force down your throat or anybody else throat, it is the beginning of a conversation, that is all it is - and I will get it in front of you sometime next week, but it is for a conversation, not for this is what I am doing to your team exercise. He also delivered the specific diagnosis for Wallaces org directly to Steve: your team has titles that are far above the rest of the organization, so there is going to be some leveling reset that ends up impacting your team - but from a comp perspective your team is not overly compensated, in fact they may be low in some places, so I think you are going to have a fine story to tell. To Ryan he was blunter about the same finding: the number of directors we have across Wallaces org is just stupid, and it does not fit what I am doing everywhere else in engineering. He deliberately left the remedy open - we could change it by making more people VPs, we could strip away VP titles, we could do a lot of different things to level it - and named Mariah as involved with probably Bjorn a bit. He deferred the Steve walkthrough to Monday because he was slammed both days.

Reasoning

Peter has one firm finding and one soft one, and for the same org they point in opposite directions: the title distribution is incoherent, but the compensation is if anything low. A directive would therefore read as a demotion to a team that is actually under-paid, so the framing had to be installed before the artifact arrived. Telling Steve he has a fine story to tell hands him the reassurance before he can ask for it. And leaving the remedy space genuinely open - up-level or strip titles, both named as live - means he has committed to the problem statement without pre-deciding the fix, which is what makes the conversation framing honest rather than cosmetic.

Additional Context

The leveling review itself was launched on 7/10 with Peter defining director-level criteria personally, and the leveling document is an open todo. What is new is the delivery mode and the specific per-org diagnosis. Steve had independently started looking at it from a relative perspective, and there is already an open Norm Bhatti comp review under Steve from the 7/6 and 7/24 decisions.

Observed Evidence

Direct quotes from two 1:1 transcripts the same day. The conversation-not-directive framing appears three separate times unprompted, and the Wallace-org diagnosis is stated to Steve directly rather than only about him.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis