Traditionally, systems development begins by defining specifications, clarifying terms, and establishing approved interpretations (Snyder & Cox, 1985). Adhering to clearly defined project boundaries helps to minimize waste during development and proactively resolve potential ambiguities. However, the assumption that system problems are understood solely by developers is flawed. Instead, an integrated, interdependent sequential system with broad support is crucial.

Information system implementation projects often lack critical execution strategies. As Arvidsson, Holmström, and Lyytinen (2014) summarized, realizing an Information System (IS) strategic intent, which involves aligning IS functionality with business objectives, is often hindered by strategy blindness. A lack of understanding of IS governance can lead to resource mismanagement, project failure, low employee morale, and economic losses for organizations.