InsuraCorp financial services companies existed as separate entities until, in 2005, its officers contemplated developing InsuraCorp into an enterprise system. The three primary business services at InsuraCorp, individual insurance, retirement services, and group insurance, had been operating autonomously. The idea was to cross-market across the three financial service divisions to create a company that could offer a synergistic financial product and services environment for their clients. When undertaking an enterprise project of this magnitude, InsuraCorp predicted there would be data governance issues. The predominant governance issues involved IT planning (strategy development), implementation (tactic), and the most critical, database viability. When attempting to merge the databases of their three primary financial businesses, several data integrity issues arose. From the beginning of the system merging initiative, InsuraCorp had decided that they would invest in purchased software to accomplish the task. This decision runs counter-intuitively to the plan for cross-marketing, sales, and financial management services InsuraCorp hoped to provide by the centralized database. Implementation of the plan was logistically difficult due to the personal nature of the data being transferred: addresses, common names, and birthdays that are prone to crosschecking problems within a data exchange. Knowing that some of the data was missing or incorrect, InsuraCorp’s project manager’s solution to the redundancy was to extract the data and move it to a “data warehouse” and “publish exception reports”. In other words, put the data in a closet and ignore the problem. Accountability and governance were not factors in the implementation of the system. Ultimately, the goal was to blend the companies to make sales and marketing easier, and supposedly better, for the client. What InsuraCorp attempted to do left their clients private financial information vulnerable with little…