Protect attention for your most critical action

Start with one outcome, not your entire inbox

Choose one result whose movement would matter this week. It could be a customer decision, a completed analysis, an important conversation, or a personal obligation. Write the outcome in observable language: 'Send the customer a proposal they can approve by Friday' is clearer than 'be on top of sales.' In Critical Path, create or open the relevant outcome and inspect the actions that genuinely influence it. You do not have to link every household errand or administrative task to a strategic objective.

Ask which action would create the next piece of evidence. For a proposal, that might be 'Draft the two pricing options and confirm margin with finance.' It is smaller than the outcome and executable without first inventing a complete project plan. If three actions seem equally urgent, choose the one that resolves the largest uncertainty or unblocks someone else. This is how attention follows consequence rather than whichever notification arrived last.

Capture the thought that deserves to survive

When an actionable thought appears during other work, open Today and use the capture bar or press N. Give it a short, verb-led title in Critical Path. 'Ask legal which clause blocks approval' is more useful than 'legal.' Add the genuine due date if one exists; do not invent today's deadline just to make the item visible. Give it an owner. Add enough context to make the next move obvious when you return, but avoid copying an entire private conversation into a task description.

Then go back to what you were doing. This is the critical handoff: the capture is valuable because it creates a credible return path, not because a larger list is inherently productive. The experimental evidence concerns specific plans for unfinished goals. A vague note without a next action may still require repeated interpretation later. If a thought requires no action, let it pass rather than creating an obligation to manage it.

Sources: Masicampo and Baumeister, Consider It Done! (2011)

Decide urgency, importance, and effort separately

Open Matrix to distinguish consequence from time pressure. A critical proposal with a Friday decision may belong in Do now. An important but later strategy review belongs in Schedule. A follow-up another person owns belongs in Delegate with a clear check-in. A request that no longer supports a live outcome can be deprioritized or cancelled. The point is to make a choice, not to color-code everything you have ever thought about.

Estimate the action's effort and compare it with your available weekly capacity. If the calendar already consumes the week, adding an important action without displacing something else is wishful planning. Break large work into an initial block with a defined output. A 45-minute block to produce a rough option table is easier to protect and review than a four-hour promise to 'finish strategy.' The estimate is a planning assumption; revise it after doing the work.

Give the work a credible return appointment

An item in a list is not yet a plan. Decide when you will reconsider or execute it. Allocate effort in Critical Path, then use Calendar to protect a block if your calendar is connected and the event is actually created. A due date, an effort allocation, and a provider calendar event are three different states; check the event receipt before assuming the time is held. If your calendar is disconnected, use the product's planning view and reserve the time manually in the calendar you trust.

Make the block specific enough to begin. Put the document or decision question in the action. Leave a buffer between meetings if the work requires a context shift. If an interruption forces a move, reschedule deliberately and record what displaced it. A credible return appointment reduces the need to keep asking yourself whether you will ever get back to the work. It does not guarantee that the work will be easy when you do.

Sources: Leroy, Why Is It So Hard to Do My Work? (2009) · Masicampo and Baumeister, Consider It Done! (2011)

Use reminders to retrieve, not to pester

For a commitment that can be forgotten, choose a useful reminder near the moment of action or review. Check which notification channels are actually connected and authorized in your workspace. Email and connected Slack can be useful for selected follow-ups. A WhatsApp or push option should be treated according to its current in-product connection and delivery status, not assumed to work because it appears in a list. Test a channel before relying on it for an important deadline.

Turn off or defer unrelated alerts during a protected block. In a weeklong crossover study, people reported more inattention when phone notifications were more frequent. External reminders have improved prospective memory in experiments, but another study found they did not eliminate intrusive thoughts. One reminder with a concrete next action often serves you better than repeated alarms without a decision.

Sources: Kushlev et al., Silence Your Phones (2016) · Gilbert, Strategic Use of Reminders (2015) · Dupre et al., The Role of Offloading Intentions on Future-Oriented Thinking (2024)

Run one focused block, then close the loop

At the start of the block, open the chosen action, define the output for this session, and put away inputs that are not needed. If another commitment comes to mind, capture it briefly and return. If the action is blocked, name the blocker and the person or event that can move it. If the estimate was wrong, adjust the remaining effort rather than pretending the original plan still fits. Focus is an allocation decision you can repeat, not a personality test.

At the end, record the truthful state. Mark it done when the output exists; delegate it when another owner has accepted it; reschedule it with a reason and new window when it still matters; or cancel it when its outcome is no longer worth the cost. This last step prevents a stale queue from becoming an unreliable memory aid. Before resting, identify tomorrow's one most consequential next action. Leave the rest in the system rather than rehearsing the entire queue.

1. Open one action and state the output you can produce in this block.
2. Silence unrelated alerts and keep only the material you need.
3. Capture any new actionable thought in one line, then return to the chosen action.
4. At the block's end, record done, blocked, delegated, rescheduled, or cancelled truthfully.
5. Review whether the chosen action actually moved the outcome and adjust the next block.

Sources: Rubinstein, Meyer and Evans, Executive Control of Cognitive Processes in Task Switching (2001)

Try the practice for seven days

Day one is for naming a single outcome and the next two or three actions. Days two through six are for protecting one feasible block each day and reviewing the action state afterward. On day seven, inspect the evidence: what moved, what remained blocked, how often you moved a block, and whether reminders were helpful or noisy. Keep the practice if it improves your decisions and presence; reduce its complexity if maintaining the system becomes another source of distraction.

Do not use a successful week as proof that you can sustain full concentration indefinitely. Sleep, breaks, and limits on simultaneous commitments protect the attention you are trying to direct. If you lead a team, use the same practice to make ownership and capacity clearer, not to monitor every minute of another person's day. The result to seek is a smaller number of better completed commitments and more honest attention for the people and work in front of you.

Sources: Sleep restriction and cognitive performance meta-analysis (2017)

Common questions