Useful deviations for deviation management information systems: From pulse methodology to a generic description

Abstract

We learn from our mistakes, and for companies these mistakes are deviations (aka. problems, disturbances, issues, hiccups, mishaps etc.). Every captured and solved deviation creates new knowledge. Not capturing this knowledge, in lean terms, is a waste of created value. A way of capturing this knowledge is to record and manage them via a deviation management information system. The case company uses digital pulse methodology to do this task. But which deviations should be recorded? Or more precisely, which deviations are worth being recorded? The lack of clear answer to these questions, as seen in this case study, can make companies unable to capture the knowledge of minor deviations. In order to solve this problem, this paper answers what deviation is and which deviations should be recorded (i.e., useful deviations), from pulse deviation management methodology point of view. In addition, further implications of the results are discussed towards creating a generic definition from the pulse methodology specific one.