The Skip-Level That Told the Founder What His VPs Already Knew

He had not run a skip-level meeting in almost two years. His calendar had simply never had room, and his VPs had never pushed him to make room, which he had taken, wrongly, as a sign nothing needed his direct attention.

His new Chief of Staff scheduled six of them over two weeks, thirty minutes each, with individual contributors two levels below him. In the very first one, an engineer mentioned, almost in passing, that the team had stopped shipping on the original architecture roadmap eight months earlier because their VP had quietly deprioritized it under pressure from a different department, without telling the founder.

He asked the engineer if this was widely known on the team. It was. He asked if his VP knew he didn't know. The engineer paused and said, "I assumed you two had talked about it."

Why the information had stopped two levels up

The VP had made a reasonable tactical call under real pressure and had every intention, at the time, of raising it with the founder later. Later kept getting pushed out, first by a launch, then by a hiring crunch, then by the simple fact that eight months had now passed and raising it required also explaining why it had taken eight months.

The delay had compounded on itself. What would have been a five-minute conversation in month one had become, by month eight, a conversation that risked making the VP look like he had been hiding something, even though the original decision itself had been defensible. The longer information sits unshared, the higher the perceived cost of finally sharing it, and the less likely it becomes that anyone volunteers it without being asked directly.

This is a structural risk of any org chart with more than one layer, and it does not require bad intent to produce a bad outcome. It requires only a nervous system pattern that makes the second conversation feel more expensive than the first. A VP under real pressure making a reasonable call in the moment, multiplied across a dozen similar moments a year, produces exactly the kind of accumulated blind spot the founder had just discovered by accident, in a meeting he had almost not scheduled.

How much is one unresolved conflict really costing your company?

What the founder did with the VP directly

He did not confront the VP in front of the team. He raised it privately, and he opened by naming what he suspected the VP was feeling rather than leading with the accusation. "I think you've been carrying this decision alone for eight months and dreading telling me. I want to hear the whole thing."

The VP visibly exhaled. The conversation that followed was longer and more honest than either of them expected, and it surfaced two other decisions the VP had been quietly sitting on for similar reasons. Naming the likely emotional state first, before addressing the content, gave the VP room to be fully honest instead of defensive, which is the practical value of affect labeling applied to a manager rather than a peer.

Doug Noll's new book Empathy Leadership: The Powerful Skill That Drives Winning Results lays out why information stalls at exactly the layer where a leader stops checking directly. See it here.

What changed about his calendar

He put a recurring skip-level rotation on his calendar permanently, four thirty-minute conversations a month with individual contributors, protected the same way he protects a board meeting.

He has not found anything as significant as the architecture roadmap again. He has found several smaller versions of the same pattern, each caught within weeks instead of the better part of a year, which is the entire point of the exercise.

‍