Several months ago, our team all switched over to using Asana. Before that, some were using Asana, some Trello, and maybe some neither. I believe the switch-over went pretty smoothly and there wasn’t much resistance to using the new software. A few things that we did which may have contributed to the good adoption were:
Before selecting Asana, we asked staff to list all the features they’d like in a task management software, did research to compare a few options, and chose the one that met most (or maybe all) of staff’s requested features
We acknowledged that this is a big shift, it’ll take a few months for everyone to get comfortable with it, but that we expect greater efficiency in the long-run; expressed appreciation for staff doing the work necessary to figure out this new tool; reminded staff that this is the tool which meets most/all of their requested features
Wrote a guide about how to use it (I thought this didn’t seem very necessary, since Asana has lots of their own tutorials and instructions, but given Sawyer’s comment, maybe that helped!)
Together as a team over the first few months, we established conventions about how we use Asana, and documented those as a separate section in the guide (new staff read this guide as part of onboarding)
We held frequent (weekly?) coworking sessions for a little while, where we could ask each other questions about Asana and/or share tips
Several months ago, our team all switched over to using Asana. Before that, some were using Asana, some Trello, and maybe some neither. I believe the switch-over went pretty smoothly and there wasn’t much resistance to using the new software. A few things that we did which may have contributed to the good adoption were:
Before selecting Asana, we asked staff to list all the features they’d like in a task management software, did research to compare a few options, and chose the one that met most (or maybe all) of staff’s requested features
We acknowledged that this is a big shift, it’ll take a few months for everyone to get comfortable with it, but that we expect greater efficiency in the long-run; expressed appreciation for staff doing the work necessary to figure out this new tool; reminded staff that this is the tool which meets most/all of their requested features
Wrote a guide about how to use it (I thought this didn’t seem very necessary, since Asana has lots of their own tutorials and instructions, but given Sawyer’s comment, maybe that helped!)
Together as a team over the first few months, we established conventions about how we use Asana, and documented those as a separate section in the guide (new staff read this guide as part of onboarding)
We held frequent (weekly?) coworking sessions for a little while, where we could ask each other questions about Asana and/or share tips