Skip to content
DevMeme
7157 of 7435
The Project Road Ends at a Cliff Labeled 'Last 10%'
ProjectManagement Post #7849, on Mar 20, 2026 in TG

The Project Road Ends at a Cliff Labeled 'Last 10%'

Why is this ProjectManagement meme funny?

Level 1: The Almost-Finished Lego Castle

It's like building a giant Lego castle and getting the walls, towers, and flags done in one happy afternoon — then discovering the last piece of the instructions says "now build the drawbridge," and the drawbridge needs four hundred tiny pieces you don't have, three of which haven't been invented. The road in the picture looks beautiful and totally finished, right up until it slams into a wall of solid dirt. That's the feeling of saying "I'm almost done!" and then realizing the leftover little bit is actually the hardest part of the whole job.

Level 2: Why "Almost Done" Is a Trap

Terms worth unpacking from this picture:

  • The last 10% is shorthand for finishing work: edge cases (what if the input is empty? huge? emoji?), integration (your code meets everyone else's), polish, and deployment. It's routinely underestimated because it's invisible in early planning.
  • Estimation is guessing how long work takes. Developers usually estimate by imagining the happy path — the smooth road — because the cliff is, by definition, made of things you haven't thought of yet.
  • An MVP (minimum viable product) is the deliberately simplified first version. Healthy teams treat it as a probe; unhealthy teams treat it as 90% of the real thing, then schedule two weeks for the tunnel.

Your first encounter with this will feel personal: you'll tell your lead a feature is "basically done, just cleanup left," and then spend three times the original estimate on that cleanup. It isn't a personal failing — it's the standard shape of software work. The professional adjustment is to redefine "done": code merged, tested, deployed, and surviving real users. Until then, you're standing on fresh asphalt looking at a hill.

Level 3: The Geology of the Ninety-Ninety Rule

The photograph is almost too perfect a metaphor to need editing: a finished two-lane road — lane markings painted, guardrails installed, embankments landscaped — labeled "Project", terminating flush against a sheer wall of unexcavated earth labeled "last 10%". Someone built every easy part of this road, in full production quality, right up to the exact point where the work stopped being road-paving and started being tunnel-boring. Then they stopped.

This is Tom Cargill's ninety-ninety rule rendered in dirt: "The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time." The joke in the aphorism is the arithmetic; the joke in the photo is the material science. The first 90% and the last 10% are not the same substance. Asphalt is CRUD endpoints, happy-path UI, the demo that wowed stakeholders. The cliff face is everything that demo deferred: authentication edge cases, error handling, i18n, accessibility, data migration, the third-party API that behaves differently in production, load testing, and the deployment pipeline nobody set up because "we'll get to it." You cannot pave through rock. The tooling changes, the velocity changes, and crucially the visibility changes — burndown charts measure asphalt laid, not meters of rock remaining.

The systemic reason this keeps happening is incentive topology. Early-project work is legible and rewarding: every sprint produces a screenshot. Late-project work is invisible and punishing: a week of effort yields "the retry logic now handles partial failures correctly," which demos as nothing changed. So organizations optimize for road-surface kilometers, estimate based on road-surface velocity, and act shocked at the cliff — every single time. The guardrails in the photo are a particularly cruel touch: process and safety rigor meticulously applied to the part that was never the risk.

And note the shadow detail: the road doesn't taper or warn. It's pristine up to the final meter. That's the MVP illusion in one frame — a project can look 90% done precisely because everything that makes it look done was front-loaded, and everything that makes it be done was left in the hill.

Description

A photograph of a paved two-lane road labeled 'Project' in large white Impact-font text, running smoothly between green grassy embankments with guardrails - until it dead-ends abruptly into a sheer vertical wall of excavated brown earth labeled 'last 10%'. The road is fully finished with lane markings right up to the unexcavated cliff face where a tunnel was clearly never completed. The meme visualizes the ninety-ninety rule: a project that looks 90% done, smooth and drivable, until you hit the final stretch - edge cases, integration, polish, deployment - which turns out to be solid rock requiring tunnel-boring effort

Comments

8
Anonymous ★ Top Pick The first 90% of the project takes 90% of the time; the last 10% takes a geological survey, dynamite, and a re-org
  1. Anonymous ★ Top Pick

    The first 90% of the project takes 90% of the time; the last 10% takes a geological survey, dynamite, and a re-org

  2. dev_meme 3mo

    Best wishes to y’all at the end of this Q!

  3. @pulsar_sp 3mo

    My project feels like this when it's last 10% before only the first public playtest, and then it's like building 10 more such whole roads

  4. @tema3210 3mo

    First 10% too actually

  5. @blue_bonsai 3mo

    All 100%>

  6. @blue_bonsai 3mo

    Touch me touch me

    1. @Daonifur 3mo

      Incoming bad touch

  7. @blue_bonsai 3mo

    NOOOOOOO

Use J and K for navigation