Wasted Time at Work: 7 GTD Fixes That Stick

Most wasted time at work is not idle time at all; it is re-decision time, and it looks exactly like work while you are doing it. Opening the same email for the fourth time. Reopening a document to remember where you left off. Asking a colleague something you already asked last Tuesday. This piece names seven places that cost sits in a normal week and gives the GTD mechanics that remove each one, with the list design and perspective rules spelled out rather than hand-waved. The honest conclusion, up front: willpower does not fix this, and neither does a time-tracking app. A system you trust does, and it takes about four weeks to bed in.
Where the hours actually go (it is not just your phone)
Three different things get lumped together as lost time, and they need different treatment.
Idle time is the obvious one: scrolling, waiting for a file to open, the ten minutes before a meeting that are too short to start anything. Interruption time is the colleague at your desk, the chat ping, the call. Both are real. Both are what every “top time wasters”list describes, because both are visible from the outside.
Re-decision time is the expensive one, and nobody counts it. Every time you look at an input and have to work out again what it means, what the outcome is and what you would physically do next, you pay the same thinking cost you already paid. An email you have read three times has not been processed three times. It has been deferred three times, with a full re-read each round.
Try a two-day audit before you change anything. Keep a tally, paper is fine, and mark a stroke every time you re-open an email you had already read, reopen a file to work out the next step, or re-ask someone something you have asked before. Most people are startled by the ratio of repeats to new work. That tally is your real target.
Discipline cannot touch this, because the problem is not that you are weak at 3pm. The problem is that the decision was never written down in a form your 3pm self can act on. A trusted system stores the decision, not the item. That is the whole trick, and the seven fixes below are just places to apply it.
Fix 1: One inbox instead of six places to check
Count your real capture points honestly. Email, work chat, a paper notebook, the notes app on your phone, sticky notes on the monitor, voicemail, a whiteboard, and the back of your mind. Six to nine is typical. Every one of them is a place you have to scan, and scanning is re-reading, and re-reading is re-deciding.
Job one: time to captured. From the moment a thought arrives to the moment it is safely in a place you will actually empty, how many seconds? If that is over about five seconds with your phone locked and your hands full, you will skip it under pressure, and the ideas you skip are the good ones you had walking out of a meeting. Five seconds is a practical working benchmark rather than an official rule, but it holds up.
Voice capture is usually the fastest route on a phone; paper is the fastest at a desk with a laptop lid down. Both are fine, provided they land in one inbox you empty rather than six you glance at. If you want the mechanics of getting voice, paper and app capture into a single funnel, the detail is in this guide to capturing anything in under five seconds with an AI assistant.
The mistake almost everyone makes: treating the email inbox as the master list. Email is a capture point, not an action list. A 40-message inbox used as a to-do list costs you a full re-read every time you open it, and you open it a lot.
Fix 2: Clarify once, so you never re-decide
David Allen’s clarify questions are the cheapest productivity upgrade available. Is it actionable? If yes, what is the outcome that means it is done? What is the very next physical, visible action?
Physical and visible is the part people skip. “Dave quote”is a reminder to think. “Ring Dave on 0161 496 0000 about the kitchen quote”is a reminder to act, and it costs zero thinking time at the point of use. You pay the clarification once instead of every time your eye crosses the line. Entries like “Mum”, “website”and “budget”are the main reason weekly reviews drag; each one restarts a conversation you already had with yourself.
The two-minute rule belongs here too, and it is more mercenary than people realise. A 90-second reply costs more to capture, tag, file, re-read and schedule than it does to send. So send it. Anything longer becomes a next action with a named outcome, written properly, and leaves the inbox.
On AI: it is genuinely useful for turning a woolly open loop into candidate next actions. Paste in “sort out the autumn mailer”and you will get a handful of plausible steps, some of which are usable. Do not let it decide what matters or maintain your lists. The jobs it does well and the ones it quietly ruins are set out in more detail in this breakdown of making ChatGPT work with GTD.
Fix 3: Context lists that match the tools and energy you actually have
A single flat list of 140 actions forces you to read 134 things you cannot do right now in order to find the six you can. That scan happens every time you look. It is the purest form of re-decision cost there is.
Contexts are not folders. The point is that the list in front of you contains only what you can genuinely do with the tools, people and energy available at that moment. The ones that still earn their place in 2026: Calls, Errands, Agendas (one per person), Low Energy, Offline, and anything tied to a physical location you visit rarely.
In OmniFocus, build it in the rule builder: tag is Errands, availability set to Available, grouped by project, sorted by due date. Your 140-item list becomes a six-item list you can work from the car park. Half a dozen views like that, properly set up, remove most daily scanning; there is a fuller walkthrough in this guide to custom OmniFocus perspectives.
Not on a Mac? Things reaches the same place with tags plus a saved filter inside Anytime, and Todoist does it with a saved filter such as @errands &!no date &!subtask style queries, adjusted to your tags. The app matters far less than the rule. One screen, only available actions, short enough to read in a breath.
Fix 4: A Waiting For list so chasing stops eating your week
Delegation without a Waiting For entry is the most expensive habit in office work. You pay once to delegate, again to remember you delegated, and a third time to reconstruct what you asked for, when, and of whom. That third payment usually happens in front of someone, which adds embarrassment to the bill.
Log it at the moment you send, with the date and the name baked into the text: “WF: Priya, signed-off copy for the autumn mailer, sent 15 September 2026”. No archaeology later. A Monday pass over that list surfaces the chase before it becomes a problem, rather than the chase occurring to you halfway through an unrelated meeting.
Pair it with an Agenda list per person. Five small questions saved for one conversation beat five interruptions, for both of you. Review Waiting For at the start of the week, not after something has already slipped.
Fixes 5, 6 and 7: support material, meeting prep and the weekly review
Fix 5: Keep project support material out of your action lists
Reference material judged on how pretty it looks is a beautiful shelf of software you never open. Judge it on retrieval speed instead: can you get to the brief, the contract and the last three emails in under ten seconds, from your phone, without remembering a folder path? If not, the structure is wrong, however tidy it looks.
Keep support material separate from the action list and linked to it. Mixing them means every scan of your actions drags you into reading notes, which is re-decision dressed up as preparation.
Fix 6: Apply the natural planning model before the invite goes out
Most recurring meetings exist because nobody ever wrote down their purpose. Run Allen’s natural planning model over one of yours: purpose, successful outcome, brainstorm, organise, next actions. Two things usually happen. The invite list gets shorter and the meeting gets shorter. A meeting with no defined outcome generates re-decision for every person in the room, multiplied by the room.
Fix 7: The weekly review is the maintenance slot, not a nice-to-have
Everything above decays without it. A repeatable checklist works: empty every inbox to zero, review the calendar two weeks back and four weeks forward, read the projects list, read Waiting For, read Someday/Maybe, and check for stalled projects.
That last one matters more than it sounds. A project with no next action is not a stalled project, it is a recurring interruption, because your mind will raise it again and again until something concrete is written down. OmniFocus has a Stalled Projects view built in; in Todoist or Things you can approximate it with a filter for projects with no available tasks. Catch them on a Friday review and they stop becoming Friday-afternoon emergencies three weeks later.
What to measure, and the traps to avoid
Measure completed next actions and finished outcomes, not hours logged. Productivity in the national statistics sense is output per hour worked, which is how the ONS measures labour productivity, and the same logic applies at a desk: more hours on the clock is not the number you want to move. If you are curious how the national picture frames individual work, we have looked at what the UK productivity figures mean for your own working week.
Surveillance-style monitoring tends to produce busier-looking work rather than better work. Keystroke counts and activity scores reward visible motion, and re-decision is extremely visible motion. Skip it.
AI assistants shift where the waste sits rather than removing it. Good at: breaking a vague open loop into candidate actions, drafting a short reply you then edit, summarising a long thread so you can clarify it once. Poor at: deciding what matters this week, and maintaining your lists, where it produces tidy-looking output that you then have to check line by line. Checking generated lists is a new daily admin tax. Watch for it.
Roll the fixes in one at a time, roughly a week each: week one, single inbox and capture speed; week two, clarify properly and apply the two-minute rule at triage; week three, build your contexts and one or two perspectives; week four, Waiting For plus the first real weekly review. Rebuild everything at once and you will abandon it by the second month. That pattern is the common thread in every productivity system that actually lasts.
Frequently Asked Questions
How much time is actually wasted at work each day?
Published figures vary wildly depending on who funded the survey and how they defined waste, so treat any single number with suspicion. The more useful measurement is your own two-day tally of re-opened emails, re-opened files and re-asked questions. Most people find repeats make up a surprising share of their switches, which is a figure you can actually act on.
What causes the most wasted time at work for office-based staff?
Unclear next steps, not distraction. When an item on a list says “budget”rather than “draft Q1 figures tab and send to Sam”, you re-make the same decision every time you see it. Multiple capture points make it worse, because each one gets scanned rather than emptied.
How do I stop wasting time on email without ignoring it?
Treat the inbox as a capture point and empty it on a schedule, two or three passes a day. Anything under two minutes gets answered on the spot; anything longer becomes a properly worded next action with the email filed or linked. The aim is an inbox you process, not a list you re-read.
Can time-tracking apps fix wasted time at work?
They diagnose, they do not cure. A tracker will show you that you spent 90 minutes in email and nothing about how many of those minutes were spent re-reading the same five messages. Use one for a fortnight to find the pattern, then change the system rather than the stopwatch.
How long does it take before a GTD system reduces wasted time?
Capture speed pays back in days. Context lists and Waiting For usually feel worth it within two to three weeks. The weekly review takes longer to stick, often a month or two, because it only proves its value once it catches something expensive before it goes wrong.
