❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

Ancient Rooms, Modern Questions: A Day at the Cambridge Summit 2026

10 November 2026 at 13:21

Sitting in a room that has been part of Cambridge University since the 14th century, eating lunch between sessions on AI, headless CMS and behavioural science, I found myself wondering what conversations had taken place in that same room across the centuries. When the railways arrived. During the industrial revolution. When computers changed everything, and then the internet after that. Each era must have had its own version of this question: what does this mean for how we work, and what do we stand to lose or gain?

That contrast between ancient setting and very modern questions felt fitting for a day that asked us to think carefully rather than react quickly.

Janus and boye attendees sitting a round a round table

The Cambridge Summit is an annual event organised by Boye & Co, bringing together around 30 people from both higher education and the private sector for a day of honest conversation, learning and networking. This year’s event was held at The Old Schools, and I was glad to be there.

Here is what stood out for me.

What I learned last week: PHP, security and more

Presented by Simon Jones, Studio 24

This was the second session of the day, and one I found particularly valuable. It centred on a pair of critical PHP vulnerabilities known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), each rated 9.2 out of 10 in severity. PHP powers roughly 70% of websites worldwide, including WordPress and Drupal, which between them account for a significant proportion of the web, so the exposure was enormous.

What made the story particularly interesting was the history behind it. Signs of one of the flaws had been identified as far back as 2024, but at the time no concrete attack path could be demonstrated and the fix was postponed due to compatibility concerns and limited team resources. It was not until August 2026 that a researcher used an AI model to confirm that unauthenticated remote code execution was possible. OpenAI submitted a separate report on the same issue the same day. Within weeks, exploit attempts were being recorded in the millions.

Patches were released on 21 October 2026. The FBI and the UK’s NCSC both advised that if an immediate update was not possible, organisations should take affected systems offline. Several countries, including the Netherlands, Finland, France, Germany and Belgium, did exactly that, shutting down web services until it was safe to bring them back up.

What struck me about this session was not just the technical detail but the candid account of how it was handled, and in some cases not handled well. It was a reminder that security is not just a technical issue; it is a communication and decision-making one too, and that known risks left unaddressed have a way of returning under worse circumstances.

Making decisions like a leader: a few words on behavioural science

Presented by Nina Dyrberg, BeWaviour

Nina Dyrberg standing presenting on confirmation bias

This was the session that stuck with me most. I went in expecting a familiar leadership talk and came out with a genuinely different way of thinking about how I make decisions.

The session was built around two decision traps that leaders fall into repeatedly. The first is moving too fast: making decisions on the wrong assumptions, falling into confirmation bias where we test an idea with a lens already angled to confirm what we think, or falling into the binary trap where a decision feels like it can only go one of two ways when in reality there are more options available. The second is moving too slow: the status quo bias that keeps us doing what we have always done, choice overload that causes us to stall when there are too many options, and the sunk cost fallacy, the tendency to keep investing in something simply because we have already invested so much.

One practical tool introduced was a matrix for working out what we actually know before making a decision: known knowns (facts we can use), unknown knowns (hidden knowledge we should trust), known unknowns (assumptions we need to investigate), and unknown unknowns (blind spots where we need to get inputs from others). Simple, but genuinely useful for working out why a particular decision feels harder than it should.

The session also addressed procrastination directly. The model was stark: harsh self-talk leads to guilt, which leads to more procrastination. The alternative, self-forgiveness, leads to fewer negative emotions and greater motivation to start again. As a leader, that is easy to overlook both in yourself and in the people you work with.

The slide that has stayed with me most was this:

“If you believe there is one right decision, you become afraid of choosing the wrong one. But if you see decisions as experiments, there is no wrong choice, only something to learn from.”

The practical takeaways were: ask what you actually know, forgive yourself when procrastinating, identify the smallest next step, ask what your future self would do, and plan the decision rather than just making it.

Open health informatics for the digital transformation of healthcare in Ukraine

Presented by John Chelsom, Seven Informatics

This was one of the most striking sessions of the day. It covered how open-source software is being used to support remote healthcare delivery in Ukraine, in extraordinarily difficult circumstances.

It is a powerful example of what open source can do when it is applied with purpose. EdWeb 2 and MyEd are both built on open-source platforms, and hearing how the same principles are being used to deliver critical healthcare services put our own work in a different perspective. It was humbling and motivating in equal measure.

Using AI to understand our work better

Presented by Ben Lee, Instruction

Ben Lee talking beside monitor presenting Using AI to understand our work better

This session opened with a brief history lesson: the 2017 Google paper “Attention Is All You Need”, which introduced the Transformer architecture behind ChatGPT. The key insight from that paper is elegant: every word looks at every other word to understand context. The example used was “bank by the river”, where the word “bank” looks to “river” to know which kind of bank it is. A useful reminder that what feels like intelligence is fundamentally about context.

From there, the session moved to a quote from Greg Isenberg (October 2026) worth sitting with: “We’re maybe 12 months from an agent that watches you work for a week and then does your job.” The slide alongside it made the crucial distinction: AI can see what you do, the steps, the tools, the order, the clicks. It cannot see why. It misses your reasons, what you checked, the times you said “no, that’s wrong.”

