The Need for Enterprise Systems Engineering
Many modern enterprise IT systems fall far short of the ideal of operating as fully integrated wholes. In many instances, this is the result of too much focus on sub-system optimization and not enough focus on overall system performance. This situation can often be brought back into alignment through an increased focus on enterprise systems engineering.
Publication Date: 18 January 2024
Modern enterprise IT systems are not single monolithic entities, but rather dynamic, interconnected networks of sub-systems, each of which has a specific function to perform. Ideally, these sub-systems all work in concert to provide the user with a seamless experience akin to that of operating a larger single system. In practice, however, this is often not the case.
Many enterprise IT systems fall well short of the ideal of providing the user with a seamless operating experience. Instead of functioning as single comprehensive wholes, these systems betray what they actually are, poorly designed assemblies of ill-fitting disparate parts.
The failure of modern enterprise IT systems to operate as comprehensive wholes largely stems from poor systems engineering. Systems engineering is the formal field of engineering that focuses on the design, implementation, and management of complicated systems. The primary responsibility of a systems engineer is to optimize the overall performance of a total system, and this often requires trade-offs in the performance of system sub-components.
Systems engineers work alongside sub-component technical experts to determine the best configuration of system components to optimize overall system performance and meet end-user needs. Both sides of this relationship are needed to produce high-performing systems. Systems engineers rarely possess the depth of technical knowledge required to determine the best detailed sub-component configuration for a system, and sub-component experts often lack the understanding of overall system requirements and how sub-components interact required to determine performance trade-offs. Working together, however, systems engineers and sub-component experts possess the full set of information and skills required to develop well-balanced, optimally performing systems.
Many organizations have the right technical experts in place to appropriately handle the development of the sub-components of their IT systems. However, many of these same organizations lack anyone in the role of Enterprise Systems Engineer, overseeing how all of the sub-components come together and are balanced to create a seamless, cohesive overall system that meets user needs. One only needs to look at the org chart for most IT departments to see that this is the case.
Most IT departments are organized by functional area or application. Such departments have a section of staff for their CRM, a different section for their HRIS, another section for reporting, one more for security, etc. Each section of staff is typically led by a Senior Manager or Director level person, who in turn typically reports up to the CIO. In this type of organizational structure, cross-sub-system oversight often only occurs at the c-suite level. Staff at this level of the organization often do not have the technical skill set or time required to appropriately serve as the systems engineer for the overall IT system.
Organizations can overcome the deficiencies of the typical IT department described above by incorporating the role of Enterprise System Engineer into their organizational structure. This role should be responsible for designing and engineering the overall, top-level IT system for the organization, and ensuring all sub-systems and similar system components are appropriately configured and balanced to optimize overall system performance. Ideally, the role of Enterprise Systems Engineer should be a 100% technical position, with no line management responsibilities, and report directly to the most senior IT management person (CIO or similar).
The performance of many modern enterprise IT systems could be significantly improved through increased focus on overall system design. To bring this about, IT departments need to increase their systems engineering expertise. Hiring and supporting dedicated Enterprise System Engineers is a great place to start.
Recent Posts
Rules Should Not apply
Some organizational rules are critically important to keeping people safe from harm. Organizational leaders should ensure these rules are always followed. Other organizational rules exist to help staff know what to expect and to keep operations running smoothly. Making project teams working on critical change initiatives follow these rules can often do more harm than good.
The Importance of Traceability
Many software development projects waste time and resources creating system functionality end-users do not want or need while failing to deliver things end-users have specifically requested. Often poor traceability practices are to blame for these failures.
How and When You Communicate Matters
Most organizations understand that communication can make or break a project. Nonetheless, few organizations actually effectively communicate with staff and stakeholders about key initiatives. In particular, many organizations wait too long to communicate with staff and stakeholders and use horribly ineffective channels when they finally do communicate.
It is So Shiny! I Need to Have It!
It seems like every few years some new, must have process or piece of technology sweeps through industries. When this happens, it can very difficult for leaders of organizations to resist the urge to jump on the bandwagon and adopt the newest thing, even if doing so might be in their organization’s best interest.
The Most Important Aspect of Change Management
It can take a lot of time and effort to complete all of the work required by many formal change management methodologies. If an organization has the resources to complete all of this work, it is often very beneficial to do so. However, if an organization does not have the resources to do this much work, significant gains can still be made by focusing solely on the most important aspect of change management.
You Might Also Like
Rules Should Not apply
Some organizational rules are critically important to keeping people safe from harm. Organizational leaders should ensure these rules are always followed. Other organizational rules exist to help staff know what to expect and to keep operations running smoothly. Making project teams working on critical change initiatives follow these rules can often do more harm than good.
The Importance of Traceability
Many software development projects waste time and resources creating system functionality end-users do not want or need while failing to deliver things end-users have specifically requested. Often poor traceability practices are to blame for these failures.
How and When You Communicate Matters
Most organizations understand that communication can make or break a project. Nonetheless, few organizations actually effectively communicate with staff and stakeholders about key initiatives. In particular, many organizations wait too long to communicate with staff and stakeholders and use horribly ineffective channels when they finally do communicate.