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

Why does scope creep still blow up my estimates?

You have already solved the easy problem. Your numbers are closer now. What remains is not arithmetic — it is character. You still plan as if the request will hold still. It will not. Scope creep is not weather that falls on you. It is a decision, made slowly, each time you say yes without naming the cost. The unknown is not defeated by thinking harder before you start. It is managed by deciding now what you will do the moment it appears. So stop asking how to estimate the unknown. You cannot. Ask instead what you will do the instant the work grows. That question is within your power. The size of the surprise never was.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The buffering technique is simple to teach; the real failure is behavioral, so most of the work is coaching the reader to act differently in the moment things change.
How the two dials adapt to you →
What’s really going on

You do not fail at math. You fail to plan for change. Build a buffer for the unknown. Name what is not yet decided. Agree, in writing, on what happens when the work grows. The task was never to guess better — it is to choose, in advance, how you respond when things shift.

🔒 What you’ll build togetherUnlock by starting
A moveBefore you give a number, list three things that could still change, and add time for each one.
A moveSet a rule now: any request outside the original scope gets named, timed, and agreed before you touch it.
A moveThe day new work appears, stop and renegotiate the deadline. Do not wait until the end to mention it.
A moveKeep a visible list of what is 'not yet decided' and show it to whoever is waiting on your answer.
A moveAfter each project, write down exactly where the estimate broke. Not to feel shame — to fix the next one.

What changes unlock by starting

  • A written buffer built into every estimate, not a hopeful round number.
  • A habit of naming scope changes out loud, the moment they happen, not after.
  • Fewer silent resentments, because you negotiate changes instead of swallowing them.
  • A record of your own patterns, so your estimates improve on evidence, not optimism.
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.