That distinction is at the heart of what the session argued: capturing expert judgement becomes the valuable bit. The practical example was building AI agents for pitch review, where the expert’s judgment was turned into a rubric, used to train an assessor agent, and pitch win rate improved from 40% to 60% in a year. The process was clear: understand the work first (interview the expert), write the playbook, validate it, build, test, check, then use it for real. Four of those seven stages require the expert.

The message I took away was that the right question is not “what can AI do?” but “what does the expert know that AI cannot see, and how do we capture it?” Before any agent is built, the session argued for a 45-minute interview covering how the work really runs: the rhythms, the decisions, the dependencies, the knowledge nobody ever wrote down, and where the work hurts. As the slide put it: “You can’t describe work you’ve never been asked to explain.”

This connects to something I keep returning to. If organisations use AI to remove the junior roles that build expertise over time, they also remove the pipeline for creating the people who can answer those questions in the future. The expert judgement that makes AI useful must come from somewhere.

Super, intelligent layouts: headless the way it was always intended

Presented by Markus Schork

Markus Schork standing beside a monitor presenting on headless content to supe rintelligent layouts

The session on headless CMS and intelligent layouts was directly relevant to EdWeb 2 and the future of MyEd portal. The core idea was that layouts should adapt dynamically based on the content that is added, rather than being fixed templates that content is forced to fit.

EdWeb 2 is already designed with this principle in mind to a degree, but this session made me think about how much further we could take it. Making layouts more responsive to what users actually input is something I want to explore further with the team.

Beyond the sessions

Internal view of the old schools gallery where we had lunch

After the formal sessions, we had lunch in a room that has been part of Cambridge University since the 14th century. It is worth taking a moment to appreciate where you are on days like this.

After the event, I joined colleagues from the Cambridge web team at The Eagle, the pub where Watson and Crick famously announced the discovery of DNA. Good conversations continued with the Cambridge University web teams.

The following day I had productive meetings with the web teams at Oxford, which alongside the conversations at the summit gave me a useful picture of how peer institutions are thinking about the development of their web services.

What I am taking away

Three things from this year:

  • Decision-making as a practice. The behavioural science session has given me a more conscious framework for handling difficult decisions, and I want to bring some of that thinking into how we work as a section.
  • Open source has reach beyond our sector. Seeing it applied in Ukrainian healthcare is a reminder of why the open-source model matters and why we should continue to champion it.
  • Ask harder questions about AI. Not whether to use it, but how, and at what cost, including the human cost of removing the roles and pipelines that build the expertise AI depends on.

Back in that room that has looked over Cambridge since the 14th century, I doubt the questions were so different. How do we use what is new without losing what matters? Worth thinking about.

If you are considering attending an event like this, my view is that the value is not just in the sessions but in the conversations between them, and the perspective you get from stepping outside the day-to-day.

UX for real-world higher education – UCISA UX Community Day recordings now available

15 October 2026 at 09:03

If you design, build or manage digital experiences in higher education, the content from this year’s UCISA UX Community Day has plenty for you. The day included a panel discussion, case studies and practical advice from UX professionals, all focused on user-centred approaches in the university context.

As co-chair of the UCISA UX Group, a highlight of my year is planning and organising our annual UX Community Day, which sits alongside our regular webinars. Now in it’s third year, this all-day event is our flagship. It’s aimed at anyone striving to make digital products, services and platforms better for those who use them.

Read more about the UCISA UX Group on our UCISA webpage

Read more about previous UCISA UX Community Days in previous blog posts:

Growing our UX maturity by leading a Community Day for UK higher education institutions

Sharing and gaining knowledge at UCISA’s UX Community Day 2025

Eighty UX HE professionals sharing, collaborating and ideating: The magic of UCISA UX24

Clearly, I’m biased, but here are my top five reasons why this event is worth your time:

  1. It provides a safe-space, non-performative opportunity for higher education professionals to speak and share – to present ideas and work and gain feedback and input – no conference pressure, no vendors or suppliers, just a supportive community ready to listen.
  2. Depending on the UX maturity of your organisation, doing UX in higher education can be lonely at times, as UX practitioners can be outnumbered by other roles. Bringing user-centred folks together to talk openly about their UX work not only fosters welcome discussions, critique and questions, it also provides reassurance, boosts confidence and sparks new ideas to take forward for everyone taking part.
  3. It offers the chance for attendees to build and expand networks and in the process, get real-life practical help from those in-the-know. Not sure how to structure a workshop? Struggling to analyse your research data? Looking for some metrics to show impact? Show up and ask your questions – chances are, someone will be able to assist.
  4. Often said, but people make our universities what they are. Taking time out for this event, to specifically think about the digital experiences of those groups of people, and how we can work to make them better, is the right thing to do and is therefore time well spent.
  5. It’s completely free to UCISA members (which includes most UK universities). Need I say more?

So much for the plug. If you missed attending the event live on 26 September 2026, don’t worry, the recordings are now available. More details below.

This year’s theme spoke to UX trends as well as the broader state of the sector

