Use a verb and a concrete result
“Draft the welcome email” tells someone what to do. “Email” makes them ask a follow-up question. Start the title with an action such as write, review, fix, test, or publish. Keep the result narrow enough to finish.
Avoid packing several unrelated jobs into one ticket. If writing an email and fixing a database permission require different owners or different reviews, use separate tickets. They can sit on the same board without sharing one completion state.
A small ticket template
You do not need a long specification for every task. A short description with three parts often gives enough direction: why the task matters, what needs doing, and how you will know it is done.
- Context: What prompted this task?
- Action: What should change?
- Done: What result should the reviewer be able to check?
What does a good example look like?
Title: “Draft the first welcome email”. Context: New users need a clear first step after confirming their account. Action: Write a short email with a warm greeting and a link to the board. Done: The team has approved the copy, the link opens the correct page, and the email looks readable on a phone.
Assign it to the person responsible for the next draft. Add the launch date as a due date only if the email needs to be ready by then. A high priority flag should reflect a real scheduling decision, rather than becoming a label on everything.
Keep the ticket useful as work changes
Update the description when new information changes the next step. If responsibility changes, reassign the task. If the deliverable becomes too large, divide it into smaller cards.
In Lanelet, teammates can edit the title, description, status, priority, assignee, and due date. If someone has changed the ticket since you opened it, a version check asks you to refresh before overwriting their work.