How To Get Things Done

The problem with productivity systems

I spent about six years trying every method available. GTD, time blocking, Kanban, bullet journaling, the Pomodoro technique, zero-based scheduling, the Ivy Lee method, the two-minute rule, the Eisenhower matrix. Most of it was noise. The stuff that actually moved the needle was much simpler than the gurus would have you believe. The core issue is that people confuse planning with doing. You can spend three hours setting up a beautifully color-coded Notion dashboard and accomplish exactly nothing. I learned this the hard way after I committed roughly forty hours in a single month to building what I thought was an optimal task management system. My actual output during that period was minimal. The system looked great. Nothing got done.

How To Get Things Done

Here is the actual mechanism, stripped of the branding and the productivity influencer aesthetic. It has three components, none of them particularly exciting. First, you need a capture system. This is something external to your brain where every open loop, idea, obligation, and half-formed thought gets dumped immediately. It can be a notebook, a notes app, a voice memo, whatever. The medium does not matter nearly as much as the consistency. The rule is simple: when something enters your awareness, it leaves your head and goes into the system. No exceptions. I used to try to remember things, and I would reliably forget about four or five important items every single week. Once I started dumping everything into a single inbox app within seconds of thinking it, the forgetting stopped entirely. Second, you need a processing routine. This is where most people fail. Processing means going through your capture system and deciding what each item actually is. Is it actionable? If no, trash it or file it as reference. If yes, what is the very next physical action required? Most tasks are not tasks at all. They are projects, which means they need to be broken down until you hit an actual action you can perform. "Plan the marketing campaign" is not an action. "Draft the email to Sarah requesting the Q3 metrics" is an action. You should not put "plan the marketing campaign" in your to-do list. It will sit there and make you feel guilty.

Third, you need a review cycle. This is the part nobody wants to do but absolutely must. Once a week, preferably on the same day, you go through everything. You check your project list. You ask yourself which projects still matter. You update action items. You delete things that are no longer relevant. A typical review takes about forty-five minutes for someone with a moderate workload. People who skip this step accumulate months of stale tasks and have no idea what they actually need to focus on. I have seen it happen repeatedly, including to myself before I started taking this seriously. The common misconception is that this method requires enormous discipline. It does not. It requires one disciplined habit and then essentially zero discipline for the rest. The habit is reviewing your system weekly. Everything else is just following what you already wrote down. Your brain is not a storage device. Using it as one is why you feel overwhelmed even when your calendar looks relatively empty.

Where the method breaks down

Let me be clear about the limitations because most guides on this topic will not mention them. This system assumes you have control over your own schedule to some degree. If you are in a role where your tasks are entirely dictated by other people without any buffer, this method becomes significantly harder to use effectively. I worked a job like that for about eight months and found that the weekly review became more of an exercise in documenting other people's demands rather than organizing my own priorities. It still helped, but the benefit was reduced. Another failure mode is when your tasks are purely cognitive rather than physical. GTD was designed around physical actions. Writing a novel, solving a complex algorithm, designing a system architecture — these are not actions you can check off after ten minutes. They are deep work blocks that require sustained attention. The method handles them poorly unless you explicitly convert them into time-bound calendar blocks rather than to-do items. I made this mistake early on and ended up with a list of ten "write documentation" items that would never complete because I never actually scheduled the three-hour uninterrupted block I needed to do it. The workaround was putting those items on my calendar first and letting the calendar drive the task list instead of the other way around. There is also a real risk of optimization addiction. You can spend weeks tweaking your capture tools, your categorization scheme, your review questions. This is not productivity. It is procrastination dressed up as preparation. I have a friend who switched task managers three times in six months because each one promised better project visualization. He completed fewer personal projects during that period than in any comparable six-month span prior. The tool change felt like progress. It was not.

What actually works in practice

Keep the capture system single and everywhere you are. One inbox. If you have three different places where tasks can land, you will lose track of at least one of them. I used to have tasks in my phone notes, in an email folder I labeled "Action," and in a paper notebook on my desk. I would forget about the paper one consistently. Once I consolidated everything into a single mobile app, I stopped losing items. Simple as that. Process daily, not just weekly. The weekly review catches what you missed, but daily processing prevents the inbox from becoming a disaster zone. Ten minutes each morning to clear your capture system is far less painful than ninety minutes on a Sunday night trying to untangle two weeks of accumulated clutter. Most days your processing will take about two minutes because nothing new has accumulated. That is fine. Show up and clear it. Write next actions with enough specificity that you can start them without thinking. "Call vendor" is useless because your brain will resist it. You will delay starting because you are not sure what calling entails. "Call vendor about late shipment and get tracking number" takes three minutes to read and fifteen to execute. The specificity removes the friction of deciding what to do next. This is probably the single highest-leverage detail in the entire system. I started applying this rigorously and noticed my task completion rate increase noticeably within a couple of weeks, mostly because I stopped avoiding items that felt vaguely defined.

Do not estimate time accurately. Just start. Most people spend too long trying to figure out whether a task will take twenty minutes or an hour before they begin. Start it. If it takes longer than expected, you will learn. If it takes less, you gain time. The estimated accuracy of your predictions has minimal impact on your actual output compared to simply starting the work. The system only works if you trust it. If you keep tasks in your head because you think you will remember them, the system collapses. I used to do this with small items under five minutes, convincing myself they were not worth writing down. They accumulated to roughly two hours of lost productivity per week because I would forget them and then feel guilty about forgetting them, which made me avoid looking at my system entirely. Once I committed to writing everything down regardless of size, the guilt disappeared and my focus improved. You do not need a premium app. You do not need a special notebook. You need one place to capture, one process for deciding what to do, one weekly review, and the discipline to actually follow through on the actions you have identified. Everything else is decoration.