Our chosen theme for the 2026 community day was UX for the real world: having lasting impact in higher education. This theme served a dual purpose. Firstly, it acknowledged how UX practice in higher education is changing: less by-the-book, more adaptable to the realities of the way things work in the ecosystem. Secondly, it captured the potential for UX to be a ‘north star’ – a prioritisation mechanism to bring clarity and direction to the sector at a time when change often has to happen fast, decisions need to be made quickly and therefore unpredictability is rife.

The theme therefore worked at two levels:

  • Top down (strategic): it reflected a growing move to ‘do UX without telling me you’re doing UX’. In other words, treating UX as part of how the organisation already works, rather than as a separate function.
  • Bottom up (practical): it spoke to the need for UX practitioners to be opportunistic and adaptable in the midst of shifting conditions – for example, moving between short- and long-term priorities, bringing users and designers closer together, and keeping track of successes.

With this in mind, the overarching theme cascaded into five sub-themes:

  1. UX within the machine: Making UX happen relies on aligning with ‘how things work’ in your organisation – understanding how things actually get done in an organisation, and planning UX work to fit.
  2. Playing the long game: You’ve reached the end of the project or the initiative, but now what? Projects are often short term, so how do we keep UX going once they end?
  3. Putting numbers on it: How have you demonstrated the impact of UX in ways decision-makers understand? Making the case for sustained UX means showing its value, including in numbers.
  4. Designing with, not for: Co-designing with students, staff and other audiences – creating a more direct link between user needs and user-centred design.
  5. AI in UX: Beyond the chatbot: AI is everywhere – but how is actually being used in UX practice? Using AI as a tool to support UX work, and recognising its growing role in shaping user experiences.

With the theme set, we went public, we started accepting speaker proposals and opened the event for sign-ups in July, ahead of the event date on 16 September 2026.

The event was met with a positive community response – from the proposals, to the sign-ups to engagement on the day

A real test of a theme is the speaker submissions and the response was strong, particularly for the ‘UX in the machine’ subtheme. It’s always a great privilege to work with the UCISA events team and fellow committee members to select and sequence the sessions and to curate the schedule for the day. We aimed for a balance of themes, talks that would appeal to seasoned UX practitioners and newcomers alike, with a mix of formats. Taking on board feedback from previous events, we also built in time to pause, reflect and interact.

The event attracted nearly 200 registrations from UCISA members, with over 100 people from 49 institutions attending on the day. It was interesting to see a split across job roles of attendees. As expected, UX/UI design and content roles were the best represented. But the audience stretched well beyond them, taking in leadership and strategy, digital learning and education, as well as technical and systems roles. We were also joined by people working in digital experience, engagement and communications and people in library services and data and accessibility positions.

I’ve often found activity in the shared chat to be a good gauge of the success of an online event. On the community day, the Teams chat was lively from the start, with people introducing themselves at the start, then going on to share comments, questions and resources, right up until the event closed at 4pm. Even once the event was over, messages were being exchanged to set up follow-ups, suggesting the day had succeeded in bringing the community together over shared goals and challenges.

Watch the recorded sessions in order, or just pick those of interest

There’s nothing quite like attending a community event live to experience it as it happens and to be part of the conversations in your own way. That said, it’s not always possible to take a day out of the working week, so thankfully UCISA records the event and makes the recordings available through the UCISA Connect portal (free to access for all UCISA members).

Access the recordings through UCISA Connect portal (log in required)

You’ll find the recordings available in two slots – one morning and one afternoon. Underneath the recordings, you’ll also find slide decks provided by the speakers to help you follow along in your own time and revisit specific topics of interest.

Here’s a synopsis of each of the sessions to guide you through:

UX Within the Machine: Making user experience work inside complex institutions (Sam Fanning, Director of Digital Experience at University College London)

Long-standing UX community contributor Sam Fanning shared how UX works at UCL. She covered UCL’s product delivery model, how the digital experience team is set up, and how they measure the success of their UX service. Sam also explored how UX can get involved earlier, and the challenge of managing dependencies between the SaaS products and bespoke builds that underpin many UCL services.

How usable is it, really? When UX evidence starts to add up (Juliana Matos, UX Manager, King’s College London)

Juliana shared her experience of tackling a long-term UX problem: demonstrating impact through metrics. She discussed sample sizes, the familiar ‘five users is enough’ rule, and the difficulties of producing statistically significant numbers. Using the Moodle VLE as a case study from King’s, she showed how the team applied the well-established System Usability Scale (SUS), and why hearing directly from users was necessary to add qualitative depth to the scores.

‘Clearing’ a path through the chaos: transforming operational processes one-on-one (Jen Doyle, Senior Content Designer (Content Operations), University of Edinburgh)

Improving a key stage of the student journey is something anyone doing user-centred work in higher education can relate to. Jen Doyle described how she and her team analysed each stage of the Clearing process at Edinburgh, looking for ways to improve the content and streamline the processes behind it. They were able to make changes and improvement resulting in easier, more efficient updates for staff and a more consistent experience for everyone.

