The Inner Steady

How to Estimate a Task You Have Never Done Before

By The Inner Steady Editorial Team

·

5–7 minutes
Hands writing beside a notebook at a simple work table.

“How long do you think this will take?” is hard to answer when you have never done the task before. You can picture the obvious steps, but the first attempt may reveal missing information, setup work, or a different definition of “finished” than the other person has in mind.

You do not need to turn that uncertainty into a precise-sounding number. Define what “finished” means, separate known steps from unknowns, and choose a small check that will improve your estimate. Then give a range with its assumptions and agree when you will revisit it.

Key Takeaways

  • A first estimate can be a range with assumptions, not a precise promise.
  • Define what finished means, list the known work, test the biggest unknown with a small check, and revise when the scope changes.

Define what “done” means

Before estimating time, make sure you and the other person mean the same thing by the task. “Put the family records in order” might mean grouping papers by year, scanning every page, naming each file, or making a folder that another relative can use. Those are different amounts of work.

Ask one concrete question about the expected result:

“When you say you’d like the records organized, would you like them sorted into a few folders, or scanned and labeled as well?”

If the answer is not known yet, write down a temporary finish line. For example: “For this first estimate, I’m counting the work as sorting the papers into agreed folders. Scanning and labeling would be a separate step.” This keeps new requests from quietly expanding the original task.

Separate the parts you can see from the parts you cannot

Make two short lists. The first is work you can already name: opening the files, collecting what you need, doing the main task, checking it, and handing it over. The second is information you still need: how much material there is, whether the files are accessible, which version is current, or whether someone must make a decision before you can continue.

Do not fill every gap with a guess. Mark the unknowns that could change the estimate most. One unclear detail may be harmless; another may double the work or prevent you from starting at all.

Research on time predictions gives a reason to look beyond the first plan that comes to mind. In experiments involving academic and nonacademic tasks, participants often focused on the future scenario they could imagine; in one study, connecting relevant past experiences with a prediction eliminated the optimistic bias observed in that study. Later experiments found that predictions were less biased when the earlier and later tasks were the same kind of task. In those experiments, simply providing feedback about the earlier task’s duration did not reduce the bias. This does not turn past experience into a formula for a new task, but it does make the type of comparison worth checking. (Buehler, Griffin, and Ross, 1994; Thomas and König, 2018)

Make the first estimate about learning the task

When much is unknown, your first useful milestone may be a short inspection or sample—not a promise to finish everything. Choose a small part that can answer a major question: open a representative file, sort a small batch, try one step, or check whether the required information is available.

Decide what you want to learn from that first part. “Spend half an hour on it” is less informative than “check whether the source files open and process five representative records.” The latter can show whether your assumptions hold.

Keep the sample proportionate. You do not need to build a full prototype for a simple request. The aim is to reduce the uncertainty that most affects the estimate, then pause and reconsider.

Give a range with the assumptions attached

After you have enough information to make a rough estimate, say what it depends on. A range is more honest than an exact finish time when the amount of work or the number of obstacles is still uncertain.

For example:

“I have not organized this kind of archive before. I can check a representative batch this afternoon and tell you what I find. If the remaining records are similar and already readable, I expect the sorting to take a few more work sessions. If many need to be identified or scanned, it will take longer. I’ll update you after the first batch.”

If you need to provide a time range now, connect its ends to real scenarios rather than adding an unexplained cushion: “If the files are already grouped, probably one evening; if I have to identify and rename them as I go, closer to two or three evenings.” Those numbers are only useful if they reflect what you have actually seen so far. Do not borrow them for a different task.

Also distinguish a completion estimate from a promise. You might say, “That is my current estimate, and I’ll revise it after I check the source files,” rather than quietly presenting an early guess as a guaranteed deadline.

Update the estimate when you know more

Once the first slice is complete, note what it actually involved: the work itself, setup, waiting for information, corrections, and checking. Compare that with your original assumptions. Then estimate the remaining work from what you observed, not from the cleanest version of the plan.

If the scope changed, say so directly. A new request is new work; it does not mean your original estimate was dishonest. For instance: “The initial estimate covered sorting. Adding scans and file names changes the scope, so I’ll estimate that part separately.”

There are also times when a useful range is not possible yet. If you cannot see the material, do not know what counts as complete, or are waiting on a decision that affects every step, name the missing information and offer a date for checking again. “I can give you a better estimate after I see the files tomorrow” is more helpful than inventing certainty.

A quick estimate note

Before you answer, write four lines:

Estimate noteWhat to write
Done meansThe specific result the other person expects.
Known workThe steps you can already identify.
Biggest unknownThe detail most likely to change the time.
Next checkThe small step that will answer it, and when you will report back.

This will not make a first estimate exact. It makes the estimate easier to explain, test, and change as the task becomes clearer. If the main uncertainty is the due date rather than the amount of work, see our guide to what to do when you get a task with no deadline. For more practical planning guides, visit Habits and Decisions.

✎ Write