Exceptions are events that cannot be handled by an information system by following normal processing rules. Exceptions arise for two main reasons: flaws in system design and post implementation changes in the system domain. Only few exceptions should arise in an information system serving its user community well. In practice, this is rarely the case and exceptions are sometimes rather common even with routine processes. In this paper, an exception‑based approach to evaluate information systems is presented together with practical examples of its use. The benefits of the analysis to information system management are elaborated on.

The purpose of information systems post‑evaluation ought to be to improve the use of systems. The paper proposes the use of narratives as a tool in post‑evaluations. The potential in narratives is that they can convey meanings, interpretations, and knowledge about the system, which may potentially lead to action. The paper offer three main suggestions: 1) evaluations should form the basis for action; 2) narratives makes evaluation more relevant; and 3) post‑evaluations should be done with the aim of improving use. Narratives should be viewed as a complement to traditional evaluation methods and as a way of making evaluation more formative and thereby moving away from the more common summative perception of evaluation. The conclusion of the paper is that narratives can advance IS evaluation and provide a richer evaluation picture by conveying meanings not included in traditional evaluations.