I don’t think a roadmap for individual features is particularly useful, frankly, for a software with as many applications and workflows as this. I think a better strategy would be to actually learn about the existing userbase and see if any unmet needs are shared among wide segments. It’s not at all uncommon to release a product aimed at one audience and find that a completely unforeseen audience has adopted it for a different purpose.
I’d love to see updates take a more thematic approach, for example, surveying users and finding that content managers make up “x” percentage of its userbase, and then finding out how they use Asana along with what features they would like to see added. For example, content managers have lamented the lack of adaptive scheduling and dependencies (which aren’t actually “dependent” in the same way they imply, and are still selectable for subtasks even though they have no effect), among other things. Instead of just adding yet another orphan feature, looking at the workflow of users and seeing how they can better connect the existing features seems like it would add more value with less effort.
The majority of my complaints about Asana do not stem from missing features, but from ones that either lack options other software has, or that don’t operate on their own logic beyond a very narrow scope of applications. The best analogy I can come up with for what I mean is this:
Imagine you need to lift a couch. You get a board and a paint can to act as a lever, and succeed in lifting the piece of furniture. That’s the feature working as intended. Now imagine you need to lift a bedframe, and try to use the board and paint can, but nothing happens because the developers haven’t configured “levers” for beds yet. That’s the kind of ‘orphan feature’ I’m referring to, which works in only one specific context/workflow despite being designed in a way suggesting broader usage.
Again, it seems like so much work to not apply a sort of ‘global logic’ to relevant features and workflows as compared to maintaining and updating all these more-or-less-standalone modules.