The skip-level you stopped doing

When did you last sit in a room with people two levels below you and ask what's going wrong? If you can't name the quarter, you're already running the company on someone else's summary.

For two years a CTO I know ran skip-levels every quarter. Thirty minutes, three engineers at a time, no agenda. He heard things no manager surfaced: a tooling problem that had blocked a senior engineer for months, friction with a peer team nobody had escalated, doubts about a product direction that hadn't reached a retro yet. He made small adjustments. Retention held. He felt connected to his org.

In year 3 he got busy. A funding round ate Q1. Two small acquisitions ate Q2. A new VP of Product ate a third quarter of his attention. He skipped one skip-level cycle, then two, then it had been six months. That October, three engineers resigned inside the same fortnight. None shared a team. Each cited reasons his managers had never raised in an exec meeting. He read the exit interviews and recognized, in every one, a theme he'd heard a year earlier in a skip-level and stopped hearing the moment he stopped holding them.

The skip-level is the cheapest piece of management infrastructure that exists. It does one job: catch the signal your direct reports filter out, on purpose or because they can't see it themselves. A manager's report to you is a summarized story. The summary is necessary, since you can't hear everything. It's also where bad news goes to disappear, where an individual's frustration gets rounded up to "team's doing well," where the first sign of a resignation gets filed as normal grumbling.

The rounding isn't malice. Managers carry competing incentives. They want to show their team is performing. They want to avoid looking like they've got problems they can't solve. They want to keep their strong people off the exec radar. Each incentive is defensible on its own. Stacked, they produce a report that runs consistently rosier than the team's real state.

Stop skip-levels and you're running on that report. It's usually directional and always flattering, because flattery is the default when nothing counters it. The skip-level is the counter-signal. Without it the manager's version wins by default, and you learn the gap the day it turns into a notice email. That's the same blind spot behind a top performer quietly breaking the team.

The discomfort is real, and it's the point. The manager feels audited. The team feels handed a channel to speak straight. You feel friction on an overbooked calendar. All three reactions are correct, and the friction is what produces the signal. A frictionless skip-level, where everyone's happy and nothing surfaces, is a meeting the team has learned to perform.

That performance is the tell. New skip-levels under a new exec produce sharp, honest signal, because the team hasn't learned yet what's safe to say. By the third or fourth cycle, if you haven't visibly acted on what came up, the team learns that speaking produces nothing. So they stop. The meetings continue. The signal dries up. You look at the quiet and conclude the team is fine, which is the opposite of what the quiet means.

So act on what surfaces, fast and in the open. In the weeks after, the team needs to see the specific thing they raised get addressed, or get named and consciously deferred with a reason. That loop is what keeps the signal alive. Skip it and the skip-level decays into ritual, and now you're running on filtered manager reports and filtered skip-level reports at the same time.

The questions that work are blunt and off any template. What's the most frustrating thing about working here right now? What's your manager doing well? What would you change if you could change one thing? You're not collecting survey data. You're giving three people half an hour with the person whose calls shape their week. The questions open the space; what you do in the next month decides whether anyone uses it next time.

The cadence that holds is quarterly, three people at a time, thirty minutes. Less often and the signal goes stale. More often and the meeting turns routine and the answers turn performed. Three at a time gives you enough cross-check that one loud opinion can't dominate while the room stays small enough for honesty. Thirty minutes gets you past the polite openers into the real ones.

The CTO restarted skip-levels that November, after the three resignations, and heard things in the first cycle his managers hadn't surfaced in six months. Two were structural: a tooling decision blocking the team and a cross-functional process grinding people down. Both were fixable. Both had been visible to the team for months and invisible to him. One half-day of meetings surfaced them.

Treat skip-levels as standing infrastructure, not a thing for when there's time. An exec whose calendar treats them as optional will drop them under load. An exec who blocks them a year out, same Friday of the same month, runs them through the same load that produced the deferrals.

Stop doing skip-levels and you've stopped hearing from your company. The resignation letters will tell you eventually. The skip-levels would have told you six months sooner.