Hi Frank
I'm part of the product team here at Workfront. Thank you so much for your detailed feedback, that is really helpful and provides the team with great insight
Before I respond to your specific questions, let me just preface this by saying that as part of our New Workfront Experience we are pushing to have a more consistent experience across the entire platform, which includes how you interact with Projects, Tasks, Issues and Documents. Therefore, some of our changes are a result of creating a more unified experience. That all said, I realise that some of these have changed the user interface. We definitely want to move to fewer clicks and not increase the time and knowledge needed to get to the relevant information within our system. I'm sorry if the latest changes has not produced the right experience for you and the team
- Updates - It is not helpful to have to click through to the document details page to see ALL of the document updates as we could do before. It will certainly lower productivity for users to click on "See All" and move to a separate screen to do this. >> This is great feedback and we've had similar from other customers as well. The main reasoning here was to have a consistent experience with the rest of the Projects, Tasks and Issues. Our thinking was that if you wanted to "dive deeper" into the update stream then you would potentially want to gain more context to the document which is why we're navigating you back to the details. However, I can completely see where someone would want to stay in the document list and filter through the comment updates without having to navigate away. We are investigating this further to determine if we can introduce a better solution here
- Updates - While it may be helpful to have the "Reply in Proof" button instead of just opening the proof and hitting reply in the proof, we have lost the ability to reply to a Proof Comment without opening the proof. And more importantly, have also lost the ability to tag additional users on responses to Proof Comments (you can only Reply to the original poster in the proof tool). Is there the option of having a "Reply" and "Reply in Proof" option? The change as it stands will result in lost productivity and confusion in our communication process. >> The reasoning that we want the person to continue any comment replies in the same context as where it was made e.g. if it was created in the proof then the reply should be there also. With proof comments you can add additional context such as drawing markups which is not available in standard document comments. So if you just reply directly in the updates you might be missing that additional context and unable to provide relevant / accurate feedback. That said, I understand that tagging additional users on responses is an important part of the feedback process. You are however still able to do that directly on the proof once you select the "Reply in proof" option. If you want to add a comment that's not related to the proof comments then you're still able to do so outside of the proof comment thread.
- Custom Forms - Similarly with Updates section. It now looks like when you click on "add custom form" it takes you to the separate Document Details page and away from the Project/Task/Issue to actually choose which form to add and to fill it out. >> I agree, this approach is not ideal for all circumstances and we will investigate this further to determine how this experience can be improved.
- Custom Forms - Similar to the point above, it looks like you can only see which forms are attached in the Document Summary section, but not the contents of the form. This seems like a huge step backwards as most of our projects include many multiple documents and the extra clicks to the Document Details page to access and update form information is not efficient at all. >> Great feedback, we will investigate and determine how this experience can be improved.
- Document Summary Section - Is there a way in the new user experience now to have the Document Summary selected by default? I know it is only a click to pull this up, but is another instance where we are adding steps to how this worked before. It is possible it is an available setting that I may have missed. >> We actually intended this to be visible by default. The team is currently working through that and will introduce it in a future release
Let me know if you have any further feedback. The team will be contact to discuss your questions in more detail
Thanks,
Etienne
