I just wrote a blog post and shot a screen recording of how I use “summary” projects to be more organised.
One of the most common problems I see when people and companies get started with Asana is that they create a tonne of projects. It’s easy to get carried away in the beginning and I get why people do this; it’s a good idea to get everything out of your head and into a system like Asana.
However, the problem with having lots of projects is that it becomes quite difficult to make sense of all the work and identify your team’s most important tasks and projects.
This is why I rely on a number of “summary” projects to make sense of the most important tasks. A “summary” project is a project that includes select tasks from other projects and organises them in a different way. These summary projects only contain tasks from other projects i.e. there are no tasks in this project alone. All tasks come from somewhere else.
Have a watch of my video to see how I’ve set this up and use things like a Kanban board to organise my most important tasks.
Would love to hear your feedback on this technique!