Assignee

Example

Sherbert the Sheep

Mandatory?

Tasks should stay assigned to one person (usually a designer or developer) for the lifecycle of the task instead of moving from person to person. The one person is principally accountable for Cantilever getting the work done. They are responsible for requesting required Strategic, Peer Review, and QA approvals.

☝

Example: If Roman takes on a new task for BPC, Roman will stay assigned to that task in Asana until it is deployed. During the Approval and QA process, other people will be assigned sub-tasks for those approvals, but the main task will stay on Roman.

For newer people it is hard to take overall accountability for a task in the Cantilever style/workflow. They don’t have the right context and ability to operate that veteran team members do. For newer folks, it can be more productive for a senior person to take assignment of a task instead, and then delegate a specific portion of the work to a newer person via a sub-task.

As a part of task clarification, PMs should add sub-tasks for any approvals they believe are required to consider the task complete. However, the assignee is also free to add additional approvals that would make them feel certain that the work is in good shape.

❗

This means that in order to work effectively at Cantilever you will also want a solid personal task management of your own. This can be your own Asana list/projects, pen & paper (Try the Bullet Journal by our friend Ryder Carroll), TextEdit, OS X Reminders, Remember the Milk, Google Tasks, Todoist, OmniFocus, Things, etc. Don‘t use your memory for this.