I’m creating an Asana Implementation Plan and Timeline for my organization. The resources provided by Asana (Webinars, Team Onboarding Checklist, Powerpoint Templates, etc.) are fantastic and an integral part of my implementation plan.
Through this process, I still have one question that is keeping me from solidifying my implementation plan.
That question is: When creating the “Why Asana” statement and assembling an adoption alliance and following the steps in Asana Way of Change, should I do this uniformly through multiple trainings for my entire organization? Or should I break my training down by department/team so that their “Why Asana” statement is specific to their team and the training will be more customized to their needs and usage.
Obviously conducting the training by team will be more work and somewhat duplicative for me, but the perceived benefit is that it will be more specific and intimate to how that specific team will use Asana. Am I overthinking this though and could accomplish the same results training the entire organization in multiple training sessions?