I was asked the following question during a recent session with an client: « As an employee using Asana, when I receive a request from another employee, should I insist on it being a task, even though the request will end up generate several tasks or even a project? ».
An example would be « Bob can you organize the Christmas party? » said in Slack, which can’t decently be a task, but rather a complex project with many involved parties (pun intended).
My advice was that “over the counter” requests, water-cooler suggestions and half-baked email demands should always be a task. Even if that task ends up being turned into other tasks and projects.
The good practice in that case is to create the resulting work, and inform the requesting person, by using a comment with mentions to the new tasks and projects. And complete the original request as a result, leaving the requesting person the freedom of following the new tasks or projects if they decide to.
PS: wow I just re-read myself and that explanation seems complicated, isn’t it?
Do you agree?