Hi @Crystal_Alifanow and @Sebastien_Levesque
In other posts I gave some advices from my experience, maybe you can find some ideas:
Hi @Mark_Nattress ,
@Marie Thank you for the mention
After I started Asana in my company a year and a half ago, we have 200 licenses today. Asana’s deployment takes time and it’s a rich experience managing that from the beginning.
So like you, I first trained the people to whom I introduced Asana, and through word of mouth, I quickly had 20, then 30 … and then too many people to train. So, I did advanced training to a few people who could carry the idea of a deployment of Asana within…
As mentionned at n°4, we have created a global team as you did @Sebastien_Levesque . Today we just use it to make sure everyone has access to a quick training project, but we don’t use it to send communications. IT guys communicate regularly on all the tools, and we can’t send seperate info just for Asana.
Another tip: if you’re a admin of your organization then you can download a csv file with very useful informations as “last login date” for instance. Every week, I analyse the csv (I created an Excel to analyse it) and I have statistics on the use of each licence, and I can filter by site, by departments, … it’s very useful to detect where you have to make effort to deploy Asana.
From my experience, mentors must be: voluntary, motivated, proactive, organized to help each other, able to explain the vision and not just the tool technically. This mean you have to organize the team, train, share, discuss,… and this takes time.
In my opinion motivation is the key, because any mentor will necessarily have colleagues among their team who will be refractory to Asana, and he will have to know how to react and continue to believe what he does.
Today I have built a team of 17 peo…
We use Asana on several sites, in several countries, so I have a mentor on each site. The deployment of Asana was by word of mouth so the difficulty was to quickly find a mentor every time a site started using it. But it is necessary, because I am convinced that without mentor deployment is impossible, or it must be imposed hierarchically but it is not too team spirit or collaborative.
So you have to find the right candidate among people who just discover Asana, not always simple … Then you hav…
To make people adopt Asana, you can also show them that you can do many more things than just following projects, for instance:
Hi,
You can use a board project to make a wiki.
For instance it could be something like this:
[image]
And when you open a task, you get detailed information.
We have created such a wiki in my company and it is very useful. In the tasks, we filled in the format of the logins, the format of the password and all additional information necessary to book a hotel, a car, … We also have a column containing useful links for all the employees (training, directory, …).
The project is visible to eve…
4 Likes