Managing knowledge in business requirements identification

This paper reflects on experiences when traditional IT approaches were used to design large IT systems and ended in failure. The main reflections focus on the reasons for system failure and how they relate to the diversity of knowledge, managing knowledge, and the understanding gaps that may exist between the business and the system developers. The study reveals that the understanding gaps mainly result from lack of knowledge of business operations on the developer side, matched by lack of technical appreciation and knowledge on the user side. To help address the knowledge‐gap problem, a practical approach employing soft‐systems, diagramming and set mapping techniques is proposed and described.