How to Estimate When You Have Never Done the Task Before
New tasks have no personal history, so estimates feel like pure guesses. They are not — they are estimates with wider ranges and more stated assumptions. Here is how to build one without inventing a number.
Find the closest task you have done
No task is fully novel. Find the one in your history that is most similar in shape, then start from how long it actually took.
Building a first dashboard? Lean on the last time you wrestled a new tool into doing something useful. The skill transfers even when the topic does not.
Ask one person who has done it
Five minutes asking someone who has done the task beats an hour guessing alone. They will know the hidden steps you cannot see yet.
Ask specifically what took longer than expected — that is where new-task estimates usually break.
Triple the wide range
New tasks deserve a 3x range, not a 2x range. "20 to 60 minutes," not "20 to 40." Honest uncertainty is wide, and pretending otherwise just relocates the surprise to a worse moment.
A wide range is not indecision. It is an accurate description of how little you currently know.
Log the actual time when you finish
Write down what it really took the moment you finish. Your next estimate of this task type will be dramatically sharper.
The first attempt is the data-collection round. Treat it as research, not as a test you failed for going over.
Let a tool set the starting range
When you have no history at all, you still need a number to start. Mibbi Estimate gives a realistic time range for unfamiliar tasks that includes the learning curve and setup friction beginners always hit.
It is a far better anchor than a confident guess — and you refine it with your own logged time next round.
Try it with Mibbi Estimate
Guess how long things might take.
Open Mibbi EstimateFAQ
- What if the task is genuinely unprecedented?
- Then estimate only the first chunk. Once you finish chunk one, you will have real data to estimate chunk two — which beats guessing the whole thing blind.
- How wide is too wide for a range?
- If the top is more than three times the bottom, the task is probably too big to estimate as one unit. Break it into smaller pieces and estimate those instead.
Related guides
- How to Estimate How Long a Task Will Take A practical method for honest time estimates that avoids the planning fallacy and produces ranges you can actually plan around.
- How to Stop Underestimating How Long Tasks Take The planning fallacy is universal — and beatable. Here is how to stop underestimating and size tasks the way they actually unfold, not how you hope.
- How to Estimate a Creative Task Honestly Creative tasks resist estimation — but not as much as we pretend. Here is the method that produces useful ranges.