For each task, the leader will check what team members need from management and/or from each other to complete the task.

The leader will assign new tasks to the team members and indicate their priority and deadlines.For each project, the leader will review prior day's tasks that are not yet checked off, either checking them off or discussing what is needed to complete them.The leader then will hold a stand up meeting with the team.The team leader will review all project tasks and upcoming deadlines first thing in the morning.Instead, read post 1 so you don't end up in adopt-and-abandon territory within the next month. If you can't list the replicable steps in your team's workflow, it is not yet time for Slacksana. That's 's time to create our 'Frankentool': Slacksana! WORKFLOW WE ARE AUTOMATING I will explain how to do that step-by-step in this post, based on a recent client's use of Slack and Asana. Still, you should customize the tool to make it work even better for the team. Stick with that tool until they're comfortable following the workflow and using a tool to support it.

Now let's do the fun part: choose and customize a project management tool to make that workflow as easy as possible to execute.Ĭhoosing the tool is easy if the team already has adopted one. In previous posts, I've explained: 1) why you must establish a team workflow before you adopt a project management tool to support it and 2) how to approach defining that workflow.

Asana slack integration