For the text selection: I am finding that on an 8.5x11 page at full page view, I have a high probability of missing the first character in a paragraph that I am trying to select. I think it's just getting used to the new cursor? But it is going to irk users here because all we do is select text all day long. For the providing feedback question--Good question and I'm going to answer very generically for historical record: it depends on my level of distress. If I am very distressed, I will use every step below, otherwise I will pick and choose. [the speech bubble thing is still pretty new to me and I don't know whether that replaces step 1, or what it does.] 1) Standard operating procedure in the past has been to report issues to Support. I hardly ever go this route, and it's really more to report something that definitely is not working as expected or to ask if something is working as expected. The workflow adopted by Support to troubleshoot an issue is often not quite the direction I need to go in, so we are often at cross purposes here. I also feel that Support tends to be a catch-all for everything so it's more difficult for me to get traction in specialized cases. Lastly, I feel that Proof is less well-supported than other features and more likely to trigger a canned response as a result. 2) CSM: Workfront Proof and our experience of it is crucial to my team's success, and if anyone were to feel very strongly about this as well, my advice to them would be to start escalating up through their CSM. This is because at the very least, everyone has a CSM--their one connection into Workfront, which can lead them to connect with other relevant parties. Your CSM should be able to for example, evaluate your concern and determine your next connection point (e.g. connect you to the Product Manager for Proof, or speak on your behalf, or set you up in a team meeting or...). 3A) Using Community to network: Additional to this set of features about to be released: Have you seen Trae's post in the Global Discussions area? Trae Winterton is the new UX designer and was offering blocks of time for people conference in with him and talk to him about what they liked about the Workfront UX and what they didn't like. My concerns with the new release all revolve around a feeling that the new UI will be less efficient to use than the old, so I hopped on Trae's calendar to talk specifically from a UX perspective. I highly recommend that if there is something UX related in Proof that you feel passionate about, that you do the same. If Trae hears enough voice coming out of the Proof group, he will spend more time here accordingly and we can only benefit from better UX design. 3B) Using Community as your voice: simply by discussing your concerns on a public forum, you can catch the eye of Workfront staff who are reading this and can amplify your concerns to the right staff (for example, the Community manager, support techs and Product have all been caught from time to time, reading and answering posts). Your concerns are also read by other Workfront users who can confirm/validate your concerns and report up through their chains (their CSMs and their network contacts). -skye
