Time Management — Examples

Example 1 — Apply your own correction factor

You recorded five estimates against what each task actually took. Turn that into next week’s plan instead of estimating from scratch again.

Estimated 1d  ->  actual 2d    (unfamiliar library)
Estimated 1d  ->  actual 1d
Estimated 3d  ->  actual 4d    (the integration took longer)

Solution

Ratio       1.5 on my own estimates
Next week   two 1d items  ->  plan 3d, not 2d
            one 3d item   ->  plan 4.5d
Slack       plan four fifths of the week; keep Friday afternoon free

Applying the measured ratio to the next plan is what stops the same over-commitment repeating, and the slack is capacity for the incident that will arrive. A plan written as if every item took exactly its estimate has no room for one surprise. The usual mistake is treating the ratio as pessimism rather than as data, then planning a week full of one-day items.

Example 2 — Say no with a trade

A reporting export lands in your inbox while the migration is committed for the week. You are about to reply that you are too busy. Write the reply as a trade.

Request  "can you pick up the reporting export this week as well?"
You      migration committed to Friday; about to refuse

Solution

"I can do the reporting export this week if the migration slips to next
 week. Which would you rather have on time? If the migration keeps its
 date, I can start the export the following Monday.

 If it helps, the export is the smaller piece, so I would move that
 rather than the migration."

The trade puts the priority decision with the person who owns the priorities, and it offers a route rather than a wall. A bare “too busy” invites escalation instead of prioritisation. The usual mistake is refusing without the exchange, so the same request returns later as a complaint about attitude.