Plan your next move
When several tasks arrive at once, it is tempting to start with whichever feels loudest. A better start is to separate three things that often get blurred together: when something is due, what happens if it is not done, and how much work it will take. Looking at each on its own gives you a reason for your order, not just a feeling.
Rank tasks by three separate questions: how soon is it due, how much does it matter if it slips, and how long will it really take. Then choose a short order of three steps and note what you are deliberately leaving for later.
Deadline, consequence and effort are different things
A deadline tells you when something is due. It says nothing about whether the task matters. A formatting job for an old report might have a deadline of tomorrow, yet nothing much would change if it slipped to next week. A task with no stated date, such as preparing what you will actually say in a presentation, can carry the largest consequence of all.
Consequence is the question of what changes if the task is late or skipped. Who is affected? Can the problem be fixed afterwards? Effort is separate again: it is your honest estimate of the time and concentration needed. A quick task with a serious consequence, like answering a supplier whose delivery depends on your reply, often deserves an early slot simply because it costs so little to remove the risk.
Sorting the sample workload
Take Priya's list and give each task a short note under the three headings. The budget update is due before Thursday, has a high consequence because the team will present those figures, and needs around ninety minutes. The supplier reply has a soft deadline of this week, a medium consequence, and takes ten minutes. The old report has a loose deadline, a low consequence, and takes an hour. The talking script has a hard deadline, a high consequence, and needs perhaps two hours including a read-through.
Written side by side, the picture changes. The report drops down quickly. The supplier reply stands out as cheap and worth doing early. The budget and script both matter a great deal, and the question becomes which one the other depends on. Since the script will refer to the budget figures, the budget has to be settled first.
Choosing an order and naming the trade-off
A plan works best when it is small enough to follow. Three steps are usually enough to start a day. Put the cheap, high-consequence item first so it stops sitting in your mind, then the task other work depends on, then the large task that needs a clear stretch of time.
Every plan leaves something out, and it helps to say so. If the old report is postponed, write down when you will look at it again, or ask whether it can be released as it is. That one sentence turns neglect into a decision, and it means you can tell a colleague honestly what is not being done and why.
See the idea
in a real situation.
It is Tuesday morning and a team presentation is due on Thursday at noon. Priya has four tasks on her list: update the budget figures in the shared slide deck, reply to a supplier asking about next month's delivery, tidy the formatting on an old internal report, and write the three-minute talking script for her section. She has about six hours of usable time before Thursday.
Priya's list reads: budget slides, supplier email, old report formatting, talking script. She starts with the report because it is the easiest to finish, and by lunchtime the budget and script have not been touched.
1. Reply to the supplier now (10 minutes): low effort, and a delay could hold up next month's delivery.
2. Update the budget figures (90 minutes, this morning): the team will present them, and my script depends on the final numbers.
3. Write and read through the script (2 hours, tomorrow morning): hard deadline, high consequence, needs an uninterrupted block.
Left for later: report formatting. I will check on Wednesday afternoon whether it can go out unchanged.
↗The cheapest task with a real consequence goes first, so a small risk is removed before it grows.
↗The budget comes before the script because one depends on the other, which stops rework later.
↗Naming what is postponed, and when it will be reviewed, makes the trade-off a decision instead of an oversight.
Make it useful
in your own context.
Write down four tasks you currently have. Use real ones, or invent a workload for a weekend project if that is easier.
- Beside each task, write its deadline, the consequence of it slipping, and your honest effort estimate in minutes or hours.
- Mark any task that another task depends on, and any that is quick but carries a real consequence.
- Choose three tasks to do first, put them in order with a one-line reason each, and write down what you are leaving out and when you will look at it again.
Choose a reasoned next action
Make the example your own. Use fictional or non-sensitive details while you practise.
Your practice stays on this page. Copy or download it to keep a useful next step; the website does not submit your notes.
Which of the three questions did you tend to ignore before, and how did the order change once you gave it equal weight?
Before your next busy day, spend five minutes writing deadline, consequence and effort beside each task, then commit to a three-step order and name one thing you are postponing.
Connect the next action to a useful goal.
Clarify what you want to do, and make any shared handoff explicit before relying on the plan.