As an example I recebtly noted that the Project “Print” had changed.
I took a screenshot 5 june, to show my users how to print, and the very next day it wasn’t valid anymore.
As the function had moved to a submenu.
But on the Asana guide page https://asana.com/guide/help/projects/actions it still shows as being a top level function.

But it’s actually a bit strange, as it is not “inner workings” – the feature is live!
So there should be no reticence in publishing that kind of info.
On the contrary, it would avoid customers’ ire. (live = affects us)

And I’m sure they could find willing curators to update the guide, even if it’s not an open wiki, happy to edit it for each new change.

It seems I might be on my way to opening another topic or two (guide update, curators, possibly something more pointed).
Feel free to beat me to it.

Same here, although I am more interested in bug fixes than anything else. A couple of times I’ve filed a bug report but its frustrating not knowing when it is actually fixed. This allows the end user to test and verify that it truly is now fixed instead of periodically doing a “try and see”, only to find the problem still exists because we’ve had no feedback on its progress. I for one look favorably on companies that share this kind of info and are more likely to stay a loyal customer.