Frequently Asked Questions About Todoist Multi-Method Productivity Organiser
20 answers covering everything from basics to advanced usage.
// Basics
What does 'externalising everything' actually mean?
It means moving every task, commitment, and idea out of your head and into one trusted place, without filtering. The moment you keep something mentally 'just temporarily,' you reintroduce cognitive load. Externalising works only when it's complete and consistent — a partial capture still leaves your brain holding remaining items, which defeats the trust the system depends on.
What is the difference between list, calendar, and board views?
List view is a sequential, text-based display suited to GTD-style next-action processing. Calendar view maps tasks to time, ideal for deadline-driven or time-blocked work. Board view organises tasks into columns representing workflow stages, matching Kanban. The principle of view flexibility says no single view fits all work — you switch based on whether you need to sequence, schedule, or visualise flow.
What is the weekly review and why does it matter?
The weekly review is a scheduled cadence where you close completed tasks, re-prioritise, and check nothing is stale. It matters because a trusted external system degrades without it — items pile up and you lose confidence in the system. Once you stop trusting it, you revert to mental tracking, undoing the entire benefit of the framework.
// How To
How do I do a proper brain-dump?
Capture every task, project, idea, and commitment into your system without filtering, prioritising, or organising. The goal is completeness — nothing stays in your head. Don't stop to decide where things go or how important they are; that comes later during processing. A raw, unfiltered dump is the foundation of a trusted external system.
How do I process my inbox after capturing everything?
Give every captured item a home: assign it to the correct project, add a label, set a due date if relevant, and place it in a priority tier. Unprocessed inbox items defeat the purpose of the system because your brain keeps re-checking them. Aim to leave nothing sitting unclarified in the inbox.
How do I use templates for recurring work?
For meetings, team projects, or repeating workflows, apply a pre-built template instead of building from scratch. Templates enforce consistency and reduce setup friction — a meeting template can standardise agendas and automatically capture follow-up tasks. Use them whenever a project type recurs, so you never rebuild the same structure repeatedly.
How do I set up a Kanban board for my projects?
Use board view and define stages as columns — typically To Do, In Progress, and Done, though you can add stages like Review or Blocked. Pull tasks through the stages as work progresses. This makes bottlenecks and progress immediately visible, which is why Kanban suits visual workflows and team handoffs better than a linear list.
// Troubleshooting
My system keeps getting stale — what am I doing wrong?
You're almost certainly skipping the weekly review. Without a regular pruning cadence, completed tasks accumulate, priorities drift, and stale items make the whole system feel untrustworthy. Schedule a fixed weekly or bi-weekly review to close done tasks and re-prioritise. Restoring that habit is usually enough to rebuild trust in the system.
I keep some tasks in my head — is that a problem?
Yes, it's the most damaging pitfall. Keeping tasks in your head 'just temporarily' breaks the trusted external system and reintroduces overwhelm. Your brain can't distinguish 'temporary' from permanent, so it keeps holding and re-checking those items. Everything must go into the system, even things you think you'll definitely remember.
I chose a method but I'm not seeing benefits — why?
You're likely only partially following the method's rules. Choosing GTD but not working from context-based next-action lists, or Pomodoro without enforced breaks, produces none of the benefits. Partial adoption is a common failure. Commit fully to one method's specific rules before judging whether it works, and don't mix in another method's logic.
Why do I feel more scattered after setting up the system?
You may be over-engineering setup before capturing tasks, or using one view for all work types. A perfect empty system helps no one — capture first, organise second. Also check that you're matching views to methods: using list view for a Kanban workflow or board view for deadline-heavy work creates friction that feels like scatter.
// Comparisons
How does this framework compare to Getting Things Done alone?
GTD is one method inside this framework, not a replacement for it. GTD excels at complex multi-project knowledge work but doesn't address energy management or visual workflows. This framework adds Pomodoro for focus and fatigue, Kanban for visual handoffs, and view flexibility — so you apply the right method per context rather than forcing everything through GTD.
How does Kanban compare to a simple to-do list?
A to-do list shows tasks sequentially with no visibility into workflow stage or bottlenecks. Kanban moves tasks through defined columns like To Do, In Progress, and Done, making progress and blockers immediately visible. For solo linear work a list is fine, but for visual workflows or team handoffs Kanban surfaces where work is stuck in a way a flat list can't.
Is Pomodoro better than time-blocking on a calendar?
They solve different problems. Calendar time-blocking assigns tasks to specific slots, good for deadline-driven scheduling. Pomodoro structures the work itself into focused intervals with breaks, managing energy and preventing burnout. In this framework calendar view supports scheduled work, while Pomodoro is an execution method — you can time-block a session and run Pomodoro intervals inside it.
How is this different from just using more apps?
Adding apps usually fragments your capture across tools, which is the opposite of a trusted external system. The framework's first principle is that everything must live in one place. More apps mean more inboxes to check and more items falling through gaps. Consolidation into a single system, not tool proliferation, is what reduces overwhelm.
// Advanced
Can I blend GTD and Kanban once I understand both?
Yes, once each is understood individually. The rule is not to blend methods before you've adopted each one fully and separately, because premature mixing produces confusion rather than benefit. Experienced users often run GTD's next-action clarity inside Kanban columns. But avoid mixing execution styles within a single work session, which still destroys focus.
How do I coordinate this system with a team?
Use board view for shared Kanban workflows so handoffs are visible, and apply GTD's next-action principle so every item has a clear owner and concrete next step. Migrate action items out of email into the shared system immediately. Meeting templates standardise agendas and capture follow-up tasks with owners, keeping the whole team's work in one trusted place.
How do I run separate work and personal contexts without them colliding?
Separate them into distinct projects or buckets while keeping everything in the same trusted system. Adaptability to context means the system bends to your needs — you might use Kanban for work projects and simple lists for personal errands. Use labels or view filters to focus on one context at a time, and process both during the same weekly review.
What's the right way to migrate off email as a task manager?
Immediately move every action item out of email into your trusted external system, then apply GTD's next-action principle so each has a concrete next step and owner. Email is a communication channel, not a task list — leaving actions there means constantly re-reading threads. Use calendar view to align migrated tasks with deadlines and stop treating the inbox as a to-do list.
How detailed should my projects and labels be?
Detailed enough to give every task a clear home and next action, but not so detailed that setup blocks capture. Over-engineering structure before capturing tasks is a pitfall. Start with broad project buckets and refine during weekly reviews as patterns emerge. Labels should map to contexts or priorities you'll actually filter by, not theoretical categories you never use.