Hey there Team Asana (@Marie, @Edda, @Matt_Bramlage, anyone else)! I’m just curious if we could get an update. The feedback is still flowing from customers but responses are less and less frequent. I have found this is actually becoming a larger issue for our team, not a smaller issue as it would if it was just a muscle-memory matter.
On a semi-related note: here’s a conversation topic for you and your team. Could you give me an example (an actual occurrence) of when the Asana team rolled out a change, heard negative feedback from customers, and then totally reverted back. I don’t mean tweaked some things based on feedback. I mean that Asana totally reverted back… said “we were wrong,” sacrificed all the wasted hard work to make the change, and took a step backwards to return to how it was and went back to the drawing board. I don’t think I’ve ever seen an example of that in this forum, despite many changes that have brought about lots of disagreement and protest.
So either Asana feels they have never moved in the wrong direction (i.e. they’re perfect), which seems unlikely, OR the team has encountered situations where they had regret, but has committed too much time and energy to go back on a change. Once investing time/energy/resources, it becomes harder and harder to go back… the old “we’ve come this far” thinking. This is very common human behavior but it is also extremely insidious to a group or organization.
I understand and respect Asana sticking to their opinions on many things. Often customers (including myself) do not always see the bigger picture and sticking to unpopular decisions is necessary for good leadership. But logically all people and groups of people are wrong on occasion, and it’s frightening how rarely people own up to that. Hence why I’m curious if I could get 1 real-world example of when this happened in Asana’s history.
Sorry to get on a philosophical soapbox, but this is my recurring gripe and it happens so much, as in this situation and others.