That task you have moved to next week three times might not be one task.
“Publish an article” looks straightforward on a list. But when you sit down to do it, you may still need to finish the draft, choose a visual, prepare the page and check how it will appear.
The title describes the result you want. It does not necessarily tell you what to do next.
That distinction matters when you return to unfinished work. If the task makes you reconstruct the whole process before you can begin, the list is holding an intention rather than helping you act.
Look inside the task
In a client workspace session, we talked through a publishing item that initially looked like a single task.
The work contained three separate actions: draft the article, create the visual and publish it.
We grouped the work under one project and made those actions separate subtasks. Each could be completed and tracked without losing its connection to the overall piece of work.
The point was not to create a more elaborate project system. It was to make the difference between “the article is unfinished” and “the draft is finished, but the visual still needs doing” easier to see.
Not every stalled task needs more subtasks
Breaking work down can help, but it is not the answer to every item that stays open.
Before adding structure, ask what is stopping the work:
- The next action is unclear. Name the specific thing you can do next.
- A decision has not been made. Record the decision needed rather than pretending execution can begin.
- You are waiting on someone. Make the dependency visible and decide when to review it.
- There is no capacity for it. Reconsider the commitment or timing.
- The work is no longer needed. Remove it from the active list.
A detailed checklist will not solve a missing decision or create time that is not available.
Choose the lightest useful structure
Use one clearer task when there is one action
“Newsletter” leaves a lot to interpret. “Review the draft introduction for the November newsletter” tells you what to do and what it relates to.
Include enough context that the task makes sense outside the project page where you created it.
Use a checklist when the steps belong together
A short checklist can work when one person completes a familiar sequence in one sitting and the individual steps do not need separate tracking.
For example, a final publishing check might cover links, formatting and the preview image. Those checks do not automatically need separate owners, dates and records.
Use subtasks when the actions need their own progress
Separate tasks are useful when the work happens across different sessions, involves different people or depends on an earlier step being finished.
Drafting, creating a visual and publishing are distinct enough that knowing which one remains can help someone decide what to do next.
Use a project when you need to manage the wider outcome
If several related actions need coordination, keep them connected to a clear outcome.
The project holds the purpose and context. The tasks describe the actions. Avoid making every small activity a project if that adds more administration than clarity.
Test the workflow before turning it into a template
Once a sequence repeats, a reusable template may be helpful. But first check what actually repeats.
Does every article need a new visual? Is approval always required, or only for certain material? Do different publishing destinations need different preparation?
Run the sequence through real work and adjust it before treating it as the standard. Otherwise, a template can preserve assumptions that make every future task harder.
A useful template should reduce repeated decisions, not generate a list of boxes nobody needs to tick.
Make progress mean something
Completing two of three subtasks does not necessarily mean two-thirds of the effort is finished. Drafting may take much longer than publishing.
Use the task breakdown to understand what remains, rather than treating a completion percentage as a precise measure of effort or readiness.
The useful question is: “What needs to happen before this can move forward?”
Your action
Choose one item that keeps rolling over. Write down what “finished” means, then identify the next action you could complete.
If several distinct actions are hiding inside it, choose the simplest structure that makes them manageable. Keep the overall context, but stop asking one vague title to do the work of an entire workflow.
If recurring work is difficult to untangle, a Clarity Session can help identify the decisions, dependencies and steps behind it. Your tailored Clarity Blueprint gives you a practical route forward, whether you implement it yourself or work with me on selected changes.