An Asana community member recently shared with me an interesting rule:
“Clients I’ve worked with have gone so far as to say that people are only responsible for doing work that’s been assigned to them in Asana (i.e. they can freely ignore all other requests)”
After years of helping teams and companies succeed with Asana, I have realized that this rule is actually a good thing!
Because the adoption of a collaborative tool depends on the commitment of all the involved stakeholders.
Because all it takes is a few colleagues who continue to send emails or fail to document their progress in Asana, for your processes to stall…
Because any recurrent action by 10% of the stakeholders risks wasting the resources of the other 90%, and even represents a risk of snowball effect towards the rejection of the tool.
Then… yes, whatever the tool you have decided to implement in your core process, a strong rule can make a huge difference in the adoption by your team(s) or company.
But too many organizations or managers still don’t commit, and just hope for the best…
What do you think ? Do have a rule?