How many Asana teams?
The structure of one’s Asana workspace is a subject that often comes into the discussion. Usually, a client would discover Asana by themselves, look at the documentation a little bit, decide on an organization, and then stick with it.
The first instinct is normally to create a single team with the whole company inside. This is especially true for small companies of a dozen people. However, larger teams might reflect the real organization of the company. For example, if you have a marketing department, an HR team and a group of developers, you probably need 3 teams to allow them to work on their internal projects, so they can focus only on the projects relevant to them.
A team does not have to represent an actual group of people. You can also create teams that represent a client, a theme, and a domain, because in Asana a team is also a way to group projects. So the marketing department can have several teams if they feel like it.
Asana also makes it easy for project handoff, where if a project is handled by one team, then entirely taken over by another, you can move the project around from team to team without having to recreate the project details.
You’ll soon realize because most organizations don’t work in silos, you need to create a cross-team project. In this case, it all depends on collaboration. If your company handles multiple projects for one client, those projects can be added inside a team and the client is added as a team member. This allows team members and the client to collaborate seamlessly, and in a centralized location.
Manager: It is your responsibility to guide people and suggest ways to organize the teams. If your organization does not work, don’t hesitate to suggest new ways of improvement! When teams and needs evolve, so should the organization.
Bonus: Be careful of the fact that team members see all the public projects inside a team. So if you have a « client team » with the client as a team member, make sure to identify this team somehow (with a clear name or emoji) so your team members don’t move confidential projects inside this team. You can use a tool like mine Asana Overview to do a regular check on the projects inside the teams.
Discover the other 4 free chapters from my ebook “Secrets of Successful teams in Asana”:
— Architectural Balance in Asana
— Keep it clean and organized in Asana
— The perfect layout for the perfect Asana project
— Working with guests and clients in Asana
or order the entire ebook, bundled with “Become an Asana superhero”.
