How to find the right productivity system for you

The wrong place to start

Most people approach productivity systems the wrong way around. They read about a new method, feel the recognition of its central problem, get excited, and start building the system before they've properly diagnosed what they actually need help with.

A month later the system has quietly died and they're reading about the next one.

The issue isn't commitment or discipline. The issue is tool-problem mismatch. A carpenter using a plumber's tools isn't lazy, they're using the wrong equipment. Most failed productivity experiments are the same thing: the right problem, the wrong system.

So before looking at any specific method, it's worth spending a few minutes being honest about what's actually going wrong.

Diagnose before you prescribe

The productivity problems people commonly face fall into a few broad categories. They're different problems and they respond to different solutions.

You can't start things. Tasks sit on your list untouched. You know you need to do them. You feel vaguely guilty about not doing them. But when the time comes, you find something else to do. This is a starting problem, not an organisational one, and it tends to respond well to methods that create external structure and manufactured urgency.

Things fall through the cracks. Important tasks don't get done because you forget about them. Commitments made in meetings disappear before you act on them. Projects drift without clear next steps. This is a capture and memory problem. The solution is an external system that remembers things so you don't have to.

You don't know what to work on. You're busy, but at the end of the day it's not clear whether you worked on the right things. Everything feels vaguely urgent. Priorities are unclear and keep shifting. This is a prioritisation and planning problem. It responds to methods that force explicit ranking of what matters.

You're overwhelmed by information. You read and save more than you can process. Notes, articles, research, and ideas accumulate but don't connect into anything useful. The knowledge isn't being turned into output. This is a knowledge management problem, and it calls for a different kind of system entirely.

Most people have some mix of all four. But usually one of these dominates, and that's where to start.

Matching problem to system

Once you've identified your main problem, the landscape of available methods becomes much clearer.

For starting problems: time-based methods

If getting started is the main difficulty, you need a system that creates a concrete, immediate structure rather than an open-ended list.

Pomodoro Technique: Work in 25-minute timed blocks with scheduled breaks. The commitment is small (just this block), the urgency is real (the timer is running), and the format works specifically for tasks you've been avoiding. Particularly effective for batching unpleasant tasks or overcoming the activation energy barrier on creative work.

Time blocking: Schedule specific tasks into specific calendar slots. This turns abstract intentions into concrete appointments, making it harder to defer work because the time for it already exists. Also helps with the related problem of not knowing where the day went.

Ivy Lee Method: Six tasks, prioritised the night before, worked in strict order. The simplicity removes the daily question of what to do next, which is itself a source of procrastination for many people.

For memory and capture problems: externalisation systems

If things are falling through the cracks, you need a system that reliably holds your commitments externally so your brain can let go of them.

Getting Things Done: The most comprehensive framework for externalising commitments. Captures everything into an inbox, processes it into lists by context and next action, and maintains the system through weekly review. The most thorough approach to open loop management.

GTD Lite: The same core principles with most of the complexity stripped away. Inbox, tasks, scheduled items, someday list. Works well for people who need the capture and next-action discipline without the full GTD apparatus.

Bullet journal: A flexible paper-based system for capturing tasks, events, and notes across daily, monthly, and future logs. The migration process (reviewing and consciously carrying forward unfinished tasks) builds in regular reckoning with what's been neglected.

Task management basics: If you've never used a consistent task management system before, starting with the fundamentals is worth the time before adopting any specific methodology.

For prioritisation problems: focus frameworks

If you're busy but not sure you're working on the right things, you need a method that forces explicit prioritisation rather than just better organisation.

Ivy Lee Method: The six-task daily limit forces hard choices about what matters today. Works at the daily level.

MoSCoW Method: Sorts project requirements into Must Have, Should Have, Could Have, and Won't Have. Particularly useful for complex projects with multiple stakeholders, or for anyone who needs help being honest about what's truly essential versus merely desirable.

Eisenhower Matrix: Classifies tasks by urgency and importance, helping you identify where your time should actually go versus where it tends to end up.

For knowledge management problems: second brain systems

If your problem is that you consume a lot of information but it doesn't turn into useful output, you need a different category of system entirely. Most task management methods don't address this.

Building a Second Brain: Forte's CODE framework (Capture, Organise, Distil, Express) provides a full system for turning consumed information into reusable knowledge. The PARA structure keeps the most actionable material visible.

Zettelkasten: A note-taking method that organises by connection rather than topic or actionability. Well-suited for long-term knowledge development, research, and creative work where cross-domain connections matter.

