GTD vs. Deep Work vs. Time Blocking: Picking a Time System That Fits

TL;DR

• Productivity systems are not interchangeable. Each one repairs a specific failure mode, and most “I tried it, it didn’t stick” stories are a mismatch, not a character flaw.
• GTD fixes dropped commitments. Deep Work and time blocking fix weeks full of motion but empty of real output. Lyubishchev-style tracking fixes not knowing where hours go. Covey’s matrix survives as a filter, not a system.
• Pick by failure type: diagnose how your week actually breaks, then install the module that repairs that break.
• No system repairs a week that contains more promises than hours. That is a workload problem in a productivity costume.

The problem

Time systems get chosen the way diets do: by whatever a podcast covered last month. Then the system collapses in week three, and the verdict lands on you — undisciplined, unserious, constitutionally messy.

Usually the verdict is wrong. The big systems attack different bottlenecks, and installing the wrong one means solving a problem you do not have. Someone drowning in dropped commitments needs external memory, not two-hour focus blocks. Someone starved of deep output needs protected attention, not seventeen context-sorted lists.

So this guide does two things. It walks through the systems that are still alive in 2026 — what each actually repairs, and where each honestly breaks. Then it gives you the part that matters: a picker keyed to your failure type, not to fame.

What’s actually happening

Strip the branding and every time system manages the same two scarce resources: memory and attention.

Memory first. David Allen’s founding observation is that your head is a bad place to store commitments — the mind is for having ideas, not holding them — which is why GTD begins by moving every open loop into a trusted external system (gettingthingsdone.com).

Attention second. In Sophie Leroy’s experiments, people who switched tasks carried “attention residue”: part of the mind stayed on the previous task, and performance on the next one dropped (Leroy, 2009). Gloria Mark and colleagues found that interrupted workers do finish — by speeding up — but pay in stress, frustration and effort (Mark et al., 2008).

And one bias taxes every plan: the planning fallacy. In the classic thesis experiment, students predicted 33.9 days to finish and averaged 55.5 (planning fallacy). Each system below is a bet on which of these constraints binds you hardest.

The system: five candidates, examined honestly

GTD: an external brain for commitments

Mechanism. Capture everything that has your attention, clarify what each item requires, organize next actions, review weekly, engage — the five steps of Getting Things Done (gettingthingsdone.com). It is bottom-up: control the runway first, worry about altitude later.

Fits you if commitments leak. You wake at 3 a.m. remembering the unsent email; you run many fronts at once — management, ops, freelancing across clients — and one dropped ball costs real trust.

Where it breaks. The weekly review is load-bearing; skip two and the lists rot into fiction, at which point the whole structure quietly dies. GTD is also nearly silent on depth: you can run it flawlessly and spend a year on beautifully organized trivia. It is a to-do list with a constitution, and constitutions take upkeep.

The shift: commitments live in the system, never in your head. First move: do one full capture — every open loop, work and personal, into a single inbox. Budget an hour; the final count tends to be sobering.

Deep Work: defend the hours that produce anything

Mechanism. Cal Newport’s argument is that valuable knowledge work comes from long, distraction-free stretches of concentration, that this ability is trainable, and that most calendars are actively hostile to it — so you schedule depth like a meeting and defend it (calnewport.com). Leroy’s attention-residue result above is the lab version of his case.

Fits you if your output is thinking — code, analysis, writing, design — and your task list is fine while the real work never gets your best hours.

Where it breaks. Reactive, meeting-dense or on-call roles can rarely buy three-hour blocks. And Deep Work is a philosophy, not a complete system: it has no capture layer and no answer for the forty small obligations circling your head. Newport himself runs it on top of time-block planning (Time-Block Planner).

The shift: depth is scheduled, not awaited. First move: one 90-minute block tomorrow, phone in another room, one named deliverable at the end.

Time blocking: give every hour a job

Mechanism. Plan the workday as calendar blocks — including email time and buffer — and when reality breaks the plan, revise the blocks instead of abandoning the day. Newport describes this as planning every minute; the point is deciding on purpose, not executing perfectly (Deep Habits).

Fits you if your to-do list is fiction. The items are real, but days evaporate into meetings, chat and “quick” favors, and at six p.m. you cannot say where Tuesday went.

Where it breaks. On the planning fallacy, mostly: people reliably underestimate their own task durations (planning fallacy), so beginners write optimistic fan fiction about Tuesday, watch it collapse by 10:30, and quit in guilt. Blocking survives only if revision is treated as the method rather than the failure — and on heavily interrupted days, revision can become a job of its own.

The shift: the calendar is a decision you revise, not a prophecy you fail. First move: block tomorrow before it starts, and double your first estimates.

Covey’s quadrants: the useful ghost

Mechanism. The full 7 Habits apparatus — mission statements, roles, weekly goal sheets — reads as legacy now, but its matrix outlived it: sort work by urgent/not and important/not, then deliberately live in Quadrant 2, important-but-not-urgent, before those items migrate into crisis (FranklinCovey).

Fits you if everything feels urgent. Firefighting roles; inboxes that set your priorities for you.

