Macbrea said:So, for anyone that says, "Couldn't they see the simple error on page xxx!" Well, probably not after staring at it for a few hundred hours.
I respectfully disagree.
Finding errors is a matter of technique and due diligence, not a matter of just reading.
You could, for example, assign each person on the team to check the entire book for errors.
You then have a committee which rates the severity of the error (1 = simple typo such as "their" instead of "there", 2 = chart disagrees with text, etc.). The first person to report an error gets credit for it (Email date/time stamp). You keep a master list that is updated each day in order to reduce the number of repeat Emails.
You then give incentives to the people by giving out prizes for people who get a certain number of points worth of errors. You give prizes to the original Editors for the points per page staying under a certain level.
The prizes are things like paid hours off from work, etc.
The point is that reviewing a document is tedious to do. Hence, a good mechanism is to give incentives to people to do it. But, if you have a day in your schedule for every 40 pages in a product where most of the team is reviewing the book and they get rewarded above and beyond for doing a good job, 90% of the errata on the current WotC site would not be there. IMO. YMMV.
Now back to your previously scheduled topic.