UX within the machine – panel discussion (Chaired by Emma Horrell, UX Manager, University of Edinburgh, Panellists: Sam Fanning, Juliana Matos and Neil Allison)

 Clearly I’m biased (again), but this 30-minute panel flew by and is well worth revisiting, even if you caught it first time round. Sam, Juliana and Neil described what ‘the machine’ looks like in their organisations, sparking ideas for making UX fit. They shared how they prioritise UX resource, show impact, and win buy-in and championing from the top, along with honest reflections on what has and hasn’t worked and advice for people new to the field. If you’ve ever wondered how to get UX applied where you work, there was plenty to take away.

Designing for students: Using quantitative UX research methods to design a new VLE student experience (Adam Ellison, Phil Tubman and Stephen Owens, all from Lancaster University)

The team from Lancaster shared a case study on improving the UX of their VLE, tackling inconsistent structure, content overload and unclear navigation. For me, this talk was a welcome chance to revisit how my own UX Service approached work on Learn, the primary VLE at Edinburgh. It was a chance to learn from Lancaster’s experience, and join a wider conversation about why VLEs deserve more UX attention.

Designing the Digital Journey to Wellbeing Support: Co-creation in Practice (Holly Thomson and Jade Alexander, User Researchers at the University of Glasgow)

Holly and Jade shared how Glasgow co-designed Wellbeing Home, a one-stop shop for wellbeing services, and Support Finder, a self-triage tool, working together with students with lived experience. They described how they used card sorting and a build-your-own homepage activity to work out how to organise services in ways that made sense to students and explained how they tested designs based on students’ real-life needs and scenarios, to ensure every user journey had clear steps for students to follow. They concluded with tips on making co-design work in practice.

AI in UX. Beyond the chatbot (Paul Boag, Boagworks)

UX expert Paul Boag shared practical ways to get more value from user research data using AI. Drawing on examples, he shared how feeding AI forgotten reports, surveys and slide decks on can surface fresh patterns and insights, and can shape virtual personas. He also revealed how AI can highlight gaps, to signal where more research is needed. His talk sparked discussion about the importance of being transparent when using AI to analyse and apply research data.

Exploring AI and the UX process (Madeline Linnell, Website and Application Developer, Oxford Lifelong Learning, University of Oxford)

Madeline shared the process her team at Oxford followed to develop an AI-assisted way for users to discover courses on the Lifelong Learning website. She covered the research process (including use of AI tools such as Google AI and Cursor) the ideation phase (using AI to brainstorm creative ways to discover academic learning opportunities), prototyping (using Google AI to generate interactive screens from static files) and user testing (using AI to analyse the findings), concluding with what the team learned and their plans for implementation.

Workshopping essentials: the fundamental principles for inclusive, democratic engagement and design (Neil Allison, Head of Prospective Student Web, University of Edinburgh)

Neil gave a practical talk which served as a primer on designing workshops. He unpacked when something should be a workshop rather than a meeting or an email, with workshops best suited to collaboration, democratising decisions, generating ideas and prioritising. He explored how to strike the right balance of facilitation to guide people through the divergent, emergent and convergent stages, and shared examples of successful workshops he has run at Edinburgh.

Thoughts, suggestions, reflections? – reach out to me on email

A UXer through-and-through, I take my responsibility of organising a user-centred UX Community Day seriously – therefore I’m always looking for feedback to guide how we do things better. If you signed up for the UX Community Day, you will have received a feedback form. If you didn’t, or the window to complete the form passed you by, you can still share your thoughts by emailing me directly. Drop me a line at ehorrell@ed.ac.uk I would love to hear from you.

 

 

Shared challenges, shared solutions: what I learned at the UCISA Web Services Community Day

13 October 2026 at 13:42

In July, I travelled to Leeds for the UCISA Web Services Community Day, hosted at Leeds Trinity University’s city campus. It was the community’s first in-person event, and the theme was Shared Challenges, Shared Solutions: practical, honest stories from people who develop, deliver and manage web services across higher education.

The room brought together colleagues from the Universities of Sunderland, Birmingham, Leeds, Aberdeen and Edinburgh, with Leeds Trinity as host. Vendors Terminalfour and Zengenti shared tools, trends and time savers for doing more with less. I also sat on the closing panel.

Here’s what stuck with me.

AI is changing how students find us

Piero Tintori, CEO of Terminalfour, opened with how the student journey has changed. Prospective students moved from search engines to social media, and now to AI. There is push back too: some younger people distrust AI summaries, so trust and authenticity matter more than ever. Students still want fast answers, mainly about costs and career paths.

His challenge to the room was simple. Open an incognito browser and search for something like “study engineering in Scotland”. The results vary wildly, and you can’t control them. AI engines draw on many sources and often don’t choose your website at all. Reddit is increasingly treated as a source of truth, which leaves the door open to inaccurate or deliberately poisoned answers. Your analytics won’t clearly show when AI is involved either.

Piero framed his advice as “adopt and drop”.

Adopt:

  • Make your degree finder excellent
  • Write content for AI as well as for people
  • Prune old content, especially PDFs, because AI has no sense of dates
  • Look ahead to structured data (JSON-LD) and llms.txt to point crawlers to a source of truth

