I have seen tasks chased repeatedly without moving forward. The problem often starts at assignment: someone hears the task name but does not know which decision is needed, what the output should look like or who can sign it off.
Define the outcome first
Before listing steps, ask why the work matters and what evidence will show it is complete. “Review customer data” is vague. “Produce a list of active customers, owners, latest quotations and open decisions by Friday” gives the team an output it can verify.
Give one person ownership
Several functions may supply data or opinions. One owner still needs to maintain the final version, follow up with contributors and report status. When accountability is divided equally, a task can stall at “waiting for another team”.
Keep the brief short and complete
- Context and goal: what decision or result does this work support?
- Definition of done: which document, approval, data set or action is required?
- Owner, contributors and decision rights.
- Deadline and update milestones; the owner proposes a date if none is set.
- Likely blockers and when support must be requested.
I ask the owner to repeat their understanding of the output and deadline. A minute spent confirming this can save several rounds of explanation.
Use meaningful progress updates
“In progress” alone is rarely useful. A good update states what is complete, what is missing, the risk to the deadline and the next action. For a blocker, the owner identifies who is needed, what is needed and by when. The coordinator helps remove obstacles while the owner remains accountable for the outcome.
For me, a task is complete when its intended user has accepted the output and the next step has an owner. That closes the execution loop.