Iteration Fatigue!
We create learning modules and online ed for a number of government agencies. We deliver storyboards that often are reviewed by 6-12 people with various levels of expertise or subject matter expertise. As a result, we are managing huge numbers of edits per iteration. How are folks managing version control? What do we need in place to keep things clean as they are being passed upward for review, back down to us for correction and back up again for the various pieces (often the storyboard and slides?
We're drowning and could use some structure tips? Many thanks
2 Replies
Aside from comments that are only about fixing typos and similar errors, all comments should be considered "suggestions." Just because one reviewer wants something said or done a certain way doesn't mean others will agree.
If possible, establish one person who has "final say." After collecting comments from the group, that person should go through the review file and indicate which comments to implement. This helps solve conflicts before you make the edits. And, hopefully, it'll help you avoid re-revising the same piece.
If there just isn't one person who has that power, it might help to set up a meeting to discuss comments and decide which suggestions to use.
Be sure to stress at the start of each review cycle what people should be looking for -- and what has already been approved (and will, therefore, cost extra to revise). That's especially important for audio and video scripts.
Hi Marguerite. That's a very frustrating but also not uncommon challenge many of us face. It's time-consuming for us to reconcile all those edits. Plus, the agency is spending a lot of time on reviews and may be able to get a similar level of accuracy for a lot less work.
I'll second everything Judy mentioned and add on to her list: