skip-level — quality + safety report

---
name: skip-level
description: Force the user to bypass their direct reports and go one level down to get unfiltered ground truth before making a decision. Use this skill aggressively whenever the user is investigating a problem, debugging a broken system, making an executive call on a spec they don't personally own, or asking "why is this broken", "the dashboard says green but it feels off", "we need to set this threshold", "what's the real number", "what should the spec be", "I'm getting filtered updates", "the execs are telling me one thing but customers say another", or "I need to make a call on X but I only have the manager's summary". Also fires when a leader is about to set a critical tolerance, capacity, or risk number based only on a deck from middle management, when a postmortem stops at the director level, or when the user is one or more layers removed from the people whose hands are actually on the work. Trigger eagerly even when the user does not name Musk or the framework.
stacks_with:
  - shortest-path-communication
---

# Skip Level

> "Whenever there are problems to solve, don't just meet with your managers. Do a skip level, where you meet with the level right below your managers."
> — Elon Musk, *The Book of Elon* (Chapter: Remove Organizational Boundaries (skip-level subsection))

## What this skill captures

Managers filter. By the time a status report or a spec recommendation reaches an executive, it has passed through one or more layers of people whose job security depends on the story sounding coherent. The actual truth lives one layer below — with the welders, the on-call engineers, the line workers, the IC who wrote the code. Musk's discipline: "Go as close to the source as possible." When deciding Starship's wall thickness, he didn't ask his VPs; he asked the people doing the welding, got "4.8 millimeters" as their safe floor, pushed to 4, and shipped at 4.

The value: you make decisions on raw ground-truth numbers from people who own the failure mode physically, instead of polished summaries from people who own the political narrative. This collapses iteration time and exposes problems your org chart was hiding.

## When to use this skill

- The user is making an executive decision on a spec, tolerance, or threshold they don't personally own (wall thickness, latency target, error budget, headcount, capacity).
- The user is investigating why something is broken or slow and has only talked to managers or read dashboards.
- A status report, OKR update, or postmortem from a director-level person feels too clean.
- The user is one or more org layers removed from the people whose hands are on the actual work.
- A team's manager says "it can't be done" or "that's the safe floor" and the user is about to accept it.
- The user is setting an aggressive timeline and needs to know what is actually possible at the IC level, not what middle management is comfortable committing to.

## The how-to

1. **Name the decision and the layer you're currently hearing it from.** Write down: what am I about to decide, and whose mouth is the input coming from? If the answer is "my VP" or "the director's slide", you are too far up.
   > "Whenever there are problems to solve, don't just meet with your managers. Do a skip level, where you meet with the level right below your managers."
   > — *The Book of Elon*
   You cannot skip-level if you have not first noticed you're operating on filtered input.

2. **Physically go to the source. Not a meeting — the actual location of the work.**
   > "Physically go to where the problem is, immediately."
   > — *The Book of Elon*
   The welder at the tank, the engineer at the terminal, the support agent on the call. Distance from the source is distance from the truth.

3. **Ask the people whose hands are on the work for the raw number, not a recommendation.** Not "what should the spec be" — that invites them to guess what you want to hear. Ask "what feels safe to you" or "what number makes you nervous".
   > "Rather than only talking to the company's executives, I talked to some of the workers actually doing the welding. I asked what they thought was safe. The line workers thought the tank walls could get as thin as 4.8 millimeters."
   > — *The Book of Elon*
   The IC will give you a physical floor. The manager will give you a politically defensible margin on top of that floor.

4. **Then push the number past their first answer and see where they flinch.** The first answer has a safety buffer baked in. The flinch point is the real constraint.
   > "'What about four?' I asked. 'That would make us pretty nervous,' the workers replied. 'Okay,' I said, 'Let's try four millimeters.' It worked."
   > — *The Book of Elon*
   "Nervous" from the welder is signal. "Impossible" from the manager is noise.

5. **Make the decision on the IC's number, not the manager's summary of the IC's number.** Then ship it and let reality be the final arbiter.
   > "One of my rules is 'Go as close to the source as possible.'"
   > — *The Book of Elon*
   The whole point of skip-level is wasted if you collect ground truth and then defer to the filtered version anyway.

6. **Do not let the manager retaliate against the IC for talking to you.** Skip-level only works once if the welders learn they get punished for honesty. Make it routine and expected, not a one-time raid.
   > "You can talk to anyone without anyone else's permission. Moreover, you should consider yourself obligated to do so until the right thing happens."
   > — *The Book of Elon*

## Common failure modes

- **Asking the manager to set up the skip-level.** They will pick the IC who tells the cleanest story. Go directly, unannounced if necessary.
- **Asking "what should we do" instead of "what's the actual number".** ICs will defer upward when asked for a recommendation. Ask for ground-truth measurements and constraints, not strategy.
- **Doing it once for theater, then going back to manager-only reviews.** A single skip-level is a stunt. Routine skip-levels are a system.
- **Letting the manager sit in the room.** The IC will mirror the manager's framing. Talk to the IC alone or the data you get is the manager's data again.
- **Using the skip-level to override the IC's "nervous" line with a worse number than they gave you.** "Nervous at four" is data; "let's try two" is reckless. The IC is the floor finder, not the punching bag.

## When NOT to use this skill

- You are the IC. Skip-level is an executive instrument; if you are the welder, this is not your move.
- The decision is genuinely strategic (market positioning, M&A, fundraising) and the IC has no special information — the manager really does know more than the line worker about whether to acquire a company.
- You have no intention of acting on the ground-truth data you collect. Skip-leveling and then defaulting to the manager's number is worse than not doing it — it burns the IC's trust.
- The org is small enough that you already talk to the ICs daily. Skip-level is a tool for layered orgs, not five-person teams.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "Remove Organizational Boundaries (skip-level subsection)" (in "Designing the Organization").