Productivity methods glossary

Every planning method, technique, and bit of jargon you run into, defined plainly — including which ones are supported by evidence and which are just popular.

Planning methods

Getting Things Done (GTD): A method created by David Allen built on capturing every commitment into a trusted system, clarifying what each one actually requires, and reviewing regularly. Its core claim is that the mind is for having ideas, not holding them. GTD is powerful and heavy: it needs inboxes, contexts, project lists, and a weekly review to work. Most people who abandon it do so because of that overhead, not because the ideas are wrong.
Daily planning: Deciding what you will do on a specific day rather than maintaining one open-ended list. It converts an unbounded backlog into a finite, achievable set of commitments — which is the difference between a plan and a wish list. Full guide →
Weekly planning: Setting the shape of a week in advance — what matters, what is fixed, and roughly where the work goes — before the week starts filling itself. It gives daily planning something to draw from. Full guide →
Day theming: Assigning each day of the week a dominant kind of work — meetings on Monday, deep work on Tuesday, admin on Friday. It reduces the cost of switching between different modes of thinking.
Task batching: Grouping similar small tasks and doing them in one block rather than scattered through the day. The benefit comes from paying the mental setup cost once instead of repeatedly.
The two-minute rule: A GTD principle: if a task will take less than two minutes, do it immediately rather than recording it. Capturing, tracking, and revisiting a trivial task usually costs more than the task itself.

Prioritising

Eisenhower matrix also: urgent-important matrix: A four-box grid sorting tasks by urgency and importance: do the urgent-and-important, schedule the important-but-not-urgent, delegate the urgent-but-not-important, and drop the rest. Its real value is the second box. Important work that is never urgent is exactly the work that gets perpetually postponed. Full guide →
Most important task (MIT): The one task that would make the day a success if it were the only thing completed. Naming it before the day starts protects it from being crowded out by whatever arrives first. Full guide →
Eat the frog: Doing your hardest or most-avoided task first, popularised by Brian Tracy from a line attributed to Mark Twain. The reasoning is that willpower and attention are usually highest early, and an avoided task grows heavier the longer it waits. Full guide →
Ivy Lee method: At the end of each day, write down the six most important things for tomorrow in priority order, then work them strictly in sequence. Its constraint is the point: six items, one at a time, no reordering mid-day. Full guide →
ABC prioritisation: Labelling tasks A (must do), B (should do), or C (nice to do), then working strictly down the letters. Simple and durable, though it tends to accumulate an unexamined pile of Cs.

Time techniques

Time blocking: Assigning specific tasks to specific slots on a calendar instead of keeping an unscheduled list. It forces you to confront how much time you actually have, which a list never does. Full guide →
Timeboxing: Fixing in advance how long you will spend on a task and stopping when the time is up, regardless of completion. Time blocking asks *when* you will work; timeboxing caps *how long*. Full guide →
Pomodoro Technique: Working in focused intervals — classically 25 minutes — separated by short breaks, with a longer break after four. Created by Francesco Cirillo and named after a tomato-shaped kitchen timer. The interval length matters less than the two mechanisms underneath it: a defined start, and a break you actually take.
Deep work: Cal Newport’s term for cognitively demanding work performed without distraction. The claim is that such work produces disproportionate value and that the ability to sustain it is becoming rarer.
Context switching: Moving attention between unrelated tasks. Each switch carries a resumption cost — the time to rebuild the mental state the previous task required — which is why fragmented days feel unproductive despite being busy.

Journaling systems

Bullet journal also: BuJo: A analog planning system created by Ryder Carroll using short, symbol-marked entries in a notebook. Tasks, events, and notes each get their own symbol, so a page can be scanned rather than read. Full guide →
Rapid logging: The bullet journal’s core writing technique: capturing entries as short bulleted fragments rather than sentences, each marked by type. It keeps capture fast enough that you actually do it.
Migration: The bullet journal practice of periodically rewriting unfinished tasks onto a new page or month. The friction is deliberate — anything not worth copying out by hand probably was not worth doing.
Daily log: A single day’s page, holding what was planned, what happened, and what was noted. Because it is bounded by the day, it never becomes an open-ended backlog. Full guide →
Habit tracker: A grid marking whether a behaviour happened each day, usually inside a planner. It works mainly through visible streaks and the mild reluctance to break one.

Why plans fail

Planning fallacy: The well-documented tendency to underestimate how long a task will take, even when you have done it before and know it ran long. Identified by Kahneman and Tversky, and the main reason daily plans are over-full. The practical countermeasure is to plan from how long similar tasks actually took, not from how long this one feels like it should take. Full guide →
Parkinson’s law: The observation that work expands to fill the time available for its completion. It is the argument for timeboxing: a task with no end time tends to acquire one only when something else forces it.
Zeigarnik effect: The finding that unfinished tasks stay in mind more insistently than completed ones. It explains why an unresolved list is mentally noisy, and why writing tasks down externally tends to quiet them.
Task bankruptcy also: list bankruptcy: Deliberately abandoning an overgrown backlog and starting fresh, on the grounds that a list too large to face is not being used anyway. A blunt instrument, but often more honest than pretending the backlog will be worked through.
Overdue pile also: backlog guilt: The accumulating stack of past-due tasks that builds up when a plan meets a real week. Left untouched it reads as a standing reminder of failure, and is a common reason people abandon a system that was otherwise working. The fix is not to hide overdue tasks but to make moving them cheap. Paper systems do this by hand through migration; good digital planners do it by letting you re-date a batch in one pass rather than one task at a time. Full guide →
Rescheduling also: re-dating, pushing tasks: Moving an unfinished task to a new day rather than leaving it sitting past due. Treated as routine maintenance instead of an admission of failure, it is what keeps a day-based plan honest as the week changes. The cost of rescheduling determines whether people actually do it. If it takes a few taps per task, the backlog wins; if a whole day can be swept forward at once, the plan stays current.