Eight hours of effort does not mean tomorrow
A task needs eight hours of work, but the only qualified person has two hours available daily. Even without interruptions, that takes four working days. An external approval can extend the calendar further. Confusing effort with duration creates deadlines that look feasible only on a spreadsheet.
Before promising a date, check availability, skills, and existing commitments. Include support, reviews, and recurring work. A plan assigning all capacity to new deliveries stops representing the actual week of the people doing the work.
Map what must happen first
In a simple example, preparing data takes two days, migration takes one, and validation takes two. If each depends on the previous step, the sequence needs at least five working days before waits or contingencies. Putting all three in the same week does not make them parallel. Dependencies matter as much as dates.
Identify dependencies on suppliers, access, decisions, and environments too. Give each an owner. “Waiting for the client” describes a state, not a plan: specify what was requested, when it is needed, and what happens if it does not arrive.
Show uncertainty before it becomes delay
For unfamiliar work, use a range with assumptions. “Three to five days if access is ready” says more than invented precision. Separate a technical estimate from a committed date. Commitment includes risk, coordination, and a decision about acceptable contingency.
Update the forecast when new evidence arrives. Do not hide unfinished work by changing a percentage. Show remaining work, blockers, and the next check. Reducing simultaneous tasks may help finish existing work, especially when multiple efforts depend on the same person.
Run a fifteen-minute review
Choose an upcoming delivery and ask: what depends on what, who is actually available, and what is the largest uncertainty? Confirm with those doing the work. Resolve unowned dependencies before adding another date. An honest forecast enables earlier action.
Sources & further reading
Sources accessed October 24, 2026. Numerical examples and scenarios are illustrative.
Ready to put this knowledge into practice?
We can work together on your team’s challenge or your next project.
Talk to Calembe ↗