Reclaiming Rigour | The Impact of Agentic Workflows on Systems Engineering

Send us Fan MailThe Epistemological Crisis of "Move Fast and Break Things" and the Agentic SolutionI. The Problem: The Legacy of "Move Fast and Break Things"The Paradigm: For over a decade, the software development industry has prioritized velocity and rapid iteration with the mantra to "move fast and break things". This focused on immediate execution and feature shipping over extensive architectural planning and long-term maintainability.The Fallout: This ideology has caused a "slow-motion disaster" across global digital infrastructure, resulting in poorly performing, finicky legacy systems. These systems are burdened by high costs to replace and massive security vulnerabilities.Calcified Fixes: Undocumented, temporary fixes have, over time, "calcified into permanent, load-bearing architectural walls," frustrating replacement efforts.II. The Demand for Rigor in Critical SystemsThe Critique: Organizations like the International Council on Systems Engineering (INCOSE) argue there is an irreconcilable conflict between pure agile executions and the rigorous demands of critical systems engineering.Life-Threatening Failure: In safety-critical domains (e.g., aerospace, medical devices, energy grids), the high defect rate of hyper-agile environments is unacceptable; lack of rigor results in catastrophic, life-threatening failure. For example, INCOSE noted a poorly calibrated ventilator could destroy a patient's lungs.The Balance: The historical difficulty was balancing commercial demand for velocity with the ethical and operational mandate for safety. Rigorous systems engineering (extensive documentation, verification) was often viewed as an archaic bottleneck.Modern Philosophy: The industry is moving past reckless abandonment, aiming to create environments that are "safe to fail," where failure triggers continuous improvement and root cause analysis.III. AI's Initial Impact vs. The Agentic ShiftEarly AI as an Accelerator: Initial generative AI coding assistants worsened the crisis by acting as hyper-accelerators for the existing "move fast" mentality. They increased code volume but failed to improve structural rigor.The Oversight: Early autoregressive models lacked persistent memory and holistic architectural awareness, enabling engineers to "break things faster" by producing code that lacked non-functional requirements like systemic security and compliance.The Agentic Paradigm: Agentic workflows introduce a fundamental paradigm shift by using a multi-agent coordination model. AI acts as a control plane, orchestrating cross-team work, maintaining long-term contextual memory, and autonomously managing traceability.The Potential: Agentic systems have the architectural potential to reintroduce "deterministic rigor" into software engineering, potentially reconciling the chaotic speed of the modern industry with the stringent, verifiable demands of traditional systems engineering.