Excellent tips Bastien! Subtasks definitely have their place, but Asana projects are so powerful and it makes sense to use them to their full potential for use cases like this. I also appreciate the advice to not fear having many projects under a certain team. Thank you.
This does a great job highlighting many of the limitations and shortcomings of Asana compared to other tools available on the market that don’t require a ton of work arounds. 👍
I love Asana, I really do. But the years-old issues that haven't been addressed, like subtasks not operating in a functional way, is disheartening. Problems are ignored on the forums in favor of adding new features with less demand.
@@aascottie I believe they are working hard on this topic in the shadows but not communicating about it because they probably have no idea if and when they'll find a "solution". I have a call with a product head soon to discuss that very specific topic.
This video changed the way I use Asana for the better. I tended to manage what should have been projects as tasks. My projects in Asana were "areas of responsibility." As Bastien points out, you end up with lots of subtasks and can't take advantage of Asana's full capabilities. Now I manage projects as true Asana projects organized into teams. It's a huge improvement and allows me to track so much more information and data in Asana, reducing the need to rely as heavily on outside notes apps, like Evernote and Notion. Search in Asana has gotten good enough that having a lot of projects isn't an issue. I've learned to spend a lot less time in the sidebar and just search for what I need.
wow Doug thank you so much. I have been preaching all this for years, and sometimes it feels like shooting at a wall all by myself. But your comment make it worth it.
We are currently evaluating Asana to use as our tool to track our tasks and have transparency of our work. I was wondering... instead of adding a link in the description field of the task - why do you not assign the task to the properties project?
The link in the description goes to the entire project for this property, that's why :) @heratik can you email me at bastien@ido-clarity.com? We can give you help and benefits with those licences!
I like your proposal, and I will use multi-homing because you could also go to the related project with one click and you could change the section in the overview by using a custom field in the property project, so that you don't have to jump between the two
Good question. A portfolio with all properties projects would give you an overview of the progress, and you could replace the columns we have with a custom field, getting rid of the master project all together!
Excellent tips Bastien! Subtasks definitely have their place, but Asana projects are so powerful and it makes sense to use them to their full potential for use cases like this. I also appreciate the advice to not fear having many projects under a certain team. Thank you.
Thanks for the feedback!
This does a great job highlighting many of the limitations and shortcomings of Asana compared to other tools available on the market that don’t require a ton of work arounds. 👍
It was not my intention to show off limitations but rather explain how to use Asana it was designed to be used.
I love Asana, I really do. But the years-old issues that haven't been addressed, like subtasks not operating in a functional way, is disheartening. Problems are ignored on the forums in favor of adding new features with less demand.
@@aascottie I believe they are working hard on this topic in the shadows but not communicating about it because they probably have no idea if and when they'll find a "solution". I have a call with a product head soon to discuss that very specific topic.
This video changed the way I use Asana for the better. I tended to manage what should have been projects as tasks. My projects in Asana were "areas of responsibility." As Bastien points out, you end up with lots of subtasks and can't take advantage of Asana's full capabilities. Now I manage projects as true Asana projects organized into teams. It's a huge improvement and allows me to track so much more information and data in Asana, reducing the need to rely as heavily on outside notes apps, like Evernote and Notion. Search in Asana has gotten good enough that having a lot of projects isn't an issue. I've learned to spend a lot less time in the sidebar and just search for what I need.
wow Doug thank you so much. I have been preaching all this for years, and sometimes it feels like shooting at a wall all by myself. But your comment make it worth it.
We are currently evaluating Asana to use as our tool to track our tasks and have transparency of our work. I was wondering... instead of adding a link in the description field of the task - why do you not assign the task to the properties project?
The link in the description goes to the entire project for this property, that's why :) @heratik can you email me at bastien@ido-clarity.com? We can give you help and benefits with those licences!
@@asana-ido that makes sense!! Will try it out!
I like your proposal, and I will use multi-homing because you could also go to the related project with one click and you could change the section in the overview by using a custom field in the property project, so that you don't have to jump between the two
how to you add the underline on the subtask text, is there a video for this kind of formatting? thanks
That's a subtask section, you can create it with Tab+N shortcut :)
How would you incorporate Portfolios into this setup.
Good question. A portfolio with all properties projects would give you an overview of the progress, and you could replace the columns we have with a custom field, getting rid of the master project all together!