How to Write a Good Task: A Template That Prevents Rework
Most rework doesn't come from bad work — it comes from bad tasks. "Fix the website" can mean a typo or a redesign. A clear task takes two extra minutes to write and saves hours of back-and-forth. Here's what a good task contains, with a template you can copy.
- Title: starts with a verb and names the result — "Write 3 onboarding emails".
- Definition of done: how we'll know it's finished.
- Context: why it matters, plus links and files.
- One owner, a real deadline, and a size between an hour and two days.
Anatomy of a good task
| Part | Bad | Good |
|---|---|---|
| Title | "Onboarding" | "Write 3 onboarding emails for new trial users" |
| Why | — | "Trial users drop off after day 2; we want to show the key feature earlier" |
| Done when | — | "3 emails drafted in the shared doc, reviewed by Maria" |
| Resources | — | "Brand voice guide, feature list, last year's emails (links)" |
| Owner | "Marketing" | "Anna" |
| Deadline | "ASAP" | "Thursday, 3 pm" |
The template
Title: [Verb] + [result]
Why: one sentence on the goal
Done when: 1–3 checkable criteria
Resources: links, files, contacts
Owner: one person
Deadline: date (and time if it matters)
Autonomy: decide yourself / propose options / check with me first
Paste it into the task description and fill it in. It takes about two minutes.
Five rules
- Verb first. "Design", "Write", "Fix", "Call". A noun is a topic, not a task.
- One result per task. If the definition of done has "and", consider two tasks.
- Size it. Between an hour and two days. Bigger tasks hide unknowns; split them.
- Real deadlines only. "ASAP" is not a date; fake deadlines teach everyone to ignore deadlines.
- Context over instructions. Explain the goal; let the owner choose the path unless the path matters.
Before and after
Before: "Website bugs" After: "Fix the checkout button not responding on iPhone Safari" — Done when: tested on iPhone 13+ Safari; screen recording attached.
Before: "Client presentation" After: "Draft 10-slide pitch for Acme's Q4 campaign" — Done when: slides in the shared folder, reviewed by the account lead by Wednesday.
Where tasks should live
Put tasks on your team board, not in chat. In Teamflows, each card holds the title, description, one assignee, a deadline, attachments and comments — and a timer, so the actual time can be compared to the estimate later. See how to set up a kanban board.
Frequently asked questions
How detailed should a task description be?
Enough that someone who wasn't in the meeting can deliver the right result. The goal, definition of done and deadline are the minimum.
Should tasks include estimates?
It helps. A rough estimate in hours, compared later with actual tracked time, improves planning. See estimated vs actual time.
What if the task is unclear to me as the manager?
Then it's not ready. Create a smaller task first: "Research options for X and propose two approaches."
Who should write the task?
Whoever requests the work — but the owner should read it and ask questions before starting.
We build Teamflows — a free kanban board with a timer inside every task — and use it every day at the Digital Plus studio to run dozens of client projects. Our guides come from that practice. Questions or corrections: mail@dp8.kz