Chevron IT Engineering should be built on a strong foundation of technical expertise, with at least 95% of its workforce being capable of coding and designing software vs this SAFE agile cr-p. Without this, the efficiency of application support and change-driven projects will suffer, leading to sluggish decision-making, misaligned priorities, and a lack of real innovation. IT should not be a management-heavy environment where non-technical roles dilute the engineering culture—just as in a hospital, where 95% of staff, including leadership, are former doctors or nurses who deeply understand the field.
A simple yet effective way to assess technical capability is by examining contributions to SHIELD and GIT. If an individual has no track record of scripting (VBScript, Ansible) or coding in languages like Python, Java, or C#, they are not truly an engineer but rather a coordinator relying on others to execute the actual work. This is a recurring issue, particularly with senior Application Engineers who delegate tasks to Software Engineers while taking credit for technical contributions they don’t make themselves.
To maintain a high-performing IT organization, there should be a clear standard: No contributions in GIT, no technical footprint in SHIELD—no job. By enforcing this, Chevron IT can cultivate a workforce that is truly hands-on, engineering-driven, and capable of delivering real technological impact rather than operating as a layer of management disconnected from the technical work.