Estimate the work, not just the finished piece
A request for “a short video” or “a simple website” describes an outcome, not the work required to produce it. Before estimating, write a brief that names the deliverable, its intended audience, the materials already available, and who will approve it. A student making a presentation might need to gather images and check citations; a freelance designer might need to prepare several file formats. Those steps belong in the estimate even though they are not the final piece.
Break the project into stages you can recognize while working: discovery, concept development, production, review, revision, and handoff. Then list the tasks within each stage. Keep the list useful rather than exhaustive. “Draft three layout directions” is easier to estimate and track than “do design,” while recording every minor action can make planning more work than the project itself.
Use ranges and name the assumptions
A single number can suggest certainty you do not have. For tasks with unknowns, give a reasonable range and explain what would place the work near either end. You might estimate that editing a set of product photos will take one to two working days if the images arrive organized and the requested style is consistent. If files need sorting or individual retouching, the estimate may need to change.
Separate hands-on effort from elapsed time. A task might require several hours of your attention but stretch across multiple days while you wait for feedback. Note any dependencies: approved copy, access to a shared folder, a decision from a teammate, or usable source files. This helps everyone see why a delivery date cannot be calculated by simply adding production hours.
Allow room for exploration and review
Creative projects often require trying an idea before you know whether it works. Treat that exploration as a planned stage, not as a failure to start producing. Define its boundary: for example, the team will test two visual approaches, select one, and then build the remaining pages from it. This gives experimentation a purpose without implying that every possibility will be explored.
Reviews also take time on both sides. Agree on who will consolidate comments, when feedback is due, and how many review rounds are included in the plan. A small team can avoid conflicting requests by having one person collect notes in a shared document. If feedback introduces a new goal rather than refining the agreed work, pause and estimate that change separately before committing to a revised date.
Turn the estimate into a working schedule
Place the stages on a calendar, allowing for other commitments and the time between handoffs. Identify checkpoints where you can compare the plan with reality: a brief approved, a first draft ready, a review completed, and final files prepared. Checkpoints are more useful than a distant deadline because they reveal trouble while there is still room to adjust.
Set aside some unassigned time for ordinary friction, such as clarifying a request, fixing an export, or incorporating a small correction. This is not permission to expand the project indefinitely. If the work is using that space quickly, say so early. Share what has changed, which part of the estimate is affected, and the available choices: reduce scope, move the delivery date, or make more time available.
Learn from the result without judging the guess
During the project, record time at the stage level rather than trying to account for every minute. Note where the plan differed from the work: perhaps concept selection was quick, but preparing files for delivery took longer than expected. Also record changes to scope and waiting time, so you do not mistake a delayed approval for slow production.
After delivery, compare those notes with your original assumptions. Use what you learn to improve the next brief, task list, and review plan. The goal is not to produce an exact number every time. It is to make an estimate that helps people decide what to do, understand what it depends on, and recognize when the plan needs to change.
