What is the "Find-Fix-Verify" pattern, as related to the process of doing editing/spellchecking/debugging, etc.?
Where is this pattern best described?
What are some advantages and disadvantages of this pattern?
closed as too broad by Snowman, MichaelT, gnat, Thomas Owens♦ Jul 15 '15 at 20:00
There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.
It seems to be a workflow pattern for crowdsourcing, first described in this paper and used with some success by Zappos to improve the spelling and grammar of product reviews on their site.
I guess the "pattern" is a simple division of labor:
Makes sense (the find/fix division probably improves overall speed, and the verify step is always needed for crowdsourcing), but not really all that impressive an idea...