:asana: The definitive guide to using the right tools for the job (aka the right Asana features for the type of project)

What a wealth of practical information all in one place–thanks for creating this comprehensive resource! I’m sure many would quibble over a number of points, but for those looking for a starting point or rules of thumb, it’s a valuable resource.

Of course, I can’t resist offering a couple of minor suggestions for change, if you haven’t already discounted them:

The Basics > Sections > Ongoing Processes > :cross_mark: Instead of creating Sections, use the Group button to display groups based on a single-select field such as Stage / Status (more here):

  • In addition to mentioning single-select custom fields, add custom task types as well as a sometimes even more streamlined way to group tasks, change stages, and avoid unnecessarily rules.

Task types > Deadline-bound > Milestones > :white_check_mark: Best placed at the end of each section / stage / phase of the project, used as markers that will surface in the project’s Overview tab, a Portfolio Timeline tab and count towards the progress of connected Goals:

  • Also mention Milestones’ value in Portfolio List view Milestone Program column cells.

Saved view tabs > :plus: Saved view tabs > Deadline-bound > :balance_scale: Could be used but not ideal if projects are created from Project Templates, which do not currently support saved view tabs:

  • I find extra tabs in these kinds of projects to be invaluable, particularly List by Start/Due Date, List by Team, List for Me, etc. to complement the overall default List view by phased section groups.

Customize menu > Fields > Deadline-bound and Ongoing Process:

  • I usually discourage use of Status and Priority custom fields for a variety of reasons, including redundancy, unreliability (too much to keep up), etc.

But again, these are minor (and the last one perhaps controversial) points compared to the great overall value of the resource you created.

Thanks,

Larry

2 Likes