In the morning the list has twelve items. By evening eight are done, but the main document hasn't been started: the day went on messages and quick favors. The list was detailed, yet there was no plan, because it never accounted for how much time was actually free.

A good daily plan answers three questions: what should come out of the day, how much time there is for it and what to do when new work arrives. You don't need to adopt a whole methodology. A short routine you repeat every morning is enough.

In short

Meetings and commitments first, then one main result, work blocks and a buffer. A task list shows what needs doing; a calendar helps check when it will fit.

Collect incoming work in one place

Before choosing tasks, write down everything you're holding in your head: assignments from chats, ideas, replies you promised, unfinished work. Don't give anything a "today" deadline yet.

"Work on the website" doesn't help you start. Turn it into a next action: "test the enquiry form and write down the errors". A large project stays a project, and the daily plan gets an action you can complete.

This is a simplified version of David Allen's GTD: capture, clarify, organize, review, do. You don't need the full method for a daily plan.

Look at the calendar first

Mark meetings, required calls, travel and breaks. Only then count the time left for tasks. If three of your eight hours are meetings, you don't have eight hours for preparing documents. A short gap between two meetings is also a poor slot for complex work.

A deadline and time to do the work are different things. "Send the proposal by 5 pm" sets the latest moment. "Prepare the proposal from 10:00 to 11:30" reserves time for the work itself. If you write down only the deadline, the preparation keeps sliding until it hits it.

Choose the main result

Ask what has to be finished today so that the day isn't wasted. To start, take one main result and a few small things around it.

If you're unsure what to move, compare the consequences of postponing: who is waiting, which next step is blocked, where the real deadline is. A new message isn't more important than planned work just because it arrived later. And if an urgent task does take first place, name the current task that moves. Otherwise you've added a commitment without adding time.

Set aside blocks and a buffer

Put demanding work in a slot where nobody will pull you into approvals. Group short replies and administrative chores if your role allows it.

Leave part of the time free for the unexpected. A support agent needs a bigger buffer than someone with a research task known in advance. You can find the right size by looking, over a few days, at how much time actually goes to unplanned work. Don't fill the schedule to the last minute: any urgent question will break it at once.

A sample schedule

Suppose a manager has to prepare a client proposal and attend two meetings:

Time Activity Expected result
09:00–09:20 Review incoming work and priorities A clear task queue
09:20–10:50 Calculate the proposal price A table with the price and assumptions
10:50–11:00 Break —
11:00–11:45 Team meeting Decisions recorded in tasks
11:45–12:15 Replies and clarifications Missing information received
12:15–13:00 Lunch —
13:00–14:00 Format the proposal A completed draft
14:00–14:30 Client meeting Next steps agreed
14:30–15:30 Buffer and revisions Review comments addressed
15:30–16:40 Smaller current tasks The agreed queue completed
16:40–17:00 Review the day Statuses and tomorrow's plan updated

The main result gets two separate blocks, and the buffer is visible in advance. If an unplanned hour-long call appears, you have to cut the scope honestly instead of hoping everything will somehow fit.

Finish with a short review

Look at what got done and what didn't. For each unfinished task choose an action: continue tomorrow, change the scope, request information, hand it to someone else or drop it.

If a task moves several days in a row, find out why. Maybe it's worded too broadly, maybe it matters less than it seemed, maybe it's waiting for someone's decision. Automatic postponement without a review only preserves the problem.

Where Pomodoro helps

Pomodoro splits work into focus sessions with breaks. It helps you start the task you picked and notice when you're being interrupted, but it won't tell you which task to pick first.

To try it, use the classic format: 25 minutes on one thing, a 5-minute break and a longer pause after several cycles. Before starting, write a small result for the session: "collect three estimates", "write the introduction". Send new thoughts that pop up straight to your inbox. If a truly urgent problem interrupts you, deal with it and replan the rest of the time. And don't cut a good meeting or deep work short just because of a timer.

You don't need a separate app for this; any timer will do. And if the problem is priorities or too little time between meetings, Pomodoro won't solve it.

How this looks in iTasker

You can dump incoming work on the bot in a private chat: a plain text message becomes a personal task. A work message in a linked group turns into a task when you reply to it with /new. In the card, the description holds the expected result, the date holds the real deadline and the reminder fires at the moment you choose.

Don't give every idea today's deadline just so it shows up in the list. Keep the queue of future work separate from today's plan. If the workload of the whole team matters, a kanban board helps.

Launch the iTasker bot