Anonymous error message system
The most efficient is a system in which errors can be entered anonymously and unassignable. For example, the error message for airlines is anonymous (see chapter 6), only the route is announced, but not the date and the flight number.
In this way even the smallest incidents are reported, without fear of consequences and without the danger of harming a colleague.
The more anonymous, the better
Anonymity is not possible everywhere. In some processes, reported errors can easily be assigned to persons.
Nevertheless, care should be taken to maximize anonymity. At a minimum, there should also be the possibility of an additional anonymous error message Company give.
Systematic detection of all errors
The fundamental question a company must ask is how to detect errors. To clarify:
- Which instruments, such as forms and computer systems, are used?
- How extensively should the errors be described?
- How are the errors categorized?
A standardized messaging system
The introduction of a standardized error message system is the most important basis and thus the most important instrument of a positive error culture.
The difficulty lies in the time-saving handling of often time-consuming reporting instruments, which are perceived by the parties as too complex and therefore impractical.
Clear standards such as an input mask, on which date, time, exact description of the error, possible causes and measures taken so far, as well as possible suggestions for improvement are recorded.
Above all, proposals for an improvement of the situation are to be recorded immediately in connection with the error message, since the directly affected employee is currently dealing with the topic and is thus required to deal constructively with the recognition of the error.
Examples of automatic capture
Examples of this are the Toyota Production System (TPS): Andon, an optical production information system that reports the occurrence of a machine error by means of light signs on a display panel, or Jidoka, a self-controlling fault detection system that detects errors and controls or stops machines via sensors.
Good examples of central reporting systems are CIRS (CIRS Medical in Austria or CIRSNET in Switzerland or ASRS in aviation), in which the entered errors of all participating institutions are recorded, processed and made accessible.
Evaluation of detected errors
If all errors and near-errors are reported, an enormous amount of data is generated. These are now systematically prepared and evaluated.
This evaluation should be carried out as centrally as possible in order to be able to filter all available data into meaningful findings.
Important is the subsequent anonymisation, where this is still necessary. Categorization of errors: When evaluating, it is helpful to distinguish the reported errors and events and to assign them to similar categories.
Thus, frequencies can be determined and hazards assessed. This often also leads to error lists, which can serve as a basis for troubleshooting. The employee has only to tick the error already in the list. This makes sense especially in production processes.
Classification into personal or subject-related errors
A decisive categorization is the assignment of whether an error has arisen directly as a result of a human error or whether there are factual reasons and causes.
This distinction is fundamental for an accurate determination of the cause.
Classification into external and internal errors
Are factors that are outside of the company, involved in the development of the error, the division into external and internal errors also provides a valuable and notwenige help in uncovering the causes and resolve the source of error.
With the help of the new networking opportunities with the corporate outside world, new instruments of a culture of error are being developed that are based on even more transparency and openness.
Open Source Model
As an example, we would like to introduce you to the open-source model: The users of a system, ie the customers, contribute to the improvement of a product. They provide data and suggestions that feed into product development.
This leads to an open exchange about undesirable developments. All - companies and customers - are interested in an ongoing improvement.
The customer is involved
They trust each other, the provider makes the customer feel like they are sitting in the same boat and are involved in the product development.
So the customer is not just a consumer, but also a participant. This model is mainly found in software development.
More knowledge - Podcast, PDF download, eCourse or personal advice
Offline download: Download this text as PDF - Read usage rights, Because we do not automatically submit the title of this text for privacy reasons: When buying in "interests" the title register if support is needed. After buying text exclusively Download at this URL (please save).
Listen to Podcast & Download MP3: You can listen to this text for free, as member even without annoying popup, or download the MP3 for a fee - Read usage rights, After the purchase page refresh, then you will find the download link here. Because we do not automatically submit the title of this podcast for privacy reasons: When buying in "interests" the title register if support is needed.
Your eCourse on Demand: Choose your personal eCourse on this or another desired topic, As a PDF download. Up to 30 lessons with each 4 learning task + final lesson. Please enter the title under "interests". Alternatively, we are happy to put together your course for you or offer you a personal regular eMailCourse including supervision and certificate - all further information!
Consultant packages: You want to increase your reach or address applicants as an employer? For these and other topics we offer special Consultant packages (overview) - For example, a personal phone call (price is per hour).