Drop:

  • Old or archived content, urgently
  • Over-engineered personalisation projects
  • Chatbots
  • Blind trust in robots.txt
  • Anything you can’t measure

He also noted that some US universities now use general AI tools in place of content quality platforms such as Siteimprove, Silktide, Semrush and Monsido. He suggested a standard may emerge that lets publishers charge AI companies for access to their content.

For any university with a large, long-lived web estate, the message is clear: what you remove matters as much as what you publish.

Putting AI and data to work

Dean Hale, Enterprise Applications Manager at the University of Sunderland, followed with a candid account of building trustworthy AI to process student personal statements.

Richard Chivers and Richard Saunders from Zengenti, the company behind the Contensis CMS, then tackled a problem every university web team knows: maintaining content quality at scale.

Their answer was Agent Skills, an open standard for giving AI tools a clear, reusable set of instructions. A prompt typed fresh each time gives different results. A skill is more reliable for repeatable tasks because it defines four things up front:

  • Task: what the AI should do
  • Context: the background it needs
  • Constraints: the guard rails it must respect
  • Output: the format the result should take

Zengenti has published a set of these skills for higher education content teams:

  • Alt text: write or audit image descriptions
  • Meta descriptions: draft page summaries for search
  • GEO audit: check how well a page performs in AI search engines, scored across five dimensions with a checklist of fixes
  • Staleness audit: flag outdated fees, dates, staff details and statistics
  • Refine for the web: turn raw copy into structured course content

Batch agents run the audits across many pages at once. The bigger idea is a shared skills library that teams, and potentially institutions, can build on together rather than each writing their own prompts from scratch. The skills are free to use and work in tools such as Claude. You can find them on GitHub: Contensis HE Content Skills.

The staleness audit links straight back to Piero’s warning that AI has no sense of dates. If AI engines will happily serve last year’s fees, finding outdated content before they do becomes a priority.

Birmingham: product thinking and knowing your estate

The University of Birmingham gave two talks that fitted together well.

In a lightning talk, Amy Commander, Web Product Owner, explained how her team has rethought the way it delivers web services. Instead of treating the website as a series of one-off projects, Birmingham runs it as a product, built on three principles:

  • Ongoing ownership: someone is always responsible for it
  • Iterative delivery: no big bangs
  • Funded as a product: steady investment rather than project-by-project bids

The team works in two-week sprints with an ordered backlog, user research and a dedicated QA tester. Notably, it does this without a scrum master. Work moves through a simple cycle of plan, build, release and review, and the team releases little and often.

What I liked most was the commitment to continual improvement over big-bang launches. Large redesigns carry large risks, and they tend to go stale soon after launch. Small, regular releases let you learn and adjust as you go.

Later in the day, Billy Fallows, Web Operations Manager, and Rob Fowles, Head of Digital Channel Management, explained why Birmingham started its web strategy with an audit of the whole web estate.

It wasn’t quick. The audit was a manual process, run from a spreadsheet, and took a long time. They kept it manageable by assessing every site against a clear set of criteria:

  • Alignment with the university brand
  • Content quality, flagging sites scoring below 50 in Silktide
  • Accessibility
  • Whether a GDPR statement was in place
  • Clear site ownership
  • Content age
  • Technology compliance
  • Audience size from analytics
  • Website complexity
  • Duplicate content

That evidence now underpins a web strategy built on four objectives and four enablers. The objectives cover audience needs, user journeys, high-impact content and alignment with institutional standards. The enablers cover governance, technology, measurement and the operating model.

Their next steps are to fill in missing data, tighten the criteria, contact site owners about a register of sites, develop policies to support that register, and act on the recommendations.

The lesson I took away is that you can’t set a credible strategy without knowing what you have. An audit is slow, unglamorous work, but it turns a sprawling estate into something you can govern. Ownership, in particular, appears on almost every list like this for good reason. A site with no owner is a site nobody will improve.

Building a content design playbook

My Edinburgh colleague Lauren Tormey, Senior Content Designer, shared how her team builds a content design playbook through a repeatable workshop format. Drawing on content strategist Colleen Jones, she described a playbook as a script for content methods and processes: a collection of “plays” for tackling common content challenges. The idea isn’t limited to content either. The GDS Service Manual, the Atlassian Team Playbook and the GDS social media playbook all work the same way.

Each workshop focuses on one style topic, such as links, and runs in three stages:

  1. Align on best practice. Everyone writes dos and don’ts on sticky notes, adding a question mark to any they’re unsure about. The team then groups similar notes and debates the question marks.
  2. Writing practice. The facilitator prepares a real piece of content that needs improving, sometimes with errors added deliberately. Everyone edits it against the practice the group has just agreed.
  3. Review outputs. Each person reads someone else’s edit, then the team discusses what they did differently and how to align.

Lauren was candid that the review stage often gets squeezed, because the first activity takes the longest. That’s the right trade-off: agreeing what good looks like is the most important part. The format is simple, repeatable and easy for any team to borrow.

The panel: shared challenges, honest answers

