Context-Based Action Lists

Context-Based Action Lists are a way to organize next actions by the circumstances required to do them: where a person must be, what tool is needed, or whom they must contact. Their decisive purpose is practical rather than merely classificatory: when a usable opportunity arises, a person can see the actions that fit it without repeatedly sorting through everything else, while the act of categorizing also helps turn an open-ended commitment into a specific physical step.

Why Context Matters

In knowledge work, projects often have no clear edges. A conference, training program, compensation structure, or essay might always be improved with more information, and the Web can supply a seemingly endless quantity of relevant data. At the same time, work increasingly crosses departmental boundaries, bringing more messages and requests into view. Roles and responsibilities also shift as organizations change their goals, products, partners, markets, technologies, and ownership, while professionals move through careers rather than remaining within one stable job description. The resulting volume of internal and external commitments is difficult to manage through memory alone.

A system for this environment has to work at both scales: it must preserve the outcomes of big-picture thinking and keep small, open details available for action. Context-based organization addresses the moment when a person moves from knowing that something should be done to deciding what can actually be done here and now. The question is not simply what matters in general, but which action is possible with the present location, tools, and access to other people.

How the Lists Work

A computer-dependent action belongs on an At Computer list. A task that requires driving around, such as stopping at a bank or hardware store, belongs under Errands. If the next step is a face-to-face discussion with a partner, it can go on an Emily list or in an Emily folder. Other useful headings might include Calls, At Home, or an agenda for a particular person or meeting. These labels make each reminder retrievable at the moment its required context becomes available.

The appropriate level of detail depends on how many actions need tracking and how often the person moves between contexts. Someone with only twenty-five next actions might manage them on a single Next Actions list, mixing items such as buying nails, talking to a boss about staff changes, and drafting ideas for an off-site meeting. With fifty or a hundred pending actions, however, one large list forces repeated resorting. On a short break at a conference, someone looking to make calls would have to sift through unrelated tasks; when going out to handle errands, they would have to isolate those items again. Separate context lists reduce that search at the point of decision.

They also support sustained activity within a particular mode. During phone time, a person can work through the Calls list; when already working at a computer, the relevant digital tasks are at hand. Switching tools and behaviors takes energy, and context lists make it easier to use the current rhythm rather than interrupt it to reconstruct what might be done. If a key person is sitting in the office, an agenda list can bring the relevant discussion points together while that access lasts.

From Reminder to Physical Action

Context is the first practical filter for choosing what to do. A person in traffic may be able to make calls but not perform tasks requiring a computer or a store visit; pulling out only the Calls list makes the available choices visible. Lists can therefore fold in or out with changing circumstances. They prevent the repeated reconsideration caused by a single inventory containing many actions that are not possible in the same setting.

This organization also imposes a useful discipline during processing. To decide whether an item belongs on a computer, phone, or errands list, the person must identify the physical action it requires. A miscellaneous list that has no context can make it easier to avoid that decision. The book consequently recommends establishing list categories while processing the in-basket: doing so grounds projects in the actual steps that can move them forward.

The same principle appears in a simple preparation trick. Someone who must bring home work back the next morning can put it in front of the door, or place it on their keys, so the object itself prompts action before they leave. The reminder is designed for the likely circumstances of the next morning, when the person may barely be conscious. The method called Put It in Front of the Door applies that logic to the mind as well as the house: make a relevant prompt available where and when it can trigger the intended action.

A review of the next fourteen days on the calendar may produce an “Oh-that-reminds-me-I-need-to____” thought. Capturing that thought somewhere that will prompt action can clear attention and help useful work happen. The calendar, however, has a distinct role: it should show the hard landscape of fixed commitments, not tentative actions a person hopes to complete on a chosen day. As-soon-as-possible actions belong in context-organized reminders, where they remain available without falsely appearing to be appointments.

Choosing What Is Possible

Context is one of four criteria for choosing an action in the moment, alongside available time, available energy, and priority. It comes first because it establishes what is physically possible: whether the required tool is present, the needed person is accessible, or the person is already at the place where an action can be completed. If those conditions are absent, there is no need to keep treating the action as an immediate option.

Context lists connect the reminder to the conditions of performance, but they do not claim that every listed action can or should be done at once. They narrow the field to feasible choices; time and energy further shape that field, and priority helps determine what deserves attention among the remaining options. Organizing by context thus reduces needless review without replacing judgment about what matters.

Organizational Use and Limits

The method answers a broader problem of coordination. Requests may arrive through voicemail, email, conversation, or written notes, and people need to trust that each will enter the recipient’s system, be processed and organized, and remain available for review as an action. If someone tracks only one medium, colleagues are forced to use that medium, making the organization’s communication process more fragile. A dependable system therefore requires more than an individual’s well-arranged lists: incoming commitments must reach a trusted process and remain visible to the people responsible for them.

No personal system can make one person do everything. Organizations need to make it acceptable for people to have more work than they can complete and to renegotiate agreements about what will not be done. That renegotiation depends on tracking commitments: an agreement that has been forgotten cannot be revisited, and a commitment lost from view cannot be discussed with the people involved. Complete collection and context-based action reminders support that ongoing process by preserving what has arrived and showing what can be acted on in the conditions at hand. The result is not a guarantee that a group is pursuing the right goal; it is a way to direct its available effort with less waste and fewer lost commitments.