Thanks, @TheAnswerLady, for the call-out.
Just for others reading this thread, I want to mention that some of us generally discourage the default creation of a project for every person’s assigned tasks (like Bob’s Tasks), which is what My Tasks is, unless there’s a specific need.
(Note that my “Default Workflows” are quite different. They’re just a handful of Team-based projects, not individual-based projects.)
Your approach addresses this topic’s need for Super Admin access, but for many organizations, that’s either unnecessary or, some would say, a potential privacy violation.
While it offers some quick-start benefits, it also has some downsides. In particular, it’s not the standard use Asana recommends, which can cause confusion and prevent the use of present or future features.
One confusion might be if you add work to Bob’s project and he’s not the assignee; how is that interpreted? That’s not a concern if you just use My Tasks.
And a feature of My Tasks is that you can share your My Tasks (with management, for example, or even a Super Admin) in a unique way. It shares the structure/view of your My Tasks you’ve set up, but only those tasks for which the shared folks already have access, either as collaborators or because they’re in shared projects. With Bob’s project, that’s not easy to do.
Although it’s effort, there’s a benefit to users setting up their own My Tasks as part of onboarding (I believe in that and make it part of all-user training, because My Tasks is so important), by working through Your Simple (or Advanced) Strategy for Asana’s My Tasks to really learn My Tasks well.
I just wanted to present another viewpoint here for others to see, not try to convince you otherwise. Asana lets us all find the approaches that work for us.
Thanks,
Larry