Business System Owner
Business System Ownership (BSO) is under represented in the cannon of IT methods. The focus of system ownership in published best practice is primarily geared towards technical system ownership or operational user involvement in system management processes. Furthermore, the transition of IT systems projects to business ownership, post systems launch, is focused primarily on project closure activity. In practice project closure can be undertaken to the detriment of planning for on-going system success. Legacy systems present a particular challenge to IT departments in terms of ongoing business engagement. Typically there will be an under representation of business managers at the right level of the organisation able to provide the required strategic direction and focus required by IT departments to support and maintain systems. As a result, IT can become the de-facto “owners” of the system, discharging their technical responsibilities, but often (understandably) not undertaking many (business) tasks that underpin the future success, even viability, of the system. At best a lack of engaged business owners can result in a potential misalignment of IT resources and priorities. At worst, long-term system viability itself can be compromised by a lack of effective business system ownership as cost control, data management, security, end user training and business process alignment can all drift as systems “age”.