👀 Overview
A task is a unit of work-to-be-done. Each Project is composed of tasks. We use 
🏅 Principles
- Clarity. Tasks need to be complete and detailed before they can be executed.
- Accountability. Tasks represent some kind of outcome that we are trying to deliver for a client. When someone is assigned to a task they are the ones “on the hook” to deliver that outcome, whatever it takes.
📏 Rules
✅ Tasks Should…
- Be written by a
Project Manager in conjunction with a 
Strategist, 
Solutions Architect, or other team member - Follow our standard format
- Stay assigned to one person for their whole lifecycle
- Use a due date representing our promised delivery date for the work
🚫 Tasks Should Not…
- Represent more than 8 hours of work
- Have a “rolling” due date
Task Anatomy
We use a standardized set of information per task. Most of this is set in an Asana custom field, while some is set as a sub-task or part of the Asana description.
| Name | Example | Mandatory? |
|---|---|---|
Update all WP plugins for the Cantilever website | ||
Big Board, FuzzCo Website | ||
Sherbert the Sheep | ||
4/15/22 | ||
“In Progress” | ||
“Medium” | ||
3 Hours | ||
Strategist | ||
“We want to make sure the client’s Wordpress site has all its plugins fully updated, ensuring that there is no security risk from outdated plugins” | ||
“You should be able to update the plugins using the WordPress control panel.” | ||
“We want to launch this by Friday so please complete this on staging by Wednesday. The client has one hour left in their budget so let’s try to spend at most 30 minutes on this.” | ||
• You have updated all the plugins on staging • You have done a quick check to make sure that the site is working properly • You have passed this task to QA | ||
