🦄 If Wishes Were Unicorns: Why Asana Might Not Have Implemented that Feature Request (and other thoughts about Asana feature development and product strategy)

Overall, this post seems to be in pretty poor taste. The full saying that the title alludes to is “If wishes were horses, beggars would ride”, but the people complaining about the lack of updates aren’t beggars: they are paying customers.

Those comments themselves come from user frustration. My team has been using Asana for about five years now, and the only somewhat significant update I can think of was the addition of “Markdown shortcuts”, but even that was extremely lackluster. It was hyped up as being markdown support, and turned out to be far less than that. People immediately asked for real markdown support, and were told it’ll be improved, and then the post was locked. Here we are 4 years later and the “markdown” support is the same broken mess it was on launch day in September 2020.

Also, as someone who also has about 30 years of professional software development experience, the explanation of prioritization in the software development process seems very patronizing. Telling me they can’t work on some things because there are higher priorities doesn’t really follow when there have been virtually no improvements for years. I can only assume that whatever they’re working on over there only impacts the highest-priced tiers.

I’d suggest that if you are frustrated by comments asking about features people have been asking about for years, then instead of directing your frustration back at the customers, who are themselves frustrated by Asana, you should direct it back at Asana. If their product managers were doing a good job of prioritization, then there wouldn’t be so much frustration evident in the forums. Merely wishing customers weren’t so frustrated won’t do anything: Asana needs to make some progress on the things their customers have been asking for.

7 Likes