Build the mental model
A goal, a project, and a task are not the same thing, and mixing them up is one of the most common reasons task lists stop working.
- Goal - a direction, e.g. "launch a learning website"
- Project - bounded work toward the goal, e.g. "build the learning site"
- Task - one concrete action, e.g. "create homepage", "write lesson", "deploy site"
- Next Action - the single physical step to do right now, e.g. "write homepage hero copy"
Most task lists fail not because people lack discipline, but because their tasks are really goals or projects in disguise, with no obvious next action attached.
Task management works as a repeating cycle, not a single static list.
Capture
Get the task out of your head and into a system, even in rough form.
Clarify
Turn the rough capture into a well-formed task with a clear next action.
Prioritize
Decide what matters most - urgent/important matrix, high/medium/low, or impact vs effort all work.
Schedule
Decide when the task actually happens.
Execute
Do the work itself.
Review
Periodically check what is done, what is stuck, and what changed.
Simple states such as Inbox, Next, Doing, Waiting, and Done make a task's position in that cycle visible at a glance, so nothing quietly disappears.
- Goal
- A broad direction or desired outcome, not something you "do" directly.
- Project
- A bounded piece of work made of multiple tasks that moves you toward a goal.
- Task
- One concrete unit of work inside a project.
- Next Action
- The single physical or mental step you would do right now to move a task forward.
TASK MANAGEMENT CYCLE
---------------------
INBOX -> CLARIFY -> PROJECT / TASK -> PRIORITIZE -> DO -> REVIEW
^ |
| |
+----------------------------------------------------------+
(unfinished or new items loop back to INBOX)Connect it to a real scenario
Start by writing down every open loop in your head, no matter how small, into one inbox. Do not sort while capturing; just get it out.
Once a day, walk through the inbox and clarify each item: is it a goal, a project, or a real task? If it is a project, break it into at least one first task.
Rewrite every vague task so it starts with a verb and names a concrete outcome, such as changing "taxes" into "gather 2025 receipts into one folder."
Next, prioritize what you clarified. Pick one method and use it consistently. Do not try to use three prioritization methods at once.
| State | Meaning |
|---|---|
| Inbox | Not yet captured or clarified |
| Next | Ready to do |
| Doing | In progress right now |
| Waiting | Blocked on someone else |
| Done | Finished |
Review these states every few days so nothing sits in Waiting forever unnoticed. The goal is not a perfect system on day one; it is a small, honest loop you actually run every day.
Try the working example
const ACTION_VERBS = [
"write", "create", "build", "deploy", "review", "email", "call",
"draft", "fix", "update", "read", "schedule", "design", "test",
"publish", "research", "plan", "organize", "clean", "buy"
];
function checkTask(raw) {
const text = raw.trim();
const words = text.split(/\s+/).filter(Boolean);
const firstWord = (words[0] || "").toLowerCase().replace(/[^a-z]/g, "");
const isSingleWord = words.length === 1;
const startsWithVerb = ACTION_VERBS.includes(firstWord);
if (isSingleWord || !startsWithVerb) {
return { task: text, status: "vague", reason: isSingleWord ? "single word, no next action" : "does not start with an action verb" };
}
return { task: text, status: "well-formed", reason: "starts with an action verb and names a concrete step" };
}
const rawTasks = [
"Website",
"Write homepage hero copy",
"Marketing",
"Deploy site to production",
"Notes",
"Review draft lesson for chapter 3"
];
rawTasks.map(checkTask).forEach(r => {
console.log(`[${r.status.toUpperCase().padEnd(11)}] "${r.task}" - ${r.reason}`);
});[VAGUE ] "Website" - single word, no next action
[WELL-FORMED] "Write homepage hero copy" - starts with an action verb and names a concrete step
[VAGUE ] "Marketing" - single word, no next action
[WELL-FORMED] "Deploy site to production" - starts with an action verb and names a concrete step
[VAGUE ] "Notes" - single word, no next action
[WELL-FORMED] "Review draft lesson for chapter 3" - starts with an action verb and names a concrete step5-minute try-it
Write down five things currently in your head as tasks. For each one, check: does it start with an action verb, and does it name a concrete outcome? Rewrite any that fail either check, then sort all five into Inbox, Next, Doing, Waiting, or Done.
One important caution
Writing a project or goal as if it were a single task, then wondering why it never gets "done."
Letting items sit in Waiting indefinitely because nothing forces a review of that state.
Spot the Well-Formed Task
Getting Things Done (GTD) method overview — Productivity Systems