Keep the conversation on the task

The most expensive thing in shared work is context that lives somewhere else. When the decision is in a chat thread and the file is in an email, everybody rebuilds the same understanding from scratch. Everything below exists to stop that.

Checklists

A checklist breaks one task into steps without creating a pile of separate tasks. Use it when the steps only make sense together and only one person is doing them. If a step needs its own owner or its own date, it wants to be a subtask instead.

Attachments

Attach the document, the brief, the photo of the whiteboard. The test is simple: would someone picking this task up cold need it? If yes, it belongs on the task and not in your downloads folder.

Comments and threaded replies

Comments support threaded replies, so a question and its answer stay together instead of scattering down the page. Two habits make this worth doing. Record decisions, not just chatter, because in three weeks the decision is the only part anyone needs. And when a conversation elsewhere settles something, paste the conclusion onto the task.

Blocked by

Dependencies appear in a section labelled Blocked by. Recording one is how a task stops looking like neglect and starts looking like what it is: waiting.

This matters for reporting as well. A task blocked on someone else and a task nobody has started look identical in an overdue count. Marking the blocker means your later review shows you where work actually gets stuck, which is usually the handover between two people rather than the work itself.