Operation: Review / Proofread
I changed it to work flow that "other writers" also participate in article review. (Reference Episode 571: Business Improvement in Website Operation (Part 1))The writers interact each other "comments that lead to skill improvement" such as "opinion on the structure" or "alternative idea for headlines or title", while "point out mistakes to be corrected" such as typographical errors or errors in names or dates.
"Editors" has reduced the time spent on reviewing articles or instructing to writers, so that he can have time to think about "ideas for new feature" and to hold "study meetings".
At those "study meetings", actual mistake examples are reported, and discussed. actual mistake examples are reported. The steady improvement in skills will lead to 'productivity improvement'.
Challenge: Holding for Long Period
However, for the writers, it may be a problem that chances of reworking on sent back work are increased, rather than jobs of proofreading are joined.In particular for a rookie writer, cases where multiple articles simultaneously come back to the Step of "2x. Rework" also occurred. And, in such a case, it becomes a situation that "time to review articles written by other writers" can not be taken...
Hmm, I think that it is better not to allow staying, by setting a deadline date and time on "3. Check" so that forcibly advance to the next Step.
[Article Proofreading-Time limitation]