{"id":131,"date":"2026-09-28T11:13:25","date_gmt":"2026-09-28T15:13:25","guid":{"rendered":"https:\/\/blogs.mathworks.com\/engineering\/?p=131"},"modified":"2026-09-28T11:13:25","modified_gmt":"2026-09-28T15:13:25","slug":"from-outputs-to-processes-my-thoughts-from-sefi-2026","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/engineering\/2026\/09\/28\/from-outputs-to-processes-my-thoughts-from-sefi-2026\/","title":{"rendered":"From outputs to processes: My thoughts from SEFI 2026"},"content":{"rendered":"
\n
<\/span><\/div>\n
The<\/span> 54th SEFI Annual Conference<\/span><\/a> brought <\/span>more than 600 <\/span>engineering educators <\/span>to the Czech <\/span>Technical University <\/span>in Prague this <\/span>September, under the <\/span>theme <\/span>“Engineering Education for Humanity in a Challenging World.”<\/span> I <\/span>came back with a <\/span>better grasp of the <\/span>problems our educator <\/span>colleagues face, and <\/span>with new <\/span>collaboration <\/span>opportunities to <\/span>explore.<\/span><\/div>\n
How do we protect the productive struggle that builds competence when a student can offload it to an LLM (e.g. creating materials, code, reports)? How do we teach which systems are worth building, not just how to build them? “How do we keep verification a real skill when the output almost always looks right?” What are the fundamental skills an engineer needs to have moving forwards? I don’t have clean answers… and frankly, I don’t think anyone does. Not <\/span>yet<\/span>. But many of us in the community are working on it!<\/span><\/div>\n
So, here are three threads that stayed with me:<\/span><\/div>\n
<\/span><\/div>\n
1. AI in teaching… but which AI, and for whom?<\/span><\/div>\n
Unsurprisingly, AI was everywhere. I did notice a mismatch I don’t think the community has fully internalised yet: <\/span>the way we talk about AI for teaching <\/span>does not mirror<\/span> the way practitioners <\/span>actually use AI<\/span><\/a>. <\/span>That’s certainly true of my own work, and of the engineers I talk to across industry.<\/span><\/div>\n
Model-Based Design together with agentic engineering are increasingly part of engineering practice in many fields, but they’ve barely crossed into how we talk about <\/span>teaching <\/span>and how we introduce these to students. To me, that gap between the AI in the practice sessions and the AI in the pedagogy sessions is the conversation worth having next.<\/span><\/div>\n
Tanya Morton’s<\/span><\/a> (MathWorks) demonstration of applied agentic workflows in Engineering practice resonated with the audience. Also, there was an audible gasp from 500+ people when she said “I reproduced a numerical experiment from my PhD in an afternoon”. <\/span><\/div>\n
In the industry panel session the room was asked to name an idea that had inspired them, the answer looked like this:<\/span><\/div>\n
\"\"<\/img><\/div>\n
Conversely, AI misuse remains a problem for many academics. By misuse I’m trying to encapsulate ideas of academic integrity, cognitive offloading, over-reliance that erodes the fundamentals, and other failure modes. But if misuse exists, there is also “appropriate” use. The most compelling suggestions weren’t about clamping down; they were about raising the bar… designing challenges that push students <\/span>further<\/span> than LLMs can comfortably take them. <\/span><\/div>\n
Loved the line from<\/span> Prof. Claire Lucas<\/span><\/a> during the panel discussion:<\/span><\/div>\n
“The risk is not that engineers are replaced. The risk is that we hold on to the wrong parts of the role. Ultimately, our responsibility remains the same: Did we design the right system? And did we design the system right?”<\/span><\/div>\n
Another framing that captured this well:<\/span><\/div>\n
“We need to shift our focus from outcome to the process in education” <\/span>– Prof <\/span>Warren du Plessis <\/span><\/a><\/div>\n
\"\"<\/img><\/div>\n
With AI in the loop, the final artifact is not a reliable proxy of understanding. As I have discussed before in EERN and other fora, artifact generation is now cheap. Assessing the thread that has led to such artifacts is perhaps a better proxy for understanding and engineering judgment. Shifting our attention from <\/span>what students produce<\/span> to <\/span>how they got there<\/span> is exactly what keeps them active participants rather than passive validators.<\/span><\/div>\n
\"\"<\/img><\/div>\n
2. Industry engagement is having a moment<\/span><\/div>\n
Industry\u2013academia collaboration ran as a through-line across the programme, most visibly in the Continuing Engineering Education working group and in the workshop hosted by <\/span>Rola Saad<\/span><\/a> (UCL & University of Sheffield) & <\/span>Pilar Garc\u00eda Souto<\/span><\/a> (UCL) , myself & <\/span>Marco Rossi<\/span><\/a> (MathWorks), and<\/span> Bridget Ogwezi <\/span><\/a>(Ansys).<\/span><\/div>\n
\"\"<\/img><\/div>\n
The workshop was a highlight. We explored “Co-Creating High Value Academic-Industry Partnerships in Engineering Education,”. We dug into the practical questions that usually get glossed over: what successful collaborations actually look like, what forms (modalities) they can take, what the real barriers are, and, most usefully, how to remove them. Personally, the prep was half the fun. We were up late on Sunday, ironing out the details. I felt like a student again!<\/span><\/div>\n
A paper capturing the discussion is on the way, and I’d recommend keeping an eye out for it.<\/span><\/div>\n
3. Project- and challenge-based learning<\/span><\/div>\n
Tying the first two themes together, project-based and challenge-based learning were clearly where a lot of people’s thinking has landed. It’s not hard to see why. If the goal is to keep students in an active, creative role, and if industry relevance is the thing everyone wants to strengthen, then challenge-led approaches sit squarely at the intersection. Give students a hard, authentic problem, and some concerns start to take care of themselves.<\/span><\/div>\n

A resource worth bookmarking: the SEFI Skills Handbook<\/span><\/h2>\n
One of the milestones of the week was the launch of the <\/span>SEFI Handbook on Teaching Transferable Competencies and Skills in Engineering<\/span>.<\/span><\/div>\n
49 chapters, 155 contributors from 56 institutions and professional bodies across 23 countries and five continents, brought together by editors Gillian Saunders-Smits, Lynn Van den Broeck and Thies Johannsen. It’s organised into five parts spanning context and challenges, practical implementation, assessment, curriculum-level integration, and evaluation. It works both as a reference to dip into and as a practical manual to teach from. <\/span><\/div>\n
Several chapters discuss project-based learning as the vehicle for developing transferable skills, which for me, is how we transition from assessing outputs to process<\/span><\/div>\n
You can find it here: <\/span>books.open.tudelft.nl\/home\/catalog\/book\/266<\/span><\/a> (DOI: <\/span>10.59490\/mt.266<\/span><\/a>).<\/span><\/div>\n

Wrapping up<\/span><\/h2>\n
If I had to compress SEFI 2026 into a single thread: the field is wrestling, productively, with how to keep<\/span> the engineer<\/span> central in engineering education.<\/span><\/div>\n
One more thing: this was my first time at SEFI, and it was one of the most welcoming and insightful communities I’ve had the chance to be part of.<\/span><\/div>\n
See you all next year in Sheffield!<\/span><\/div>\n<\/div>\n