I think Asana’s default behaviour in selecting the team a project gets added to leads many projects created in - and therefore shared with - the wrong team.
When you start from Create > Project:
Asana chooses the topmost team under the Teams section of the side-bar:
As the team is pre-filled, many people will read over this step, and just:
- give their new project a name
- See the “Continue” button light-up bright blue
- Hit Continue without noticing the team the project is being added to - and shared with.
If custom onboarding is used, this both increases the problem, and provides for a solution.
The problem increases because the team selected for onboarding will be everyone’s first team, and therefore topmost in the list.
This turns that team into a nightmare for preventing unintentional oversharing of teams because in addition to it being the most likely place for projects to be unintentionally shared with, it’s also likely the team with the most members.
At the same time it provides a solution, because of recent changes allowing to limit the people allowed to add work to the team to team admins:
Because when the topmost team in the sidebar doesn’t allow for the adding of projects by anyone but team admins, the interface doesn’t choose a default team, and now requires a team to be selected:
My proposal is to making this required team selection the default behaviour, as it is a pattern interrupt that forces someone to conciously decide who their project will be shared with.
)