The day closed with a panel chaired by Claire Gibbons of Leeds Trinity University. I joined Jenny Tompflitt, Scrum Master at the University of Leeds, and Mike McConnell, Applications Operations Manager at the University of Aberdeen. Three institutions with different structures, and yet our answers were strikingly similar. That says a lot about how widely these pressures are felt.

What is the biggest challenge facing your team?

For me, it’s scale. My team looks after four key web services: the MyEd student portal, our EdWeb 2 website platform, Staff Profiles and Search. MyEd is built on aging technology and needs rebuilding. The website platform keeps growing. Two of the four services need refreshing. All of them need more resource than they have.

More and more of the university relies on central services, so demand keeps rising. Teams also tend to work in silos, solving the same problems separately.

Then there’s AI. Expectations are high across the sector, and there is real pressure to show progress. The challenge isn’t enthusiasm. It’s finding time for teams to properly explore the tools and understand where they add value, before being asked to deliver with them.

How are you coping with doing more with less?

My answer was to sharpen the axe before swinging it. That meant three things.

Streamline honestly. We asked teams to put everything on the table, then rebuilt our priorities from the bottom up. Once that was clear, we invested time in building staff capability and shared the load across sections, so no team solves things alone.

Borrow selectively. We bring in external help for specific pieces of work, but strategic thinking stays in-house.

Make technology work for us. Building services on the same technology pays off. On Pantheon, one update reaches more than 600 websites. MyEd will continue to adopt a headless approach on the same foundations.

The approach is as much about people as technology. When Staff Profiles was delayed, we involved stakeholders in the decision instead of simply announcing it. It was slower, but it built trust.

Where are you most optimistic?

Not the technology. The people, and a shift in how we lead.

Universities may compete for students, but we don’t compete on how we run our web services. That gives us something the private sector often lacks: we can learn from each other, collaborate and share ideas openly. Days like this prove it. I’m also seeing teams move from “launch and forget” to continuous improvement, as Amy described at Birmingham. Tight budgets are hard, but they also push us to streamline and focus on what matters most.

If I had to put it in one line each:

  1. Four services, one team, and no time to properly explore the AI everyone is telling you to use.
  2. Smart technology choices, selective expertise, and people who own the change.
  3. The people coming through, and leadership moving from compliance to commitment.

What I’m taking away

Three things:

  1. Old content is now a live risk. AI engines don’t know what’s out of date, so they will serve last year’s fees as readily as this year’s. Pruning, staleness checks and estate audits are no longer housekeeping. They protect the student experience.
  2. Continuous improvement beats big launches. Birmingham’s product model and our own panel discussion pointed the same way. Own your services, release little and often, and fund them as products rather than projects.
  3. Collaboration is the sector’s advantage. Every institution in the room faced the same pressures: rising demand, flat budgets and expectations around AI. We don’t compete on this, so we can share what works and avoid repeating each other’s mistakes.

Should you attend next time?

Yes. For a first in-person event, the Web Services Community Day delivered exactly what its theme promised: honest stories, practical ideas and plenty of time to talk with peers facing the same challenges. Thanks to Claire Gibbons and the team at Leeds Trinity University for hosting, and to UCISA for organising.

If you work on web services in higher education, join the UCISA Web Services Community and come along to the next one.

Websites are not forever, and neither is fragmentation: reflections from HE Connect 26

The annual HE Connect came to Edinburgh this week, and I had the privilege of opening it before spending two days listening to peers wrestle with the same problems we have. Here’s what stuck with me, from large University web estates to AI recommending (or rejecting) your university before you’ve even said hello.

Coming home to HE Connect

At the end of HE Connect 25 in Manchester, it was announced that the 2026 edition would be held in Edinburgh. I wrote then that I couldn’t wait to welcome colleagues from the UK and beyond.

Reflections from a conference focussing on digital leadership in higher education: HE Connect 25 – Blog post by Stratos Filalithis

On Tuesday 6th of October, digital leaders from across higher education and agencies specialising in the sector met at the Royal Society of Edinburgh, and I welcomed everyone with presenting on “Websites are not forever: what to keep, what to fix, what to retire.”

In it, I followed the lifecycle of a website, from the excitement of launch to the less glamorous questions of maintenance and retirement, and argued that most of our estates are in trouble because we’re much better at the first stage than the last. I also made the case that AI and security have turned forgotten content from an untidy habit into a real, current risk. Furthermore, I had the opportunity to do a 5′ lightning talk going through our work in digital sustainability and testing Artificial Intelligence’s (AI) capabilities in supporting accessibility testing.

A large room hosting approximately 40 attendees sitting in rows of chairs. A man is standing presenting in front of a large screen having a photo of a landscape with sea and forests.

On Wednesday 7/10, I presented a 5′ lightning talk covering our work in Digital Sustainability and testing AI’s capabilities against accessibility testing.

I’ll share more in a separate post, because this one is about what I was most looking forward to: sitting back, listening and learning from digital leadership peers sharing their challenges, experiences and approaches, and discussing with them in an honest, collaborative and constructive way.

HE Connect 26 programme and speakers

If there was one common thread, it was this: nobody designs fragmentation. It happens to us as “a result of disconnected and, sometimes, very sensible decisions”. The interesting question is what we do about it.

