You may underestimate a task because you picture its main action and leave out the time needed to start, switch, wait or check. “I can write the report in an hour” may refer to the typing. The whole job may also include collecting the figures, getting a reply and making revisions. Before you give a time, look at how long a comparable task actually took and what was included.
Make a clear distinction between effort and elapsed time. You may need forty minutes of work and an afternoon for someone else to respond. Give a time range if the uncertain part matters, and say when you can make the estimate firmer. A useful promise tells someone when they can rely on the result and what you will do if a key dependency changes.
- Define when the task counts as finished.
- Use one or more comparable tasks you actually completed.
- Include setup, transitions, review and waiting where they apply.
- Separate your work time from the time the whole job will take.
- Confirm an early checkpoint when someone else depends on the result.
eduKate Singapore · Mindset and character
Find the part you need
Choose where to start, or open the chapter list to read in order.
Chapters 1–7
Chapters 8–14
Chapter 1 of 14
Why the first estimate can feel so convincing
You imagine the job as it would go on a good day
A student estimates twenty minutes to finish a science answer. They imagine opening the right page, remembering the example and writing. The actual job includes finding the marked draft, checking one instruction and deciding which diagram to use. Those steps are easy to leave out because they are smaller than the writing. Together they can determine whether the work fits the evening.
Researchers Roger Buehler, Dale Griffin and Michael Ross studied the planning fallacy, the tendency for people in their studies to make overly optimistic estimates of their own completion times. The researchers found that people often focused on a future plan and could improve their estimates when they connected relevant past experience to the prediction. You can use that distinction by asking what happened last time, including the ordinary delays that your best-case picture leaves out.
You remember the active work and forget the surroundings
You recall that the journey took twenty minutes because that was the time on the train. Leaving the house, walking to the station, waiting and getting from the destination station to the meeting added another twenty. Both numbers may be correct for different questions. If someone needs to know when you will arrive, use door-to-door time. If you are choosing what to read on the train, the train time may be enough.
A similar difference appears in writing and group work. You might have spent thirty minutes editing a file and a day waiting for a reviewer. The next person does not care which minutes involved active work if they cannot proceed until the file is approved. Define whose timing the estimate is meant to support.
You may be estimating the time you wish you had
Someone asks if you can send a task before lunch and you look at the free space in the morning. You say “two hours” because two hours are available. You have not checked whether the job will fit. Treat available time as a constraint. Then estimate the work independently. If the two do not match, offer a smaller scope, ask for help or agree a different deadline. A crowded calendar does not make the work itself shorter.
Chapter 2 of 14
Define what finished means
Name the first usable result
A rough list, a complete draft and a checked final copy take different amounts of time. Ask what the person needs. “Do you need a list of options for discussion or a checked recommendation?” may reveal that the first version is smaller than you imagined. It may also reveal that the first version must include approval. Give an estimate for the actual deliverable.
Think about the next person. A teacher may need the answer submitted in a specific place. A colleague may need the attachment to open and the numbers to match an approved source. A person waiting for a lift needs you at a location, ready to leave. The job ends when the promised outcome is usable, which can be later than when you finish your favourite part.
- Start. What needs to be open, available or prepared?
- Work. What are the main actions?
- Check. What could make the first result unusable?
- Handover. Who needs to receive or approve it?
- Finish. What will tell everyone the job is complete?
Agree what counts if conditions change
A group may ask for a full report by Friday while a supplier has yet to send figures. You can offer a verified summary if the figures arrive by Thursday, and a clearly marked partial update if they do not. Confirm which outcome would help. A conditional promise makes the dependency visible. It gives the decision-maker a chance to set a different plan before the deadline passes.
If you need an approval you have never requested before, find out how it works. Ask which person can act, what information they need and how long it ordinarily takes. The estimate can remain provisional until you have the answer. You can still give an update time. “I’ll confirm by three whether Friday is possible” tells the person what to expect now.
Chapter 3 of 14
Use your past work to make the next estimate
Choose a comparable example
Look for a task with similar size, difficulty and dependencies. A five-slide presentation that reused a template may not tell you much about a twelve-slide presentation with new data. It can still give you information about one part, such as checking the slides on the classroom computer. Use the parts that compare and name the ones that are new.
Record both your estimate and the result for a few tasks. “Expected forty minutes. Took fifty-five. Needed fifteen minutes to find the source.” That gives you a usable adjustment next time. If a delay was unusual, write that down too. Look for recurring differences instead of applying the longest delay to every estimate. Several examples can tell you which amount is ordinary and which depends on special conditions.
Include the quiet gaps around the task
Set aside time to open the work, switch from the previous job and leave the result in the right place. At home this may include clearing a table or packing supplies. At work it may include checking permissions, getting a second set of eyes or sending a confirmation. For travel it may include leaving the room, waiting for transport and walking to the exact entrance. These actions are small and real.
If you are scheduling two tasks together, check whether one can finish before the other begins. A call may have to end before you can travel. A reviewer may need the file before they can read it. A person can do some work while waiting, but the whole schedule still depends on when the answer arrives. Put the waiting period where it belongs instead of assuming it will be invisible.
Chapter 4 of 14
Give an estimate other people can use
Use a range with a reason
“I can probably send it between two and four. I’m waiting for a check on one figure and I’ll update you at one.” This is more useful than giving an exact time based on an unknown reply. If someone needs an exact decision, find out why. They may be able to use the first part by two and leave the final figure until later. A range can prompt a better agreement.
Distinguish the earliest possible time from the time you are willing to promise. If a journey can take thirty minutes when everything lines up, decide how much uncertainty the arrival can tolerate. A casual meeting may allow a short delay. An appointment with a strict check-in time may call for an earlier departure. The time you promise should reflect the actual consequence of being late.
Flag the delay when a checkpoint fails
Suppose you promised to send a review at five and need a draft by two. At two the draft has not arrived. Tell the people affected now. “I haven’t received the draft. I can still review it today if it comes by three. If it’s later, I’ll confirm a new handover.” This gives them time to help or adjust their plans. Waiting until five leaves fewer options.
If you caused the delay, explain what you will do. “I missed the time needed to verify the examples. I can send the checked version tomorrow morning or the unverified draft today.” Let the recipient choose if that is their role. A useful update gives an accurate account and a choice about how to proceed.
Chapter 5 of 14
Examples from school, home and work
A student plans a revision evening
Mei plans to finish a worksheet, revise two topics and pack for the next day in two hours. She looks at her last three worksheets and sees they usually take most of an hour when she checks corrections. She marks one topic as essential and leaves the second as optional. She also chooses a stopping point for the worksheet if a question needs help. The new plan gives each task a realistic place.
Afterward, Mei records where the plan held. The first topic took twenty-five minutes and the second would have overlapped dinner. She can use the information next time. The goal is an accurate account of how her evenings work, not a schedule that looks full on paper.
A family gives an arrival time
A family agrees to reach a venue by ten. The drive usually takes thirty minutes, but getting everyone out, finding parking and walking to the entrance can take twenty more. They choose a ready-to-leave time, not just a driving start time. One person prepares the bags, another confirms the entrance. If they know the venue is unfamiliar, they can allow time to locate it. The plan covers the whole journey.
If one person is often late, look at which part repeatedly takes longer. Maybe they are the one checking that everybody has their supplies. Sharing the preparation may work better than asking them to hurry. Give the preparation a place in the schedule and name who owns each part.
A team estimates a report with outside approval
Ari can draft a report in ninety minutes. The source data usually arrives in the afternoon and the approver only checks work at set times. Ari gives the team two timings. “I need about ninety minutes once the data arrives. The approved copy is likely tomorrow morning if we make today’s review window.” The team can plan for the approved copy rather than assuming the report will be ready ninety minutes from now.
If the data arrives late, Ari updates the team about which window was missed. They can decide whether an unapproved draft has any useful role or whether the decision must wait. The estimate protects both the work and the people who will rely on it.
Chapter 6 of 14
Work out which part of the estimate is uncertain
Use separate estimates for different kinds of work
A presentation includes collecting examples, arranging them and rehearsing. You may have reliable evidence for the rehearsal and very little for finding examples. Estimate the familiar part using past work. Give the uncertain part a range or a checkpoint. “We can rehearse in forty minutes once the examples are ready. I’ll know by Tuesday how many we can use.” This gives the group more information than one number for the entire project.
A list can reveal when one uncertainty controls the finish. If the task requires access to a room and nobody has confirmed the key, finding the key may matter more than improving the estimate for setup. Ask the person who can confirm access. You can still do work that will be useful either way. Distinguishing the uncertain part gives you a way to reduce it.
Look at what depends on a reply
People often make a plan that assumes someone else will respond as soon as asked. A reviewer may have their own schedule. A friend may be working. A supplier may need time to check an order. Ask when the person can reasonably respond and tell them when you need an answer. If the deadline will pass before they can reply, use another route or change the plan. A dependency deserves an owner and a time.
You can set a fallback that serves the actual purpose. If a classmate does not send their example by six, you might prepare the version that uses the examples already verified and ask the teacher how to handle the missing section. A team may postpone a decision until an approval arrives. Choose the fallback based on the consequence of working without the information, and tell people who rely on it.
Chapter 7 of 14
Build a useful record without tracking every minute
Record a few ordinary tasks end to end
For one week, select several tasks you often misjudge. Write when you actually began, when the result became usable and what happened in between. Use a simple note. “Started at seven. Opened the current file at 7.15. Finished at eight. Needed another ten minutes to upload.” You now know which times belong to setup, active work and delivery. If someone needed the file at eight, that last ten minutes matters.
Include examples that went well and ones with an ordinary interruption. You may notice that late afternoons are more fragmented or that a regular review always takes longer when another team is involved. The record need not be perfect. A few honest observations can be more useful than a precise-looking estimate based on your best day.
Make the estimate serve the next decision
If you are deciding what fits before dinner, record the elapsed time for the whole task. If you are deciding how much work you can assign a colleague, consider the active effort and any waiting they can use for other tasks. If you are giving a delivery time, include the next person’s availability and any required approval. The same record can support several estimates when you know which decision each one serves.
Review the assumptions before applying the record. The last report used a template and this one starts from a blank page. The last journey happened on a quiet morning and this one is at a busy time. Keep the comparable parts and estimate the changes separately. Over several tasks, look at which adjustment brought the prediction closer to the result.
Chapter 8 of 14
What to do when the task is already running late
Communicate the new estimate when it can still help
You planned to send a draft at four and at two discover a missing source. Start by deciding whether you can still deliver the requested result. If you need a reply from someone else, check their timing. Then update the person waiting. “The source is incomplete. I can send the checked sections at four or the whole draft tomorrow if the missing information arrives this afternoon.” They now have a choice.
Avoid promising a revised exact time before checking the part that caused the delay. If you cannot give a reliable finish, give a reliable update. “I’ll confirm by three whether the review can happen today.” A promise to send an update can be kept even when the result depends on another person. Make sure the update contains the decision the recipient needs.
Keep the required checks visible when reducing scope
When time is short, there may be room to cut examples, postpone a supplementary section or send a smaller version. Ask which part the recipient can actually use. A summary may help someone prepare for a meeting. An unverified figure may be unsuitable for a decision. Do not present work as checked if it is still provisional. A smaller reliable result can serve a different purpose than a full draft with uncertain status.
Afterward, write down what made the first estimate wrong. You may have left out checking, picked a poor comparison or accepted a deadline without discussing scope. Change the process that failed. For example, include the reviewer’s availability before promising delivery, or request the source earlier. This is more practical than deciding you simply need to work faster.
Chapter 9 of 14
A worked example from estimate to handover
Nia agrees to prepare signs for a school event. She thinks the work takes an hour because that is how long she spent designing the last set. On review, she remembers that she waited for the final room list, printed a sample and walked to another building to collect the finished signs. The whole process took most of an afternoon. She now asks when the room list will be confirmed and who can approve the sample.
The organiser says the room list will be available Tuesday morning, and the printer needs the approved files by two. Nia can do most of the layout before Tuesday and reserve the morning for names, directions and proofing. She promises an approved file by one if the list arrives by ten and the organiser can look at the sample before noon. She puts the important time in the shared plan.
On Tuesday the list arrives at eleven. Nia can still finish the signs for rooms already confirmed, and two room labels need further checking. She tells the organiser which ones are ready and asks whether the unclear labels can be printed separately. They agree to print the confirmed signs and leave the last two until the information arrives. The task has changed shape, but the people relying on the signs know exactly which part they can use.
At the next event, Nia can reuse the evidence. The design took an hour. Checking the names and the first print took another thirty minutes. The important risk was the room list. She plans around those facts and asks for the final list earlier. Her first guess still contains useful information about design. It simply did not describe the whole job.
Chapter 10 of 14
Apply the same method to appointments and chores
A household job may include finding supplies, moving furniture, doing the work and restoring the space. If another person needs the room afterward, include the final step. Before promising to finish a cupboard in half an hour, check whether everything taken out can go back before the next person arrives. A shorter version might be to sort one shelf and leave the rest for a time when you can finish it.
For an appointment, start with the arrival requirement and work back. Include the walk, waiting and any instructions about check-in. Check which parts are in your control and what you will do if one step takes longer. If a delay would have a real consequence, choose a departure based on a realistic range rather than the shortest journey you remember. Tell other people when you need to leave and what has to be ready before then.
If someone else is usually responsible for collecting the supplies or confirming the route, make their work visible. The trip or task may look quick to the person who starts after everything is ready. Share the preparation where appropriate. Better estimates often reveal work that a household or team can distribute more fairly.
Chapter 11 of 14
Practise one estimate before making another promise
Choose a task you expect to repeat. Write your first estimate without changing it. Then define the finish, find a past example and add any missing setup, waiting or review. Give the revised estimate separately. After the task, compare both with the result. The purpose is to see which information changed the prediction and whether that change was useful.
If the revised estimate is still wrong, look for a specific reason. Maybe you assumed you could work continuously and your role required interruptions. Maybe you counted the wrong part as the finish. Maybe a real surprise made any earlier prediction difficult. Use the explanation to make the next estimate more useful. A realistic plan leaves room to learn without treating every delay as proof of poor character.
Chapter 12 of 14
When several tasks compete for the same hour
Make the overlap visible
A student has one free hour and three tasks that each seem to take twenty minutes. If all three require finding materials, changing rooms or asking another person, the hour may not fit. Put the tasks in sequence and identify which can genuinely overlap. Waiting for someone to answer can overlap with another task. Two jobs that both need your attention cannot use the same minutes. Leave enough room for the change between them.
A useful schedule also shows which task has priority if there is a delay. “Finish the application first because it closes tonight. Review the notes only if there is time.” This allows the plan to survive an ordinary interruption. If all tasks are presented as equally urgent, ask who can decide which one moves. The time constraint belongs in the decision.
Estimate the work that comes from interruptions
A person who covers a reception desk may be able to edit a document during quiet periods and cannot assume a continuous hour. If the job needs concentration, find out when cover is available. If it can be broken into short sections, estimate how long it takes to resume each one. A useful promise accounts for the actual working conditions. It need not assume a level of focus the person cannot reasonably obtain.
The same issue appears at home when somebody starts a chore while caring for a child or waiting for an important call. Decide which part can be paused safely and where it can restart. If a job cannot be interrupted without creating more work, choose a more suitable time or arrange help. The estimate is partly a decision about the setting in which the work can happen.
Chapter 13 of 14
Use an early test on a new task
If you have never made a particular kind of presentation, try building one slide from the real source. Notice how long it takes to find the material, make it clear and verify it. The result gives you a better comparison for the rest of the work. Check whether later slides are similar or have different requirements. A small test can reveal a hidden task before you promise a full result.
A team can use the same idea before committing to a large job. Prepare one example, have the right person review it and ask whether the quality and format are suitable. Estimate the remaining work after the example is accepted. If the test reveals a problem, the group can change the method while the cost is still small. Be clear about what the test proved and which uncertainties remain.
Keep a record of any work that happened before the task officially started. Reading a brief, finding the right person and preparing a place to work can all use time. If you want a repeatable estimate, include the work someone will have to do again next time, even if it happens on a different day.
Chapter 14 of 14
Frequently asked questions
Why do small tasks take longer than I expect?
You may remember the central action and omit setup, switching, checking or waiting. Measure one ordinary example from the actual start to the usable result.
Should I add the same buffer to every task?
Use the uncertainty and consequences of the particular task. A familiar routine with little variation may need less room than a new task that relies on other people. Past examples can help you decide.
What if I have never done the task before?
Find a comparable task or ask someone who has done it. Estimate the known parts and identify the unknown part. Set an early checkpoint to improve the estimate once you see the work.
How can I give a deadline without overpromising?
State what is included, which dependency matters and when you will update the person. If the requested time cannot fit the full scope, offer a smaller usable result or a different date.
What if I keep underestimating even after recording times?
Compare which part is still missing. You may be measuring active effort while promising elapsed time, or choosing examples that went unusually well. Change one part of the estimating process and review it over several tasks.
Back to contents · Previous chapter · Sources and next reading
