Hi Mark, We're relatively new to Workfront -- been live since Feb. 1 of this year -- and have been using Proof HQ since the beginning. It may just be me, but for my team, the advanced proofing has been a huge success. And, with the exception of the outage earlier this week, I have never had it fail on me. I've included some answers to your questions below. Feel free to reach out to me, as well, if you would like to talk more. Thanks! 1. Training/adoption for our internal clients who aren't WF users. It took us quite awhile to get our clients using the markup tools in Acrobat, will WF Proof adoption be a challenge for them? If your users know how to use markup tools in Acrobat, then Proof will be a snap. The trick will be making sure your users know what icon means what in the tool and that they have a clear process for marking proofs and leaving comments. There are nuances, don't get me wrong, but if you clearly communicate them at the offset, you'll be fine. For instance: Assuming you've developed automated workflows (highly recommended), if a designer submits a proof and your user begins to mark it and comment on it, they will need to 'Make a Decision' to ensure that those comments/revisions make it back to the designer. If they make a comment and then abandon the proof, thinking that their comments will get to the right person, they won't. The alternative is to tag the designer or individuals (who must be in the workflow) who need to see the comment. Are they likely to shy away and just send an email and tell us what they want changed? This is hard to say because everyone is unique in how they respond to something new. In our experience, we've had few detractors. And, most of those stragglers have come around. How did you train infrequent users and did they adopt? Our firm is pretty small in comparison with other companies, so training has been on a 1-1 basis. When I bring a new user on board, I'll sit down with them for 30 minutes and show them around. I initially held a larger training session that was essentially a webinar, that was supplemented by step-by-step guides that I created. Our firm has an extremely high adoption rate. Truth be told, we didn't really give them an option. 2. Can clients download a file (PDF?) to circulate to others on their teams? Y es, they can download a file (PDF or otherwise) to circulate. Can they then upload it again after reviewing? If someone comments in the PDF itself, they could upload the file back to the project, depending on their access level. However, the file would not go back into the workflow. My recommendation would be to have one point-person who is responsible for sharing said PDF with their team. Once they've gathered feedback, that person should enter all comments into the proof and render a 'decision'. This keeps things clean and makes sure that one person is the decision maker. Will the file include any edits they are suggesting? This I'm not sure about. And, are you asking if they file they download from Proof would maintain comments? If so, I'm still not sure. 3. Will we have to redo all of our templates to include WF Proof? Is that an easy fix? We don't work Proof into our project templates. Each designer (the only users on our team who are responsible for initiating proofs) knows the process for proofing out deliverables. When a graphic (assigned via a task) is ready, they create a new proof and select the correct workflow and off they go. I'm not sure how you would include it in a template unless that step was its own task. 4. I saw a few comments from users on the latest update to WFProof and there were some pretty serious issues. I, along with most of my team, have been using the newest Proof interface since it was available, so there was no issue there for us. The only problem that we experienced (and I'm not 100% sure if it's fixed), is that some users were getting an email notification for each comment left in Proof. As you can imagine, if you have 60 comments on a proof, that can be a horrible experience. Other than that, things have been fine for us. Brandon Hamm Bravo Group