Where it breaks. As a complete system it is vague about execution — the matrix classifies work, it does not schedule any. And its hard part is political, not analytical: Quadrant 3 is other people’s urgency, and no matrix declines that meeting for you. Run it as a filter inside another system, not as the system.

The shift: importance outranks urgency, by standing policy. First move: label today’s list Q1-Q4, then put one Q2 item into an actual calendar block this week.

Lyubishchev tracking: the little-known gem

Mechanism. Alexander Lyubishchev, a Soviet entomologist, logged every working hour from 1916 until his death in 1972 — 56 years, five-minute precision, stable categories from core research to correspondence, with monthly and annual audits (Polynov). Daniil Granin’s documentary novella about him, This Strange Life, carried the method far beyond entomology, decades before tracking apps (Voprosy Literatury).

Fits you if you genuinely do not know where time goes. You feel busy, your output disagrees, and every plan is built on imaginary numbers. Tracking replaces the imaginary numbers — which also makes it the natural first two weeks before adopting anything else.

Where it breaks. Measurement is not change: you can log everything and alter nothing. The audits cost real time — his monthly reviews ran 2-3 hours and annual ones 17-20 (Polynov) — and the method prescribes nothing. It is a mirror, not a map.

The shift: estimates must earn the right to be believed. First move: track two ordinary weeks in five or six categories, app or paper, without judging yourself. Then read the totals.

System	Built for	Fails when
GTD	Too many open loops; nothing gets forgotten	You need depth, not capture
Deep Work	Output that needs long focus	Your calendar isn’t yours
Time blocking	Chaotic days, reactive work	Plans die by 10 a.m. daily
Covey matrix	Priorities blur, everything urgent	You mislabel urgent as important
Lyubishchev tracking	You don’t know where time goes	Tracking becomes the hobby

The picker: match the system to the failure

The real question is not “which system is best” but “how does my week fail.” Match accordingly:

• Commitments leak — promised things vanish, people chase you — install GTD. Your bottleneck is memory.
• Nothing deep ships — the list runs, the real work starves — install Deep Work’s rule through time blocking. Your bottleneck is attention.
• You cannot say where time goes — run two weeks of Lyubishchev tracking before buying anything else. Your bottleneck is information.
• Everything is urgent — overlay Covey’s filter on whatever you run. Your bottleneck is priority, and possibly the word “no.”
• All of the above — sequence it: track first to see reality, then block to allocate it, then capture to stop the leaks. Systems are modules, not religions.

How it hangs together

These five are not rivals; they are layers of one machine. Capture (GTD) is the memory layer. The matrix (Covey) is the priority filter. Blocking is the allocation layer, depth (Newport) is the quality-of-attention layer, and tracking (Lyubishchev) is the feedback loop that keeps the others honest.

Each famous book sells one layer as the whole building. Your job is smaller and calmer: find the layer failing this quarter, install that module, and add the next one only when it becomes the new bottleneck. More on the attention side of the stack lives in our focus section.

When this won’t work

No time system cures overcommitment. If sixty hours of promises live in a forty-hour week, GTD will document the impossibility, blocking will schedule it neatly, and tracking will prove it with decimals. The fix is renegotiating the load itself — our rules for protecting your energy deal with exactly that contract-level problem.

Two smaller honesty notes. If your calendar belongs to someone else — shift work, on-call rotations — blocking and Deep Work degrade fast, and capture plus tracking are the realistic modules. And if attention stays broken across every context despite structure and sleep, this is not medical advice: a persistent pattern like that is worth discussing with a clinician.

The boring bottom line

There is no best system; there are four bottlenecks — memory, attention, priority, information — and a module for each. Diagnose the failure before installing the fix, steal parts without guilt, and expect maintenance, because every system rots without it. A tracked, blocked, captured week is still just 168 hours. The systems only stop you from losing them twice.

Sources

• Allen, D. What is GTD. https://gettingthingsdone.com/what-is-gtd/
• Newport, C. Deep Habits: The Importance of Planning Every Minute of Your Work Day. https://calnewport.com/deep-habits-the-importance-of-planning-every-minute-of-your-work-day/
• Newport, C. The Time-Block Planner. https://www.timeblockplanner.com/
• FranklinCovey. Habit 3: Put First Things First. https://www.franklincovey.com/courses/the-7-habits/habit-3/
• Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes. https://www.sciencedirect.com/science/article/abs/pii/S0749597809000399
• Mark, G., Gudith, D., Klocke, U. (2008). The Cost of Interrupted Work: More Speed and Stress. https://www.ics.uci.edu/~gmark/chi08-mark.pdf
• Wikipedia. Planning fallacy. https://en.wikipedia.org/wiki/Planning_fallacy
• Polynov, A. Life. Basics of time-measurement. https://medium.com/@alexpolynov/life-basics-of-time-measurement-ac3b4015fe61
• Trimoruk, V. Personal time. Lyubishchev’s system, Daniil Granin’s recommendations. Voprosy Literatury. https://www.voplit.com/jour/article/view/287?locale=en_US

The Russian-language predecessor of this article (2011) is preserved in the archive.