A few things come to mind…When I started using Asana six years ago many of these functions were not yet available and it also depends on which tier you are using but if I were start today, I would say:
leverage the rules and custom field capabilities
use the custom fields to create helpful dashboard views
bundle related projects together in a portfolio, or if your project has many complex moving parts you can create multiple projects and treat the portfolio like the entry point to all the facets of the work
forms / reporting are underused in my organization but can do some really cool things for you
star your frequently used projects so they are at the top of your nav bar
keep archiving / closing out projects that are no longer active
if you are a big Outlook user, many folks I know like to sync Outlook with Asana so that you can see tasks in your calendar, create tasks from emails, etc.
Asana has a fair number of affordances for complicating your implementation. I’d avoid any temptation to use them all right away. Start with the simplest possible structures, and understand them fully. Then build out Teams, Projects, Rules, Templates etc. organically, only as the need arises and you understand that the basics aren’t enough anymore.
Be user-centric. If you’re a superuser setting up Asana for your org, learn your users’ most important wishes and deliverables, and then build out specific Asana behaviors and workflows to meet them.
Great tips. As a newer Asana user myself, could you please elaborate more on how to integrate Outlook with Asana? I have my Asana notifications set up to notify me, via Outlook, of any new tasks/mentions related to me, but would love to utilize this feature more.