Trade a company-wide VP definition to get Greg to ratify the engineering ladder - structure first, names later

Situation

In the Aug 24 1:1, Peter walked Greg through the engineering leveling spreadsheet. He deliberately separated ratifying the STRUCTURE from mapping the PEOPLE, saying he wanted Greg bought into the structure and cared much less about the mapping for now. The ladder collapses roughly 27 levels to four IC levels - Engineer, Senior, Principal, Distinguished - plus Technical Fellow retained as a title outside the ladder rather than a level, and leadership reporting to Peter as either VP or Director with no Senior anythings. Greg objected to VP on optics grounds. Peter did not defend the word, he defended the need: I wanted a senior leader and a junior leader title, what we call them I am far less interested in. The two then jointly settled a company-wide convention: VP spans organizations and reports to a C-suite, SVP means junior C-suite where no CXO title is being given, Directors can report to either. Peter committed unilaterally: you will never see me arguing for a VP that does not report to me. Greg accepted, and asked that the ladder not be built in a vacuum but be made cross-applicable and run as an org-wide initiative with Mariah. Peter agreed and took the write-up. They ended at Peter stating they were 85 percent aligned.

Reasoning

The gate Peter was working was not the ladder, it was the precedent. He named it out loud: the problem you are going to have now is we have VPs all across the rest of the company, so now I have to have conversations with people about how they become a VP at CIQ. Rather than take the title and absorb that cost, he traded - he let Greg define VP company-wide, which prices the title everywhere at once, and got engineering VPs in exchange. Going to the CEO first, and going with structure only, is the same move: he wanted the framework ratified before any name could make it contentious, because once a specific person is attached the conversation stops being about the ladder. The reason he wants the ladder at all is management leverage, not tidiness - he said it lets him define what he expects at each level clearly, which he cannot do across 27 levels, and it removes the finger-pointing and why-am-I-not-there questions by giving one story instead of a different story per person.

Additional Context

This executes the Aug 13 decision to take the re-leveling from principle to a concrete ladder, and closes the open todo to walk Greg through the leveling document before taking it anywhere else. Next step per the conversation is a written ladder document, then a session with Greg and Mariah Rippee.

Observed Evidence

Peter: But what I am trying to do is lessen the sprawl of levels that we have across what is a very small engineering organization overall. Peter: But I wanted a senior leader and a junior leader title. That is what I care about. What we call them, I am far less interested in. Greg: vice presidents are somebody who is reporting to a C-suite. I would be good with that as a general rule. Peter: This is still so much simpler than what I am sitting on top of right now. Massively simpler and removes most of the finger pointing and why am I not there questions from people. Greg: my ask would be then is if we can draft kind of what the ladder of titles look like from an engineering perspective and then see how that crosses over with the rest of the org and then let us use this as an initiative with Mariah.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis