Designing the Engineering Environment, Not Just the Engineer: Cognitive Foundations for Sustainable Systems Engineering Practice
Abstract
Why do systems engineering practices degrade under pressure, and can the working environment be designed to prevent it? People attend to the signals they trust, and trust follows feedback. A delivery deadline offers clear criteria and immediate consequences, while a skipped review may cause no visible problem for months, so under pressure attention shifts, rationally, from process quality to delivery. This precision-weighting account makes process drift a property of the engineering environment rather than a failure of individual discipline. The environment here means the persistent system of tools, processes, governance, and information flows within which a team works. Two results follow. First, competence can be embedded in the environment itself, in templates, automated checks, and structured workflows. The paper calls this embedded competence designed cognitive reserve and argues that, to a good approximation, environmental and individual contributions to a team's spare cognitive capacity add up separately. If that approximation holds, and practice quality rises with spare capacity, the environment alone sets a floor on practice quality, whoever is doing the work. Second, a leverage framework groups the model's environmental quantities into four categories of intervention and shows that, when lever effects are separable, combined interventions are never worse and almost always better than any single one. The framework complements ISO/IEC 29110 and ISO/IEC/IEEE 15288 by explaining why some prescribed practices survive pressure and others drift. A two-year study of a nine-person firm, where an automated pipeline and a shared visual alert kept 88 of 90 dependency vulnerabilities patched within 24 hours of disclosure, grounds the framework in practice.