Estimate the work you can see
A request such as “design a landing page” sounds like one task, but it contains several kinds of work. You may need to understand the goal, review existing materials, explore directions, make a draft, gather feedback, revise, prepare files, and hand them off. Estimating the whole request as a single block makes it easy to overlook the less visible steps.
Start by listing the actions needed to reach a specific deliverable. For a landing page, that might mean reviewing the brief, sketching a layout, designing one initial direction, refining it after feedback, and exporting the agreed files. Give each action a rough time range rather than an exact figure. A range acknowledges that the first draft may come quickly while a difficult layout problem may take longer. Add the ranges together only after you have defined what each one covers.
Separate making time from waiting time
An estimate can describe two different things: the hours you expect to spend working and the elapsed time before the task is finished. They are not interchangeable. A design may require several hours of focused work but span many days while you wait for copy, decisions, or feedback. If you promise a delivery date based only on making time, a short pause outside your control can put the schedule under pressure.
Write down the dependencies next to your task list. Which materials must arrive before you can start? Who approves a direction, and when will feedback be available? You cannot predict another person’s response time, but you can state the assumption behind your timeline. For example, an estimate can say that the next stage begins after consolidated feedback arrives. This makes the plan easier to revisit when a dependency changes.
Give uncertainty its own space
Some tasks are uncertain because the execution is unfamiliar. Others are uncertain because the outcome has not been chosen: the audience is unclear, the content is unfinished, or several people may disagree about the direction. These are different problems. More production time may help with an unfamiliar technique, but it will not settle an unresolved decision.
For unfamiliar work, allow time for a small test before committing to the full approach. For unclear direction, propose a brief discovery or concept stage with a defined output, such as a few rough options and a decision about which one to pursue. You can estimate that stage now and estimate later work more closely once the direction is approved. This is more useful than hiding a large, unexplained cushion inside a single number.
Define what a revision includes
Revisions are part of most creative projects, but “revision” can mean anything from adjusting spacing to changing the purpose of the piece. An estimate becomes more dependable when it describes the expected review process. Note how many feedback rounds the plan includes, whether feedback will be collected in one place, and what counts as a change to the agreed direction.
This does not require rigid rules for every small request. It gives both sides a shared starting point. If a draft needs substantial new content or a different concept, you can discuss the effect on time before doing that work. If the changes fit the agreed scope, you can proceed without treating every comment as a new negotiation.
Check the estimate as you work
An estimate is a planning tool, not a test you must pass. Compare your planned time with the time you actually spend at a few natural checkpoints: after exploration, after the first draft, and after a review round. If one stage takes longer than expected, ask why. Was the task larger than it appeared, did you lack an input, or did you spend more time exploring than the deliverable needed?
Use what you learn to update the remaining plan and communicate early if the delivery window may change. Keep brief notes on completed projects, including what the estimate covered and where it missed. Over time, those notes can help you recognize recurring steps you tend to forget. The goal is not perfect prediction. It is a clear enough plan to protect focused work, set reasonable expectations, and adapt when the work reveals something new.
