Hi Asana team,
You’ve recently announced some great new features-- in the forums, in today’s blog post, and during events.
I’d like to make some suggestions for how you communicate these features to help us manage our teams’ (and our own) expectations and to reduce the work about work that these announcements generate.
- If a feature is not 100% rolled out, the relevant Asana Guide article should include a prominent disclaimer at the top to indicate this. That disclaimer can be removed when the feature goes to 100%. For example, my teams don’t currently have access to the updated My Tasks or read-only links. Yet those articles don’t mention the phased roll out, leaving people to wonder what’s wrong with their version of Asana.
- Similarly, the Vimeo integration announced today looks exciting. But the “Video messaging in Asana is coming soon to all users” language on the integration page is buried in the middle of the page and not differentiated in any way. Do I have it? Do I not? Should I click the install link?
- If a feature has significant limitations, please mention that in communications. For example, the Clockwise integration mentioned in today’s blog post looked super exciting. But it only works in Google cal. Writing “our new Clockwise integration for Google Calendar” would have told me that there’s no need for me to go to the integration page to have a look, only to discover that this won’t work in my client’s Microsoft365 stack.
Small issues, yes. A few minutes saved here and there adds up. This is all about clear communication to reduce work about work (to use Asana’s catchphrase).
Thanks for reading and for considering these suggestions.