# Epics Are Dead: Planning When Work Ships in Days — Pilot to Production

> The Epic was a holding pen for months of slow delivery. When a milestone ships in days, that tier is dead weight. Here's the three-tier model that replaces it.

Canonical: https://thegrowthproject.com/podcast/epics-are-dead/

*Pilot to Production*, the Growth Project podcast — hosted by Sam and Maya.

- Listen: https://thegrowthproject.com/podcast/epics-are-dead/
- Read the article: https://thegrowthproject.com/blog/epics-are-dead/
- Audio: https://thegrowthproject.com/audio/podcast/epics-are-dead.m4a?v=804b2c80

## Transcript

**Sam:** We shipped a milestone last week in three days. Planned Monday morning, live by Wednesday night.

**Maya:** Real, in production, customers touching it. The plan had a Project. It had Tasks. It had no Epic.

**Sam:** And nothing was missing.

**Maya:** Nothing.

**Sam:** Welcome to Pilot to Production, from the Growth Project. I'm Sam.

**Maya:** And I'm Maya. Today: why the Epic just died, and why AI is the thing that killed it.

**Sam:** Okay, big claim. The Epic is a planning staple. Defend killing it.

**Maya:** Start with what the Epic was actually for. Be honest. It was never about the work. It was about the wait.

**Sam:** The wait.

**Maya:** You had a strategy, a quarter's worth of intent. And you had the smallest thing an engineer could pick up in a sprint. Between those two sat a chasm of weeks. The Epic was the scaffolding across it.

**Sam:** A place to park the thesis while fourteen sprints of tickets ground through the backlog.

**Maya:** Exactly. You wrote the brief, broke it into stories, groomed it every fortnight, re-estimated when reality moved. It wasn't a planning tier. It was a waiting room.

**Sam:** So a coordination tax you paid because delivery was slow.

**Maya:** Right. Now watch what happens when delivery stops being slow.

**Sam:** When the outcome that used to take a quarter takes a week.

**Maya:** You write the brief on Monday. By Wednesday the work is in production. By the following Monday, your first grooming session, the Epic is describing something that already shipped.

**Sam:** You're refining acceptance criteria for code that's been live for five days.

**Maya:** The Epic doesn't speed up. It rots. It was built to stay stable while slow work churned underneath it. Now the work outruns the document meant to govern it.

**Sam:** And here's the trap I think most teams fall into. They keep the Epic and just move faster inside it.

**Maya:** Which means they spend their new velocity grooming a tier that no longer holds anything. The tool built to manage the wait survives the death of the wait.

**Sam:** Okay, so if the Epic's gone, what's left? Walk me through it.

**Maya:** Three tiers, nothing more. Project, Milestone, Task. Project is the durable container. The thing that doesn't ship and doesn't die. A customer engagement, a product line, a platform. Lifespan in quarters or years.

**Sam:** The only tier that should stay stable.

**Maya:** Because it's the only one describing something that genuinely persists. Then the Milestone. A shippable outcome with a thesis. This is where the Epic's job went.

**Sam:** Wait, so you didn't delete the Epic's job.

**Maya:** We absorbed it upward. The Milestone carries the why, the plan, and the acceptance criteria. Same thesis, radically shorter half-life. A real milestone answers three questions. Why are we doing this. What's the plan. How do we know it's done.

**Sam:** And if it can't answer all three?

**Maya:** Then it's not a milestone. It's a wish. Last tier, Task. The unit of execution. Tasks are cheap now. You can spin up ten and throw away seven.

**Sam:** Because the cost of getting one wrong dropped through the floor.

**Maya:** And the real prize underneath all of this isn't fewer Jira levels. It's living documents. Every operator has felt the shame of the stale brief.

**Sam:** The strategy doc nobody reads because everyone knows it's six weeks out of date.

**Maya:** A brief goes stale because there's a long gap between writing it and shipping against it. The Epic guaranteed that gap. Collapse the tier and you collapse the gap. The brief never gets the chance to lie.

**Sam:** Fresh by construction, not by discipline. And you're saying this isn't really an AI productivity tip.

**Maya:** No. The lazy reading of AI is "the same work, faster." That's the least interesting part. Velocity past a threshold changes the shape of how you plan, not just the rate you execute.

**Sam:** We've seen this movie before, though.

**Maya:** We have. Batch releases made sense when deployment was a Friday-night event. Then deployment got cheap and continuous delivery made the release-batch gone, not faster, gone. Long-lived feature branches died when merging got cheap and trunk-based development took over.

**Sam:** Each time a coordination structure built around a cost disappeared once the cost did.

**Maya:** The Epic is next. AI didn't make it faster. It made the delay the Epic managed disappear. So the structure has nothing left to do.

**Sam:** Alright. First thing tomorrow, somebody's listening to this. What do they do?

**Maya:** Find your slowest tier. The level you spend the most time maintaining relative to how much work it actually contains. That's your Epic, whatever you call it. Then ask what it holds.

**Sam:** And if the answer is the thesis for work that's still in the backlog.

**Maya:** Ask how long that work really takes now. If it's days, the tier is holding air. So move the brief up. Put the why, the plan, and the acceptance criteria on the milestone. Then time-box your briefs to your delivery speed. If you ship in a week, no brief should describe more than a week of work.

**Sam:** And the last step is the one people will flinch at.

**Maya:** Delete the empty tier. Don't migrate it. Don't archive it just in case. Remove it. A tier that exists to be maintained will be maintained, forever, by someone.

**Sam:** Project holds the context. Milestone holds the thesis and ships before it goes stale. Task gets it done.

**Maya:** Three tiers, because the fourth was only ever the wait. Speed doesn't just compress your timeline. It audits your structure.

**Sam:** This has been Pilot to Production, from the Growth Project. If you're planning for a velocity your process wasn't built for, that's the gap we close, at thegrowthproject.com.

**Maya:** Thanks for listening. See you next time.