# Getting Started Actions

**URL:** <https://forum.asana.com/t/getting-started-actions/83981>\
**Category:** Ask the Community\
**Created:** [19 May 2020 18:21 UTC](https://forum.asana.com/t/getting-started-actions/83981 "2020-05-19T18:21:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Bernie\_Orelup](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/bernie_orelup/32/46893_2.png) [@Bernie\_Orelup](https://forum.asana.com/u/Bernie_Orelup)\
**Post date:** [20 May 2020 04:53 UTC](https://forum.asana.com/t/getting-started-actions/83981/2 "2020-05-20T04:53:24Z")

</div>

Hi @Jake_Frasier, congrats on the new position! I would recommend checking out : “Creating an Asana Adoption Plan & Establishing Asana Conventions” in the onboarding training , it is definitely worth a read. [Help Your Team Adopt Asana | Product Guide • Asana Product Guide](https://asana.com/guide/team/onboard/change-management-strategy)

It focuses on first establishing “The Why” around why Asana is being implemented with your team. You then really want to let the processes which will run through Asana to define the expectations around its use. Here is another forum post which talks a bit more on this topic: [Best Practices for general employee USE of Asana](https://forum.asana.com/t/best-practices-for-general-employee-use-of-asana/71301). Hope this helps!

---

_[View the full topic](https://forum.asana.com/t/getting-started-actions/83981)._
