Wednesday, October 28, 2026← Weras Labs main siteTürkçe
WerasBlog

What's happening in AI, software, technology and science; plain and sourced.

Subscribe
Guides

What Is the GTD Method? Applying Getting Things Done Step by Step

The five steps of David Allen's Getting Things Done method, the lists you need, the two-minute rule and a weekly review template that keeps the system alive.

What Is the GTD Method? Applying Getting Things Done Step by Step
Image: Jakub Żerdzicki · Unsplash · Unsplash License

The GTD method (Getting Things Done) is a way of organizing work in which you move every task and commitment out of your head into a trusted external system and turn each one into a concrete next step. Made famous by David Allen's 2001 book, the method has five steps: capture, clarify, organize, reflect and engage. The core idea is simple: your mind is good at having ideas, but it's a poor place to store them. Once your tasks live in a system you trust, your mind is free to focus on whatever you're doing right now.

What problem does GTD solve?

For most people, the to-do list is scattered: half of it in their head, half across different apps, some of it in email and some in meeting notes. That scatter causes two problems:

  • Constant background tension. The feeling that you've forgotten something keeps part of your mind permanently busy.
  • Vague tasks. Items like "Website" or "Budget" sit on a list without a clear action and get postponed, because you have to think about them first.

GTD solves these two problems with "capture everything" and "clarify everything," respectively.

The five steps

1. Capture

Write down everything that has your attention (tasks, ideas, promises, reminders) in one inbox or a small number of them. An inbox can be a notebook, a note on your phone or the inbox of your task app. What matters is that there are only a few of them and you can reach them easily from anywhere.

Start with a "mind sweep" session: set aside half an hour and list every open loop that comes to mind. Work, home, personal projects, things you've promised, things you want to do.

2. Clarify

For each item in your inbox, ask these questions:

  • Is it actionable? If not, throw it away, add it to a "someday/maybe" list or file it as reference material.
  • If so, what's the next physical action? Not "Budget," but "Ask accounting for last year's budget file."
  • Will it take less than two minutes? Then do it right now. This is GTD's best-known rule.
  • Should someone else do it? Delegate it and add it to your "Waiting for" list.
  • If it'll take longer: If it has a specific date, put it on your calendar; otherwise add it to your next actions list.

In GTD, any outcome that takes more than one step is a "project." Write the outcome on your projects list and the first step on your next actions list.

3. Organize

Clarified items go onto these lists:

ListContents
ProjectsEvery outcome that requires more than one step
Next actionsConcrete steps you can do right away, grouped by context
Waiting forWork you've delegated and are tracking
CalendarOnly things tied to a specific day or time
Someday/maybeIdeas and wishes you aren't committing to right now
ReferenceInformation that needs no action but should be kept

Grouping next actions by context is GTD's signature feature: "@Computer," "@Phone," "@Office," "@Errands" and so on. If you have five phone calls to make, you can knock them out one after another in a fifteen-minute gap.

The calendar rule matters: only things tied to that day or time go on the calendar. "Would be nice to do this week" tasks clutter the calendar and make it less reliable.

4. Reflect

This is the step that keeps the system alive. Every day you look at your calendar and next actions list; every week you review the whole system. Without a weekly review, lists go stale, trust erodes and tasks migrate back into your head.

5. Engage

When deciding what to do, GTD suggests four criteria: your current context, the time available, your energy level and priority. You'll pick different tasks in the twenty minutes before a meeting, on a low-energy afternoon, or at a moment when all you have is your phone.

Weekly review template

Once a week, say on Friday afternoon, set aside an hour:

  • Get every inbox to zero: notebook, email, notes app, papers on your desk.
  • Look back at last week's calendar and capture anything left over.
  • Look ahead at the next two weeks' calendar and add anything that needs preparation.
  • Review your projects list: does every project have at least one next action?
  • Clear completed or obsolete items from your next actions list.
  • Check your waiting-for list and send reminders where follow-up is needed.
  • Skim your someday/maybe list: anything you want to make active?

Example: one item's journey through GTD

In a meeting, your manager says, "Let's look at new CRM options," and you jot it down.

  1. Capture: The note goes into your inbox.
  2. Clarify: It's actionable and takes more than one step, so it's a project. Outcome: "CRM options compared and a recommendation made to my manager."
  3. Next action: "Ask the sales team for their three biggest problems with the current CRM." That's an email, so the context is @Computer.
  4. Organize: The project goes on the projects list; the email goes on next actions; once sent, the team's expected reply goes on the waiting-for list.
  5. Reflect: If no reply has come in by Friday, you follow up.

This process turns a vague "I need to look into the CRM" reminder into a project whose progress you can track.

Common mistakes when applying GTD

  • Writing vague next actions. "Deal with the report" isn't an action. An action should start with a verb and be physically doable: "Write the introduction of the report draft."
  • Turning the calendar into a wish list. Only day-specific items belong on the calendar; otherwise it gets hard to make decisions by looking at it.
  • Multiplying inboxes. Keeping notes in five different apps weakens the capture step. Two or three collection points are enough.
  • Setting up the system and then skipping the review. This is the most common mistake. Treat the weekly review like a meeting that has its own block on your calendar and never gets postponed.

Which tool should you use for GTD?

GTD is tool-agnostic; a notebook works as well as a digital task app. What matters is that the tool allows quick capture, supports lists and contexts, and is accessible from every device. For help choosing a task management tool, check out the to-do list guide on our blog. If your team needs a work tracking tool shaped around its own processes, take a look at our custom internal tool development service.

Conclusion

The GTD method is a way to get tasks out of your head into a trusted system and turn each one into a concrete next step. Start with a mind sweep, clarify every item and never skip the weekly review. The system only works as long as you trust it.

#gtd#task management#productivity#work organization

From Weras Labs

We can help you with this

We turn what you just read into working software for your business. You talk to the person writing the code; price and timeline are clear from day one.

Frequently asked questions

What is GTD's two-minute rule?

If you see during clarifying that a task will take less than two minutes, you do it immediately instead of adding it to a list. Tracking tiny tasks like that takes longer than just doing them.

What does "project" mean in GTD?

In GTD, any outcome that requires more than one step is a project, regardless of size. "Buy a new computer" and "redesign the website" are both projects, and each should have at least one next action.

Which app should I use for GTD?

GTD isn't tied to a specific app. Any task tool that allows quick capture, supports lists and context tags and works across all your devices will do, and so will a well-kept notebook.

How long does the weekly review take?

Usually around an hour, depending on the size of your system. It gets shorter when done regularly; when skipped, lists go stale and your trust in the system drops.

About the author

Habip Dayan

Habip Dayan

Founder of Weras Labs

Habip Dayan is the founder of Weras Labs, a company that builds software products for professionals and teams. He has been building software since 2018 and writes about AI, cloud architecture and product design.

Comments

Be respectful; no ads or personal data. Comments that break the rules are removed.