PARA method: The organisational backbone of BASB, but useful as a standalone structure for anyone who wants a principled way to file digital information. Projects, Areas, Resources, Archives, organised by actionability.

Evergreen notes: A complementary practice of writing concept-based notes that are revised and refined over time rather than forgotten in a collection of dated journal entries.

How to try a new system

Once you've identified a likely candidate, give it a real trial. Two weeks minimum, four weeks for more complex systems. Here's what to look for:

Is it solving the actual problem? Not "does this feel productive," but "has the specific problem I identified improved?" If things were falling through the cracks, are they falling through the cracks less? If you were struggling to start tasks, are you starting them more reliably? The test is functional, not emotional.

Can you maintain it? A system you use at 70% is almost always better than a system you abandoned after two weeks of perfect use. The maintenance cost matters as much as the theoretical benefit. If keeping the system running is taking significant willpower or time, it'll fail at the first stressful week. Look for the system that requires the least maintenance to stay useful.

Does it integrate with your actual life? A system that requires completely different behaviour from what your work or environment supports won't last. The best system is one that makes small demands: check this list in the morning, capture into this inbox, spend five minutes in review before you close the laptop.

Common mistakes

Switching too quickly. Most systems take a few weeks before they feel natural. Switching after five days, before the habits have formed, means you never learn whether the system would have worked. Give each genuine attempt a fair run.

Solving the wrong problem. Starting a knowledge management system when your problem is procrastination, or adopting a complex capture system when you just need to prioritise better, produces effort without benefit. The diagnosis step is worth spending time on.

Building the system instead of using it. There's a well-documented tendency among people who struggle with productivity to spend their productive time configuring their productivity system. A perfectly maintained Notion database with zero output is not a productivity system, it's a form of procrastination with good branding.

Looking for the system. No single method solves everything. Most people who have a working system are using a combination: something for task management, something for information organisation, maybe something for time structure. The goal isn't to find the one true system but to solve each distinct problem with the right tool.

Chasing complexity. More thorough doesn't mean better. The Ivy Lee Method is six tasks and a rule about order. It has survived over a century because it works. The system that fits your life and gets used is always more valuable than the system that addresses everything theoretically but gets abandoned in the third week of January.

A rough starting point

If you're not sure where to begin:

Start with GTD Lite or the Ivy Lee Method if your primary problem is tasks being forgotten or not getting done. Both are simple enough to set up in an afternoon.

Add time blocking or Pomodoro if getting started and staying focused are also issues.

Once those foundations are stable, look at PARA or Building a Second Brain if information overload and knowledge management become the next bottleneck.

The order matters. Building a knowledge management system before you have a reliable way to complete tasks is optimising the wrong layer. Sort the doing first, then build the knowing.

Frequently asked questions

Do I need more than one productivity system?

Most people end up with some combination: a task management method, maybe a time structure method like Pomodoro or time blocking, and possibly a knowledge organisation system. These address different problems and don't generally conflict. What to avoid is multiple overlapping systems for the same problem, two task managers, two note-taking apps with no clear role distinction. That's friction without benefit.

How long should I try a system before switching?

At least two weeks, ideally four. Some systems (like GTD) take considerably longer to embed before they feel natural. The test isn't whether the system feels easy but whether the problem it's supposed to solve is actually improving.

What if no system seems to stick?

That's worth taking seriously as information. A system that won't stick despite genuine effort is often mismatched to your actual problem, requires more maintenance than your situation allows, or is solving a secondary issue rather than the primary one. Revisiting the diagnosis is usually more productive than trying yet another system.

Is there a productivity system that works well for ADHD?

Several of the principles that matter most for ADHD are common to many systems: externalising commitments, reducing decision overhead, making the next action concrete and visible. The main challenge with ADHD is that maintaining most systems requires executive function. Starting simple, building one habit at a time, and using tools that handle organisation automatically tend to work better than implementing any single method in full. See also: ADHD energy and the voltage curve.

Where do apps fit in? Should I choose a system or an app?

Choose a system first, then find an app that supports it. Most productivity apps are tool-agnostic enough to run any of the methods covered here. Choosing an app first and then adopting the method it's built around often works, but the risk is that you end up constrained by the app's design rather than selecting the method that actually fits your problem.

This guide covers methods with dedicated /learn guides: Pomodoro, Time blocking, Bullet journal, GTD, GTD Lite, PARA, Building a Second Brain, Ivy Lee Method, MoSCoW Method, Zettelkasten, Kanban, and Evergreen notes.