Task management: a system that survives a busy week

Task management is not a tool problem. Almost everyone already has somewhere to put tasks; what collapses is the practice, and it collapses in a specific way — the week gets busy, the list stops being updated, and within days it is a museum of things you might once have done. From then on the real list is in your head, and the app is decoration.

A system that survives that week is built around one property: it must be cheaper to update than to work around.

The four moves that make up task management

• Capture — everything lands in one inbox the moment it appears, in whatever wording you first thought of it. Sorting comes later; hesitation at this step is what sends tasks back into your head.
• Clarify — turn each item into a next action starting with a verb. "Website" is a topic and will be skipped every time; "draft the homepage copy" gets done.
• Decide — for each task, one of four outcomes: do it now if it takes two minutes, schedule it with a real date, delegate it with an owner, or drop it. A task with none of the four is decoration.
• Review — a short weekly pass over everything open, closing what is done, re-dating what slipped, and deleting what stopped mattering. This is the step people skip, and it is the one that keeps the list trustworthy.

The honesty test: if you can see a task on the list and know without checking that it is out of date, the system has already failed. Two minutes of pruning restores more value than any feature. For work that crosses teams, the handover is where things are lost — a handover document is cheaper than the recovery.

Priorities that mean something

Five priority levels are four too many — everything ends up High. Two work: what must happen today, and everything else. If today's list is longer than what a day holds, the list is a wish and the choice is being deferred rather than made.

Due dates deserve the same discipline. Give a date only when one genuinely exists — a client deadline, a dependency, a meeting. Fake deadlines are why real ones stop being believed, and a list dense with overdue items carries no signal at all.

Where personal and team task management differ

Personal lists optimise for capture speed and daily review. Team task management adds two requirements: every task has exactly one owner, and status is visible without asking. Shared ownership is how work stalls — two people each assume the other is on it — and status that requires a meeting to discover is not status.

The other team-specific need is a place for blockers. A task nobody can move should say so, on the task, with what it is waiting for; otherwise it looks identical to a task nobody has started.

Ettex Board is the shared half of that: cards with a single assignee and avatar, colour labels and priority flags, due dates, checklists inside cards to break work into steps with visible progress, WIP limits to keep a column honest, swimlanes for larger boards, comments and @mentions so discussion sits on the task, activity history on every card, live updates for everyone at once, and instant search across all boards. Cards move offline and sync later, and boards export to CSV or JSON. For personal capture, Ettex Notes has checklists inside any note, which is often the right home for the inbox step.

Large pieces of work need decomposing before they can be tracked at all. A work breakdown structure splits a deliverable into progressively smaller components, which is what turns "build the warehouse" into items somebody can own.

Why systems fail

• Too many lists. Two places to look means neither is complete, and completeness is the whole value.
• Elaborate setup. Custom fields and colour schemes are procrastination that feels like progress.
• No review. Without it, the list decays into noise in about two weeks.
• Tasks written as topics rather than actions, so every glance requires re-deciding what to do.
• Tracking someone else's work in your own list instead of delegating it with a name and a date.

Two adjacent practices decide whether a task list reflects reality. An issue log separates problems from work — they need different handling — and project closure is the step that stops finished work sitting on the board indefinitely because nobody declared it done.

Good task management is unglamorous: one inbox, actions written as verbs, four possible decisions, and a weekly pass to keep the whole thing honest. The tool matters far less than whether the list is still true on Friday.