How to Process Commute Ideas When You Get Back to Your Desk
When an idea arrives during a commute, capture just enough to recognize it later; when you reach your desk, decide whether it becomes an action, a project, reference material, a later idea, or something to discard. This short return-to-desk routine keeps a useful thought from getting buried in a notes app or mistaken for a task that needs doing.
Capture a reminder, not a polished note
If you are walking, driving, or managing bags and tickets, wait until it is safe to enter a note. Use one quick capture method you can find again, such as a voice memo, a notes app, or a pocket notebook. The method matters less than knowing where the note will land. The [Getting Things Done overview](https://gettingthingsdone.com/what-is-gtd/) describes capture as collecting what has your attention, then clarifying and organizing it later. That is a useful distinction for commute ideas: the ride is for saving the thought, not building a complete plan.
Include a few retrieval cues so the note makes sense after the ride. A compact format is:
**Idea:** the thought in one sentence.
**Why now:** the prompt, problem, or conversation that sparked it.
**Possible next step:** an action only if one is already obvious.
For example: “Try a one-page guide for choosing a weekend walk; friends ask how to pick a route; compare three nearby options.” This records the idea and its context without assuming it deserves a full project. If you can only capture a phrase, do that; add context as soon as practical.
At your desk, clarify each note before sorting it
Open the one place where commute captures collect. Process each note from the top, one at a time, and ask: **What is this, and does it call for an action?** Avoid copying it into several systems before you know what it means; duplicates make it harder to tell which version is current.
The official GTD workflow separates capturing from clarifying and organizing. Clarifying means deciding whether something is actionable and, if so, identifying a next action or a project; non-actionable items can be discarded, kept as reference, or put on hold. Apply that decision to an idea in this order:
1. **Is it still useful?** If the spark has passed and you do not want to keep the thought, delete it. Capturing an idea does not obligate you to pursue it.
2. **Is there a concrete next action?** If it can be handled in one sitting, rewrite the note as a visible verb-led action: “Sketch three headings for the walking guide.” Keep it in the task list or project where you will look for that kind of work.
3. **Does it need several actions?** If the result requires multiple steps, name the outcome as a project, then add just the next physical action. For example, “Create a route-picking guide” might start with “List the criteria readers need to compare.” The idea becomes workable without pretending you have already planned every step.
4. **Is it worth keeping but not acting on now?** Save it as reference or place it in a clearly named “Later ideas” list with a review date or review trigger. Avoid giving it a false due date simply to make it visible.
Todoist’s [Inbox guidance](https://www.todoist.com/help/todoist/get-started/use-the-inbox-in-todoist-HwHvYErS) offers one concrete example of this pattern: collect tasks in an Inbox, then process them by moving them to relevant projects, assigning dates where useful, or deleting what is unnecessary. You do not need Todoist to use the logic; a notebook or another task system can serve the same role.
Decide whether to act on the idea today
Sorting an idea does not mean it must interrupt your desk work immediately. Before switching tasks, check what you have available: the right context or tools, enough time for a meaningful step, and the attention to do it. The GTD article [“Choosing what to do”](https://gettingthingsdone.com/2023/01/choosing-what-to-do/) names context, time available, resources, and priorities as criteria for choosing an action.
A practical decision sequence is:
**If it is time-sensitive or important to the work already in front of you**, schedule or begin the next action, depending on your commitments and available time.
**If it is worthwhile but not current**, place it in the appropriate project or idea list and set a realistic review point.
**If you cannot tell what the note means**, add a question or context cue, then review it once more while the commute that sparked it is still easy to recall.
**If it no longer matters**, delete it and continue.
For example, suppose the commute note says, “People want easier ways to choose a walk.” At the desk, you decide the thought is worth exploring but not an urgent task. You turn it into a project called “Draft a simple route comparison guide,” add the next action “Write down five route-selection questions,” and leave it for your next planning session. If it is a passing thought rather than a goal, keep it in a low-priority idea list—or let it go. The example illustrates the decision process; it is not evidence that this particular guide will be useful to a particular audience.
Keep the return-to-desk routine small
A commute capture system can fail in two opposite ways: a note is too vague to reconstruct, or processing it becomes a second project. Use a short pass rather than trying to perfect every thought. Preserve the original phrasing when it contains an important image or turn of phrase, and add a plain-language action separately if needed. If the capture device has not synced or the voice memo is difficult to search, transfer the note manually and confirm it is readable before deleting the original.
A simple repeatable routine is:
1. Open the single inbox or notebook where commute ideas go.
2. Read each item and restore missing context.
3. Choose: delete, reference, later idea, single action, or multi-step project.
4. Put any chosen action where you normally review work; add a date only when it reflects a genuine commitment or useful reminder.
5. Start the action only if it fits the work you can reasonably do now.
If your ideas arrive while you are walking or driving, keep capture secondary to safe travel: dictate or type only when stopped or when it is safe and permitted to do so. If the note is important but you cannot capture it safely, repeat a short keyword to yourself until you can stop and record it. The aim is to get back to the desk with the thought recoverable, then make a deliberate choice about whether it deserves attention.
A useful test for whether the system is working
After a week, review the commute-capture inbox. If many notes are unclear, add one context cue during capture. If the inbox grows without decisions, reserve a few minutes for processing when you first sit down or during a regular planning review. If most ideas are discarded, that is not necessarily a problem: capture gave you a chance to assess them rather than forcing you to remember them or act on every passing thought.
The useful endpoint is a note that has a clear home and a clear status. Once an idea is an action, project, reference, later possibility, or a conscious discard, you can return to your desk work without carrying the whole thought in your head.