Lakeside Software officer makes case for SRE in digital workplace IT

The article argues that real-time detection and remediation are not the same as prevention. Even if IT responds in milliseconds, it is still reacting to an issue. Automated remediation may keep an employee from noticing and keep an engineer uninvolved, but recurring problems still carry costs: employees lose time when technology does not work as expected, and IT spends time investigating and fixing familiar conditions.

SRE, which emerged from Google’s approach to running large-scale production systems, applies software engineering principles to operational problems. The article describes Service Level Objectives as measurable reliability targets and error budgets as recognition that no service will be perfect all the time. It says these ideas translate increasingly well to the digital employee experience because the devices, applications and services employees rely on have a direct bearing on whether work gets done.

The article recounts a partner’s request for evidence of emerging risk while it is still at 0–2%, because at 5–10% beyond baseline the service desk will already have lit up. The partner was describing deviation from a normal baseline, not the percentage of employees affected, and wanted enough evidence to spot deterioration before support demand showed the consequences.

Digital employee experience data can expose issues that conventional operational measures miss, according to the article. At a large Fortune 100 insurance organization, the team found that approximately 25% of call-center downtime was effectively invisible to IT. By combining endpoint telemetry with proactive automation, the organization reduced ticket volume by 35% in a year and avoided more than 45,000 tickets through a single self-service automation.

The article also cites a large hospital network where a small number of recurring issues generated a disproportionate amount of service desk activity. Those issues included file synchronization, security services, CPU utilization, network services and collaboration tools. Using endpoint data to identify and address the recurring causes reduced annual ticket volume by roughly 50,000 incidents, with estimated savings of approximately $1.6 million.

The article maps SRE’s concept of toil to workplace IT. Toil is the repetitive operational work needed to keep a service running, and automation can remove much of it from engineers. But if the same remediation keeps being required, the article says that pattern deserves attention. Automation will sometimes remain the sensible answer, while in other cases the evidence may point to an application, configuration, update or another underlying problem that can be tackled more permanently.

PIMCO, the global investment management firm, provides another example cited in the article. Its infrastructure team used endpoint evidence and change correlation to reduce root-cause investigations that had previously taken days to minutes. The article says the speed matters, but so does the ability to understand what changed, isolate the cause and get closer to eliminating a recurring issue rather than repeatedly treating its symptoms.