Coherence, not centralisation

That line came from Samantha Fanning, Director of Digital Experience at University College London (UCL), and it might be my favourite of the conference. UCL is a similar size to the University of Edinburgh, having around 50,000 students and 17-18,000 staff, so it was hard not to see our own estate in her slides.

Her advice was simple: don’t focus in superficial approaches to fix “the front door”, like a homepage. The issue is not the door, it’s the house itself. Part of UCL’s approach is a 3-space model, which covers all levels from trusted, owned and governed centrally, institutional knowledge and services, owned and governed centrally; to local knowledge and innovation. The principle to take away is to create shared foundations before seeking control, make ownership visible, and aim for coherence, not centralisation. UCL backs this with their own design system and experience framework. A well researched and supported design system is fundamental to implementing effective digital governance, and establishing one is one of our own objectives here in Edinburgh, too.

Johannes Nygaard, Chief Digital Advisor at the University of Copenhagen, showed what web estate transformation looks like. In 2023 they had one site serving everything from recruitment to science communication: 130,000 pages, 900 editors and 1,200 subsites. Two stepping stones, a new CMS and a new governance structure, signed off by the university’s senior management, included simple core principles: Every site targets specific external audiences, and who the most important are, resources should be prioritized based on importance of interaction and traffic, usage of templates for sites and pages. Perhaps the most controversial one in a University setting is that pages and sites with very little traffic would be closed, but it’s also the difference between a managed web estate and a digital museum.

Both of these sessions struck a chord with our work in Edinburgh, especially since the contain some of the possible answers to our own fragmented web estate challenges, and I have been encouraged to see what takes place in UCL and Copenhagen.

When AI is the front door

Piero Tintori, CEO of Terminalfour, brought numbers justifying the rise of AI usage in selecting a University programme: About 7% of prospective students go to an AI chatbot first for a specific institution request, with 18% of then having removed one from consideration based on an AI-generated result only. Still, 73% of parents name the college website as their top source, and 43% of applicants still start on a university website compared to 13% who start with AI. Most people still visit and trust our websites more than AI, but the latter covers the ground faster, and we will need to keep checking these numbers to keep track of if, and how fast, the prospective students and parents decisions change.

A very interesting sharing was that old content pollutes AI answers. Archived and outdated pages get used as sources, results vary from session to session, and the parts most likely to be wrong are the ones that matter most, like entry requirements, fees or key programme information. Piero’s answer was a move to content engineering: modelling, metadata, schemas and separating content from design, with AI helping to reduce the effort involved by ensuring the published content is accurate across all the web estate. My action will be to expedite action to archive and retire heritage content.

It’s clear that, especially in the age of AI, effective web governance and coordination is the key to address the evolving challenges and risks that carries a devolved web publishing environment.

Why is digital so hard?

Kris Purdy, Head of Digital Experience at the University of Glasgow, asked exactly that. His answer was even though digital sits in the middle of business, user and technology: “we built the digital, but we didn’t build the organisation to support it.”. Glasgow’s challenges are very similar to our own: many websites without a named owner, and uncertain plan for decision making, consolidation and retirement. Our own estate is larger, but the problem is exactly the same one, and I am very happy working closely with Kris to share how best to address these.

I really liked the mention of the “missing link” between strategy, which sits at board level, and delivery, which sits at team level. The defined step between approval and development, which translates strategy into “how”, is often the most critical part to unlock effective change, yet is missing either due to lack of funding, availability or prioritisation within our organizations.

This workshop triggered my interest a lot since I wanted to hear what the delegates had to say, especially those representing agencies as there could be insights directly related to our own web estate journey.

Governance is about people (again)

One unsurprising common theme across all sessions and informal discussions was that people is the catalyst and enabler to any change. This is not a technology challenge and has never been. Its fast evolution, though, like AI currently, amplifies the risks of not having a coherent and effective governance structure, alongside the appropriate technology.

This was a key takeaway from June Shannon’s and Paul Leigh’s sessions, both from the University of Limerick, too. In a very similar note, Helen Robertson and David Jones from GAIN Higher Education in their session, “What does your frontline know before your numbers do?”, also made a very good point: the person closest to the problem is the one closest to the solution. Finally, I thoroughly enjoyed Lucía Tornero González’s, who travelled from Madrid, about how Universidad Pontificia Comillas is approaching the graduate experience, creating everlasting moments for them and their families.

A big thank you to Janus Boye, who organised and facilitated the conference, and to every speaker for being so open about what works and what doesn’t. If any of this sparks a thought, a challenge or a question, I’d love to hear from you. Use the comments below, or get in touch directly at stratos.filalithis@ed.ac.uk.

Digital Leadership in Uncertain Times: What I Learned at the Boye and Co Group Meeting

Last month, I attended the Boye and Co Digital Leadership Group meeting at the Royal College of Surgeons in London. The group exists to connect digital leaders across organisations so we can learn from each other’s challenges and avoid mistakes others have already made.

The turnout was smaller than expected. Last-minute cancellations meant the group was more intimate than usual, but that actually made it better. More time for real conversation. Better questions. The kind of peer learning that doesn’t happen in bigger conferences.

