I believe Asana Rules is a feature you can struggle to grasp at first, but then wouldn’t be able to live without it.
I came to this realisation the other day when I looked at the way we manage quotes in Asana (we use Asana as a light CRM). This process involved 72 rules. Yes, you read that right 
I managed to clean it up and get it down to 50ish using the new editor with branches and grouping rules under a master project. But still, what on Earth do we do in there?
For context, a lot of our tasks in Asana have a “type” (a dropdown “task type” e.g. “quote”, “invoice”, “meeting”…) as well as an an “Actions” dropdown which allows us to trigger actions in bulk (e.g. “Mark quote as signed” would trigger a task completion, due date change, comment post…).
Here’s a glimpse at what Rules are good for based on our own use case for managing quotes:
-
5 rules are about managing the “Actions” dropdown
-
one rule is about creating an invoice automatically when a quote is signed, using a custom made action
-
one rule is about adding a fire emoji if a task’s priority becomes “high”
-
two rules are about default values: default task type, default status, default multi-homing
-
two rules are managing approvals needed from the selected consultant on the quote
-
one rule is about renaming a task based on the different fields it contains
-
18 rules are about defining prices and hours depending on the engagement type
-
7 rules are about creating the right sessions based on the engagement type
-
6 rules are about adding subtasks based on status to make sure we don’t forget important steps or follow-ups
-
and a few others
Without all those rules, we would miss important information and deadlinse, as well as have inconsistencies everywhere or waste a crazy amount of time doing it all manually!
Bastien, Asana Expert
