Should I build new teams and new projects or just one team and various projects?

Hey there :slight_smile:

I just started using Asana and I was wondering how to organize workflow :slight_smile:
We have around 10 people in the team and not all of them are responsible for all the projects. Sometimes one project includes 2 members and over time needs another 2.

How do you usually do it? Do you add a new team for a new project or do you create one big team of your company (10 people) and create projects within the team and invite particular team members to a specific project?

I’d appreciate your advice.

All the best :slight_smile:
Aga

1 Like

Hey @aggie!

It depends quite a bit on how many projects you intend to run.
Your goal should probably be to keep things easy to find and try to find the sweet-spot between having enough teams so there aren’t far too many projects in each one. But at the same time, you don’t want 20 teams with 2 projects in each.

Except for collaboration, I find the main purpose Teams to be structuring your projects.
We’re a bit over a hundred and never create a new Team unless it’s a major initiative that requires 5 or more Projects to be created within the team.

To visualize, I recommend just writing up some made-up teams and projects in a Sheet and try to see what a good combo could be.
A bit of advice, though - it’s a lot easier to create new teams than having to remove old teams.

Company-wide Team

  • Vacation 2020
  • Comcal
  • Ideas & Suggestions!

Marketing

  • Summer Campaign
  • New release SS20

And so on.

@aggie, This exact question is addressed in:

which links to the free chapter that walks you through how to create the right structure for your workflow.

Larry

That’s a great guide! Although I don’t personally fully agree with having so many teams in all organizations.
We try to avoid any team only linked between people.

Our vision is that any team should be connected to our organization elsewhere and things you’d might want a report on.
Otherwise we try to manage one-on-ones and similar in the team where they belong, such as your department or, if cross-function, where it makes the most sense.

We’ve scaled from 10 people to 130 in 3-4 years and the amount of teams created made a mess.
As previously mentioned, I’d much rather expand on teams as they are needed instead of getting put in a situation where you have too many teams.

1 Like