@auren @asana 1. We require everyone across all functions to use Asana. Each functional area has at least one of their own projects, which gives them their area to manage within Asana (some functional areas have multiple projects). We then create sections in each project for multiple topics.

@auren @asana 2. For example, Marketing has its own project, and within that are sections for Podcast tasks, Product Marketing tasks, Social Media tasks, etc. Development has a project going for each sprint that it's working on. HR has two projects, both a public and private one.

@auren @asana 3. On day one when someone starts, we talk about the company's comm policy, which includes the requirement to use Asana. If someone has never used Asana before, we put them through training for a couple of hours (which is usually all that is required).

@auren @asana 4. I think the most important thing for adoption is that the executive team uses it religiously and that everyone in the company has freedom to create a task for anyone else -- both top down and bottoms up. I insist on asks of me going into Asana tasks so that I can prioritize.

@auren @asana 5. Overall, adoption is at 100% because we insist on it, but also because people find it easy to use once they get the hang of it.