We’re a small nonprofit organization of 10 people and are implementing Asana. We are having a debate whether we should just have one Team for our whole organization or develop 1 for the or and 2-3 for the ‘departments’ of our organization (ex. Program and Policy/Advocacy). Since we’re such a small team, there’s a lot of cross-collaboration across departments, hence the whole need for Asana in the first place. Does any one have experience in setting up their workspace either way and what worked or didn’t work about it?
1 Like
Welcome, @Angela_Giganti,
I’d recommend one “All Staff” team with everyone, then one each for every team of people (even if a very small number, even if just one but might change later) who are either a formal or informal set of collaborators.
This will allow you to make work objects like projects accessible to groups of people to simplify the process; you can always augment or override to accommodate the situations you mention.
Thanks,
Larry
1 Like
Hey @Angela_Giganti, what a great question!
When it comes to building the different teams I’m 100 percent on board with what @lpb is sharing. One team to have all members of your organisation and separate teams for the different groups of people based on their departments would be the best way to do it.
When it comes to cross collaboration between them, you can utilise rules, bundles and multihoming in order to facilitate the hand-offs between different teams and move work forward. If you’re not familiar with the features mentioned above I would suggest to sign up for the Creating Basic Workflows in Asana live training.
2 Likes
Even if that means only 2-3 members per team?
1 Like
Yes:
1 Like
That’s a very good question.
I’ll provide a link to this post by @lpb .
It’s very informative but easy to understand, so I highly recommend it.
1 Like