Engineering underpins almost every national priority, but its education system remains optimised for a world that no longer exists. The discipline is now confronting the limits of incremental change, and the wider sector will soon face the same reckoning. When the pace of system change falls out of sync with the pace of real‑world change, no amount of tweaking will do.
The question is whether higher education can redesign its own architecture before external pressures do it for us.
Higher education loves the language of evolution. It sounds sensible, measured, and reassuringly well-governed: nudging systems along, adjusting an assessment here, a module menu there. It’s the kind of change that fits neatly onto committee papers and doesn’t scare the horses.
The trouble is, evolution only works when the environment changes slowly but engineering is living through a period where the environment has changed faster than the system built to educate its future practitioners. The result is a widening gap between what engineers need to be able to do and what our structures reliably produce. Incrementalism hasn’t closed that gap. If anything, it has helped it widen.
I write from engineering education, but the underlying question – whether incrementalism can meet the scale of change facing higher education – is not discipline‑specific. Engineering simply makes the problem visible sooner, because as a vocational subject the labour‑market signals are sharp and the consequences of misalignment are hard to ignore.
The world has changed faster than the curriculum
Engineering roles have become more integrated, often spanning functions that used to be separate. The work is more interdisciplinary, more data‑rich, and more entangled with societal and environmental complexity. Boundaries between mechanical, electrical, software, and systems engineering have been blurring for years. Automation has reshaped production. AI is reshaping design. Global supply chains are increasingly geopolitical. Net‑zero is non‑negotiable.
Yet most engineering curricula remain structured around siloed disciplinary content. In some cases, this purity is reinforced by the more than 40 professional engineering institutions licensed to accredit degrees. Delivery patterns and assessment models remain familiar. We have pockets of innovation – challenge‑based learning here, a sustainability thread there – but the underlying architecture remains largely unchanged.
This is not unique to engineering. Many disciplines face the same tension between legacy structures and emerging professional realities. But engineering exposes the misalignment more quickly because the world engineers work in is unforgiving of outdated capability.
Formation pathways no longer match the labour market
One of the quiet revolutions in engineering has been the growth of work‑based learning and apprenticeship pathways. Often described as “alternatives” to traditional degrees, they are mainstream (and in many ways “gold standard”) routes into the profession. They integrate academic learning with real engineering practice, developing judgement, adaptability, commercial and societal awareness, and professional identity in ways classroom‑only models struggle to replicate.
Yet our systems still treat these pathways as exceptions. Funding rules, QA frameworks and institutional incentives are still built around a model of learning that happens in classrooms, in semesters, and at a distance from real work. The result is predictable: we under‑invest in routes that build capability, and over‑invest in routes that deliver content. This isn’t just an engineering problem – it’s a structural feature of how we design education for applied professions. If we want capability, not just qualifications, the centre of gravity has to shift toward work‑based formation.
Employers have a role here too. Small contributions to courses or advisory boards are valuable, but they cannot substitute for being part of how professional capability is actually formed. The expectation that universities will produce commercially ready graduates, while students take on £55k of debt, is a system design choice, not an inevitability. If we want engineers who can contribute from day one, employers need to be co‑producers of that capability, not just end‑users of it.
Systems built for stability struggle with responsiveness
Higher education is structurally optimised for stability. Accreditation rewards coverage. QA rewards consistency. Funding rewards volume. Workload models reward content delivery. None of these are bad things – engineering is safety‑critical – but together they create a system where meaningful change is difficult to enact and even harder to sustain.
Incremental change is appealing because it is absorbable: a new module is bolted on, a project week added, a digital tool introduced. But the underlying logic remains the same; the system bends just enough to accommodate the innovation without questioning its own assumptions. This is a sector‑wide pattern – engineering simply experiences the consequences more acutely because the external environment is moving faster.
So what would a revolution actually look like?
Revolution is a dramatic word, and not always a helpful one. I’m not advocating chaos or the abandonment of disciplinary depth. Engineering needs rigour, standards, and the intellectual formation that only higher education provides, but it also needs a system designed for the world we have, not the world we inherited.
A revolution in engineering education would mean redesigning the architecture, not rearranging the furniture. It would mean:
- Capability‑centred curricula, organised around what engineers need to be able to do, not historical departmental boundaries.
- Progression‑based models, where students move forward when they demonstrate capability
- Employer‑embedded learning as a core part of formation
- Assessment that develops judgement, not just reproduction under time pressure.
- Accreditation that recognises the full range of pathways into, and through, engineering.
- QA that is empowered and resourced to support doing the right thing, not just doing things right.
None of this is unique to engineering. Healthcare, computing, design, parts of the humanities face similar pressures as digital and societal change reshapes practice. Engineering simply offers a clear case study of what happens when the system’s pace of change falls out of sync with the world’s.
The national stakes are high
Engineering capability underpins almost every national priority: productivity, infrastructure, manufacturing resilience, digital transformation, and the net‑zero transition. If engineering education does not transform itself, the economy will do it for us through shortages, bottlenecks, offshoring, and missed opportunities.
The deeper question is sector‑wide: if engineering needs a systemic redesign to meet the demands of the next decade, it is unlikely that other disciplines can rely on incrementalism either. The challenge is not to choose between vocational relevance and intellectual development, and this is not a call for the whole sector to become vocational. However, much of higher education is structured around disciplines where vocational formation is not central, and that architecture is now struggling to support subjects whose environments are changing at pace. Engineering just hits those limits sooner. If parts of the university require vocational architectures, then the institution needs to support multiple operating models under one roof.
A sector‑wide invitation
The theme of the Engineering Professors’ Council’s 2026 Congress – Evolution or Revolution – is timely. Engineering education is at a crossroads, and the choices we make now will shape not just our discipline but the wider higher education landscape. The question is not whether change is needed. The question is what kind of change we want, and whether we are willing to redesign the systems that govern how change happens.
Engineering may be the canary in the coal mine, but the air is getting thin across the sector. It’s time to decide whether we keep nudging the system along, or whether we finally accept that the architecture itself needs attention.
