The getting things done method is a way to get open loops out of your head and into a system you will actually look at. Design Productive covers time management, business systems, and tools that earn their place. This article stays on that ground. It walks through the five steps published by Getting Things Done, then shows a five-person team how to run them for two weeks without buying a new app.

The official description is short on purpose. You collect what has your attention, process what it means, put reminders where they belong, review often, and do the work from that system. The Getting Things Done fundamentals page describes those five moves as collect, process, put it where it belongs, reflect, and simply do. The rest of this piece is how a small team builds that space with lists they already have. Source: Getting Things Done five steps.

Collect before you sort

First, pick one inbox. A notebook page, a single note in the tool you already pay for, or an email folder named Inbox is enough. The point of the first step is that every open loop lands in the same place. A loop is anything that would tug at you later: a client ask, a broken signup, a tax form, an idea for a sales page.

However, do not organize while you collect. If you stop to file each item, the capture stops and the rest stays in your head. Set a timer for twenty minutes. Write one line per loop. Stop when the timer ends, even if the list feels unfinished. You can collect again tomorrow. A system that demands a perfect brain-dump on day one gets abandoned on day two.

Also tell the team what the inbox is for. If four people keep private lists and one shared channel, nothing is trusted. Agree that new work enters the shared inbox before it enters a meeting. That is a business rule, not a personality trait.

Process one item into a next action

Next, empty the inbox by deciding, not by rearranging. Take the top line. Ask whether it needs a physical action. If it does not, it is trash, reference, or a someday item. Reference goes where you look things up, not on the action list. Someday goes on a list you do not see every morning.

If it does need action, write the next visible move. Handle the proposal is not a move. Email Priya the revised scope table is. If the outcome needs more than one move, name the project in a few words and park only the next move on the action list. The official process step is that split: next action, and a project when one action is not enough.

Then apply a two-minute test only as a relief valve. If the next move is truly short, do it now and cross it off. If you use that test as an excuse to live in the inbox, you never reach the list. Cap the processing block at thirty minutes. Unprocessed lines stay in the inbox until the next block. They are not failures. They are unprocessed.

Put reminders where you will see them

So the third step is placement. Actions that must happen on a date go on a calendar. Actions that can happen as soon as you have time go on a context list: at the desk, on a call, waiting for someone else. Waiting is its own list. If you mix waiting with doing, you will reread stalled items every morning and feel behind.

For example, a founder, an operator, and a specialist can share three lists and keep their own calendars. The shared lists are Projects, Next actions, and Waiting. The calendar stays personal because only that person knows which hour is already taken. Do not build twelve contexts. Calls, desk, and errands cover most small teams. Extra contexts become shelves you never open.

Because this site already talks about tool sprawl, resist a new platform for the test. A column in the task tool you have is a system. A fresh subscription is a project of its own. Link the project name to the working file so a missing deck is not a separate loop. The mapped page for this topic lives on Design Productive’s time-management note, beside the wider time management cluster.

Review on a set day, then do the work

The fourth step is a review, and it is the step teams skip. Once a week, one person reads Projects, Next actions, and Waiting out loud or in a shared note. Delete what is dead. Rewrite any next action that is still vague. Check the calendar for the coming week and pull dated work off the action list so it is not nagging you twice.

Keep that review to thirty minutes. If it becomes a status meeting, people will stop updating the lists. The review asks what the next action is, and whether it is written. It does not ask for a speech about priorities. Priorities show up when the list is short enough to choose from.

The fifth step is simply doing. When you sit down, look at the calendar first, then the desk list, then waiting only if you are following up. Choose one next action and finish it or move it forward with a new next action. Do not reopen the inbox until the capture block. Mixing capture and doing is how the getting things done method turns back into a pile.

A two-week trial

• Days 1 and 2: capture only, one inbox, twenty minutes.
• Days 3 to 5: process the inbox into next actions and projects.
• End of week 1: a thirty-minute review. Rewrite any next action that is still vague.
• Week 2: do work from the lists. Capture new loops into the inbox, not into chat.
• End of week 2: keep the lists or name the one step that failed. Do not add a tool until that step is clear.

What the getting things done method leaves out

Leave out scorekeeping. The lists are not a record of who looked busy. If the review becomes a ranking, people will write impressive next actions they do not intend to do. Leave out copied slogans. The method works when the next action is specific, not when the notebook looks tidy.

Also leave out claims you cannot check. This article does not say the method saves a set number of hours, and it does not say a course is required. The five steps are public on the fundamentals page linked above. Training exists if a team wants it later. A small team can test the steps with a notebook and three lists first.

Finally, leave the system smaller than your ambition. A handful of projects with clear next actions beats a long list with none. When a project has no next action, it is a wish. Put it on someday or delete it. That choice is the whole point of processing.

The sequence is the same next Monday as it is today. Collect into one inbox. Decide the next action. Park it on the calendar or a short list. Review once a week. Do the written action before you collect again. The getting things done method has done its job when the next action is obvious and the inbox is the only place new work lands.