Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why does scope creep still wreck my estimates?

You sit down, you estimate carefully, the number looks sound. Then the work shows you what you could not see at the start, and someone adds "just one more thing." The timeline breaks. This happens again, and you decide you are bad at estimating. You are not bad at seeing the future. No one is. The error is treating an estimate as a fact instead of a guess you agreed to defend, and then absorbing every change to it in silence, hoping to make it up later. That silence is the real leak, not your math. What is yours to control: build the buffer honestly before you commit, and name every scope change the day it happens, not the day the deadline dies.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The technique — buffering, breaking work into checkable pieces — is quick to teach, but the real fix is the daily discipline of speaking up, so guidance leads.
How the two dials adapt to you →
What’s really going on

The estimate was never your failure. No one sees the unknowns before they arrive. What is within your power is how much room you build for them, and what you do the moment scope shifts. Stop grading yourself on the forecast. Build the buffer, and speak the instant the work changes.

🔒 What you’ll build togetherUnlock by starting
A moveState a buffer out loud on every estimate — say '20% extra for what I can't see yet,' not just a padded number no one questions.
A moveThe moment new work appears, stop. Write down exactly what changed before you touch it.
A moveWalk to whoever added the work that same day. Tell them what it costs the timeline. Do not wait for the deadline to say it.
A moveCut the work into pieces you can check in days, not weeks, so you meet the unknown early instead of late.
A moveRefuse to absorb scope quietly. Make the trade visible every time — this went in, so that comes out or the date moves.

What changes unlock by starting

  • Your estimates survive contact with the unknown because the buffer already expected it.
  • Scope changes get named and negotiated instead of hidden until they blow up the deadline.
  • You stop treating a missed date as proof you failed and start treating it as information.
  • People around you learn that adding work has a spoken cost, so they add it less carelessly.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.