Thanks Tracy! Obviously for this specific point, the wording on the Beta 1 Release Activity notice currently states "You will now be able to select two document proofs within any single document list...". Imagine what sort of commentary you would have gotten if the wording had been changed to "Proofing license holders will now be able to select two document proofs within any single document list...". Similarly if in the video, if Etienne had started out the demo saying, "I'm logged in as a user with a Reviewer license and proofing license, this is the bare minimum I need in order to view the Compare proofs button" -- we would have all definitely raised a red flag to that. Several of us would have started asking why, and wanting to know what the intent was in giving that feature very specifically to the proofing license holders rather than to the reviewers. My question this morning to Skylar was "are we misusing the feature?? What was it SUPPOSED to be used for?" Similar pain points in the past (not necessarily related to feature releases) -- 1) We floundered around for months after we bought Workfront because we were never really clear who was able to tag whom in a Proof. The salesman who demoed the product had been very clear that tagging was possible and that it would help us collaborate in real time. Had we known all the restrictions on tagging (now sort of clearly documented in "https://support.workfront.com/hc/en-us/articles/223451948-Tagging-in-a-Proof-" title="Tagging in a proof">
https://support.workfront.com/hc/en-us/articles/223451948-Tagging-in-a-Proof- ), we would have raised a lot of red flags before purchase. These restrictions make the tagging feature almost useless for us. We LOVE the idea of tagging people who aren't involved with the proof (to pull in SMEs who would normally not be involved)--but sadly, this was not the intent of the tagging feature, and I wish we had known that. 2) We were sometimes confused in when a feature is being released for the standalone Workfront Proof or the integration. (you guys have actually improved greatly on this point. 2016 Leap sessions were very confusing, but nowadays things are pretty clear) Short term fix? I feel like we (the people who have to read the feature releases) have to start giving the proposed new feature a side eye--doing a search on words like "You" and "User" and asking who "you" is and which "users" are being referred to. So maybe one way you can help is to make sure these are all clear. In the latest release activity note, you seemed like you were pretty clear--features are grouped as affecting either administrators or "all users." But two points: A) the feature release content is intermingled (features for admins are intermingled with features for all users) and all feature content starts with some variation of "You are now able to do XYZ". I just don't think it's fair to expect people to scroll back and forth trying to see which features belong to which listicle at the top of the article. B) even if you take a close look at the "all users" list of features, then you can see for example that, allocated to "all users" is the ability to create a project from a template. MANY of us know that in this specific case "all users" means Planner licenses. But for those not in the know, or those who are new, it would be a kinder, clearer thing to say "Planner license folks can now create a project straight from a template." In this way, if they were reading top to bottom, the next feature would say "System administrators can now configure Workfront..." and once again everyone would be quite clear. I don't have many answers for you and this probably isn't even a good solution, but it's all I have! Maybe it can inspire someone else to come up with something better. :) -skye
