@Thomas_Jensen, we handle this in two ways:
We make huge use of template tasks and template projects in our workflow. Our project templates are created based on type of work - I’m in Marketing, so think sales proposals, brochure creation, communications. Our proposal manager created the proposal project template and brochure creation template, and I’ve created the communications template. That means I am automatically a collaborator for any task in any project based on that template.
For template tasks, which we use in on-going or continuous projects that don’t need an entire project template, we do the same thing. I’ve created the template task for those I want to be more in the loop for, and others have done the same. Our workflow is for Teammates to duplicate the task (using the Duplicate Task function, not just “ctrl+c”) which allows you to select “collaborators” as one of the options to copy.
In either case, we can add additional “default collaborators” as part of the template, which means they will be a collaborator of either projects or tasks that are created based off of the templates.
For outlier tasks or projects, my team tags me in when they know I need to be involved or be informed. I try to think of following asana tasks as being cc’d on emails. To ask an employee to cc me on all of their emails would definitely make me a micromanager, so I don’t do that with Asana tasks. I’d wind up with so many notifications, that I’d miss the ones everyone really needs me to see!