Here’s what stuck with me.

On CMS Migrations: You’re Not Alone in This

Sam Hope-Evans at Soundcloud shared the start of their journey moving from a vendor to OpenSource CMS. What struck me wasn’t the technical choice, it was that they were asking the same questions we’ve been asking at Edinburgh: Is our current system giving us what we need? Can we move without losing everything? What does discovery look like when we’re under pressure?

Using AI in their discovery phase to build prototypes and get buy-in from stakeholders quickly without spending valuable time developing prototypes. When they asked me about our Drupal 7 to Drupal 10 migration, I realised how much we’ve learned that’s worth sharing. The pitfalls (data quality, stakeholder fatigue, scope creep). The wins (getting to a modern platform, being able to move faster). The ongoing question they’re wrestling with: cloud-hosted or on-premise?

If you’re thinking about a CMS migration, the lesson is this: talk to people who’ve done it. Not vendor reps. People in organisations like yours who’ve lived through it. That peer learning is invaluable.

On Legacy Systems: The Long Game

Mahesh Patel at The Royal College of Surgeons shared how they consolidated from 100 separate CMS instances down to one Umbraco system. They’re also grappling with medical data systems that need overhauling. How do you start looking at legacy infrastructure when you’re managing multiple competing priorities?

This resonated deeply. We’re managing four services simultaneously across the university. Our website platform EdWeb 2 was a significant architectural shift: we rebuilt from Drupal 7 (which used organic groups to simulate subsites within a single installation) into Drupal 10 with 160+ separate websites built on a single codebase. When we push updates, all 160 sites get them automatically. It’s modern infrastructure, but we’re still evolving it.

MyEd is different. We’re managing the legacy system in production while simultaneously starting a parallel modernisation project to rebuild it from the ground up with Drupal at the heart. That’s not a simple upgrade. It’s building the new while keeping the old running. Staff Profiles is coming next. The question of ‘how do we tackle these transformations without breaking what’s already working?’ is one I’ll been trying to figure out for years.

Their approach resonated with me: be clear about what needs to move first, understand the data, plan for the long game. Don’t try to solve everything at once. That’s exactly what we’re doing: one service transformation at a time, while maintaining the others.

On AI: The Uncomfortable Conversations

Simon Jones at Studio 24’s presentation on the ethics of AI pulled no punches. And it’s worth repeating what they said, because it challenges the hype.

AI is being sold as a solution to everything. But the reality is more complicated:

The real costs are often invisible:

  • Financial: AI companies are running at a loss. Most aren’t profitable. You’re investing in something that hasn’t proven it’s sustainable and it’s becoming more expensive than developers.
  • Human: Data taggers in developing countries get paid little wages. Communities live near data centres can strain local resources (AI consumed 21% of all electricity in Ireland in 2023). The environmental cost still unknown.
  • Creative: Copyright issues (Authors suing OpenAI over copyright infringement (https://www.bbc.co.uk/news/technology-66866577). Bias in training data and Quality dropping as AI trains on itself.

The harms are real:

  • Phishing attacks and security risks are on the increase.
  • Misinformation and ‘AI slop’ being generated which users are believing.
  • Bias in training data and system prompts.
  • Filter bubbles and reduced trust – AI starts to mimic the user.

But there are genuine opportunities:

  • Understanding large codebases and content
  • Speeding up routine tasks
  • Research and discovery
  • Accessibility (tools available like ai that focus on inclusive models)

The key question Simon posed: Before you adopt AI anywhere, ask yourself:

  1. What’s the business value?
  2. Is it high-risk? (Chatbots, for instance, can be high-risk and not actually helpful.)
  3. How important is accuracy?
  4. Who benefits? Who could be harmed?
  5. How can you test it?
  6. If it goes wrong, how do you give people recourse?

This matters because AI FOMO is not a strategy. Just because everyone’s talking about it doesn’t mean it’s right for your specific problem.

What I’m Taking Away

Three things:

  1. Peer learning beats everything else. The group exists because we’re all managing similar challenges in different contexts. The value isn’t in vendor pitches or abstract frameworks. It’s in hearing from the Royal College of Surgeons about consolidating systems, from Soundcloud about CMS choice, from Studio 24 about navigating AI responsibly. You can’t get that in a conference. You get it from peers who are living it.
  2. The unglamorous work matters most. CMS migrations, legacy system consolidation, data quality. These aren’t flashy. They don’t make headlines. But they’re the foundation of everything else. The organisations doing well aren’t the ones chasing every new trend. They’re the ones making deliberate choices about their platform and sticking with them.
  3. Be cautious of cost, all kinds of cost. Financial, human, environmental, security. When you’re evaluating any new technology (AI included), understand the full picture. Ask the hard questions. Don’t let FOMO drive the decision.

Should You Attend Next Year?

Even with lower attendance, this was worth my time. I came away with real insights, real connections, and a clearer sense of how other digital leaders in the UK are navigating the same pressures we are.

If you’re leading digital work in a university or similar organisation, find peer groups like this.

❌
❌