Every task needs one owner
Shared ownership is the most reliable way to guarantee nothing happens. A task assigned to a team is a task assigned to nobody until someone claims it.
One named owner, with reassignment as an explicit action, keeps accountability legible. Team queues are useful for intake, but work should leave the queue with a name attached.
Link the task to the record
A task that says "follow up with Nordic" is a reminder. A task attached to the Nordic account, and to the specific opportunity it concerns, is context.
The practical benefit appears when someone else picks it up: they open the record, see the history, and can act without a briefing. The secondary benefit is that stalled accounts become visible through their outstanding work.
Use priority sparingly and dates honestly
Priority fields degrade fast. When everything is high, the field carries no information and people revert to judgement.
Due dates suffer similarly when they are aspirational. A date should mean something happens or something breaks. Where a task genuinely has no deadline, leaving the date empty is more honest than inventing one.
- One owner per task, always named.
- Linked to the customer, deal or record it concerns.
- A real due date, or none at all.
- Subtask checklists for multi-step work, rather than five near-identical tasks.
Subtasks for work with steps
Onboarding, proposals and handovers are single commitments made of several steps. Splitting them into separate top-level tasks fragments the commitment; leaving them as one hides the progress.
A checklist inside the task keeps both: one owner and one deadline for the commitment, with visible progress through the steps.