Write task descriptions that survive a handover
A useful task description should make sense to someone who was not in the meeting. It explains the expected outcome, the relevant context and how the work will be reviewed without becoming a transcript of every discussion.
Lead with the result
Describe what should be different when the task is complete. Separate the outcome from a suggested method unless the method is a real constraint. Add links to the authoritative source material rather than copying fragments into several places. This makes the description easier to maintain when a requirement changes.
Name the open questions
List the decisions that still need input and identify the person responsible for resolving them. Avoid burying an unresolved assumption inside a confident instruction. If the task depends on another piece of work, explain the dependency in plain language. A clear blocker is more useful than a status that quietly remains unchanged.
Define the review
State who will review the work and what they will check. Keep the criteria observable where possible, such as a working route, an agreed document or a verified data source. Record important decisions as the task progresses. The goal is a description that supports collaboration, not one that becomes so detailed nobody can find the next step.
