01 Map your current commitments
Before adding a project, list what already claims your time. Include care, travel, administration, and recovery as well as visible work. Separate an active promise from an interesting possibility so your schedule reflects actual responsibility.
02 Choose a priority for this season
A priority gives you a reason to choose among competing tasks. Connect it to a result you care about and a realistic time window. Let the choice guide what gets your limited discretionary attention.
03 Define the result you can deliver
Translate a broad goal into something another person could inspect. Define its audience, purpose, and necessary qualities. A result gives direction to the tasks you choose next.
04 Decide what is outside the project
Scope makes a project small enough to finish. State what belongs in the current version and which attractive additions can wait. A clear exclusion helps you notice when a task no longer serves the agreed result.
05 Separate deadlines from preferences
Dates have different meanings. Identify externally required deadlines, personal target dates, and dependencies that must happen first. This helps you respond when a week changes without treating every date as equally fixed.
06 Find the next visible action
A project name rarely tells you what to do when you sit down. Choose an action with an observable endpoint that advances the result. If you cannot name it, define the question that must be answered first.
07 Break a deliverable into stages
Stages reveal the order in which work becomes usable. Identify what must be understood, produced, reviewed, and delivered. Keep stages tied to outputs so a checklist can show real movement.
08 Estimate with a range
An estimate is a planning assumption you can improve. Use a short range and name the uncertainty behind it. Compare actual time with the estimate after the task so later plans use better information.
09 Reserve room for the unexpected
A usable schedule leaves some capacity unassigned. Look at the interruptions your recent weeks actually contain and preserve room for them. Decide what can move when a real exception arrives.
10 Choose a daily work list
A daily list should fit the day that exists. Select a small number of actions using your calendar, available capacity, and project priority. Keep the full backlog elsewhere so it does not become today's implied promise.
11 Prepare an attention window
Set up one work period around a defined action. Gather its inputs, choose a finish, and decide how to handle interruptions before you start. The window can be short if that is what the day supports.
12 Reduce one digital trigger
Identify a specific digital event that repeatedly pulls you away from your chosen task. Change one setting or placement, then observe whether the action becomes easier to sustain. Preserve access needed for real responsibilities.
13 Keep a distraction capture note
An unrelated thought can be recorded without being acted on immediately. Keep a short capture list beside your task, then choose when to review it. The review closes the loop so capture remains useful.
14 Respond to an interruption
An interruption changes your state of work. Decide whether it requires immediate attention, a scheduled response, or a return to the current task. Leave a restart note before switching when circumstances allow.
15 Restart after a switch
Returning requires recovering context. Leave the file, decision, and next step clear enough that you can resume without rereading everything. Check assumptions that might have changed while you were away.
16 Batch compatible small tasks
Grouping similar tasks can reduce repeated setup when they share tools and context. Choose a bounded batch with an endpoint. Keep time-sensitive tasks on their own schedule when delay would matter.
17 Resolve a blocked task
A blocked task needs a missing input, decision, permission, or response. Name the blocker explicitly and assign a next check. Choose another useful action while waiting if one is available.
18 Request what you need clearly
A useful request explains the required input, purpose, format, and date. Give the recipient enough context to respond and enough room to state a constraint. Confirm what is agreed before building the plan around it.
19 Limit simultaneous active work
Several unfinished projects compete for setup and follow-up. Choose a realistic limit on active work and define what happens when a new request arrives. Keep waiting work visible without repeatedly restarting it.
20 Make a review checklist
A checklist preserves known requirements when attention is limited. Build it from the purpose of the deliverable and errors you have actually encountered. Use it on the final artifact rather than on your intention.
21 Choose when revision is enough
Revision should improve the result against its purpose and requirements. Distinguish necessary corrections from optional polish. Set a final review point so repeated tweaking does not quietly replace delivery.
22 Complete the handoff
Finishing includes making the result available to the intended person in a usable form. Confirm location, access, version, and next responsibility. Keep evidence of delivery when the commitment requires it.
23 Close or pause a project deliberately
A project can end through delivery, cancellation, or an intentional pause. Record its status, preserve useful materials, and resolve remaining promises. Closure reduces the chance of treating an abandoned task as an invisible obligation.
24 Design your next four weeks
Combine a priority, a scoped deliverable, a small active-work limit, attention windows, and a review rhythm. Use observations to adjust the plan weekly. Keep a usable record of what finished and what changed.