Paul Reed — Staff Incident Operations Manager at Chime — delivered a 45:16 presentation titled "The Ironies of A^2 I^2

At QCon San Francisco, J. Paul Reed — Staff Incident Operations Manager at Chime — delivered a 45:16 presentation titled “The Ironies of A^2 I^2,” arguing that modern AI compounds decades‑old paradoxes of automation. Reed said the result matters because advanced automation can simultaneously increase the centrality of human operators while eroding the manual skills and system knowledge those operators need to recover from incidents, raising the risk and cost of outages for builders and on‑call teams.

Reed laid out concrete failure modes and human‑factor observations observed in practitioner incidents. He warned that manual skills deteriorate when unused, that creating effective mitigation strategies requires deep system knowledge, and that the Efficiency — Thoroughness Trade‑Off (ETTO) steers operator behavior during degraded conditions. Those dynamics, he argued, make rare but consequential interventions harder to perform reliably.

Using incident stories labeled “AI‑fueled,” Reed described how over‑reliance on automation can worsen outcomes: in some cases he cited, it doubled recovery times. He connected that increase in recovery windows to the way automation strips context and rehearsal opportunities from teams, so operators lose both the tacit understanding and the muscle memory needed to diagnose and fix problems quickly.

Reed framed these patterns against a wider industry shift in which software increasingly behaves as a safety‑critical system. He said more software professionals now study human factors and system safety alongside traditional operators like pilots and nurses, and he invoked recent large‑scale outages — including examples tied to major cloud and infrastructure vendors — to underline how interdependencies across the Internet amplify systemic risk.

Bridging theory and practice, Reed drew on his Human Factors and System Safety Masters background to translate academic concepts into operational takeaways. He engaged developers, SREs, platform engineers and on‑call staff in the audience to ground the talk in real team responsibilities and positioned incident analysis and systemic‑risk identification as ongoing duties for engineering teams, not one‑off exercises.

His practical recommendations for builders and incident teams focused on preserving operator capability as AI is deployed. Reed urged teams to incorporate human‑factors learning into training, create deliberate opportunities to exercise manual skills, design systems for graceful degradation, and establish clear human — AI handoffs. He said such steps are necessary to shorten detection and recovery windows and to keep control loops resilient as automation expands. The session and an accompanying reading list are available for practitioners who want to explore the incidents, ETTO, and mitigation approaches in more detail.