1. State the outcome
Replace broad labels with a result someone could recognise. “Website” might become “publish the revised services page.” “Taxes” might become “collect the missing receipts for the accountant.” The outcome can still be large; its purpose is to explain why the work matters.
2. Separate the project from the next action
A project is an outcome that needs more than one step. It may need notes, milestones, files or decisions that do not belong in a single task title. The next action is the smallest useful move that changes its state: ask for a quote, outline the page, compare two options or schedule a review.
3. Look for dependencies and waiting
Ask whether you can act now or whether somebody else must reply, approve or deliver something first. If you are waiting, write down who or what you are waiting for and when a follow-up would be reasonable. Do not schedule a blocked action as if it were ready to do.
4. Define “done for now”
Many independent-work tasks do not end with a perfect final state. Decide what is enough for this pass: send the draft for feedback, get the estimate approved, publish the first version or document the decision. This prevents open-ended work from expanding into every available hour.
5. Place it where capacity exists
Estimate effort roughly, check fixed commitments in your calendar and choose a day with enough room. Avoid assigning every task to the same day simply because that is when you hope to finish it. If the plan changes, revise the date and keep the context with the work.
Example: “Prepare the client launch”
Outcome: client has an approved launch-ready landing page. Possible project steps: confirm copy, build page, test form, get approval. Next action: send the client the two outstanding copy questions. Dependency: final copy approval. Done for this pass: answers received and page build can begin. This is much easier to schedule than one enormous “launch” task.
Use the one-task method to choose what to start today, then place it in a realistic weekly plan. Cadence helps keep the task and its day visible; it is not a full project-management database.
More rewrites
| Vague task | Outcome | First physical action |
|---|---|---|
| Sort out the website | Homepage explains the service in one screen | Open the page and write the new headline |
| Chase invoices | Three overdue invoices followed up | Email Acme about invoice 1042 |
| Plan the workshop | Agenda sent to attendees | List the three things they should leave knowing |
| Fix onboarding | New users reach the first key screen | Watch one recording of a new user |
Signs a task is still too vague
- You have moved it more than twice.
- You cannot say how long it will take.
- It begins with "look into", "sort" or "think about".
- You would not know when to stop.
When that happens, the next action is nearly always smaller than you think: open the file, write the first line, ask one person one question.
Where Cadence fits, and where it does not
Cadence is a weekly planner for Mac and iPhone: one board, a column per day, tasks you drag when plans change. It has no timers, projects, tags or recurring tasks, so the method on this page is something you run yourself and place into the week. It costs $19 once for Mac, with no subscription and sync through your own iCloud. More in the weekly planner guide.
Try it this week
- Find the task you have moved most often.
- Rewrite it as an outcome, then write the first physical action.
- Do only that first action today.
Starting is most of the resistance. Once the file is open the rest usually follows.
Rewriting takes a minute and saves the hour of circling.
Questions people ask
What is a next action?
The first physical, visible thing you would do: open, write, call, send. If you can do it without deciding anything else, it is a next action.
Should every task be this detailed?
No. Only the ones you keep not starting.
What about tasks waiting on someone else?
Write them as "waiting for Sam: figures" with the date you asked, and put a follow-up on a specific day.
How big should a task be?
Small enough to finish in one sitting, usually under two hours.