Why the three levels matter
A plan becomes hard to use when every intention lands on the same list. “Improve our newsletter,” “create a welcome sequence,” and “draft the first email” are related, but they ask different things of you. The first gives direction, the second names a result to produce, and the third is an action you can sit down and do. Treating all three as equal-sized tasks makes it difficult to tell what is ready for today and what still needs thinking through.
A simple hierarchy can help: goals describe a desired direction or outcome, projects produce a defined result, and tasks are the individual actions that move a project forward. The purpose is not to make a perfect planning system. It is to make decisions at the right level, so your daily list contains workable actions rather than reminders of everything you hope to accomplish.
Goals set direction
A goal answers, “What am I trying to change or achieve?” It might be “make the newsletter more useful to new readers” or “create more space for deep work.” A helpful goal is specific enough to guide choices but broad enough that more than one project could support it. You can also note how you would recognize progress, such as receiving clearer reader questions or protecting regular writing time, without pretending the outcome is entirely within your control.
Goals do not usually belong on a daily to-do list. “Create more space for deep work” is not an action you can complete on Tuesday. Keep goals somewhere you review when choosing projects and making trade-offs. If a proposed project does not support a current goal or an important responsibility, ask whether it deserves your time now. Not every project needs a grand goal, but knowing why it matters makes prioritizing easier.
Projects define results
A project is a piece of work with a finish line. “Create a three-email welcome sequence” is a project because you can tell when the sequence is ready. It may take several work sessions and involve decisions, drafts, feedback, and setup. A good project name points to its intended result rather than a vague activity: “publish the team onboarding guide” is easier to plan than “work on onboarding.”
For each active project, write down what “done” means and identify a next action. You do not need to map every step in advance, especially when later steps depend on what you learn. If a project feels too large to finish within a reasonable planning horizon, divide it into smaller deliverables. For example, “reorganize all our information” might become “create a shared index for current project files.” That result gives you a clearer place to start and a clearer point at which to stop.
Tasks make the next move clear
A task is an action you can take without first figuring out what the instruction means. “Draft the opening email” may be clear enough; “newsletter” probably is not. Starting tasks with verbs can expose the difference: outline, ask, compare, revise, schedule, or send. If you keep postponing a task, check whether it hides several steps or an unresolved decision. “Finalize the sequence” might actually mean “choose the three topics,” then “draft email one.”
Your daily list should be a selection from your projects and responsibilities, not a copy of every possible task. Consider the time and attention available, then choose a manageable set. It is fine to include maintenance work, such as replying to a colleague or filing an expense, even when it does not sit neatly under a goal. A plan should reflect the work you actually do, not force every small obligation into a larger narrative.
Connect the levels, then keep the system light
When something new appears, sort it before scheduling it. Ask whether it is a direction, a finishable result, or a concrete action. For the newsletter example, the chain might read: goal, “make the newsletter more useful to new readers”; project, “create a three-email welcome sequence”; task, “outline the first email.” The link between levels helps you see why an action matters. It also makes it easier to change course if the project no longer serves the goal.
Review the levels at different rhythms. Check tasks when choosing what to do next, look over active projects regularly to find stalled work, and revisit goals when deciding what to start or stop. In collaborative work, agree on the project result and who owns the next action rather than assuming a shared goal gives everyone the same plan. Keep room for rest and unexpected work by leaving some capacity unassigned. The best structure is the smallest one that helps you choose a useful next step and recognize when the work is done.
