Procrastination is rarely laziness. It usually comes from not knowing where to start, and from having only a vague sense of how long the work will take. The Pomodoro Technique removes both excuses by shrinking the commitment: one task, twenty-five minutes, then a break. Notion handles the other half by giving every task a home and every finished session a record. Together they form a loop you can keep: plan, work, log, review.

This guide is written for people working in the UK who want something that survives a real week — the Tuesday that begins with two unexpected calls, the Friday afternoon when the office empties, the January scramble around the self-assessment deadline. None of it requires a paid Notion plan, a dedicated timer app, or a personality transplant. A kitchen timer, a phone face-down on the desk, and one page in Notion is enough to start tonight.

Why the Two Fit Together

The technique itself is deliberately low-tech. Pick one task, set a timer for twenty-five minutes, work until it rings, take five minutes away from the screen, and after four rounds take a longer break.

Its weakness is memory. The timer tells you what to do now, but nothing about what you finished last Tuesday or whether your estimates were anywhere near accurate. Notion has the opposite profile: excellent at holding lists, dates and history, and hopeless at creating urgency. A beautifully organised database will not make you start anything.

Side by side, they cover each other. Notion answers "what should I be working on?" The timer answers "for how long, and when do I stop?" That second answer does more for procrastination than most planning systems, because knowing there is an end makes beginning much easier.

There is a quieter benefit too: calibration. After a fortnight of logging, you stop guessing. You learn that a client proposal takes four pomodoros, not one, and that the monthly expenses reconciliation you dread takes exactly two. Estimates stop being hopeful and start being useful.

Most people do not have a time problem. They have an estimation problem wearing a time problem's coat.

Set Up a Task List Built for Timers

One database is enough. Add only the properties that earn their place:

• Task — the name. Start it with a verb so it is obviously doable: "Draft the HMRC letter", not "Tax stuff".
• Status — a select with four options: Backlog, Today, Doing, Done. Four is deliberate. More options mean more decisions, and decisions are where momentum dies.
• Estimate — a number property for how many pomodoros you think it will take. Be honest. If you have never done the task before, write a three and expect to be wrong.
• Actual — a number property you fill in as you go. This is the honest one, and it is the reason the system improves.
• Energy — a select with Deep, Shallow and Admin. Deep work gets your first pomodoros of the day; admin fills the tired hour after lunch.
• Date — a date property, used sparingly. Only put a date on something if missing it has a consequence.

Three Views You Actually Need

Let the database do the tidying so you never have to.

1. Today — filtered to Status = Today, sorted by Energy. This is the only view you look at while working.
2. Backlog — everything not yet scheduled, sorted by date. Visit it during planning, not during work.
3. Log — filtered to Done, sorted by the date you finished it. This becomes your evidence on the days you feel you achieved nothing.

The Daily Loop: Plan, Work, Log, Review

The whole system is four steps repeated. The discipline is in not skipping the last two.

1. Plan (five minutes, once). Open the Backlog, drag three to six items into Today, and write an estimate next to each. Three to six is not arbitrary: that is roughly eight to twelve pomodoros, which is a full working day once meetings and email are accounted for.
2. Work (twenty-five minutes at a time). Pick the top item, set the timer, and do only that. No tab-hopping, no "quick check" of the inbox.
3. Log (thirty seconds). When the timer rings, add one to Actual and note in one line what you did. "Wrote the intro and the pricing section" is enough.
4. Review (ten minutes, Friday). Compare Estimate with Actual across the week and adjust your instincts for next week.

What to Log After Each Session

Keep it to a sentence. The point is not a diary; it is a trail of breadcrumbs so that future-you knows where the work stopped. A useful entry reads: "Halfway through the methodology section — needs the 2019 figures before it can continue." That single line saves ten minutes of re-reading tomorrow.

A Worked Example: Tuesday Morning

It is 9:15 and you have opened Notion. Today holds four items: "Draft quarterly report (est. 4)", "Reply to supplier emails (est. 1)", "Review Amara's invoice (est. 1)", "Book dentist (est. 1)".

You start the report. The timer runs, the phone is face-down, and at 9:40 you log one pomodoro and write: "Section one drafted, needs charts." You take five minutes, make a cup of tea and look out of the window rather than at a screen. Back at 9:47, second pomodoro, and the charts are pulled. Third pomodoro and the summary is written. You are ahead of your estimate.

Now you are tired, so you switch to Admin energy: the emails, the invoice, the dentist, three pomodoros and you are done before noon. The remaining energy in your day goes back to the report rather than to whatever shouted loudest. That is the whole trick — the timer did not make you work harder; the log made your estimates trustworthy, and the estimates made the plan realistic.

Handling Interruptions and Broken Pomodoros

Real life intrudes. A colleague rings, a delivery arrives, your child needs collecting. The rule is simple: note the interruption and either deal with it or defer it, but do not restart the clock unless less than a minute has passed.

• Internal interruptions — "I must remember to email the landlord." Write it on a scrap of paper and carry on. Do not open Notion; opening Notion is the interruption.
• External interruptions — if it takes under two minutes, do it and count the pomodoro as partial. If it is longer, log the pomodoro in Notion with a note, and restart later.
• Repeat offenders — if the same task breaks three pomodoros in a row, it is not a focus problem. It is badly defined. Split it in Notion before you sit down again.

Breaks, Done Properly

A break spent scrolling is not a break; it is a change of work. The five minutes exist to let your attention recover, which means standing up, moving, looking at something far away or making a hot drink. The longer break after four pomodoros should be fifteen to thirty minutes, and it should include leaving the room you work in if you can.

Two small rules protect the rhythm. First, breaks end when the timer says so — never when you reach the bottom of a feed. Second, if you are mid-sentence when the timer rings, you may finish the sentence and no more. Anything else turns a twenty-five-minute block into forty.

Common Traps and How to Avoid Them

• Over-engineering the database. If you spend Sunday building a dashboard with rollups and progress bars, you have decorated the system instead of using it. Build the four properties, then stop.
• Treating twenty-five minutes as sacred. Some work needs fifty-minute blocks — writing, coding, deep analysis. Use two pomodoros back to back with no break, and log them as two.
• Logging only successes. Log the abandoned pomodoro too. A session where you stared at a blank page for twenty-five minutes is data, not shame.
• Planning the whole week on Monday. Plans made on Monday rarely survive Wednesday's inbox. Plan the day; review the week.
• Confusing the tool with the habit. Notion will hold your intentions beautifully for months without ever doing the work for you.

Making It Stick Past Week One

Novelty carries most habits for about ten days. After that, the system has to be easy enough to run when you are busy and low on willpower. So keep the daily plan to five minutes, keep the log to one line, and keep the weekly review to a coffee break.

If you miss a day, do not rebuild anything. Open the Today view, pick one item, and set the timer. The system's greatest strength is that it forgives you instantly: there is no streak to break, no chart to reset, no evidence of failure anywhere on the page. Just a list of things you have already done, and one thing waiting to be started.

Start with a single pomodoro today. Log it. Tomorrow, do it again.