Written by Joseph Omann, Training Specialist for RoboHead
For many of us, effective Review management is a crucial part of our workflow and ensuring the right people are included at the right time during the review process is essential. When you use RoboHead, you have the ability to adapt your account’s set up to work with the way the team prefers to work. There are two common ways that customers choose to set up their reviews. I like to call them the ORMS and MROS Methods . Both methods have their own benefits and knowing when to use these methods is an important part of effective review management.
Do you ORMS?
The ORMS Method, or One Review with Multiple Stages, allows users to create a single review that would include multiple stages within it. These reviews can include as many stages as needed and each stage can be customized to include different participants for each stage. This method of Review management is very useful when your review process includes different participants or review teams during different stages of the process
For example, I have a review where an image must first go through an internal review with my marketing team before it gets sent to someone for a legal review. With the appropriate add-ons in RoboHead, we can take it a step further and add a stage that includes the external client where they would provide their feedback and ultimately approve or reject the material.
If I want the stages to advance based on what’s happening with the review, I can have the stages advanced when any or all of the review participants provide their feedback or indicate their approval. This way, I don’t have to manually start the review’s stages, RoboHead can do it for me. However, I can still advance stages manually if I want, which you may want to do if you’re new to this method and want a little more control over the process.
When to MROS
The next method of Review Management you might use is MROS Method, Multiple Reviews with One Stage. Some might consider this method the more traditional approach to review management, where we set up reviews that would represent the other phases of our review process, but that might be because that’s how it was done before we could set up stages within the review.
This process is helpful when you want to handle the file types or stages separately and want each to have its own review. The MROS Method is also helpful when the different reviews are tied to specific predecessor tasks in the project schedule, this method makes it easier for us to manage those different reviews that are tied to either other tasks or even other reviews in the project. Lastly, the MROS Method is helpful when we want to create a separate review for our comments/feedback and request approval types of reviews.
It’s a Win-Win
There are benefits to each of these approaches. The MROS method allows us to treat each review as a separate entity, which makes it easier for me to tie them to predecessor tasks and other reviews. The ORMS method allows us to create a one-stop shop for all of our review work, where multiple files, versions, teams and feedback is all in one place.
Those of you that have had training with me might remember me stressing the importance and convenience of project templates and how they can really speed up the project creation and management process, but I’d like to stress that for reviews as well. Take the time to build up your review process within your project templates, regardless of the method you use, the time spent setting it up will be time saved later on.
Put RoboHead to work for you.
Joe Omann | Training Specialist
Joe has been with Aquent Cloud for almost two years with 10 years of experience as a software instructor. In his free time, he enjoys fishing, cooking, working out, playing video games, and spending time with his dog, Roxy.
