Double Your Next Estimate

How long is that task going to take? Your gut says an hour. You block an hour. Setup eats that block, the finish spills past it, and the work you meant to do later shows up on Friday evening.

Here’s the rule I give anyone who is new to estimating a specific type of task. Take your gut feeling and multiply it by two. If you think it takes an hour, block two hours. As you gain experience and data, you can reduce this multiplier to 1.5x. Never estimate at 1x. It is better to finish early and have free time than to be late and stressed. Doubling the block reduces the anxiety of being wrong. You start with a safety net.

Too much time on the calendar? Keep the 2x until you have data on that type of task.

Name the finish line first

You can’t pace yourself if you don’t know the distance.

Before you estimate a task, define exactly what done looks like. That’s your Definition of Done. If you’re writing a newsletter, is done when the draft is written, or when it’s scheduled to send? A vague Definition of Done leads to scope creep and estimation errors. A specific Definition of Done creates a clear finish line. Anxiety drops. The estimate gets accurate. “Scheduled for Tuesday at 3 PM” is a finish line. You know what complete means, and you know when you get to stop.

Write your Definition of Done before you write your estimate. One sentence. If that sentence is still fuzzy, the number beside it will be fuzzy too.

Score the energy

You don’t need Scrum to use story points. Define a personal Fibonacci scale based on energy and resources. A point measures energy and focus.

1 point. 30 minutes. An admin task.

3 points. 1 to 1.5 hours.

5 points. Half a day.

8 points. A full day.

If a task exceeds 8 points, break it down further. This non-linear scale forces you to decompose large, vague tasks into manageable chunks. Two 8-point tasks are two full days. A 5 is already half a day. Add them up before you fill the week.

Try the 1-3-5-8 method for your next week. Write the Definition of Done, then assign the points. Anything over 8 gets split before it lands on your calendar.

What happens when a quick task scores a 5? Give it a half-day block.

The start and the finish

Brooks observed that project work follows reverse compound interest. With financial investments, gains accelerate over time. Project work often follows the opposite curve. The beginning is the most resource-intensive phase: setup, planning, and overcoming inertia. The middle is the steady flywheel. The end slows down again as you polish and finalize. Most people underestimate the cost of the start and the finish.

Brooks’s curve counters the momentum myth. The middle can run like a flywheel. The start and the finish still need buffer of their own.

Picture a 100-floor building. When you estimate a simple task, like building one floor, you might assume linear progress. One floor equals one day. On a complex project, the initial stages are disproportionately difficult because of hidden complexities. Foundation, wind resistance, plumbing. The first few floors take much longer than expected. That creates a false sense of security for the rest of the project. One floor can take one day. The foundation under a complex project does not follow that pace.

Starting is the hardest part. Your initial estimates come in too low. The setup phase is where the hidden complexity sits.

Add extra buffer time specifically to the start and the end of a project. Let the middle run as the flywheel.

Does the project feel slow at the start? That is the cost most people underestimate.

Put insurance on the calendar

Hate estimating? Start here anyway.

If you are bad at estimating, or you hate the process, use buffer time as an insurance policy. Fifteen minutes is the daily block to start with. Use up to 30 when you need a wider catch-up window. Add 30 minutes of buffer for every day of travel. When the estimate is wrong, you finish the task without derailing your entire week.

Block 15 minutes of buffer time every day. Put the block on your calendar. Use it when a task runs long.

Fill the white space

Look at your available capacity first. Find the white space in the week. Use your story points to see what fits into that space. If it doesn’t fit, decide what to delegate, cancel, or defer. Make that call up front.

This is capacity-first planning, the Tetris method. White space is the board. Story points are the pieces. If a piece doesn’t fit, you delegate, cancel, or defer it while the choice is still yours.

Plan your week by filling the white space. The hope-it-works-out strategy leads to Friday evening panic.

Which task will you defer when the points are bigger than the white space?

The next big task

Apply the 2x multiplier to your next big task.

Write one sentence for the Definition of Done. Take the gut estimate. New to that type of task, block twice as long. Already have experience and data, use 1.5x. Do it today, on the next thing in front of you.