My VP Of Engineering Protects The People Who Don't Build. What Do I Do?

My VP of Engineering protects the people who don't build.

He came from a name everyone in the room respects. And the layer he has built — the process, the ceremony, the "engineering excellence" framework, the RFC pipeline that takes six weeks to approve a button — has exactly one function: shielding the cohort he hired from the question "what did you ship."

This is the protection racket, and it is structural, not personal. The genius fluid VP cannot allow output to become the metric, because output would expose the cohort, and the cohort is his hiring record, and his hiring record is his pedigree made flesh. So he installs process as a smokescreen. The process is not incompetence. The process is the product. It exists to make "who ships" unanswerable.

He hires in his own image — same schools, same vocabulary, same allergy to the dock. The monoculture is not an accident. A monoculture cannot rat on itself. Everyone is implicated in the same performance, so everyone defends it.

The kitchen reads the org chart for the racket and names it. The process that protects versus the process that produces. Who he shields, what they have shipped, and what the layer costs you in throughput and headcount. A defensible read for the founder or board that has felt the drag and cannot yet point to its source.

The seminary cannot reform the seminary. The VP will never fire the cohort, because the cohort is the VP. The way out is a read from outside the priesthood — someone who does not need the lanyard and is not implicated in the performance.

The man warning you about the stack is the man protecting the stack. IP, not IQ. Pedigree is not production.

$2,994.99 · 48-hour delivery · no scoping call. Read the name. Map the racket. Walk. The read is here if you would rather not run it yourself.