1 task, 1 task . Avoid creating t
Posted: Mon Jan 20, 2025 4:10 am
asks that look like shopping lists. Often each task requires further study. Adding them under a task that groups together multiple tasks would make it an unreadable papyrus. Make it more digestible: break down a job into as many micro-tasks as possible, then associate each of them with a single task.
Without a date it is not a task . Serial procrastinators mali b2b leads will disagree, but do this and you will help them too… do not define a simple due date, but a due period. This will prevent the notification of a task still to be completed from surprising someone when it is too late.
Each task should always be assigned to a single person . Yes, even if a group is going to be responsible for it. This way, it will be clear who is responsible for carrying out that task and you will avoid a buck-passing that could cause avoidable slowdowns.
The schematic title is evil . It must be as descriptive as possible of the action that must be performed, so as to facilitate understanding even some time after the assignment of the task. We therefore recommend that you start each title with a verb and avoid acronyms or abbreviations that your colleagues may not know (e.g. no “Copy ads BG”, yes “Create new corners for Business Genetics ads”) .
Avoid slowing down those who come after you . It often happens that the Copy Team has to produce content that then passes into the hands of the Ads or Growth Team. This is an example of those typical chained tasks that suffer delays due to the lack of updates between teams. So always make sure to notify who is due to come on the scene next.
Without a date it is not a task . Serial procrastinators mali b2b leads will disagree, but do this and you will help them too… do not define a simple due date, but a due period. This will prevent the notification of a task still to be completed from surprising someone when it is too late.
Each task should always be assigned to a single person . Yes, even if a group is going to be responsible for it. This way, it will be clear who is responsible for carrying out that task and you will avoid a buck-passing that could cause avoidable slowdowns.
The schematic title is evil . It must be as descriptive as possible of the action that must be performed, so as to facilitate understanding even some time after the assignment of the task. We therefore recommend that you start each title with a verb and avoid acronyms or abbreviations that your colleagues may not know (e.g. no “Copy ads BG”, yes “Create new corners for Business Genetics ads”) .
Avoid slowing down those who come after you . It often happens that the Copy Team has to produce content that then passes into the hands of the Ads or Growth Team. This is an example of those typical chained tasks that suffer delays due to the lack of updates between teams. So always make sure to notify who is due to come on the scene next.