|
Introduced Error is the addition of intentionally incorrect data into a document or system to enable contributors on a project or process such as technical writers or computer programmers to proceed regardless of technical precision or indecision on the part of responsible managers or subject-matter experts. History This project management methodology was articulated by David Petry, a technical publications manager, in 2010, to describe a means of technical documentation that targets a higher rate of pre-production corrections because knowledgeable reviewers tend to react more strongly to incorrect data than to missing data. The method has since been extended to other fields, including computer programming and a variety of test environments. In a paper presented to Las Cumbres Observatory Global Telescope Network, Petry said, “Missing and incomplete data is often due to content experts who resist finalizing data as long as they are allowed to due to a variety of technical contingencies and job-protection strategies.” In studies conducted at Las Cumbres and at QAD Inc, Petry noted that the introduction of information which content experts have not generated themselves, right or wrong, will result in a concrete, specific responses from those experts about the data, far more often than missing or incomplete data. But this is only true if a content expert does conduct a review. In the absence of a review, introduced errors will tend to result in incorrect outcomes or outputs that can lead to observed errors which in turn can lead to finalized values without the reliance on experts. Applications The Introduced Error method addresses organizational hierarchies and processes in which gaining a final or working decision on wording, defaults, definitions, or values is a cause of bottlenecks. It is used by those in lower echelon or late-in-the-process positions, enabling these individuals to complete their project responsibilities. It is best used in organizations that use peer or technical reviews so that incorrect data is caught. The first uses were in technical writing. In a system where review processes were not enforced, user and training documents for programmers, systems engineers, quality assurance personnel and end users were developed to completion using intentionally incorrect content and data. Each instance was marked in the electronic file using standard listing functions in word processing software and a list and count generated. This number divided by the total word count serves as a rough estimation of content expert reluctance in an organization. During review, if it occurs, corrected instances are removed and unmarked. The remaining quantity of introduced errors divided by the total word count at the time of publication is rough measure of unnecessary design or content. This value may be re-evaluated after modifications resulting from user input. Petry Dish Method There are two forms of introduced error. The Petry Dish Method makes the introduced errors as nominally correct as the author of the data can make them. In this model, content experts may catch the errors if a review is initiated, but those less knowledgeable may not. The Petry Dish Method is so named because a highly-focused and microscopic ‘lens’ is required to catch the errors, as in a Petri dish. The advantages of this method are that, if the program or document, etc., is released, it performs very nearly like the intended document. In testing where reviews were initiated, this method was shown to make the reviewers more attentive and cautious, and they caught more of the errors. Carney Method The Carney Method inserts obviously wrong data - in quantity, measure, type, scope, etc. - so that it will not be missed, even by casual reviewers, such as managers. This is more practical in documentation, but quantity and measure values can often be successfully ‘twisted’ in science data or coding variables. These errors, if not caught during the review process, must be changed to more normalized information prior to publication. The advantages of the Carney Method are that reviewers are shown to be less suspicious of the process. Limitations Introduced Error does not take into account data that is added or approved by someone considered an expert, intentional or otherwise. These are simply mistakes.
|
|
|