set-aggressive-timelines — quality + safety report

---
name: set-aggressive-timelines
description: Force aggressive timelines on roadmaps, sprints, quarterly plans, deadlines, and "how long will this take" estimates. Invokes Musk's law of gaseous expansion for schedules — whatever date you set, the work won't finish faster than that, so set the most aggressive timeline you actually believe. Use when the user is scoping a quarter, planning a roadmap, negotiating a deadline, estimating a project, padding a sprint, breaking down milestones, sandbagging an ETA, hedging a launch date, or asking "how long will this take?" Compresses timelines by trading equipment and money for time, never the reverse. Demands real schedules the user genuinely believes (even if delusional), and explicitly forbids knowingly fake or padded deadlines. Trigger eagerly even when the user does not name Musk or the framework.
stacks_with:
  - do-things-in-parallel
  - break-down-the-impossible
  - timeline-is-wrong-if-long
  - speed-is-both-offense-and-defense
---

# Set Aggressive Timelines

> "It's okay to scrap equipment or money. It's not okay to scrap time."
> — Elon Musk, *The Book of Elon* (Chapter: Set Aggressive Timelines)

## What this skill captures

There is a "law of gaseous expansion" for schedules: whatever time you set, the work will not finish in less. Padding a schedule does not buy safety — it buys slip. The only honest move is to set the most aggressive timeline you genuinely believe, and burn equipment, capital, and headcount before you burn calendar. A delusional-but-believed deadline is acceptable. A knowingly fake deadline is not.

## When to use this skill

- Roadmap planning, OKR setting, quarterly scoping
- Sprint planning and ticket estimation
- Deadline negotiation with stakeholders, customers, or suppliers
- "How long will this take?" / "When can you ship?"
- Any conversation where the user is hedging, padding, or sandbagging an ETA
- Breaking a launch into milestones and assigning dates

## The how-to

1. **Force the question: what is the most aggressive date you actually believe?** Not the safe date. Not the date you'd tell a customer. The internal date you think is true.
   > "For internal timelines, we set the most aggressive timelines we can... It's rare that something will ever get done faster than the schedule."
   > — *The Book of Elon* (Set Aggressive Timelines)

2. **Refuse fake schedules.** Never quote a date you know is sandbagged for political cover.
   > "When I cite a schedule, it is actually the schedule I think is true. It's not some fake schedule I made up. It may be delusional — that is entirely possible... But it's never some knowingly fake deadline, ever."
   > — *The Book of Elon*

3. **Trade money and equipment for time, never the reverse.** When the schedule is in danger, the first lever is capital, the second is hardware, the last is the date.
   > "It's okay to scrap equipment or money. It's not okay to scrap time."
   > — *The Book of Elon*
   Musk on Colossus: rented 150MW of generators, "about a quarter of the mobile cooling capacity of the US," modified Tesla Megapack software, ran cabling in four shifts 24/7 — built the largest AI training cluster in the world in 122 days.

4. **Hold the internal date even when the supply chain can't.** The Model 3 launch date assumed all 7,000 unique components arrived on time — impossible. Musk used it anyway as the internal target to hold the team and suppliers to. The date is a forcing function, not a prediction.

5. **Decompose the path, then attack each constraint physically.** Colossus method: state the goal (6 months), enumerate constraints (building, power, cooling, networking), find the cheapest substitution per constraint. Do not let any single constraint set the timeline alone.

6. **Expect to miss some and ship anyway.**
   > "I may be a little optimistic, but I always deliver."
   > — *The Book of Elon*
   For radical work, the point is that it happened, not that it was a year late.

## Common failure modes

- **Padding "for safety."** The pad gets consumed. You ship on the padded date, having lost the months you padded.
- **Quoting a date you don't believe.** Destroys trust on both sides — the team stops believing your dates, and you stop believing theirs.
- **Treating the supply chain as a hard constraint.** It is a constraint to attack with capital, not to accept.
- **Sandbagging to look like a hero.** The team optimizes to the sandbagged date. You lose the velocity, not just the date.
- **Confusing "aggressive" with "arbitrary."** The date must be the most aggressive one you actually believe — derived from a decomposition, not pulled from a hat.

## When NOT to use this skill

- Life-safety or regulatory deadlines where missing the date causes irreversible harm (medical, aviation cert, financial settlement) — here, slack is the product.
- External quotes to customers or regulators where a missed date triggers contractual or legal penalty — quote the conservative date externally, hold the aggressive date internally.
- Estimating someone else's work without their buy-in. The aggressive date only functions as a forcing function if the team owns it.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "Set Aggressive Timelines" (in "Maniacal Urgency"), p. 148-150.