Hi everyone! Looking for some advice and best practices on onboarding teams to the proofing process. A lot of us are experienced WF users, but using the proofing process is new to our team.
We have our designers owning the proofs and setting up the workflows (due to volume of work) on most projects. All of us are finding the process to be pretty complicated and glitchy. We are trying to use automated workflows that include all the relevant users/roles/etc. pre-set to make it very simple for us.
What are some things you all did to make the process easier and more straightforward for the teams? What tips, tricks and workarounds do you use to make the system work for your team?
Some specific issues we are struggling with are:
- Controlling access to the proofs when it is not a user's turn. (Private stages only seem to hide the comments, not the proof itself)
- Dealing with the "Workfront" stage that is created whenever a user looks at a proof.
- Creatives needing to make a decision on their own proof when they are an author or moderator. This holds up the next stage.
Thank you in advance for advice!
