Interesting question! Asana is certainly active with development of new service tiers and marketing of the same. There have also been new features on occasion. However, it’s not clear that the opinions expressed in these forums have much effect on development choices. There is a long backlog of universally desired and obviously advisable features that have not seen any progress in the 2+ years I’ve been on this forum. Many of the new “features” are really just requests to fix the poor design directions of past years - like lack of sorting, filtering, global views, and generally numerous failures to use database best practices that have been established for nearly half a century - like normalization. It’s my opinion that Asana has a huge legacy deficit - something like this: https://medium.com/engineered-publicis-sapient/the-database-deficit-how-full-stack-developers-blind-spot-harms-agile-teams-7a1647ac10ea - and are finding complete reworking of their data models a complex and daunting task.
One example is the fact that projects have always needed to be created as a board or a list. Even though conceptually, this is just a difference in view, in Asana they were created as two different entities. People have been begging for years to allow viewing any project in either type of view. It’s actually been worked on for ~~1 year and long promised, and even has been rolling out for months now - though I’ve not had it rolled out to my organization. I believe some users have seen it rolled back.
Even with all the above, we continue to use Asana…our own inertia plays a big factor, especially retraining the org to a new system. Asana does have many good points and its friendly UI makes it low barrier to entry for small teams with limited IT bandwidth. It’s when you try to scale beyond a small group that the downsides start to sting.