❌

Normal view

There are new articles available, click to refresh the page.
Yesterday — 17 November 2026Main stream

Scottish Web Folk 2026: a canny, reflective and honest conference

17 November 2026 at 09:00

I’ve had the privilege of attending the Scottish Web Folk conference for the last three years and this year’s event was as informative and candid as always, tackling the topic of ‘Human vs Machine’.

At other conferences and in other industry presentations, excitement about what the machines, specifically AI, can do, often whips up a don’t-get-left-behind fervour. But at this event, I think it would be fair to say that the machines were being viewed with a canny, human eye. We are deep into our new AI era and have an increasingly solid understanding of its possibilities and parameters for safe use in web.

We’ve been here before

In his keynote speech, Andrew Millar from the University of Dundee kicked off the ‘Human vs Machine’ discussion by looking back at points in our industrial history where technological leaps had forced change in the labour market, and then made valuable the associated, human, skills that would correctly manage the new technology. The printing press, for example, made redundant scribes and copyists, created a need for typesetters, and had the knock-on effect of requiring judgement and authority to manage the wider dissemination of the printed word. When computers arrived in offices, the filing clerks that were able to shift from paper to software found their analytical and decision-making skills could usefully harness digital categorisation and reporting. Not long after inception, the internet brought new levels of digital publishing reach, and the associated friction between volume and credibility, but the human vs machine tension has taken a new turn with the introduction of AI-generated web content and AI search.

What I took from the keynote speech was not just that we’ve lived through technological change and adapted, but that we’ve been incrementally building the human muscle required to manage the current technological era where AI is ever more dominant. Judgement, authority, analysis, decision-making and credibility are going to be central to managing AI into maturity.

Highlights of the day

My thoughts were focused on advocacy and responsibility as the conference unfolded. What do we already know about wielding our new technologies well (or facing the fall-out afterwards)? A few sessions in particular stood out.

Just because we can doesn’t mean we should

Stratos Filalithis from UoE and Kris Purdy of the University of Glasgow gave an ‘unscripted’ presentation that shared their frustrations of uncovering enormous legacy web estates. Both Universities, beyond their central platforms, had experienced a two-decade boom in affiliated web publishing without fully centralised or localised content management.

Stratos and Kris shared their strategies to build an accurate picture of their Wild West estates, and then spoke of the challenges ahead of defining ownership and instilling governance to create a supported and managed herd. Not just ‘unscripted’, but ‘unfinished’, the honest, unpolished session offered no pat answers but was a resounding cheer for the humans that tackle backlogs and runaway technologies every day. Collaboration, sharing and never accepting defeat are still singularly human approaches.

We already know how to write for AI

Under-managed, Wild West web content poses a risk to reputation because it potentially serves redundant, out-of-date or incorrect information. Well-managed content, however, seems to be largely AI ready, so it’s heartening to hear that existing skillsets are still valuable here.

Paul Costello and Rob Allen from Numiko showed in their work for the University of Oxford that the findability strategies that have served SEO are still central to GEO (generative engine optimisation; optimising for AI chatbots like ChatGPT or Claude) and AEO (answer engine optimisation; optimising for AI search).

Nick Daniels, Katie Spearman and Mel Batcharj from the UoE UX team presented core approaches to writing for AI, and these are already embedded in existing content design practice. Clear, concise content, meaningful headings and links, and accessible text all create AI-friendly content. If you missed the talk at Dundee, and the session at the UoE, their blog is well worth bookmarking for actionable takeaways.

June Content Improvement Club: Is your content AI ready? – Website and Communications Blog

We have to design technologies for operators as well as end users

As technology and its associated processes mature, we have to design for its operators as well as its end users. This is high on the agenda for me as service manager for the University’s web platform, supporting our internal user community to deliver content for their external users.

Lauren Tormey’s session set out to apply design practice to the processes of an internal team creating user-centred content for UoE Degree Finder. In incremental stages, she workshopped a playbook with an already expert Prospective Student Web Team to

  • stress-test existing content guidance
  • uncover new contexts where ‘If X then Y’ had not yet been defined
  • empower the team through live editing workshops so that everyone was equally experienced in applying the styles as defined in all contexts

With major revisions overdue on our self-service resource, the EdWeb 2 Hub, I have direct takeaways from this session to recreate our existing content stylesheet and editing practices. The platform has evolved significantly in the 18 months since the Hub was initially published, but the team updating the Hub while also supporting the user community day-to-day is tiny. Workshopping our existing styles and processes to update the content might feel like a diversion under our current time pressures, but it’s also an opportunity to stress-test our content practices and invest in the team. It’s important that we are equally and consistently skilled at managing updates, whether working at volume during intense platform evolution or in a more settled pattern of rolling revisions.

Final thoughts

In his keynote speech, Andrew Millar quoted an episode of Doctor Who where an AI bot was nudging the world towards Armageddon. The Doctor observes that it’s not the machine that’s the problem, but the pressures and choices around it.

As professionals working in the higher education web space, it’s our responsibility to employ that canny, human eye to embrace the technologies that benefit us when used correctly. Are we using them because we should or because we can? Are we thinking of the legacy that our actions now will leave? What knowledge have we already accumulated that can inform our use of new technologies?

And how do we ensure that everyone using our technologies, whether operators or end users, is supported and protected from pressures to do more faster so that collectively we all contribute to the successful maturation of a new technology? I came away from the conference with the sense that as long as we keep sharing our experiences of past, current and new technologies, and are honest about our challenges and approaches to managing them, our choices can be positive.

Before yesterdayMain stream

Just do it for me? Balancing human and AI input in content improvement

6 November 2026 at 14:07

Working with student interns and contributing to the Drupal community, I’ve experimented with AI in various  tools designed to support content improvement. I reflect on what I’ve learned about peoples’ preferences for engaging with AI tools and consider wider design challenges for web content to support co-browsing.

Writing good quality, user-centred content has always been a challenge, and accordingly, a suite of tools evolved to address this; Hemingway, Grammarly and many more. With their ability to learn patterns and predict word sequences, the advent of LLMs provided a new direction for content improvement. Where previous tools had used fixed rules, algorithms and formulas to flag content problems and score sentences, LLMs changed the playing field as they were able to be prompted to rewrite and create text and to adapt words and sentences not only in line with fixed rules, but also aligned to different interpretations of style.

The UX Service’s content design course, Effective Digital Content, and our ongoing Content Improvement Club meet-ups are both designed to help staff publishing digital content for the University. It’s been encouraging to see a positive uptake for both training formats, however, we realise we can do more to help staff publish the best quality content they can, and to this end, for the past few years it’s been a privilege to support a series of interns in the UX Service to look at how we can innovate and apply AI to the persistent challenge of writing good quality, user-centred content.

Thinking beyond – embracing the spirit (or grasping the nettle, depending on how you look at it) of AI innovation, it’s sensible to note that, more broadly, the browsing landscape of the web is increasingly shifting to include AI agents as well as humans, giving cause to consider what using AI to design content to be consumed by AI might look like. That’s the subject of another blog post (or several).

For now, as I begin another phase of work with a new student in the role of AI and UX Innovation intern (Viktor Sharha), it felt timely to pull together what I’ve learned so far.

Designing, creating and editing content happens in various ways

When designing any user-centred assistive features, a good place to start is the current workflow or user journey people adopt to achieve the task in question. In other words, to look at the stages content editors currently go through to make sure their content is as good as it possibly can be.

One of my earliest research tasks when I joined the University was to usability test the Editorial Style Guide, to find out how publishers used it to keep their content consistent in EdWeb. This work gave me insight into the type of workflows publishers followed to get compliant content published. Some publishers worked in Microsoft Word, using the in-built spelling checker for typos, and cross-checking against a printed-out copy of the style guide for University-specific errors before pasting content into the EdWeb body text. Others went straight to EdWeb, checking their content line-by-line with a PDF version of the guide. Others relied on colleagues giving their work the once-over before pressing publish. Some used Grammarly and Hemingway, some didn’t.

Overall, there wasn’t a dominant content-publishing workflow, with unified friction points waiting to be alleviated through a standard user-centred design process. Instead, there were varied approaches, habits and ways of working which people had adapted over time to suit their specific circumstances and to address the areas they found difficult as individuals. Tools were used at different stages of the process, and to a greater or lesser extent depending on personal preferences.

Therefore, designing content improvement tools isn’t one-size-fits-all

It follows that, since people follow different pathways to create, design and edit content, tools to assist this process need to be developed in different ways to suit varied preferences. Since 2025, interns in the UX team have prototyped our own different content improvement tools to test with publishers, and we’ve also tested open-source tools that exist already, developed within the Drupal community. From our testing and research, we found pros, cons and nuances associated with different tools. The summary below pulls together detail of the tools and how they compared.

Tool 1: Drupal Editoria11y – no AI, flags errors in the editing interface

Editoria11y is a Drupal module built by John Jameson from Princeton University that automatically checks content inside the editorial interface. It was originally designed to catch accessibility issues, but it can be configured to check content against other rules too, such as institutional style guide conventions.

What it does and how it works: Editoria11y checks content as authors type, and also on previews and published pages. It includes an indicator bar to show how many issues are on the page and has inline markers to show where each issue is, as well as a dashboard summarising site-wide errors. When an issue is opened, a pop-up modal explains the problem and suggests a fix.

What worked well: In tests, publishers were able to make sense of the inline markers and understand how these related to the indicator bar for the whole page. They liked the tracked change visualisation in the pop-up modals, and were able to work through successive modals, accepting or ignoring the suggested changes.

What needed improvement:  Some publishers found the number of markers overwhelming, and since the pop-ups covered the text, it was difficult to judge each recommendation in context. In the pop-ups, some of the rule descriptions used formal grammatical terms (such as ‘ordinal suffixes’) which were unfamiliar to some publishers meaning they were confused about the problem to be fixed. Since rules were applied mechanically, there were instances where errors were missed, or where awkward fixes were suggested (such as swapping ‘1st floor’ for ‘1 floor’ due to straight removal of the ordinal suffix) – these degraded publishers’ trust in the tool.

Read more about what we found testing Drupal Editoria11y

Embedding the rules: What we learned UX testing a style guide helper tool built with Drupal Editori11y

Tool 2: ELM-powered content design chatbot – with conversational advice

This tool was developed by student Mostafa Ebid during a 2025 summer internship. It connected ELM, the University’s AI platform, to EdWeb2, so publishers could get help with their content by conversing with the University’s suite of LLMs without leaving the Drupal editing interface.

What it does and how it works: This tool sits in a chat sidebar next to the main Drupal editorial interface and offers three modes: Write Content, Design Content and Proofread. In response to a user prompt to improve content, it activates an orchestration of agents (each with specific tasks such as checking the style guide, structuring pages, profiling audiences) which read the page content and act on it accordingly, publishing the revised content in the chatbot window.

What worked well: In tests, publishers understood how the tool could be used as a writing partner, and were impressed with the way it restructured content with headings, bullet points and calls to action and hyperlinks.

What needed improvement: When faced with the empty chatbot interface, some publishers weren’t sure where to start, and they didn’t notice the three modes to work on content. Some were also unsure of the sources the chatbot was using for its revised content and skeptical that the revised content contained hallucinogenic content. They would have appreciated tracked changes to be able to pinpoint what had changed and found the long thin sidebar chat interface awkward to review the updated text. The chatbot was also limited to reviewing body text content, whereas publishers needed it to review content in other page components used in Drupal.

Read more about what we found developing and testing the ELM-powered content design chatbot:

Initial insights from UX testing our Drupal AI content assistant tool

Tool 3: QuillMark v1 and v2 – some AI, clusters errors with correction suggestions

QuillMark was an AI-enhanced tool which worked in Drupal to check content against the University’s Editorial Style Guide. Shlok Gupta built and tested two iterations of Quillmark during his 2026 summer placement as AI and UX Innovation Intern.

What it does and how it works: QuillMark sits in a side panel of the Drupal editorial interface and scans content on the page in two stages. The first stage uses code-based pattern matching (without AI) to catch straightforward errors. The second stage brings in AI to find deeper issues (such as passive instead of active voice) and to suggest fixes. Findings from both stages are displayed in the side panel – each finding describes the problem, links to the relevant rule in the style guide and offers an ‘Apply fix’ button (which can be reverted). Findings are grouped by category, and this panel also includes an indicator of the environmental impact and cost of the scan.

What worked well: In tests, publishers understood that the tool was there to help them correct content on the page, they liked the environmental and cost indicator, the suggested fixes and the links to the style guide reassured them that the tool was applying University-specific rules.

What needed improvement: Publishers reported feeling overwhelmed by the number of findings on a single page and they wanted a way to deal with related findings and fixes in bulk, to avoid going through them one-by-one. Related to this, they wanted

Read more about what we found developing and testing the QuillMark tool:

QuillMark, iterated. How user research helped us evolve an AI-enhanced Drupal style guide assistant

Tool 4: Drupal AI Content Review – full AI, with a plan provided to improve content

As part of the Drupal AI Initiative, I’ve contributed to shaping the self-explanatory Drupal AI Content Review module. This module plugs into a Drupal site, references content rules and good practice from context items in Drupal Context Control Center (within the same site) and uses the configured AI provider to review site content

What it does and how it works: The feature reads the page content and checks it against criteria set by the site owner, such as tone and voice guidelines, inclusive language rules and target readability levels. These rules are stored in the Drupal Context Control Center, along with examples of good and bad content. The review gives the page a score for each criterion and recommends fixes to improve it. Accepted recommendations become an improvement plan, which is applied in the editorial interface. Re-reviewing the page shows the updated scores, with the option to keep making improvements. Over time, the rules can be refined by adding more examples of good and bad content to the Context Control Center.

Read more about Drupal AI Content Review on Drupal.org

Read more about the Drupal Context Control Center on Drupal.org

View a demonstration of AI Content Review in a mocked-up university website as part of the Drupal AI demo on the Drupal Forge platform

What worked well:  In tests of this module within the AI demo, people liked seeing the red, amber and green indicators against page content for an easy visual highlighting areas to be worked on, and they liked being able to select a checklist of recommended improvements to apply to improve their content.

What needs improvement: The screens explaining the recommended improvements were difficult to scan read, and it was also difficult to compare the original text and the text with the recommended improvements side-by-side (despite colour shading to denote which was which). The stage where the recommendations were turned into an improvement plan felt like an unnecessary extra step, it would have been better to have implemented the recommendations directly. Also, it was presumed that implementing the plan would have corrected all errors resulting in a score of 100%, without the need for further work and re-review. Finally, it wasn’t immediately clear how to use the Drupal Context Control Center and the AI Content Review together.

When designing AI-enhanced tools, consider three AI design maxims

Taking on board variations in blending human effort and automated operations, there are three approaches to designing AI features and AI-assisted workflows worth considering. These are defined below, with ideas for how they may apply to content improvement.

1.      Human-in-the-loop

In this set-up, humans typically share the task-load with AI – actively working alongside an automated operator to supervise or influence actions, and to approve AI decisions before they happen (ensuring AI outputs are not released without the green-light from a person).

Human-in-the-loop tends to be adopted when:

  • there is a need for human judgement to get something correct
  • the consequences of an error could be high-profile or damaging
  • trust in an automated tool is still being built, and the boundaries of its capabilities are still being realised
  • the goal is for the system to facilitate shared learning between the person and the automation

For content improvement, human-in-the-loop is appropriate in these scenarios:

  • ensuring correctness of important factual data – for example, prices, dates, contact details, terms and conditions
  • checking the tone of sentences in line with inclusive language guidance
  • verifying accuracy of high-stakes published content such as legal information, policy wording or written instructional content
  • rewriting complex topics in plainer language
  • writing meta descriptions or page summaries to be accessed by search mechanisms
  • translating content into other languages

2.      Human-on-the-loop

These systems involve the AI or automator acting on its own, with the human reviewing and spot-checking at intervals, monitoring output quality over time, and intervening to correct failures periodically, where required.

Human-on-the-loop tends to be adopted when:

  • there is a high volume of low-risk tasks to be completed, which would be tedious for humans to do themselves
  • consequences of errors are minimal
  • there’s a need for tasks to be completed quickly, and including human-input at each task would be too time-consuming
  • consistency is required across tasks, and there’s a risk of human error introducing variability

For content improvement, human-on-the-loop is appropriate in these scenarios:

  • fixing straightforward style rule violations such as correcting spelling errors
  • categorising and tagging text content (for example, to facilitate its discovery in search)
  • scanning content for readability and accessibility, to flag or report areas to be addressed

3.      Human-out-of-the-loop

In this arrangement, the human sets up the AI to act autonomously, and leaves it to proceed, with no routine review.

Human-out-of-the-loop tends to be adopted when:

  • there are very low-risk, behind-the-scenes tasks to be completed where errors have little or no consequence and can be fully reversed

For content improvement, human-out-of-the-loop is appropriate in these scenarios:

  • autocorrecting typing errors
  • detecting content duplication
  • auto-optimising media content to defined parameters

Choice, pacing and transparency are constant design requirements

Testing four different tools has showed that options always need to be available, whatever balance of human and AI the tool includes. People approach AI differently based on preferences and past experiences. Some love nothing more than a good grappling of a sticky sentence, some just want an agent to do the work for them, and many sit somewhere in between, happy to have some AI help as long as they have the final say.

Alongside humans in, on and out of the loop, it’s important to remember the fourth option: human only, where people can choose to do their content unaided, using the methods they relied on before AI came along. AI shouldn’t be forced on anyone, so all tools need to come with a ‘no thanks to AI’ option.

AI is a fast-evolving and non-deterministic technology, so at any point in time it may work differently to the way it did before.  Responding to challenge from a design perspective, it’s important to factor in pacing. People need to be taken through how a tool works, and the options available. They need time and space to experiment and try it out, so they can learn for themselves how it can work for them. Pacing not only matters in the way tools are introduced, but also in the way their outputs are presented, to avoid the overwhelm that comes when AI does the heavy lifting all at once, and so people know what changed and how, and they have a way to accept, decline or edit what it produced.

If people don’t trust an AI tool, they won’t use it. Earning trust requires transparency, explainability, relatability and reliability – so AI tools need to be upfront about what they can and can’t do, with clear, intuitive interfaces and labels. Reliability will always be hard to promise given AI is probabilistic, so instead of accuracy guarantees which may fall short, a better approach is to design for experimentation, so people can find their feet and make their own judgements.

Designing for humans and AI together – metadata, markdown and MCPs

Looking at the broader digital landscape, the challenge widens from designing tools that help humans make content to designing websites with content ready for both humans and agents to use.

In co-browsing, people are increasingly arriving at a website with an agent alongside them, handing off some tasks while keeping control of others and wanting to see what their agent is doing. That means firstly deciding which tasks belong to humans and which one to AI, and secondly designing for each. Humans need intuitive interfaces. Agents need data they can read and act on without ambiguity:

  • metadata, such as schema markup that tells an agent what a page is about, who it’s for and how it connects to other content
  • markdown versions of pages and llms.txt files, which give agents clean, structured text without layout and navigation getting in the way
  • MCPs (Model Context Protocol servers), which let sites expose what they can do as well as what they say, from simple actions declared directly in HTML to more complex ones written in JavaScript – in preparation for use by the emerging WebMCP browser standard.

Labels matter for humans and agents alike, because words are becoming a currency that machines read as well as people. Alignment on terminology facilitates the creation of a single source of truth, to prevent the human experience from drifting from the agentic experience. On another level, humans need a way to consistently communicate with AI – to give AI the rules and instruct it and to train it with new insight. ‘Rosetta stone’ mechanisms like the Drupal Context Control Center will play an important part in designing for human and AI interaction and collaboration and I am excited to keep working and researching in this area to address these evolving design challenges.

 

Scottish Web Folk 2026: Humans vs Machine

There is no doubt that there has been a step change in how Higher Education has delivered web services over the past few years. However, stepping foot in the University of Dundee’s conference hall for another Scottish Web Folk, I’m delighted to report that it’s still very possible to fill a room with brilliant people who are happy to nerd out about our work!

You can read about my previous experience here:

Scottish Web Folk 2025: Challenging times, brilliant people

Old rules no longer apply

As is tradition, the University of Dundee’s Andrew Millar, opened the conference with a presentation which presented the theme of the day: “Human vs Machine”.

He put forward the idea that the amazing technologies which are transforming digital services also come with significant risks and challenges.

For example, indicators which were once used to assess the effectiveness of a web service can no longer be relied upon: Page views are less relevant now that many users will find an answer from a chat bot without visiting a website. A site’s ranking in search engines is less relevant now that a chat bot can find answers from anywhere on the web. And so on.

There is tension between the perception of human- and AI-generated content

While there is undoubtedly an increase in the use of chat bots to find information, a recent Gallup survey of 14-29 year olds found that only 3% trust work solely made by AI, 28% trust AI-assisted work, and 69% trust work made without AI.

Andrew Millar presenting a slide which includes the statistics of the trustworthiness of AI among Generation Z

In a panel discussion, Marta Krukowska from the University of Bangor described a situation in which an image purchased from a major vendor and used on their website turned out to be AI-generated. This caused some reputational damage in the student community as it put the doubt in users’ minds that other content might also be AI-generated.

The perception of these technologies is clearly in flux and are likely to shift significantly over the coming years. While it may be beyond us to influence this process, Millar put forward what he sees as our role:

  • Advocate: Speak for the user who is not in the room through research, accessibility, and plain language.
  • Defend: Protect accuracy and our voice. Ensure that what AI says about us is correct. Guard our data and intellectual property.
  • Decide: Own what is published in our name through approval thresholds, escalation, and a working stop button.

Digital practitioners have moved from theory to practice

Ensuring that our web content is correct and parsable by AI tools is essential going forward.

Only thinking about human users can have unintended results

Rob Ryder-Richardson from the University of Dundee described a situation in which something that was designed to help human users had unintended consequences when interfaced with AI.

Their course information pages dynamically displayed different data depending on the geographical location of the visitor – good for humans, but AI crawlers are almost exclusively based in the United States.

Therefore, when asked about course entry requirements, some chatbots were confidently asserting that the University of Dundee only accepts US SATs and that UK-based qualifications were ineligible.

The solution was to essentially develop a dataset which AI crawlers could use to find information, invisible to human users who would likely find such information unnecessary and overwhelming – structured in a way which is clear and unambiguous.

AI can be used proactively to improve the quality of web services

Richard Saunders from Zengenti described the benefits of developing a collaborative toolkit which team members can use to assess their webpages proactively to improve quality.

As a manager of a service which contains a surprising amount of content, one of the biggest challenges I have is ensuring that this content is accurate, pertinent, and accessible. While this task is currently done manually, there is certainly benefit in automating this task with AI skills.

In contrast with using one-off prompts, AI skills are plaintext workflows which provide a consistent instruction to the LLM. These work best when each one is focused on one particular outcome, and so developing a library of these within a team can provide a toolkit which can be used to consistently audit a website’s content.

I look forward to applying new best practice

While the technical implications for AI often dominate the conversation, Scottish Web Folk reminded me that successful digital transformation is fundamentally a human endeavour. Two sessions from the University of Edinburgh highlighted to me that before we can deploy such technologies, we must first master collaboration.

Neil Allison presented a masterclass on delivering effective workshops. Too often, digital teams conflate “meetings” and “workshops” and gather stakeholders only to disseminate information rather than create it. He outlined common pitfalls that cause a workshop to be ineffective: such as a lack of clear objectives, prominent voices stifling creativity, and lack of tangible outputs.

A slide featuring a diagram of a good workshop: the opening phase is divergent, the exploring phase is emergent, and the closing phase is convergent

Lauren Tormey delivered a case study on developing content design playbooks. Tormey explained how to co-create a set of best practices using a repeatable, structured workshop format.

As part of a team who hopes to deliver significant changes to our digital services in the near future, I found this talk to be invaluable and look forward to employing these strategies in my workshops soon.

We have a responsibility to help deliver better, future-proofed web services

AI is no longer a distant, theoretical concept, but an immediate operational reality. The path forward requires focusing on both delivering effective technology and ensuring excellent collaboration on the human level.

To take this forward, I propose the following action plan:

  • Ensure our success metrics are defined according to user requirements.
  • Audit our content for AI readability.
  • Deliver excellent workshops to determine our course of action.

Or in other words:

Advocate. Defend. Decide.

Key Takeaways from Scottish Web Folk 2026

2 November 2026 at 14:56

It was a busy day at the Scottish Web Folk conference, packed with ‘quick-fire’ sessions that lasted just 30 minutes each. The theme was Human vs Machine, however I took away no negative vibes about AI. The general feeling was positivity, and I enjoyed hearing how AI is altering things – how it can enhance our workflows and what it can add to a process with the correct guardrails in place.

Andrew Millar, Head of Digital Engagement & Marketing at the University of Dundee, kicked off the day. His session was thought provoking, and I jotted down several key takeaways that set the tone for the day ahead:

  • AI is a gateway to something both amazing and terrifying.
  • Just because things have worked out previously regarding innovation, we shouldn’t view that as comfort; we must accept the responsibility that comes with it.
  • Machines are now using our content and information to speak on our behalf.
  • How has this shift broken our existing metrics?
  • The machine has inserted itself into the conversation and is now providing the answers.
  • How do we determine if it is actually using our content?
  • We are using AI more and more in our daily lives, yet people are trusting it less.
  • A new acronym for me: GIGO – Garbage In, Garbage Out.

These points framed the day perfectly, as the subsequent presentations addressed these challenges and more.

The human side of digital transformation

It was interesting to hear from Mark Kennedy, Web Development Manager at Ulster University, about how he leads his web team of four, who support over 400 publishers. Mark and his team do not sit within Information Services, but instead they are integrated into Marketing and Communications. He mentioned that this can come with some challenges but also fosters more involved collaborations around content. For us in the Web Development Team at the University of Edinburgh, we are somewhat removed from the quality and accuracy of the content our publishers upload to their sites. As a wider team, we focus on providing the tools, training, and advice required to produce good-quality, accessible content. In contrast, at Ulster, the web team works closely with their MarComms colleagues, acting as gatekeepers for good content.

This close working relationship benefitted the team when Mark’s MarComms colleagues requested a sandbox to experiment with the new component-based platform, they built a publish-ready site within just one week. Although intended only as a playground, they fully embraced the reusable components – a surprising yet fantastic outcome that truly illustrated the human side of digital transformation. It struck me how accustomed we become to our own ways of working and the specific colleagues and disciplines we interact with daily. Mark’s talk sparked a thought: what would it be like if we were structured differently?

Post deployment testing

I also attended Rob McCreary’s talk (University of Dundee) on testing. He emphasised the importance of introducing automated testing techniques to enable quick fixes that can be deployed with confidence, specifically detailing how his team uses Behat feature files to confirm the live environment is healthy immediately after deployment. This was quite a complex topic, and while our team is just at the start of introducing automated testing, here are my main takeaways:

  • It’s not only developers who ship bugs – integrated content can too.
  • Import and integration failures can reach the live page before anyone notices.
  • A GitLab pipeline can run a test report and display the results clearly.
  • Build in a clean-up process: if entities (pages or users for example) are created as part of a test, they must be cleaned up afterwards.
  • Fast smoke tests can provide an early warning system.
  • Scheduled regression tests cover the wider system without holding up releases.

Side note: As I write this post, I find myself cross-referencing my notes, reviewing photos of the slides, and looking up terms I didn’t fully grasp during the sessions. This process itself feels like part of the lesson to me.


Thorough scoping with the help of AI

Matthew Jones and Robin Butler from Vepple, a virtual experience platform for universities, presented on using AI to draft development specifications. Their workflow begins with an MRD (Market Requirements Document), which outlines the problem statement and testable acceptance criteria. The most intriguing part of their talk was the concept of a ‘Grilling Session.’

At the time, I jotted down that this should be ‘thorough in a positive way,’ but I wasn’t entirely sure what that looked like. Researching it later revealed that this practice flips the conventional use of AI on its head. Instead of the user simply prompting the AI to generate content, the AI agent takes the lead. It prompts the developers with tailored, iterative questions – effectively ‘grilling’ the user to clarify scope and refine requirements. This rigorous interrogation ensures nothing is missed before the AI outputs a PRD (Product Requirements Document).

As they put it: “The agent writes with us and not for us.”

Once the specification is solid, the agent can slice it into actionable tickets for humans to follow, organising them into epics (projects). They also mentioned that automated tests are used to ‘pin’ existing functionality, ensuring that new changes remain small and manageable.

Takeaway: We don’t keep a platform in good shape by going faster – we do it by being thorough.

A presentation at Scottish Web Folk 2026

Findability and AI-driven search

Paul Costello and Rob Allen from Numiko talked about their work on findability with the University of Oxford. I know about SEO – it’s been around for some time! – but GEO and AEO were new to me. These stand for Generative Engine Optimisation and Answer Engine Optimisation, which are basically the same thing: looking at how AI-driven search works. This ties neatly back to the points from the introduction.

Honestly, this session was very content-focussed, so it’s not entirely relevant to my daily work as a developer. But I think it’s still really interesting and valuable for us to understand. And actually, it makes a lot of sense:

  • Think of a list of non-branded prompts that a user might type into an AI.
  • Structure your content around the questions users will actually ask.
  • Clear out old, out-of-date content.
  • Make sure how you talk about your organisation matches how the audience would phrase it or ask it.

It’s a simple idea – if people are asking AI questions in their own words, our content needs to speak the same language.

Extensive web estates and the importance of governance

To finish the day, I sat in on an unscripted presentation by Stratos Filalithis (University of Edinburgh) and Kris Purdy (University of Glasgow). There were no slides, just an open conversation between them and the audience about governing their massive web estates. It’s incredible just how large these estates are and I was genuinely surprised when Stratos quoted around 2,000 sites.

It’s a huge task – finding these sites, documenting them, establishing if they’re still required, tracking down owners, checking where they’re hosted, and essentially (fitting perfectly with the theme of the day) auditing the content.

The scary part? Sites from the late nineties could still be out there, serving AI agents with outdated answers! Eek!!!

Conclusion

Looking back at the day, the common thread wasn’t about fearing AI but was much more positive – it was about how we prepare our content and how we can employ agents to help with workflows, development, scoping to name just a few use cases.

Quality matters more than speed.

If we don’t audit our estates, we risk those forgotten sites from the late nineties feeding bad information to AI agents. And if we don’t speak the same language as our users, AI won’t find our answers anyway.

The landscape will keep changing, but if we focus on getting the basics right, we’ll be ready for whatever comes next.

QuillMark, iterated. How user research helped us evolve an AI-enhanced Drupal style guide assistant

2 November 2026 at 10:25

AI and UX Innovation Intern Shlok Gupta and I worked together to build and test Quillmark, an AI-powered Drupal content design tool that tackles the persistent problem of keeping content consistent with the University’s style guide. This post covers how we iterated from version 1 to 2.

Leading a UX Service, it’s critical to stay informed about the latest technologies, as these dictate user expectations and perceptions. I recognised the potential for AI to transform publisher experiences of using Drupal when Drupal AI experts Freely Give came to work with our team in January 2025. Since then, I’ve been committed to experimenting with AI application in content management, both through my involvement with the Drupal AI initiative and by supporting a succession of interns in my UX team at the University.

As a technology, AI is becoming increasingly mainstream. That said, its rapid rate of evolution and flux means adopting it consistently remains a challenge, as does designing AI features that are centred around user needs and expectations. AI features can be built and released in a matter of days, but can just as quickly become superseded and obsolete as technologies and capabilities change, and user expectations and perceptions of AI features can vary widely depending on individual experiences, trust factors and preferences. Continuous research is necessary when developing any user-centred software, but it’s particularly important when designing user-centred AI features, which I wrote about in a related blog post:

Stop chasing, keep researching: Why continuous contextual learning is the only way to build useful AI features

In the spirit of continuous research, the students who occupy the AI and UX Innovation Intern role in my UX team spend as much time testing as they do building. Shlok Gupta joined the team from May – August 2026, in which time he prototyped and tested two versions of an AI-enhanced style guide checker tool in Drupal. Shlok described his process to build and test Quillmark v1 in two blog posts, and also produced a video to show it in action:

Building QuillMark: testing a Drupal style-guide assistant with web publishers

Quillmark: the technical details behind my Drupal style-guide assistant

View a video of Quillmark v1 on MediaHopper

In this post, I continue the story, to explain how version 2 was built based on feedback from version 1, and what we learned testing version 2 with publishers.

QuillMark v1 had a non-AI stage and an AI stage and the ability to flag and fix errors

Shlok designed QuillMark v1 to have two stages as a way of making most economical use of AI time and tokens. Stage 1 used basic pattern-matching and code-based rules to catch straightforward style-guide errors without AI, and stage 2 then brought in AI to find and recommend fixes for deeper issues. This meant AI resource wasn’t spent identifying and resolving simpler problems that didn’t need it. The screenshots indicate how v1 worked.

Screenshot showing Quillmark v1 (in the right-hand panel of a Drupal site) ready to review content

Screenshot showing Quillmark v1 (in the right-hand panel of a Drupal site) ready to review content

From right-left, four screenshots showing detail of the QuillMark guide in the right-hand panel before a scan, the panel expanded to show the guide, results of a stage 1 scan and detail of selected stage 1 findings

From left to right, detail of QuillMark in the right-hand panel – before a scan, expanded to show the guide, results of a stage 1 scan and detail of selected stage 1 findings

Three screenshots of QuillMark, showing the panel ahead of running the stage 2 scan, combined results of the stage 1 and stage 2 scans and detail of selected stage 1 and stage 2 findings alongside each other

From left to right: the panel ahead of running the stage 2 scan, combined results of the stage 1 and stage 2 scans and detail of some stage 1 and stage 2 findings alongside each other

QuillMark screenshot showing how a finding from a stage 2 scan mapped to a sentence in the passive voice highlighted in the editorial interface

QuillMark screenshot showing how a finding from a stage 2 scan mapped to a sentence in the passive voice highlighted in the editorial interface

QuillMark screenshot showing the highlighted sentence changed to active voice - which resulted from pressing the ‘Apply fix’ button on the finding

QuillMark screenshot showing the highlighted sentence changed to active voice – which resulted from pressing the ‘Apply fix’ button on the finding

Tests revealed the need to simplify QuillMark v1

In the tests of QuillMark v1, participants were asked to read a guide about how the tool worked, use it to scan some pre-prepared content and then review the resulting findings and say how they would act upon them. The results indicated several areas for improvement.

All participants understood that QuillMark v1 was a tool to help them correct content errors. Despite being directed to read the guide upfront, however, some participants were unclear of the difference between stages 1 and 2.  Having run stage 1, participants were uncertain what stage 2 of the tool would do. Some identified the AI detail in the stage 2 labels and therefore realised that stage 2, unlike stage 1 used AI, but others thought stage 2 was the ‘repair’ or ‘fix’ stage to follow stage 1 as the diagnostic stage.

As they reviewed the different categories of finding in the right-hand panel, most participants said they felt the amount of information was overwhelming, and difficult to scan read. They especially found it difficult to interpret abstracted recommendations to fix errors, preferring to receive suggested fixes through the ‘Apply fix’ option. As a way to reduce the overwhelm, some participants said they would be inclined to go and fix several of the errors manually first, and then rescan, so that the tool only presented them with the errors they missed themselves.

Other observations from the test participants fell into two categories, lack of understanding of how Quillmark worked, and feedback on how they felt it could work better for them.

Participants were confused about how to use QuillMark and how it worked

Several aspects of participants’ behaviours indicated they weren’t sure how QuillMark worked. These were as follows:

  • There was some confusion over how to start QuillMark running. Participants did not immediately realise that the Stage 1 and Stage 2 buttons would start the tool. They looked for a button that said ‘Run’ or similar. When they worked out how to activate the different stages, they were unclear about what was happening in each.
  • Several participants raised questions about the cost and environmental impact of running the AI stage of the tool, saying this would affect whether they would choose to use it.
  • There was a lack of clarity from participants about whether QuillMark was using generic grammatical rules to flag errors and make recommendations or if it was using the specific University of Edinburgh style guide rules
  • Several participants did not initially recognise that QuillMark could suggest fixes as well as flagging errors.

Participants suggested ways to change QuillMark, to help it support publishing practices better

When they had got used to working with QuillMark, several participants suggested ways they felt it could work better. There were as follows:

  • A request to be able to apply bulk fixes to recurring errors, rather than addressing them one-by-one (for example, removing full stops in repeated headings or switching sets of times from the 24 hour clock to the 12 hour clock)
  • An ask from several participants to be able to preview fixes offered by the ‘Apply fix’ buttons before accepting them to change the text in the editorial interface (however, they soon realised they could switch between the ‘Apply fix’ and ‘Revert fix’ buttons to achieve this).

QuillMark v2 worked in the same way but the interface was simpler

Taking on board the feedback from the QuillMark v1 tests, Shlok made a version 2 which included several changes:

  • A single ‘Scan’ button to start both stages of the tool working, replacing the need for publishers to run stage 1 and stage 2 scans in sequence
  • Progress indicators that appeared once ‘Scan’ had been pressed, to communicate what was happening, and to affirm that the editorial style guide was being checked
  • Inclusion of an ‘Advanced settings’ panel giving users the option to decide whether to include deterministic error scanning and fixing and the use of AI to suggest replacements
  • A panel that estimated monetary cost and environmental impact of each scan resulting in the findings

View a short video demonstration of QuillMark v2 on Media Hopper

The screenshots indicate how v2 worked and show the differences between v1 and v2

QuillMark screenshot showing the tool in the right-hand panel ahead of a scan being run on a page of content titled ‘Research projects’

QuillMark screenshot showing the tool in the right-hand panel ahead of a scan being run on a page of content titled ‘Research projects’

Series of QuillMark screenshots, from left to right, showing the tool with the guide displayed, and the successive stages once ‘Scan’ has been pressed – reviewing, preparing, checking editorial style rules and then the notification that QuillMark has completed the scan.

QuillMark screenshots, from left to right, showing the tool with the guide displayed, and the successive stages once ‘Scan’ has been pressed – reviewing, preparing, checking editorial style rules and then the notification that QuillMark has completed the scan (showing that AI suggestions are included in the ‘Advanced settings’ pane

Tests showed v2 was better, but still had room for improvement

The testing protocol for QuillMark v2 remained the same as for v1, however, this time participants were asked to use the tool on three separate pages of University website content, to give them more practice of engaging with the tool to learn how it worked.

Participants found it easier to understand how QuillMark v2 worked

With the new blue ‘Scan’ button, participants were more easily able to get started with running QuillMark. Since it was running an AI and a non-AI stage QuillMark v2 took longer to produce findings than QuillMark v1, but the newly added progress indicators kept participants informed about what was happening.

The indicator with the data about environmental and monetary costs was noted by all participants, and some said this was welcome information to help them make responsible choices about AI use.

Participants were still directed to the guide, which some wanted to refer back to once they had got started with the tool, to remind them of how it worked.

There were fewer questions about the source of the rules powering Quillmark v2 than for v1, and several participants verified that the tool was using rules from the University editorial style guide by pressing the ‘Link to rule’ button on individual findings (which connected to the relevant page or section of the style guide).

Some still found the interface and display overwhelming

Although QuillMark’s interface had been simplified by the removal of stage 1 and 2 indicators, participants still commented it contained a lot of textual information and was difficult to scan. Some were unclear what the different labels in the findings meant (Errors vs Warnings vs Notes), and several found it easy to miss some of the tool’s functionality simply because there was too much to read through.

Participants were still uncertain about the ‘Apply fix’ button

As they worked through the individual findings, participants were able to recognise the need for corrections that had been highlighted, but some did not appreciate that QuillMark v2 offered a fix as well as flagging the error.

As they used QuillMark v2 to scan a page about research projects, the tool flagged an instance of poorly worded link text (‘Project Website’). The ‘Apply fix’ button contained a suggested improvement (‘Visit the Hillforts Atlas website’) but several participants did not select this, instead they manually addressed the error themselves, by checking the link destination and then writing appropriate link text. Those that did notice that ‘Apply fix’ had made a suggested improvement were happy to accept it and apply it.

Screenshot showing a QuillMark v2 finding flagging poorly written link text

Screenshot showing a QuillMark v2 finding flagging poorly written link text

Screenshot showing QuillMark v2 a fix to improve poorly written link text applied in the editorial interface

Screenshot showing QuillMark v2 a fix to improve poorly written link text applied in the editorial interface

They still wanted repeated findings to be consolidated, to be addressed together

Some categories of findings contained recurring instances of the same issue. Participants wanted these to be grouped or summarised instead of being listed individually, as they wanted to address all the findings on a particular issue together in one action (either dismissing them or applying suggested fixes), rather than going through them one-by-one. This problem was particularly prevalent on pages where the content followed a structural pattern, for example a series of headings all written in non-sentence case (with misuse of capital letters) or a labelling convention applied consistently to rows of a table (for example numerals in sequence).

Screenshot showing individual instances of an error flagged as separate findings in the QuillMark v2 interface

Screenshot showing individual instances of an error flagged as separate findings in the QuillMark v2 interface

There was concern over saving progress when working through lots of findings

In the tests, one of the pages scanned by Quillmark v2 generated 166 findings to be addressed. As participants worked through those in a particular category (for example ‘Links and calls to action’) they felt uncomfortable that they were unable to save as they went, seeking some reassurance that their work was being logged sequentially. They looked for a ‘Save’ button associated with each individual finding, and some wrongly assumed the ‘Dismiss’ button saved the change they had made (whereas in actual fact, this button removed the finding from the list to be addressed).

QuillMark was unable to reconcile multiple errors on the same content

In some instances, a piece of content contained multiple style guide errors, so it appeared in separate findings in separate categories. An example was ‘Prof Smith’s website’ used as a piece of link text. This error appeared in the ‘Spelling, wording and abbreviation’ category, flagged for the incorrect use of ‘Prof.’, but also in the ‘Links and calls to action’ category, flagged for unclear link text.

When participants encountered an error in one finding, they corrected it there, but then when the same piece of content was also flagged for another error in another category, Quillmark v2 had already noted that the content had been changed, and had no way of layering on another, different correction. In these instances, a warning flag disabled the ‘Go to field’ preventing participants from going to the incorrect content, therefore forcing them to try and find the location of the incorrect content themselves, which they found disorientating and tricky, especially in long pages of content.

Screenshot showing the blocker message that displayed when there were multiple errors on a single field of content

Screenshot showing the blocker message that displayed when there were multiple errors on a single field of content

Participants wanted QuillMark to fix heading levels and reposition inline links

Errors relating to content structure, such as incorrect heading hierarchies and inline links were flagged by Quillmark, but the tool was unable to suggest an automatic fix to apply. Several participants said they would have liked for an autocorrect functionality for these errors, since they found them difficult and fiddly to manage within the EdWeb2 editorial interface.

The next iteration of the tool will focus on one category of style rules: Links

Since the last round of tests on QuillMark v2, Shlok completed the internship, and was succeeded by Viktor Sharha in the role of AI and UX Innovation Intern, to continue the work on the Drupal style guide checker tool. Taking all the findings from the tests of QuillMark v1 and v2 together, I concluded that the most pressing problem to address was that of overwhelm.

When a page contains many errors or style guide violations, there is a dual design problem: Firstly how to detail each error, the root cause and the suggested fix, so that publishers understood what was wrong and how it can be corrected, and secondly to do this concisely, taking up the minimal space possible, to avoid publishers having a long scroll through multiple errors with the associated cognitive load.

Going forward, it made sense to focus on the first problem of presentation of individual findings first, and to do so at a site level (recognising that publishers may not do their checking on a page-by-page basis), before scaling this up to design for multiple errors. To maintain a tight remit, and to focus on the style guide violations which are highest priority to fix, we have decided to specifically look at links, to consider how the tool can spot instances of poor link text, how it can describe ways to improve these, and the options for applying automated fixes.

Reflections from the Scottish Web Folk Conference 2026 – ‘Human vs machine: who does it better?’

2 November 2026 at 09:59

Scottish Webfolk has become a staple fixture in my October work calendar for the last three years. Despite the very early start to make it north for the conference starting just after nine, by the time you arrive you realise it was worth making the trip. This year there were over 100 attendees from 26 different universities, with a strong line up of presenters from Edinburgh.

Andrew Millar, Head of Digital Engagement & Marketing at University of Dundee started with his key note opening talk, which is always a highlight and this year was no different as he introduced the theme of the conference ‘Human vs machine: who does it better?’

Andrew’s talks are always grounded in realism, especially given the challenging times the higher education sector is facing, but with ample optimism and insightful narrative woven throughout so that by the end you feel energised for a day or learning, sharing ideas and discussing common challenges.

A different take on a familiar theme: AI

It’s probably not a great surprise that the conference had an AI theme. However, I felt this time it was as much about the importance and value of ‘keeping a human in the loop’ as it was about leveraging the benefits of AI-based technologies and tools.

In his talk Andrew referred to the quote: “the threat was never the machine, it’s how people use it” which really stuck with me.

AI is the latest in a whole historical timeline of technological advancements, as Andrew explained. Whilst it is revolutionary, it still needs humans to ensure that it’s used for the greatest benefit. So in that sense the day highlighted to me that machines and humans need to work in tandem, rather than in competition to get the best results.

My third presentation at the conference – ‘AI search summaries: a new lens on old content problems’

For this year’s conference I co-presented with Nick Daniels and Mel Batcharj for what was to be my last UX Service talk. We shared how we trained our web publishing community at Edinburgh on how to make their content AI-ready in the ever-evolving AI search landscape.

We highlighted how evergreen content design principles still stand strong in the new era of AI search and shared how we used the prominence of AI to teach these principles in a slightly reframed way. The aim being to enable publishers to optimise their content for AI search, whilst also tackling persistent problems with our web estate content.

The key takeaway was that website content that is well structured, well maintained and accessible is just as important for AI as it is for users.

You can read more about this training in my previous blog.

June Content Improvement Club: Is your content AI ready? 

Web governance: a problem shared is a problem halved

Another highlight of the day for me was the refreshing session which Stratos Filalithis from Edinburgh and Chris Purdy, Head of Digital Experience from the University of Glasgow hosted, which they called ‘Digital Unscripted’. There were no slides, instead an honest conversation about the challenges both universities are facing to tackle their huge, unwieldy web estates.

I’m used to starting off presentations at conferences explaining that Edinburgh has a huge web estate with over 1,000 web publishers (today was no different). This is often met by surprised faces, especially for those universities with a centralised digital marketing team who oversee the production of all web content. So, it was somewhat comforting to hear that Glasgow faced similar challenges to Edinburgh in terms of managing vast amounts of diverse web content and that both institutions were sharing knowledge and expertise to try to bring order to the chaos.

I found this interesting as a lot of my work recently has been focussed on developing guidance (alongside subject matter experts) for website owners on their key responsibilities when creating and managing a website.

The difficulties and governance risks associated with large web estates felt like a very relevant topic to be discussing given AI’s ability to unearth long forgotten about content in its answers, but also in the wake of the PHP vulnerability incident which highlighted the importance of ‘knowing what you own’ from a web registry perspective.

Scottish Web Folk – much more a community event than a traditional conference

I think the ‘Digital Unscripted’ session, along with the panel discussions where representatives from different universities shared their perspectives on challenges they were facing for me sums up that really Scottish Web Folk is more a community event than a traditional conference. There’s a real sense of sharing solutions to mutual problems and discussing the challenges that nobody has yet managed to resolve, rather than just highlighting successes. I think it’s the community emphasis and collegiality that keeps bringing people back year after year.

Using a survey to understand digital design tool usage across the University (as part of the Figma design component library project)

2 November 2026 at 08:24

This year, as part of the Figma component library project, we researched how colleagues across the University use digital design tools in their work. This post explores how we approached the research, from designing and distributing the survey through to analysing the responses and identifying emerging themes. 

In a previous blog post, intern Kaile Liu introduced the wider Figma project, and its aims and objectives: 

What I am working on as a Digital Developer Intern (Figma) 

Request access to the project brief for more details:

Figma project brief

We needed to understand how digital design work happens across the University 

To begin with, we needed to understand how staff across the University design, collaborate and deliver digital work. 

There are a wide range of tools, workflows and practices currently in use. Understanding these existing ways of working would help us explore where Figma fits within the wider digital landscape, rather than looking at Figma in isolation. It also supports the work we are doing to improve our Figma component design library.

To hear from colleagues across a wide range of roles and disciplines, we chose a survey as the main method for this research.

Five questions framed our research 

As well as understanding what tools people use, we wanted to find out how those tools support their work and where there may be opportunities to improve existing ways of working.  

Our research was underpinned by five key questions: 

  • What tools are people using day-to-day? 
  • How do those tools support their work? 
  • Where do people experience challenges or inefficiencies? 
  • How do teams collaborate when creating digital content and services? 
  • Where are there opportunities to provide better support, guidance and training? 

These questions helped us build a broader picture of digital working practices across the University. Additionally, working this way allowed us to look beyond any individual or singular tool.

Hearing from more than just traditional design roles was important 

Design work happens across many different roles at the University, including roles not traditionally associated with design or that do not have ‘design’ in the job title. For example, a communications officer creating digital content, a developer sketching a wireframe, a UX practitioner co-creating a prototype or a learning technologist building online resources may all be making design decisions as part of their work. 

This meant looking beyond traditional design roles and hearing from colleagues who use digital design tools in different ways.  

Initial conversations helped us shape the research 

Before designing the survey, we carried out an initial set of user interviews with staff from across the University. We also drew on existing University communities and communities of practice to understand the different roles involved in digital design work. These conversations gave us an early view of how colleagues use and collaborate through digital tools. They helped us identify the groups we wanted to hear from and shape the questions we wanted to ask in the survey.

Adapting our survey to broaden our understanding of ways of working

Based on these interviews, we recognised that a single set of questions would not capture the differences between roles particularly well. Instead, we adapted the survey so that respondents would answer shared questions and then be filtered to questions relevant to their role and ways of working.

This, in essence, would give us a more consistent set of responses while still allowing us to explore some of the differences between roles.

Role categories allowed us to tailor the survey 

We created a filter with seven options: 

  • Marketing and Communications 
  • UX and Human-centred Design 
  • Graphic and UI Design 
  • Developer 
  • Project or product manager 
  • Research 
  • Other (for participants who did not feel represented by the other groups) 

Participants selected the options that best reflected their work, determining which role-specific questions they were shown. They also provided their job title.

The survey combined common and role-specific questions 

The survey consisted of three main sections. The questions included a mixture of multiple-choice and open-ended responses. This allowed us to identify broader patterns while also giving colleagues opportunities to explain their experiences in more detail. 

The opening section included five common questions about participants’ roles, the types of digital design work they do and the tools they use, including tools for collaboration, diagramming and presentations. 

The middle section included around four to six role-specific questions, depending on the participant’s selected group. These explored aspects of digital working relevant to each group. For example, marketing and communications colleagues were asked about the tools they use when designing marketing materials, while developers were asked about the tools and approaches they use during the design phase of projects. 

The closing section included 15 common questions focused on colleagues’ experiences and expectations of digital design tools, including Figma. We asked which tools colleagues would be likely to use, whether they experienced challenges with their current tools and how their work might be affected if they lost access to Figma. 

We wanted the survey to reach as many colleagues as possible

We distributed the survey primarily through existing Teams channels and University communities, which helped us reach a wide range of roles. These included groups focused on marketing and communications, human-centred design and digital development, as well as distribution via heads of IT. 

The survey received 55 responses  

We heard from 55 staff across a range of roles. Based on the categories participants selected when completing the survey, these were as follows: 

  • Marketing and Communications: 20 
  • Developers: 10 
  • UX and Human-Centred Design: 6 
  • Graphic and UI Design: 3 
  • Project or product manager: 2 
  • Other: 14 

Although seven categories were available in the survey, no participants selected ‘Research’ as their primary category, so it is not shown in the breakdown. 

The ‘Other’ category included colleagues working in areas such as product and project management, learning technology and academic support. 

We refined the groups when analysing the responses 

The survey categories gave us a useful starting point, but participants did not always recognise themselves within the roles specified (even when their job title directly reflected one of the options). For example, a participant selected themselves as ‘Other’, but their job title indicated that their work was within graphic design.

In order to evaluate the responses effectively, we revisited participants’ selected categories alongside their job titles and descriptions of their work.

This helped us six create groups that gave us a more useful basis for comparing responses:

  • Developers and technical specialists 
  • UX practitioners 
  • UI and graphic designers 
  • Marketing and communications staff 
  • Product and project managers 
  • Learning technology and academic support staff 

Some of these groups needed to be created on the back of this, as we had not identified those specific roles. For example, Learning Technologist was not an option for participants to select, but emerged as a useful category based on the number of respondents who had this as their job title. 

After this assessment, we were in a better place to begin analysis, as these groups gave us a more useful basis for comparing responses while still reflecting the range of roles represented.

Analysing the survey results required two approaches 

The survey produced both quantitative and qualitative responses, and we used different approaches depending on the type of question and response. 

For the role-specific questions, we used FigJam (Figma’s whiteboard for online collaboration) to review and compare responses across the different groups. This included both quantitative and qualitative responses, allowing us to look at the detail within each role as well as compare responses across the wider dataset. We used Power BI, a data visualisation platform, to explore the common quantitative questions, which gave us a consistent set of responses across all participants. 

We used FigJam to explore the role-specific responses 

We created a large collaborative FigJam board to organise the responses. FigJam supported discussion within the project team, allowing us to work in tandem and analyse the data as a group (in person and asynchronously).

We read through responses from each group, compared them across different roles, and identified recurring patterns and themes. FigJam also allowed us to consider the quantitative responses alongside the more detailed qualitative answers, giving us a fuller picture of ways of working. 

Screenshot of three frames on FigJam full of stickies. There is a blue section, titled Developers, an orange section titled Marketing and Communications, and a green section titled Graphic visual and UI design.

Section of our analysis on the FigJam board

Power BI helped us explore the common quantitative responses 

Power BI allowed us to visualise responses across the opening and closing questions. We wanted to do this as they were common questions asked of all participants. Power BI allowed us to bring our data to life by presenting the data in a more visual way, highlighting the common patterns and themes more easily.

Screenshot of Power BI visualisations. There are seven individual bar graphs of different colours, alongside a larger bar graph with these seven combined. The large bar graph has a right skewed narrow tail. There are also two sets of pie charts, each consistening of seven smaller charts and one larger combined. The data itself is not visible.

Section of our Power BI visualisations for the project.

Grouping responses helped us identify recurring themes 

The open-ended questions in the role specific sections had more detailed responses. This required us to compare responses across the different role groups and group similar comments together to identify recurring themes. 

As we worked through the responses, we also noted areas where a follow-up conversation with a participant could provide more context.

We also captured key quotations that illustrated what participants were telling us in their own words. These will be useful for when we playback findings to colleagues and complete a written report. 

The research will inform the next stage of the project 

The research highlighted both the diversity of digital working practices across the University and common themes across different roles. 

The next stage will bring these findings together into a report. It will highlight where Figma currently supports existing workflows and where its integration will provide more consistent, unified delivery of digital practices across the University.

At Scottish Web Folk 2026, the theme was Human vs Machine. The takeaway was Human plus Machine.

The theme of this year’s Scottish Web Folk conference in Dundee was “Human vs Machine”, and AI dominated the programme, as you’d expect. But session after session told another story: the successes came from humans and machines working together, with people firmly in charge of the judgement calls. Here’s my reflections from a day packed with very interesting sessions and networking with colleagues from the Higher Education sector.

Four years in, and still the friendliest room in Scottish higher education

The annual Scottish Web Folk conference began in 2023 to bring Scottish universities’ digital and web professionals back together after the hiatus of the pandemic. Colleagues from University from Dundee (can’t say thank you enough to Andrew Millar and Rob Ryder-Richardson enough for keeping this community together) organise a day of more than twenty sessions, with teams from across the UK and Ireland attending. When I reflected on the 2024 edition, I called it a ceilidh, and the description still fits.

The Scottish Web Folk ceilidh at Dundee – Blog post by Stratos Filalithis, October 2024

Alistair Campbell used the title of “Challenging times, brilliant people” for last year’s conference, and this description still stands, even stronger.

Scottish Web Folk 2025: Challenging times, brilliant people – Blog post by Alistair Campbell, November 2025

A large lecture theatre, with people sitting on the foreground and a large screen welcoming attendees of the Scottish Web Folk 2026 conference.

The opening of the Scottish Web Folk 2026 conference.

This is a working conference rather than a showcase: people turn up to talk about their challenges and successes and leave with valuable insights, ideas and new friends to follow up after the day. The University of Edinburgh was very well represented, with colleagues from our teams sharing their work.

Scottish Web Folk 2026 conference programme

In Edinburgh and Glasgow, we “never waste a crisis”

During the last few years, Kris Purdy, Head of Digital Experience at University of Glasgow, and I have met regularly to exchange thoughts and ideas, and compare your approaches against very similar challenges in our web estates. In this year’s conference, we were given the opportunity to stand and share our stories, findings and action plans to bring order to our chaotic web estates. We agreed to “freestyle” the session, having an open discussion without any slides. This allowed us to be frank in an informal environment, and, hopefully, better engage with our audience, allowing questions to be asked during our discussion and not waiting until the end, as is the usual format.

We spoke about our common challenges, like the risk of not knowing the size, shape and individual ownership of our websites, and differences, for example Glasgow’s web estate counts approximately 900 websites, half of which are hosted in their corporate website, while Edinburgh’s web estate counts more than 2,000 websites, with less than 8% using the centrally-supported web platform, EdWeb 2. Some of these numbers triggered audible gasps from the crowd, like the fact that Google regularly indexes more than 2 million pages and files under our corporate domain (ed.ac.uk), which is way more than those hosted in our web platform, or expected to manage.

There was a very special mention to last week’s PHP2Shell vulnerability incident which highlighted the need for an up-to-date web estate registry, as well as the immediate and quick action everyone took to update it with information about ownership, technology usage, which helps identify those websites that need to be retired immediately. This is a crisis we will not waste.

Through our journeys, though, we identified a very strong conclusion: the lack of clear web estate governance and ownership increases multiple risks across reputation, ability to stand out in search results, content accuracy, compliance, cyber security and higher costs associated with the web services. As I have blogged recently, these risks are untenable in the are of the great amplifier: Artificial Intelligence (AI).

2,117 websites and counting: welcome to our Wild West Web Estate – Blog post by Stratos Filalithis, October 2026

With a day full of insights and interesting sessions, here are the main themes that stood out for me:

The threat was never the machine

The customary introduction by Andrew Millar, Head of Digital Engagement & Marketing at University of Dundee, sets the tone for the rest of the day, and this time was not different. I fully agree with his argument that humanity had always had a challenge with transformative and disruptive technologies. AI is the most recent addition in a list having the printing press, factory power, office computers and the web, all of which provided a turning point making some things scarce and other more valuable.

Slide titled “Not the first turning point”, comparing the printing press, steam power, office computers, the web and AI. Each earlier shift made one skill cheap and another valuable, such as judgement and trust after the printing press. For AI, drafting and summarising are no longer scarce, but what becomes valuable and who loses out are marked with question marks. Caption: “It worked out previously…

Andrew Millar’s slide listing the human technology turning points and their impacts.

Each of these technologies had an impact relative to their era and world, making AI the most impactful (yet). What we do with it, though, is up to humans since technology by itself is not a threat. How we use it and for which purposes and benefits is. Andrew concluded by pointing out that to achieve this, we need to make sure to ask the right questions, like “Did the user get the right answer, anywhere in our website?” instead of “How many people viewed this page?”, or “Does key content have an owner and a review date?” instead of having “Machines make unlimited content”.

Most of the sessions in the day were focussing on just that, how to leverage the powerful technologies at hand to enhance our capability, experience and skills to fulfil our objectives.

AI bots are an audience too

This wasn’t the first time that I attended a session about building website and webpages for AI bots. This is a very real subject because optimizing how AI bots scan and index our content, supports what they respond on our behalf to a rising number of user using them as their first point in searching for a programme, degree or research opportunities.

Rob Ryder-Richardson shared how University of Dundee improved their programmes’ entry requirements presentation to ensure both humans and AI bots got the most out of it. The journey through each iteration of the page exposed that the human experience is not necessarily useful for an AI bot, which then impacts the accuracy of their responses. More specifically, personalised content via location was triggering wrong answers by AI bots, since they had indexed their responses based on their location, the United States of America, and not the visitor’s location, which could be any other country in the world.

The current solution is to publish a single, plain HTML page containing all information in structured tables. This page more than 60,000 lines, making it unusable by humans but perfect for AI crawlers, allows AI bots to provide accurate answers per location. His “five things to check on Monday” slide provided an easy guide for everyone to check on their websites (higher education or not):

  • check what bots are allowed to reach.
  • turn JavaScript off and look at your key pages.
  • check what a US visitor sees on any content personalised by location.
  • write ten questions applicants really ask.
  • put them to Google, Gemini, ChatGPT, Claude and others, then see what they say about you.

And yet, humans still hold the keys

However much AI might have dominated the sessions and discussions, the human element was hard to miss. From Andrew’s opening session, highlighting human-verified as a key element for a good website, and Ulster University’s Mark Kennedy highlighting the role a very small team of 4 plays to support a community of around 400 publishers, to the very informative panel discussion where Marta Krukowska, from Bangor University, highlighted how students are asking real-life questions to make their decision to apply for any University, and Neil Allison, from The University of Edinburgh, raising the issue of cost of living for those considering Edinburgh as their study destination, all had one thing in common: real people.

Later in the day, Neil’s session focussed on how to make the most of stakeholder workshops, He provided easy, practical guidance and real-life examples to maximize engagements and outcomes in a very useful, and directly applicable, guide to human input. His premise is that workshops take many forms, but a few fundamentals sit underneath every successful one: bringing people together, solving a problem and ending with something tangible that everyone can get behind.

A slide with the title "What should a workshop facilitate?" listing Sharing, Collaboration, Democratisation, Ideation and Prioritisation as the key goals of a workshop. A diagram showing a workshop journey from diverging to exploring ideas and then covering to those that matter at the end.

Neil’s slide listing a successful workshop’s facilitation phases and goals.

A slide with the title “What should a workshop facilitate?” listing Sharing, Collaboration, Democratisation, Ideation and Prioritisation as the key goals of a workshop. A diagram showing a workshop journey from diverging to exploring ideas and then covering to those that matter at the end.

Human plus Machine

The theme of the day was “Human Vs Machine”, but the best sessions were about both: bots that need clean structure and humans who need honest answers, AI that speeds up the build and people who still decide what is worth building. The old, but always relevant acronym GIGO: Garbage in, garbage out, that Andrew referenced in his opening talk, has never been more true, and people are still the ones deciding what goes in.

As for what’s next? I have already booked Wednesday 27th of October 2027 in my calendar to travel back to Dundee for the 5th Scottish Web Folk conference.

Thank you to everyone who spoke, sponsored and chatted over coffee and lunch. If any of this sparks a thought, a challenge or a question, I would love to hear from you. Please get in touch directly at stratos.filalithis@ed.ac.uk.

Architecting a new website to support dementia research at the University

23 October 2026 at 12:32

Alzheimer’s and dementia research is a flagship strength of the University.  Websites of different research units play a key role in supporting this work. The UX Service worked with the Alzheimer Scotland Dementia Research Centre to design and launch Dementia.ed, a new home for dementia research at the University.

The University of Edinburgh is internationally recognised for research on dementia and Alzheimer’s, with different research activities occurring across groups, labs, centres in and across the various Colleges. The team at the Alzheimer Scotland Dementia Research Centre had identified a need to join up different research activities, to ensure connections could be made across different research initiatives by facilitating an interdisciplinary University network.

A website was the proposed way to meet this need, with the intention that this site would provide visibility of the different research areas, to enable academic researchers to exchange knowledge and expertise within the wider dementia and ageing research community. The site was also anticipated to have a secondary, non-academic audience: people with a general interest in learning about and supporting dementia research.

With the go-ahead to build an EdWeb2 site confirmed, Angel Garmpi from the ASDRC contacted the UX Service for help to shape the new site.

Before creating a site, we thought through a content strategy

In the seminal textbook on content strategy, ‘Content strategy for the web’ by Kristina Halvorsen and Melissa Rach, the authors introduce content strategy as a way to avoid being tormented by a burden of excess content to be managed. Starting a site from scratch is a golden opportunity to make decisions upfront to prevent content spiralling out of control, leading to website bloat and content debt further down the line.

The framework in the book outlines four elements of content strategy:

  1. Substance – what content does the site need and why?
  2. Workflow – how does the content get created and maintained?
  3. Governance – who owns the site and is responsible for its content?
  4. Structure – how should the content be organised so it can be found?

These elements served as a useful way to tease out key considerations from the start, setting a path for good decision-making and planning for the longer-term, past the website launch.

Substance: Content for dementia researchers and for people interested in dementia research

By considering questions about what the site was for, and who would visit the site and why, we were able to establish the site substance.

The ASDRC team had identified five main purposes for the site:

  1. To facilitate a network where researchers could come to collaborate with others on research work
  2. To showcase and bring together the different groups, centres and parties involved with and supporting dementia research
  3. To be a source of information where people interested in dementia research could come to read about latest insights
  4. To serve as a volunteer hub to capture details of people wishing to participate in dementia research (or make tissue donations)
  5. To act as a payment portal where supporters of dementia research could make financial donations.

Using these purposes as a starting point, we defined primary and secondary site audiences and their associated tasks to flesh out detail of the site substance.

Site audience 1 (primary): Academic researchers working on dementia and ageing

Needs and tasks:

  • Meeting other researchers and groups working in related fields
  • Establishing peers to collaborate with and exchange knowledge
  • Getting support and help with grant and funding applications

Content to support:

  • Contact details of the different groups
  • An entry point to join the network
  • Ways/touchpoints to stay informed such as events

Site audience 2 (secondary): People interested in tracking dementia research developments

Needs and tasks:

  • Finding out about dementia research in relation to a specific condition of interest
  • Staying up-to-date with advances in specific areas of dementia and/or ageing research
  • Identifying relevant academic papers and publications to form the basis of journalistic content

Content to support:

  • Publications and updates about dementia research
  • News articles about topical research areas

Site audience 3 (secondary): People wishing to take part in dementia research

Needs and tasks:

  • Registering to donate brain tissue
  • Volunteering to participate in academic research studies

Content to support:

  • A place to register interest in becoming a research participant

Site audience 4 (secondary): People wishing to make monetary donations

Needs and tasks:

  • Donating money to contribute to the progress of dementia or ageing research

Content to support:

  • A portal where financial donations can be made

Workflow: content is curated and published by the ASDRC

Considering the site substance led us to think about where this content would come from – the sources and the subject matter experts behind it. All too often, websites are built and filled with content for a launch, but without mapping out the content sources and understanding the underlying creation processes, launch-day content is at risk of quickly going stale because there is no plan in place to maintain it.

To fulfil its primary purpose of facilitating dementia research networks, the bulk of the content for the Dementia.ed site was planned to come from the different University-wide dementia research groups and initiatives. This content would be captured as links to the different sources, to ensure it was current. Events from the different groups needed to be highlighted as network-forming opportunities, so these were planned to be pulled together in a single location on the Dementia.ed site by the ASDRC team. It was also felt that the site should provide a round-up of news from different areas, which again would be curated by the ASDRC team.  Finally, the site would include static content such as: practical information about the ASDRC and the dementia research network, contact details, information about how to join the network and details for how to contribute, either donations or by participating in a study.

Taken together, this meant the initial content-related work requirement from the ASDRC team would be: to create the static content for the site in the different sections and to establish the correct links for the different research groups. Going forward, there would be a maintenance required to check the static content and the links remained correct, and to produce events and news content, which all  seemed doable given resource in the ASDRC team.

Governance: ASDRC team owns the site and manages the content

Considerations of how the new site would be governed were related to the workflow processes. A prerequisite for obtaining an EdWeb2 site is the need for a named site owner to take overall responsibility for the site, and the same ASDRC team member responsible for creating, curating and maintaining the site content had been assigned the role of site owner. This kept things straightforward in terms of decision-making about the site’s content and overall direction, although there was a need for the site owner to forward-plan a content calendar for maintenance, curation and creation tasks, and to assign responsibility to other ASDRC team members as a back-up to avoid a single point of dependency.

Structure: content arranged under common user tasks

Starting the design of a new website from a blank canvas can be difficult as there are lots of questions to consider at once. What should the menu contain? What should be on the top of the homepage? How should the content link together?

Another core textbook useful in site building is ‘Information Architecture’ by Peter Morville and Jose Arango. In this book, the authors encourage thinking about how to group or categorise content (in an organisation scheme) as well as how to establish relationships between those groups or categories (in the organisation structure).

Typically, websites adopt ambiguous organisation schemes – with content arranged by topic, subject, audiences and/or tasks to encourage browsing and discovery. This approach was appropriate for the Dementia.ed site to enable it to support the different audience groups and their associated needs and areas of interest. We considered a task

For the organisation structure – a non-hierarchical flat arrangement made most sense. Given the site was anticipated to have a relatively small number of pages, and would have clear calls-to-action for the different audiences, it didn’t seem necessary to plan a heavily hierarchical structure. For the content in the different research group sites, a hub-and-spoke model could be adopted, with Dementia.ed acting as the central hub, linking off to the different sources.

Before building, we needed to sense check the proposed site map with users

With ideas for the site mapped out, it was tempting to just get building in EdWeb2. Before creating the new site, it was wise to test assumptions with some testing.

Usability testing – where audiences are given a task to perform online and are observed as they do it – always provides an excellent source of insight into how audiences naturally interact with a digital artefact like a website, how they make sense of the menu labels and use on-page content elements to find their way to complete their tasks.

When it comes to new sites, however, it can be difficult to know what to test with users. If you mock-up a prototype, which parts should you include and which can you omit? Asking participants to make sense of menu labels that lead to empty pages can feel unnatural, and setting participants tasks can fall flat if there’s no real-life site content where they can find the information they need to complete tasks authentically. All that said, it’s impractical to build out an entire site just for testing purposes, as it’s likely the testing will reveal ways it needs to change which can end up adding more work.

We used another research network site as a proxy to test with

Thinking through the options with the ASDRC team, we came up with a plan. The ASDRC team had started looking at other research network sites for inspiration and ideas about how to build Dementia.ed, so we decided to adopt one of these sites for the basis of a test.

We chose the Edinburgh Mental Health Network (EMHN) as a testing site. This site included top level menu items: People, Research, News, Events, Blog and Contact. It had a total of 13 main pages with additional pages within the News, Events and Blog sections.

Access the Edinburgh Mental Health Network website

Since the site supported researchers in mental health as well as audiences with a more general interest in the topic, we were able to shape a usability testing protocol to use the site to assess how two audience types sought to complete representative tasks:

Audience 1: Academic researcher wanting to join the research network

Representative tasks:

  1. Find out what the network is, and its goals and values
  2. Find out how to become part of the network and what this would entail
  3. Find out about upcoming activities
  4. Find research opportunities in the network
  5. Find out how to develop your research project and involve people with lived experience
  6. Find content you can use in support of a funding application

Audience 2: Non-academic with a personal interest in the research area

Representative tasks:

  1. Find out what research is being done across the network
  2. Find out how the network is managed
  3. Find out how to keep up with what’s happening in the network
  4. Find out how you can contribute as a research participant for studies
  5. Find out how to donate money to support the research

Some of the tasks mapped clearly to specific sections of the EMHN site, whereas others were more ambiguous – they could have been completed in multiple sections. In all cases, it was useful to see how participants approached the tasks, so we could use their expectations to design Dementia.ed in the most audience-focused way possible.

We learned which menu labels worked, and which didn’t

The results of the testing gave us a clear steer on which elements of the Edinburgh Mental Health Network site supported the different user groups completing their tasks and therefore would be a good fit to adopt in the new Dementia.ed site. The tests also showed areas where the approach of the EMHN site was lacking – and therefore where different structuring and/or labelling was more appropriate.

The Events and News sections worked well

To complete tasks about finding out about activities and keeping up with what was happening, participants naturally gravitated towards the Events and News sections of the EMHN site, where their expectations of finding events to sign up to and articles to read were met.

The EMHN site was lacking a specific place for information about the network

When working on tasks geared at finding out what the network was, what its goals and values were, and detail about how the network was run, participants looked for an ‘About’ section when they used the EHMN site. When they realised this didn’t exist, they tried multiple other locations including the homepage and the Research section. This suggested an ‘About us’ section would be useful to include in the Dementia.ed site.

The People section didn’t resonate as the way to become part of the network

The EMHN site presented information for academic researchers to join the network in a ‘People’ section, which also contained information about the management of the network as well as researcher support resources. In the tests, participants struggled to find this content when tasked with finding out how to join the network, suggesting that a more explicit ‘How to join’ section would be more helpful to support this key task.

The Research section was too broad to usefully support specific tasks

Test participants gravitated towards the ‘Research’ section of the EHMN site for various tasks: to find research opportunities, to find help with research project development, to find content to support funding applications, to find out how to be a research participant and to find out how to financially support research activities.

On arrival in this section, when they realised it only contained content detailing different research activities, they went elsewhere. This suggested the need to separate out content about research activities from content supporting specific research-related tasks and to label it accordingly. In other words, instead of having a large, general ‘Research’ section, opt for smaller, more specific sections such as: ‘Research areas’, ‘Participate in research’ and ‘Donate’.

The new site has a flat structure, with content arranged by topic and tasks

Keeping site of the content strategy work, and using the results of testing the proxy site to make key decisions about structure, the new Dementia.ed site was built and launched.

The site contains six main sections, adopting a mix of topics and tasks to signpost the different sorts of content. The ‘About’ section contains background information about the dementia research network, with a dedicated page bringing together links to the different research centres and groups in a hub-and-spoke approach. A ‘What’s On’ section combines pages to Events and News content. The other four sections are labelled in task-focused ways, to ensure relevant audiences can quickly get to the content they need to complete their tasks: Join the network, Get involved, Contact us and Donate.

To ensure audiences reach content in the most direct way possible, the content in each section is either available as a top-level page, or a sub-page, avoiding long pages and deep hierarchies which may confuse those visiting the site.

Access the Dementia.ed website

If you need help architecting your website, get in touch

From start to finish, the process to design and launch the Dementia.ed website took a few months, including a few meetings between the UX Service and the ASDRC team, some short usability tests and an overall site review.

The ASDRC team provided the vision of what they wanted to achieve, and subject matter knowledge of their audience base and their associated tasks. With this information, the UX team could apply expertise to translate goals into a user-centred website, which is manageable for the ASDRC team to maintain.

We’re happy to offer help, advice and support to other University teams. If we can help, please contact us through the UX Service website.

Contact the UX Service

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.

Testing alternatives to video in student communications

Our previous research found that students often skipped videos on University webpages. This follow-up explores whether audio, timestamped videos or structured transcripts better support students in finding the information they need. 

In June, I wrote a blog post about whether students watched videos on University webpages, describing my research as part of the UX Service. 

Do students actually watch videos on websites? 

As part of that research, we ran a small qualitative study with three student participants, observing their natural behaviour as they encountered video content embedded in a student-facing newsletter from the University. We asked a simple question: when a University-wide communication points students to video content, do they actually watch it? 

Our first case study suggested the answer was often no. Two of the three participants were not engaged by video content, with one actively avoiding it and another being highly selective. In contrast, one participant was receptive to video, likely due to its relevance to his current situation, highlighting the importance of timing and context in determining video engagement. 

This blog post continues where that left off, testing why and what students would rather have instead. 

We investigated student reactions to alternative forms of video content

The obvious next question was what students would choose instead of a video if given the option. We decided to run A/B tests, which are controlled experiments that typically compare multiple versions of a digital interface, for example, a webpage to determine which performs better based on user behaviour. We recruited six participants and showed them the same newsletter in three different formats. 

  • Two participants were shown an audio version. 
  • Two were shown a video with timestamps. 
  • Two were shown a transcript, restructured into digestible text rather than auto-generated wall of text. 

The findings from this short experiment were interesting. We learnt that, of the three alternatives, the audio format was the least well perceived by the participants. The main reason was because an audio version offered no visual elements, no way to scan ahead, no quick way to extract the one piece of information someone actually needed. Even when the participants were explicitly told that audio was lighter in weight and reduced the carbon footprint of the web estate, it was still the least preferred option. 

The video with timestamps on the other hand, was much more positively received. Timestamps allow people jump straight to the relevant section rather than watching linearly, therefore allowing a more efficient way to consume information. 

Of all three alternative formats, the transcript was the clear preference of the participants, since this permitted them to quickly skim through the content and find the key information they were looking for. The transcript participants favoured wasn’t just “text instead of video”,which can often appear as a ‘wall of text’ it was text that had been deliberately restructured to pull out the key takeaway points. Taking these findings together, we learned that, for video transcripts to be easily read, and to ensure people can extract most value from them, it is worth putting effort into structuring and presenting text from transcripts, and not simply relying on the auto-generated ones.  

Our research revealed ways to make video content more impactful and effective

From a relatively small experiment, we learned a lot about the effectiveness of different formats of student communications and student preferences. The main findings were as follows: 

  1. When it came to assessing content in student communications, students did not seem to be primarily concerned with the digital sustainability of the format. While digital sustainability considerations did not drive student format preferences, it’s worth noting that the most preferred format (structured text) had the lowest environmental impact of those tested. 
  2. Audio did not appear effective for this type of student communication. Audio formats lack the scannability that students rely on, making them a less suitable choice for this type of communication. 
  3. Complying with accessibility requirements does not guarantee usability or a good user experience. A transcript can meet accessibility requirements, yet still fail to provide adequate scannability, highlighting the importance of considering both accessibility and usability. 
  4. Students prioritise their time and seek relevant information, emphasising the need for formats that can be easily updated and kept current. 
  5. More research is needed on video and text complementarity. Further study is required to determine the most effective ways to combine video and text to support communicating with students in the most effective ways possible.  
  6. When researching the effectiveness of student communications, hearing direct feedback from students is essential. A useful next step would be to ask students directly about their experiences with structured text content versus timestamped video and compare the accuracy as well as the completeness of their recall. 

We’re planning to continue our research into effectiveness of video content

Our findings have implications for the development of educational content. We shared our results with the Careers Service, who were interested in using our research to inform their content development. This collaboration has the potential to impact how they work with media in the future. Looking ahead, we would like to investigate how students interact with videos on social media platforms like LinkedIn, as their attitudes towards video seem to differ depending on whether it’s for entertainment or educational purposes. This could provide valuable insights into the role of video in student learning and engagement.

Can AI do a content audit of my website? A review of different ELM models and AI products

Content audits are a long-time staple of the user-centred website toolkit, but they take time and effort to complete, which many website owners struggle to find. In my ongoing AI experimentation, I tried using AI tools to help me with auditing web content.

Every day brings a raft of new AI developments. When choosing how to use AI, I’m less sold on getting it to do creative tasks for me because I like doing those myself. Instead, in pursuit of freeing up my time, I prefer to use AI to help me with the tedious tasks I never get around to, the ones I know will take me longer than I think, the ones I put off again and again. Here’s looking at you, content auditing.

Websites are easy to grow but difficult to keep in check

When people come to the UX Service for help with their websites, they tend to use several phrases to describe their site. These have included:  ‘It’s a mess!’ ‘It’s a bit out of control’. ‘It’s grown arms and legs’. None of this is unusual when you consider the lifecycle of websites. Over time, websites change hands. Pages once carefully crafted are easily forgotten as new editors take over. New content is created without knowing what’s already there. Very often, content needs to be published to a deadline and it’s quicker to publish a new page than seek out and amend an existing one. Seldomly do publishers want to get rid content that’s taken time and effort to produce.

Read some thoughts on content housekeeping by UX Service team members (current and past):

Digital housekeeping – applying content management practices to improve digital sustainability by me

Be a gardener by Ari Cass-Maran

Content Audit Findings and the 100k Challenge by Milo McLaughlin

How to get a grip of your website (and then keep hold) by Neil Allison

A content audit is the best place to start improving a website (not the homepage)

When people seek to bring order to disarray on a website it’s difficult know where to start, so typically, they start on the homepage with ideas to change images or add new content. While this gives sites a superficial makeover, it doesn’t really help site audiences in search of content. Fewer and fewer website audiences are starting out on homepages, instead they’re parachuting directly into site content from Google search and increasingly, from AI summaries. What does this mean? It’s more important than ever to make sure your web content is up-to-date, accurate, useful and relevant for your website users. Here’s looking at you, content auditing.

Read more about getting your content ready for AI from a recent Content Improvement Club session:

Auditing a website needs a methodical approach (which is where AI can help)

If audits are so important, why are they so easy to put off? Short answer, they can take prolonged amounts of time and concentrated effort. The larger and more complex your site is, it’s likely that there will be more content to review, and the more difficult it may be to maintain a consistent auditing approach. Going through multiple, long pages of web content, it can be easy to run out of the time you’ve allocated for your audit. Breaking the audit into chunks may lead to different results from different sessions as biases creep in. Bringing colleagues in to help can share the load, but can also introduce new perspectives and contradictory auditing decisions. There’s a need to maintain ruthless objectivity, to counter human subjectivity and avoid errors infiltrating. Here’s looking at you, AI.

If you can plan and describe a website content audit, you can ask AI to help you do it

Website content audits can be done for many purposes, but commonly, doing a content audit involves making decisions about what content to keep, what needs to go and what needs to be changed – all in pursuit of reaching a future state of your website. A good way to decide what content to keep is to consider who it’s for and the purposes it serves. If a piece of content doesn’t meet audience needs and doesn’t align with the site purpose, then it’s probably a candidate for deletion. A good content audit of a website therefore typically requires several things:

  1. An inventory of every piece of content in the site. Typically arranged in a spreadsheet, with one row per webpage. Can be organised into sections or content types, or grouped by root URL
  2. A note of the site audiences, ideally in order of priority (answering the question ‘Who is this site primarily for?)
  3. A list of the main reasons those audiences visit the site (answering the question ‘What tasks do people complete on this site?’) together with a list of the main goals of your site (answering the question ‘What do we want people to do on this site?’)

Considering each of these things as different pieces of data, where item 1 is data to be audited, items 2 and 3 are factors or auditing criteria used to decide what happens to those data (typically one of three outcomes: ‘Keep’, ‘Delete’ or ‘Modify’), I reasoned that I could give AI these data, tell it what a content audit was and and ask it to complete this process for a given website.

I experimented with ELM to help me do a content audit of a website

The University’s AI platform, ELM was the natural place to start experimenting with applying AI to aid content auditing. The ELM interface allows you to input a prompt, as well as add additional files and data sources. It also allows you to select different models to handle queries. I was curious to see the differences between the different models – both non-reasoning ones and reasoning ones so I needed to design a prompt that would work for both.

Read more about ELM and its models

ELM website

ELM new model guides (University log in required)

Being mindful of the environmental cost, I wanted to start with a small AI model (Llama 3.3)

AI comes with a significant environmental cost, which is highly dependent on the LLMs you use. Powerful models with more reasoning power are especially resource-intensive to run, so to avoid unnecessary wastage of tokens and other resources I’ve found it’s sometimes best to start with a smaller model and size up accordingly, as the need arises. The trade-off is that smaller models have limited reasoning power, however, so the responses they provide and the tasks they are able to complete can be limited.

Based on my previous experience of using AI and thinking about its potential application to a typical content auditing process, I had a hunch that providing a small model with something like a site inventory (such as a XML sitemap) and detailed data about website audiences and purposes could overload its context window and produce inferior results.

I therefore decided to begin with a lightweight prompt ‘Can you help me do a content audit of this website? (with a link to the website)’ to give a small model something manageable and learn how it approached handling the query. I chose a website that the UX team had recently worked on, so I was familiar with its content, and I entered the prompt, starting with the Llama 3.3 model – an open weights model (costed on computing power rather than per-token usage) which is hosted in University data centres (instead of being cloud-based). I toggled on the option to include web search so ELM was able to access the website.

The same prompt to different ELM models produced varied results

Having starting with Llama 3.3, I moved on to other models: Open AI’s GPT 5 and then Anthropic’s Sonnet 4.6. To assess and critique responses from each, I adopted the mindset of a person reluctant to begin a content audit and looking for AI help to kick-start action on this, and used this as a roleplay to review and compare the responses.

The response from Llama 3.3. was too generic to convince me to start auditing

Despite a glitch in formatting the response, Llama 3.3. provided some general information about content auditing. Its response included an initial assessment of the site, which made objective judgements of the homepage (assessing it as ‘well-structured, with a clear introduction’), the navigation menu (labelling it ‘easy to use with links to key sections’), content quality (noting it as ‘high-quality, informative and engaging’) and accessibility (pulling out that the site had an accessibility statement).

The response then acknowledged that in order to do a thorough content audit on the site in question there was a need to provide guidance on the aspects to focus on, and rounding off, the response noted some of the aspects a typical content audit would examine: content quantity, content quality, accessibility and consistency across different parts of a site.

Reviewing this response, I felt that if I was a site owner looking to improve my site, this response could very easily persuade me that I didn’t need to bother auditing it at all – and I wasn’t left any wiser about how to meaningfully provide guidance on the aspects to focus on if I did decide to proceed with an audit.

Likelihood to convince me to audit: 3/10

Open AI’s GPT 5’s response was detailed and thorough but a bit overwhelming

As would be expected from a reasoning model, the response when I used GPT 5 was more detailed than Llama 3.3’s. Arranged in two sections, the first part included preliminary observations using the site URL provided – which were split into the following categories:

  • Information architecture and navigation – commending the site’s positioning on user intents, yet suggesting improvements with more explicit audience pathways and call-to-action signposting
  • Content coverage and freshness – using the site’s range of content types to assess content structure and assessing freshness based on recency of news items
  • Call to actions – acknowledging that the site had were multiple calls-to-action which could be combined into primary CTAs for each audience
  • Accessibility and usability – calling out the need for more meaningful and less duplicated alt text on the site images
  • Trust and governance signals – recognising the role of the site’s strong branding to demonstrate authenticity
  • SEO – suggesting the site’s page titles and meta descriptions were reviewed for relevance

The second part of the response outlined a plan for a full audit. The plan began by posing three questions to be answered:

  1. What are the primary goals? e.g. increase visitors, boost traffic, showcase outputs
  2. Who are the priority audiences? (with suggestions of the different groups)
  3. What’s in scope? (suggesting either the entire site or specific sections)

The response then provided a suggested series of 7 steps to follow to complete the audit:

  1. Inventory and crawl (with detail of the inventory to start with and the tools to complete the crawl)
  2. Editorial quality review (with detail of criteria to score each page – such as inclusivity, accuracy, audience-fit etc)
  3. UX and IA review (with suggestions to evaluate navigation labels and connections between content and pathways to achieve top tasks)
  4. Accessibility (with suggestions of accessibility checking tools to use as well as manual checks to complete)
  5. SEO and technical (with suggestions to check data points like metatags, internal links, robots files and performance)
  6. Analytics (with suggestions to use analytic data such as bounce rates, page views, site searches etc)
  7. Recommendations and roadmap (detailing prioritisation measures to make the identified site changes)

It rounded off suggesting a template structure for the content inventory (and offering to create this template as a Google Sheet), an idea for a scoring rubric, and reiterating different tools to use (naming products like Screaming Frog, Google Analytics and SEMrush). To conclude, it offered to do the audit, requesting answers to the three initial questions and asking for access to a sitemap, external tools and governance documents (such as style guide and brand voice guidelines).

Reviewing the response, which was presented as text content, I found it a bit too much to scan and digest, and putting myself in the place of someone facing content auditing with some reluctance, it felt that this large amount of detail could be off-putting to even start the process. I could appreciate the relevance of suggesting of external tools, but knowing that each of those would require setting up accounts and logins, as well as going through a process to integrate with Open AI, it had the effect of making me mentally push content auditing to the bottom of a to-do list.

Likelihood to convince me to audit: 6/10

Anthropic’s Sonnet 4.6’s response gave structured guidance which was easier to follow

The output from the Anthropic model stood out compared to the others from ELM since it was not just plain text, instead, it had been structured with headings, tables and icons. This made scanning and digesting this response much easier than the others.

The response was structured into 10 sections, as follows:

  1. Site overview – table summarising the site name, owner, primary purposes and date of confirmed content
  2. Information architecture – list of the top-level navigation elements with an assessment of what worked well and issues identified in a bulleted list
  3. Content inventory – table of pages, with noted audiences, details of last update (if known) and inferred status (on a red, green and amber scale)
  4. Calls to action – list of CTAs on the homepage, with assessments and recommendations
  5. Content freshness – table containing list of most recent items in each section and related assessment
  6. Accessibility – list of accessible features that were present, table of items that needed checking and recommended accessibility tools to make the assessment
  7. SEO and technical – table containing an SEO assessment, considering elements like meta descriptions, structured data, mobile responsiveness – each with an allocated status, associated notes and combined recommendations
  8. Content quality and tone – list of observations and recommendations
  9. Priority recommendations summary – table of priority actions with an effort/impact score
  10. To complete the full audit I need – list of requirements to complete the full audit (including sitemap, CMS page list, Google Analytics data, etc.)

Content within each of these sections was comparable to that included in the GPT 5 response, but in the Sonnet 4.6 response, these sections referred directly to information from the site in question – for example, instead of making general assessments of site aspects like navigation and content coverage, it contained direct detail about the site itself with mention of specific pieces of content, noting what was already known (for example, referring to issues noted in the accessibility statement). Arranging this in tables with use of icons and red, green and amber priority indicators made it easy for me to pinpoint what to address and with what urgency, and having this consolidated in the final table was easier to parse than reading it in text format (as in the GPT 5’s response).

Reviewing this response from Sonnet 4.6, it was the best of the bunch from ELM, it contained enough detail to help me get started but not so much that it was overwhelming. Putting myself in the position of a time-poor site owner unsure where to start, I had clear pointers of the priority areas and a mix of quick wins and bigger tasks to choose from.

Likelihood to convince me to audit: 7/10

Three sets of two side-by-side screenshots, showing the output from Open AI GPT 5.5 (on the left) compared to the output from Anthropic's Sonnet 4.6 (on the right) showing Anthropic's more structured and visually appealing approach to presenting the responses

Three sets of two side-by-side screenshots, showing the output from Open AI GPT 5.5 (on the left) compared to the output from Anthropic’s Sonnet 4.6 (on the right) showing Anthropic’s more structured and visually appealing approach to presenting the responses

As well as ELM, I experimented with Chat GPT and Claude to provide content audit help

Models within ELM can also be accessed through interfaces provided by AI products. Two of the best-known AI products are Chat GPT (by Open AI) and Claude (by Anthropic). I was curious to see the responses each of these products would provide in response to my query asking for content auditing help so I prompted each of them in the same way. In both cases I used the free versions.

Chat GPT gave a suggested approach and produced initial findings

The response from Chat GPT was comparable to the output from ELM choosing an Open AI model, but the response was structured and annotated with tables and icons, in a style similar to the Anthropic response. It began with a suggested audit approach which set out different areas to consider and related questions. In the next section (headed ‘Initial observations’) it contained an analysis of the site itself, which included site strengths and highlighted the following six areas for improvement on the site in question:

  1. Homepage is quite academic – pulling out some audience questions that would be relevant to be answered on the homepage instead of the content that was there
  2. Navigation could be more task-focused – noting that the current navigation was driven by organisational structure rather than tasks users would want to complete
  3. News archive – picking out the need for recent articles
  4. Calls to action – acknowledging that many of these are worded to provide information not prompt an active response
  5. Content consistency – advising a uniform page structure for easier reading
  6. Audience segmentation – recommending clearer delineation between groups of site users

The response concluded with an example audit table and some content recommendations, organised under ‘Keep’, ‘Improve’ and ‘Review’.

Reviewing this response as a whole, I liked the up-front suggestion of an auditing approach and the example audit table which was then supplemented with detail about the site itself and recommendations relevant to different aspects of the site in question. This helped me visualise what the audit outputs could look like, and I could see ways to get there.

Likelihood to convince me to audit: 7/10

A screen showing the output from Open AI after being prompted for help content auditing. The suggested audit approach laid out in a table with columns for the different areas of auditing and associated questions to ask in the right-hand column

A screen showing the output from Open AI after being prompted for help content auditing. The suggested audit approach laid out in a table with columns for the different areas of auditing and associated questions to ask in the right-hand column

Another screen showing the output from Open AI after being prompted for help content auditing. An example audit table is laid out with rows for each URL, and columns containing associated purpose, audience, quality and recommendations.

Another screen showing the output from Open AI after being prompted for help content auditing. An example audit table is laid out with rows for each URL, and columns containing associated purpose, audience, quality and recommendations.

Another screen showing the output from Open AI after being prompted for help content auditing. Content recommendations are laid out with colour coding for 'Keep', 'Improve' and 'Review'.

Another screen showing the output from Open AI after being prompted for help content auditing. Content recommendations are laid out with colour coding for ‘Keep’, ‘Improve’ and ‘Review’.

Claude presented interactives to actively take me through an audit process

Anthropic’s Claude interface took a different approach to the other AI products, immediately asking about the main goal of the audit with options to pick. I picked ‘full inventory’. It then asked the desired breadth of the audit with another set of options, from which I picked ‘full site crawl’. The next screen asked me about the output format, and I picked ‘spreadsheet’.

From top to bottom, the interactive screens produced by Claude asking about the main goal of the audit, the breadth of the audit and the format for the audit output. Each has multiple choice answers to select

From top to bottom, the interactive screens produced by Claude asking about the main goal of the audit, the breadth of the audit and the format for the audit output. Each has multiple choice answers to select

After approximately 2-3 minutes, with a running commentary of what was being done, Claude presented a list of ‘headline findings’ of bugs, orphaned content, out-of-date content and broken content (dead links, incomplete calls-to-actions etc). It also produced a downloadable Google Sheet with two tabs – the first containing a summary of the issues to be fixed, their locations and a reason why they needed to be fixed, the second with a full inventory, with one row for every URL in the site and columns logging the page title, content type, date, status (with colour-coded options: ‘Keep’ (green), ‘Update’ (amber), ‘Rewrite’ (dark amber), ‘Review’ (blue) and ‘Critical’ (red)) and recommended actions for each page.

Screenshot of the audit output spreadsheet produced by Claude, showing one row per page URL and different columns logging content types, date, status and recommended actions.

Screenshot of the audit output spreadsheet produced by Claude, showing one row per page URL and different columns logging content types, date, status and recommended actions.

 

Reviewing this response, it was by far the most effective at making me feel I was starting the content auditing process and supporting me through it. Being presented with the opportunity to answer questions upfront meant I could control how the audit went, and having a spreadsheet created for me to review saved a lot of effort making this from scratch by scraping the site for a sitemap and page metadata.

Likelihood to convince me to audit: 9/10

Conclusion: If you’re putting off auditing your website, try getting AI to help

If you’re looking to improve your website, doing a content audit is one of the best steps you can take – working out what you have, what’s working and what’s not will put you in a strong place to move forward and make positive changes. Depending on how well you know your site, and how much time and resource you have to spend on it, you may appreciate some help to get started auditing its content.

From my quick experimentation with the different AI tools available I learned that, with the exception of the small non-reasoning model, each AI product offered something to help initiate the content auditing process of a website. At a basic level, asking AI to look at your website will pull out something you may not find yourself such as an out-of-date page, an irrelevant CTA or an accessibility glitch. AI can also take a zoomed-out look at your site that you may be too close to adopt yourself – such as reviewing your navigation pathways, appraising your audience segmentation or analysing the consistency of your content voice and tone.

If you’ve never audited a website before, AI can offer a lot of guidance to get you started, and whether you choose to do it yourself taking recommendations from the AI on tools and/or processes or whether you prefer to hand the heavy-lifting to AI to get your audit spreadsheet started – leaving you to deal with the more nuanced decisions that require specialist knowledge and experience, these tools can save you time and effort and may just be the nudge you need to do this all-important website maintenance task.

 

Using scenario-based research to understand how colleagues find inclusive language guidance

Earlier this year, the User Experience (UX) Service researched how colleagues find and use the University’s Inclusive Language Guide. This post explores why we used scenario-based research, what it revealed about colleagues’ behaviour and how the findings are improving the guide. 

The Inclusive Language Guide is only useful if people can find it 

The Inclusive Language Guide sits within the University’s Editorial Style Guide and provides practical guidance when writing about disability, race and ethnicity, and sex, sexuality and gender. The guide was developed in 2022 through a co-design process involving colleagues from across the University.

Inclusive Language Guide 

Having useful guidance is only part of the challenge. Colleagues also need to know it exists and be able to find it when they need it. 

More recently, we reviewed the Inclusive Language Guide to understand how discoverable it was for colleagues creating digital content. Emma Horrell has written about how this work prompted improvements to the guide’s visibility and signposting across the University. 

You don’t know what you don’t know: Improving the way we position inclusive language at the University

Why we used scenario-based research 

We wanted to understand more than whether colleagues were aware of the Inclusive Language Guide. Awareness alone does not tell us what people do when they need support, so we used realistic scenarios to observe how colleagues responded to situations where they might need guidance. 

We focused our research questions on four areas: 

  • How colleagues approached decisions about inclusive language. 
  • Where colleagues looked for support and whether they could find relevant guidance. 
  • Colleagues’ awareness of the Inclusive Language Guide and what they expected it to help with. 
  • Any gaps, ambiguities or areas of confusion. 

These questions shaped the structure of the interview and activities we designed. 

Researching colleagues approach to inclusive design decisions 

We combined semi-structured interviews with scenario-based activities to understand both colleagues’ existing experiences and how they approached real content decisions. 

We spoke to nine colleagues who create digital content 

We carried out nine interviews with colleagues in different roles across the University. Participants had a range of experiences creating digital content, including two student interns who brought perspectives of those newer to the University’s digital landscape. 

We began by exploring participants’ existing experiences 

Before looking at the scenarios or the guide itself, we asked participants about the types of content they create and whether they had ever needed to check terminology or wording before publishing. For example, we asked whether they had been in a position where they needed to consider how to word something to make sure the language was not excluding anyone. 

This helped us understand the approaches colleagues already used and the sources they relied on when dealing with these topics. 

Realistic scenarios showed how colleagues look for guidance 

We introduced a series of realistic scenarios based on everyday content tasks. 

Rather than asking whether participants knew about the guide, the scenarios allowed us to observe how they approached these situations in practice.

Example scenarios included: 

  • writing promotional content about a Pride initiative and wanting to ensure the language used was fair and respectful 
  • writing about someone who had experienced trauma and wanting to avoid misrepresenting them 
  • checking the preferred terminology for the chair of a company board before publishing a news article 

In posing the scenarios, we gained insight into where participants would usually look for this type of guidance, how confident they felt making language decisions and what they understood by the term ‘inclusive language’.

We adapted our scenarios as we learned more 

One of the original scenarios asked participants how they would write about someone elected to lead a company board. Rather than focusing on terminology, several participants described how they would research the individual or organisation before publishing. 

While this reflected realistic editorial practice, it did not help us answer the research question we were exploring. 

For later sessions, we refined the scenario so that it focused specifically on checking the preferred terminology for the role before publication. This encouraged participants to think about language choices and produced richer insights into where they expected to find guidance. 

What we learned: Four themes around finding and using inclusive language guidance

Across interviews, there were four themes that emerged consistently. 

Colleagues valued inclusive language even when they had not heard of the guide 

Across the interviews, participants consistently demonstrated that they valued using respectful and inclusive language. They were already thinking carefully about inclusive language, but they did not always know where to access University specific guidance.  

Many described that they would check terminology with colleagues or seek advice from specialist teams when writing about unfamiliar topics. They wanted confidence that they were using appropriate language. 

Awareness of the importance of inclusive language was much higher than awareness of the Inclusive Language Guide itself. 

Colleagues expected to find guidance through different routes 

The scenario-based activities helped us understand where colleagues naturally looked for support. 

Participants frequently described turning to colleagues, managers, Equality, Diversity and Inclusion (EDI) resources, staff networks and external websites. A few participants did eventually land on the guide, but they had not recalled it or looked there first. 

Several participants also relied on previous examples when writing content. Others spoke about balancing official guidance with lived experience and perspectives from the communities being represented. 

This highlighted an important consideration. Colleagues expected inclusive language guidance to be connected to the places they already look for support, linked from elsewhere rather than existing solely within the Editorial Style Guide.  

Improving signposting therefore remains just as important as the guide itself. 

Colleagues understood the phrase ‘inclusive language’ in different ways 

Participants interpreted the phrase ‘inclusive language’ in different ways. 

Some described it as “using the correct terminology”, while others framed it more broadly as “not leaving anyone out”. Those with accessibility backgrounds often drew direct connections between inclusive language and accessibility. 

Despite these differences, the term ‘inclusive’ was recognisable, with several participants using it unprompted when working through the scenarios.

Colleagues looked for practical guidance first 

After exploring how participants would approach different situations, we asked them to navigate the Inclusive Language Guide. This helped us understand whether the structure matched their expectations when looking for support. 

Several participants were unsure where the practical guidance began. Some mistook the introductory blog post for the guide itself, while others expected the examples and practical advice to appear much earlier on the page. 

Although participants valued the context and principles behind the guidance, they prioritised practical information they could apply immediately. The examples within the guide were consistently highlighted as the most useful content. 

The research continues to inform improvements to the Inclusive Language Guide 

Our findings have allowed us to identify some key areas for improvements to the Inclusive Language Guide.

Making practical guidance easier to find 

One area of focus is the guide’s landing page. We are reviewing its structure so that practical guidance is easier to find while retaining the contextual information that participants found valuable. 

The findings highlighted that the current structure does not always support the way colleagues use the guide. Participants wanted to move quickly to practical guidance while still being able to access the wider context when needed.

We are also reviewing page titles, navigation labels and the ordering of content to make it clearer where the guide begins and how it relates to the wider Editorial Style Guide. We’re considering how to better support both first-time and repeat use, making it easier for people to quickly find practical guidance while still providing the context and principles that many participants found valuable.

We’ll also consider how best to surface practical examples and support the different ways colleagues use the guide, whether they are reading it for the first time or returning to quickly check terminology and writing conventions.

Improving connections with related guidance 

The research also prompted us to consider how the guide connects with related guidance across the University’s web estate. 

Participants frequently expected to find inclusive language guidance within EDI resources or other specialist guidance. Improving discoverability means not only improving the guide itself, but also making sure it is connected to the places colleagues naturally go when seeking support.

As outlined in Emma’s blog, since completing the research, we have worked with colleagues responsible for complementary guidance across the University’s web estate to improve signposting between services.

This work will help ensure colleagues can find appropriate support regardless of where they begin their journey. 

Scenario-based research helped us understand behaviours 

The research reinforced an important principle in content design: guidance needs to be easy to find as well as useful.  

By combining colleagues’ existing experiences with scenario-based activities, we gained a better understanding of how people approach inclusive language decisions. These insights have already informed improvements to the Inclusive Language Guide and will continue to shape how we approach future content research.

QuillMark: The Technical Details Behind My Drupal Style-Guide Assistant

I previously introduced QuillMark, a tool I built to help web publishers check content against the University’s editorial style guide. In this post, I explain the technical design and methodology behind the prototype.

Introduction

My name is Shlok, and this summer I am working as an AI and UX Innovation Intern in the Information Services Group (ISG). During my internship, I have been developing QuillMark, a prototype tool designed to help web publishers check their content against the style guide. This post outlines the system design, methodology and AI pipeline behind the prototype, including how deterministic checks, language models and a MapReduce approach work together to improve reliability while keeping publishers in control.

 

QuillMark highlights violations in your existing text rather than generating an entirely new version. This:

  1. avoids the risk of AI making unnecessary changes to unrelated parts of the page, which would require a manual audit each time
  2. allows publishers to clearly see each violation and accept or reject suggested changes
  3. reduces output tokens, lowering both hallucination risk and cost

 

Problem: The style guide contains a large number of rules, around 60–70. If all rules are sent to the LLM at once, the model may not check the text against every rule reliably.

 

Research: https://openreview.net/pdf?id=R6q67CDBCH

 

Solution → MapReduce (Divide and Conquer: Map → Collapse → Reduce)

 

System Design and Methodology

 

Pipeline:

  1. Deterministic checks to flag blatant violations
  2. Fine-tuned small model flags likely obvious violations
  3. Large model audits the final page deeply for complex deeper violations

 

The deterministic checks are used to flag “obvious” violations that are directly detectable using regex or code. For example, this could include the use of a forbidden word, or a spelling convention such as using “benefited” instead of “benefitted”. These issues can be detected using a direct search of the page and do not require AI.

 

The second stage uses a smaller fine-tuned model. This model would be fine-tuned on the Style Guide rules and training examples. It would again be used to detect relatively “obvious” violations, but ones that are not simple enough to be detected reliably through deterministic checks. These issues are not highly complex, so they should still be visible to a smaller model.

 

After the publisher fixes the deterministic violations and the violations found by the fine-tuned small model, there are likely to be remaining deeper and more complex issues that both previous approaches did not pick up. The final large model can then focus mainly on these more complex issues. This means it spends less attention on obvious violations and more attention on issues that are easier to miss.

 

This improves the process in two ways.

 

First, it allows the final large model to focus on deeper issues. If the whole page was passed directly to the large model from the beginning, it would likely flag many obvious violations first and might miss some subtler issues. By fixing the most obvious issues earlier, the large model can focus more on smaller, judgement-based, or easily missed problems.

 

Second, it may reduce cost compared with running the large model multiple times. One alternative would be to run the large model once, fix the obvious issues + some deeper ones it finds, and then run the large model again to find the remaining deeper issues. In the first run, the large model may spend much of its output on obvious violations. In the second run, after those obvious issues are fixed, it may be able to look more deeply. The proposed approach tries to achieve a similar effect more cheaply by using deterministic checks and a smaller fine-tuned model before the final large-model review.

 

This pipeline is shown in Figure 1.

 

Style Guide Violation Detection Pipeline
Figure 1: Style Guide Violation Detection Pipeline

 

Using MapReduce to reduce instruction-following degradation

Based on personal experience with large language models, as well as existing research such as the Curse of Instructions, we cannot rely on a large language model to follow a very large number of rules at once. In this case, the style guide contains around 60–70 rules. If all of these rules are passed to the model in a single request, the model may not check the page against every rule properly. It may follow some rules, ignore others, or miss violations because there are too many instructions to apply at the same time.

 

To solve this, I propose using a MapReduce approach, which is a divide-and-conquer technique: Map → Collapse → Reduce.

 

The rules would be broken into smaller chunks, with each chunk containing a fixed number of rules. Each chunk would then be sent as a separate request, asking the model to check the page only against that smaller set of rules. This allows the model to focus on fewer rules at a time and check them with more attention.

 

After all the chunks have been processed, the responses would be gathered together and combined into one report. This is the collapse stage. The combined findings would then be passed through another large language model request in the reduce stage. This final request would clean up the output by removing duplicate findings, resolving overlapping issues between chunks, and filtering out possible false positives or hallucinated violations.

 

This approach makes the checking process more reliable because it avoids asking the model to apply all 60–70 rules at once. Instead, each group of rules is checked more carefully, and the final report is produced by combining and cleaning the results. This helps ensure that all rules are checked with more equal rigor, rather than relying on the model to remember and apply every rule in one large prompt.

 

The MapReduce approach is shown in Figure 2.

 

MapReduce Approach for Style-Guide Rule Checking
Figure 2: MapReduce Approach for Style-Guide Rule Checking

 

Update: Large-Model Cleanup from the Reduce stage was excluded from the prototype as the probability of duplicates occurring is low and the cost of such a cleanup is relatively high with minimal benefit.

 

Read more about the technical system plan: https://blogs.ed.ac.uk/website-communications/building-quillmark-testing-a-drupal-style-guide-assistant-with-web-publishers/

Watch a video demo: https://media.ed.ac.uk/media/t/1_yozad8ie

 

Future enhancements:

  • Strengthen Deterministic Regex-matching with more training data (web pages)
  • Audit deterministic findings using a cheap, local AI

Building QuillMark: testing a Drupal style-guide assistant with web publishers

I introduce QuillMark, a Drupal prototype designed to help web publishers check content against the University’s editorial style guide. I reflect on how I developed and tested the tool with publishers, focusing on what their feedback revealed about usability and how it will shape the next version.

Introduction

My name is Shlok, and this summer I am working as an AI and UX Innovation Intern in the Information Services Group (ISG). During my internship, I have been developing QuillMark, a prototype tool designed to help web publishers check their content against the style guide. This blog post explains the problem I was trying to solve, how I built and tested the prototype, what I learned from publishers and what I plan to do next.

 

The problem

Our style guide contains more than 60 rules covering areas such as spelling, punctuation, tone, formatting and terminology. Previous research showed that web publishers found it difficult to remember and apply every rule while writing and editing content.

 

This is understandable. Publishers are often working under time pressure, and checking a page manually against dozens of rules adds a significant cognitive burden. Even experienced publishers can miss small details, particularly when they are concentrating on the meaning and accuracy of the content.

 

I began exploring whether a tool could make this process easier. The aim was not to replace publishers’ judgement or rewrite their content automatically. Instead, the tool would identify possible style-guide violations, explain the relevant rule and allow the publisher to decide whether to apply or dismiss each suggestion.

 

This became QuillMark.

 

Read more about the Style Guide

 

Why I built the prototype in Drupal

Drupal is where publishers already create and edit web content, so it made sense to build the prototype directly into that environment rather than create a separate tool.

Before starting development, I attended Drupal in a Day to understand the platform, its content-editing interface and how a custom tool could fit into an existing publishing workflow.

 

Building QuillMark within Drupal meant publishers could check their content without copying it into another system. It also allowed me to test the tool in a realistic environment, using the same types of fields, buttons and interactions that publishers encounter in their day-to-day work.

 

Read more about Drupal in a Day

 

Planning the checking process

Before writing the prototype, I planned the system in detail.

 

One of the main design decisions was that QuillMark should highlight individual issues in the existing content instead of generating a completely rewritten version. Rewriting an entire page could introduce unnecessary changes and would require the publisher to audit every sentence. Showing individual findings makes it clearer what the tool has identified and keeps the publisher in control. This also prioritises the HITL (Human-in-the-Loop) framework, which I intend to use in my AI-based projects to ensure that people remain involved in reviewing decisions made by AI.

 

The system design proposed three types of checking:

  1. Deterministic checks for clear violations that can be identified using code or regular expressions, such as prohibited words or spelling conventions.
  2. A smaller AI model for relatively straightforward issues that require more context than a simple text search.
  3. A larger language model for more complex, judgement-based rules involving areas such as tone, structure or plain language.

 

The plan also used a MapReduce-style approach. Rather than asking a language model to apply all 60–70 style-guide rules in one prompt, the rules would be divided into smaller groups. Each prompt could then concentrate on a limited number of rules before the results were combined. This was intended to reduce the risk of the model overlooking instructions because it had been given too many at once.

 

The original design included an additional AI step to remove duplicate findings and resolve overlaps. I left this out of the prototype because duplicates were expected to be relatively uncommon, while the extra model request would increase cost and complexity.

 

Read more about the technical system plan: https://blogs.ed.ac.uk/website-communications/quillmark-the-technical-details-behind-my-drupal-style-guide-assistant/

Coding the prototype

I developed the prototype iteratively, beginning with a small number of style-guide rules and expanding the checks once the basic workflow was working. For development, I used Codex. I gave it my plan and asked it to design the architecture. After reviewing it, I asked it to proceed with the implementation.

 

The first stage used deterministic checks for issues that could be found reliably without AI. These checks searched the content for recognisable patterns and returned the location of the issue, the relevant style-guide rule and, where appropriate, a suggested correction.

 

The second stage used a large language model to identify issues that depended more heavily on context. I divided the rules into smaller prompt groups so that the model could focus on a manageable set of instructions during each request.

 

The prompts asked the model to return structured findings rather than a rewritten page. Each finding needed to include enough information for QuillMark to:

  • identify the relevant content;
  • explain the problem;
  • show the related style-guide rule; and
  • suggest a possible correction.

 

Publishers still had to approve or dismiss each finding. This human-in-the-loop approach was intentional. Style rules can depend on context, and an automated suggestion will not always be appropriate. QuillMark was designed as a decision-support tool, not an automatic editor.

 

Watch a video demo: https://media.ed.ac.uk/media/t/1_yozad8ie

 

Designing the usability test

Once the first iteration was complete, I adapted an existing usability-testing template to create a test for QuillMark.

 

I conducted three sessions with web publishers. Participants were asked to work through a series of tasks covering the main parts of the prototype, including running the checks, understanding the two stages, locating an issue in the editor, reviewing a rule and applying or reverting a suggested fix.

 

I observed how participants used the interface, where they hesitated and whether the information on screen matched their expectations. I also asked how they might use the tool as part of their normal publishing process.

 

The purpose was not only to find technical bugs. I wanted to understand whether the concept itself was useful and whether the interface communicated how the tool was intended to work.

 

What publishers told me

The publishers thought the tool would be useful as a final check before publishing. They said they would still use their own judgement and would not automatically accept every suggestion.

 

Most of the feedback was about the usability of the tool. Some parts were unclear, such as the difference between the two stages and some of the button labels. There was also too much information on the screen, and some issues were repeated. The publishers also wanted to see what a suggested fix would change before applying it.

 

What I learned

The testing suggested that the core idea is useful, but the user experience needs to become simpler.

 

Publishers do not necessarily need to understand which checks use regular expressions and which use an AI model. They need to know what issue has been found, why it matters, what the proposed change is and what action they can take.

 

The sessions also reinforced the importance of designing for scanning. More explanation does not always create more clarity. In a publishing workflow, concise labels, clear states and well-grouped findings may be more valuable than displaying every piece of supporting information at once.

 

Next steps

My next step is to refactor and review the prototype code before making changes based on the usability feedback. This will include reviewing the AI-generated code to check whether each section is needed, whether the same result could be achieved more simply, and whether any parts repeat code that already exists. I will compare the generated code with the rest of the codebase so that it follows the same structure and does not add extra functions or files without a clear reason.

 

Where the code is longer than needed, I will simplify it by removing repeated checks, combining similar sections, and reusing existing functions. I will also keep individual files to a manageable size, generally no more than 1,000 to 3,000 lines depending on the file. Larger files will be split where this makes the code easier to follow, and hardcoded rules will be moved into the database where possible.

 

The next iteration will focus on:

  • clarifying or simplifying the two-stage workflow;
  • reducing repeated and overwhelming findings;
  • improving button labels, status messages and colour distinctions;
  • previewing changes before they are applied; and
  • making the interface more concise and easier to scan.

 

June Content Improvement Club: Is your content AI ready?

Our June Content Improvement Club session focused on AI. In particular we discussed the changes in search behaviour, how that’s impacting the way people consume content and some of the things you can do to make your content ready for this new search landscape. Attendees also got the chance to work in groups to put some of our top tips into practice.

This topic clearly resonated with with our community, as it was fully booked shortly after being advertised, so we ran a second session to enable more people to attend.

Changes in search behaviour in the wake of AI overviews

We started off the session by providing a bit of context around what has led to the change in the way people now search for information.

AI overviews help answer your question on the search results page itself

In 2024 AI overviews were launched by Google to answer search queries directly on the search results page. AI overviews take snippets of content from relevant webpages (often combining multiple sources) using Google’s existing search index and the same ranking systems as regular search.

Since their introduction, AI overviews have rapidly increased and are now a prominent feature on the majority of search results pages. U.S data from the end of 2025 shows that overviews appear in over 60% of all search queries, doubling from 2024.

New Data: Google AI Overviews Now Appear in 60% of Searches

The information source is attributed using tags, which contain a link to the website itself. However, we are seeing a trend of people finding the information they need and relying on the overview without visiting the website where the information originated. This is known as ‘zero click behaviour’.

Screenshot of an AI search summary about how to apply to the University of Edinburgh, with the University logo displayed. There is a circle around the source tag for emphasis.

Example of an AI overview

 

 

 

 

 

 

 

 

 

The rise in ‘zero click behaviour’

The introduction of AI overviews has meant that people have started to become accustomed to getting an instant answer on the search results page. People are more often relying on overviews, rather than clicking a link to a relevant webpage to locate the information themselves. This means fewer people are making it to your webpage and if they do it may well be later on in their search journey.

In Q1 2026 studies report that 65% of searches on Google did not result in a click to anywhere.

Zero-Click Crisis Worsens – SuperPrompt

This figure is predicted to be significantly higher for those using mobile when searching.

Also statistics from 2025 show that 80% of people used answers directly on search pages and 50% relied on AI summaries for answers.

Zero-click searches reshape marketing strategies in 2025

These changes in search behaviour do require you to think a bit differently about the way your content is being used. This is summed up well by Guus Goorts, an education marketing coach, who says:

LLMs [Large Language Models] increasingly visit  your website on your audiences’ behalf.

Ways to make your content ready for AI

In the session we focused on the things that you can do to optimise your content for AI. Hopefully you will be glad to know that much of the evergreen content design advice we provide still stands strong in the face of the new AI search landscape.

Clear, self-contained content gives AI better material to work with

As AI can sometimes take just snippets of your page or grab sentences out of the wider context, one step you can take is to try to make sure that content makes sense even outwith its surrounding context.

The more self-contained and specific your content is, the more likely it is that AI systems will interpret it correctly and present accurate information to users. You can achieve this by avoiding:

  • non-specific or generic headings that rely on page context, but do not make sense when lifted off the page – for example ‘Funding’ rather than ‘Postgraduate funding options for international students’
  • references to content elsewhere on a page such as ‘see below’ or  ‘as mentioned above’ as AI may retrieve the sentence without the content it refers to
  • vague descriptors in the form of unclear or missing subjects such as ‘This must be submitted with your application’ as if the surrounding text is missing, neither the reader nor AI knows what ‘this’ refers to
  • videos without transcripts, captions or summaries as AI tools cannot watch video content, they process text far more reliably than video

Answer questions directly and avoid unnecessary preamble or woolly language

AI predicts likely answers from the content it finds. It can potentially miss the answer if it’s buried in long winded sentences, or not clearly explained.

In the session we gave the example of a prospective student asking: “What accommodation does the University offer?”

We provided two example bits of content that the AI could draw from.

Example 1 : ‘Our accommodation includes single rooms, shared flats and accessible housing.’ This contains the answer directly, it names the accommodation types and it can be lifted into an overview without losing meaning.

Example 2: ‘There are lots of options of different accommodation with various numbers of rooms depending on your needs.’ Whilst this sounds friendly it doesn’t provide much useful information. Phases such as ‘lots of options’ and ‘to suit your needs’ take up space without answering the question.

Content that is well structured and accessible is still key

Making sure your content is both well-structured and accessible is still key when we are looking at how AI will use and interpret it.

Frequent, meaningful headings add structure

Headings are one of the main ways people navigate content, they act as signposts, helping users quickly identify relevant sections and understand what information sits underneath them at a glance.

Frequent, meaningful headings also play an extra role in supporting the AI-generated summaries we know are becoming increasingly common. This is because headings help AI understand the structure of a page by breaking content into logical, retrievable chunks.

Headings also create a hierarchy that shows the relationship between different pieces of information on a page. Therefore, you should always mark up headings with the correct heading level, rather than using bold, underline or larger font sizes. AI also uses the heading hierarchy to:

  • understand, summarise and cite your information
  • work out which topics are primary, which are subordinate, and how information is grouped together

You can read more about using headings effectively in the style guide, our previous blog post and also on Caroline Jarrett’s ‘Editing that works’ website.

Accessible content and AI overlap

Content that has been made accessible is a big step towards being AI-ready as screen readers and AI systems rely on many of the same signals, although the outputs are different. Therefore many of the things you hopefully already do to make content accessible will also help AI understand it. We can demonstrate the overlap by looking at headings, link text and alternative text.

Headings: screen reader users use headings to navigate the page structure, whilst AI tools will use them to understand and prioritise your content.

Link text: descriptive link text provides context and helps screen reader users decide where to go next, whilst AI tools will use this link text to help interpret page meaning and relationships between content.

Alternative text: well written alternative text helps users who cannot see images extract meaning from them, whilst it also provides text that AI can use to understand image content.

You can read more about how to make your content accessible in Mel’s blog posts from previous Content Improvement Club sessions:

Descriptive link text supports users and AI

Descriptive link text is important for users as it helps them understand where the link will take them at a key decision point. This is increasingly important for AI too as AI search and retrieval tools use links and their surrounding context as signals to understand the relationship between different pieces of content.

Therefore, a link labelled ‘Accommodation options for postgraduate students’ provides a much stronger signal than ‘Learn more’ as it helps AI understand both the destination content and how it relates to the current page.

Descriptive link text also helps AI-generated summaries and citations. When AI retrieves content to answer a question, it attributes the source(s). Clear link text can reinforce what a linked page is about and strengthen the connections between related topics.

You can read more about writing effective link text in the style guide and Caroline Jarrett’s ‘Editing that works’ website:

Write for humans, using plain language

In the age of AI, it’s still important that we write for humans first and foremost. This means using language that your users understand within your content and explaining terms they might not know. Short paragraphs and sentences will also help.

Google’s advice for content to be successful with Google Search is to focus on creating ‘people-first content’, rather than content made ‘primarily to gain search engine rankings’.

Creating Helpful, Reliable, People-First Content | Google Search Central 

You may find Nick’s blog post from a previous Content Improvement Club useful on this topic:

Now you’re speaking my language – what we covered in the February Content Improvement Club session

We worked in small groups to put the theory into practice

After our whistlestop tour of advice to help make content AI-ready, we then worked in small groups, using pages that attendees had brought along to the session. We each picked one or two areas to focus on and shared suggestions to improve the content and talked about what was perhaps already working well. This created some interesting discussion and allowed attendees to gain feedback and new perspectives on their content from colleagues they may not usually work alongside.

Frequently Asked Questions – the debate continues

The debate around the effectiveness of Frequently Asked Questions (FAQs) is one which has been circulating for some time within the content design world. It has reared it’s head again in relation to AI, given the rise of the ‘answer economy’ where people are typically asking more focused questions and looking for a quick answer.

The main point of contention is whether or not we should be writing more content in a question and answer format. There are different views on this topic, we’ve seen advice to use questions in your content that aim to match the questions that users are asking AI tools.

On some interpretations of this advice, you could read this as a call for more FAQs on websites. We’d like to urge caution before you take this approach though as FAQs aren’t without their problems.

FAQs can often:

  • duplicate content that you have elsewhere on the site – this causes problems for site maintenance and search engines don’t tend to like it
  • answer questions that aren’t really frequently asked
  • make content hard to scan because they push keywords away from the left of the screen as they often start with ‘Can, What, How, Where’

So in summary, don’t rush to change all your headings to questions and create more FAQ sections. If you do use questions, answer them without waffle.

The University of Bath have written a helpful article about this topic.

Why AI doesn’t need Frequently Asked Questions (FAQs) | Digital Content and Development

Content maintenance is more important than ever

The final point we covered was the fact that content maintenance is more important than ever. This is because all published content can be cited by AI to generate an answer regardless of when it was last reviewed or updated. Therefore ensuring that you know what live content you have and whether it’s up to date is key if you want AI to bring back accurate information in response to search queries.

Duplicate content can also confuse AI, so regularly auditing your content to make sure there is effective cross referencing between pages and that the same information doesn’t appear on multiple pages, will again make it easier for AI to interpret and find what it needs.

How to hear about future sessions

We promote these sessions via our mailing list. If you’re interested, please sign up:

Join the UX and Content Design mailing list (University login required)

Suggest a topic for a future session

We’re keen to continue covering topics that colleagues across the University would find useful. It would be really helpful if you could let us know any ideas you have using this form:

Suggest a topic for Content Improvement Club (University login required)

Other training that we offer

More training is listed on the User Experience Service website:

Training | User Experience Service

Redesigning the ‘Understand what your content is for’ module of the Effective Digital Content course

A year on from the relaunch of our Effective Digital Content online course, we’ve recently made some improvements, particularly in relation to the ‘Understand what your content is for’ module. We’ve rewritten the module, moving from a video to a text-based format.

In this blog I’ll share a bit about the updates we’ve made and the thinking behind them.

Over the last year we identified ways to improve the module

It was always our intention that the course would follow a cycle of continuous improvement, where it would evolve when we identified ways to make it better for learners.

Over the past year, we’ve learnt quite a lot about what makes a module effective through our work to adapt the course for external audiences. Although this project has paused for now, the work has allowed us to improve the course for University colleagues.

We’ve also continued to learn about people’s preferences in how they like to consume information, as well as the environmental impact of the content we create and maintain.

Developing a proof-of-concept course for external audiences gave us a fresh perspective

When exploring how we could evolve the course for external audiences earlier this year, we had to think about new ways to teach certain concepts. The video in the first module explaining the importance of understanding the audience and purpose of your content was one of the areas we knew would need most work. The video had been produced many years ago, specifically for University staff and therefore contained various terms and references that wouldn’t be appropriate for an external course.

We knew how important it was to get this module right as the principles it teaches underpin the rest of the course topics. It involved going back to the drawing board to consider the key learning outcomes of the module and the practical skills we wanted to teach. This process provided the opportunity to re-imagine what the module could become and importantly whether we needed video to convey key messages.

Screenshot of notes from a Miro board showing the key learning outcomes we decided on for the module, as well as sticky notes to identify what outcomes come from: reading the text, doing the set exercises, selecting own web content and doing activities on that content, and getting feedback on exercises on own content.

Planning the learning outcomes for the module on a Miro board.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ongoing user research showed video was not always the preferred format

We were also aware from speaking to colleagues who had taken the course and in usability testing of the new module, that video was not always their preferred method of obtaining information. Some colleagues mentioned that their preference would be to view or download the transcript instead of watching the video in full, even if the video was relatively short. The benefits of this approach were that they could digest the information at their own pace and be able to refer back to relevant points more efficiently, rather than having to locate the correct place in the video.

These insights, alongside the time intensive process involved in producing and maintaining a new video influenced our decision to reconsider whether a text-based format would work better.

The environmental cost of media use cannot be underestimated

We’ve also been learning through ongoing research into digital sustainability about the environmental cost of media use, particularly images and videos. We’ve learnt the importance of considering the value that the media brings before choosing it as a medium to communicate your message. You can read more about this work in my previous blog.

Videos and images – when do they add value and not just page weight?

As a result, we’ve been questioning whether the video we previously used in the course enhances clarity, context or understanding, or whether we could convey the same information without it.

The module has evolved but the underlying principles remain

We came to the conclusion, based on user feedback and our own inclinations about how to improve the module, that we would remove the current video in the internal course and replace it with a freshly written text format module.

The underlying principles of the module stand true – that the starting point is always to think about the audience and purpose of your content. As a result, the accompanying workbook activities for the module remain unchanged.

There are a few new additions to the module

We’ve added in a new section to explain the key concepts of user needs and business needs, which should help to provide a good foundation for later modules. There are also some more practical University related examples of key concepts.

The previous iteration of the module didn’t have any interactive elements. We’ve received positive feedback on the quiz questions we’ve included in other modules of the course so we decided to include two multiple choice quiz questions so you can check your understanding as you go.

How to take the course

If you’d like to take the Effective Digital Content course, you can find more information on our course page, including a link to enroll through People and Money.

Effective Digital Content

Representing the University at UCISA Women in Tech 2026: My takeaways and reflections

I was pleased to have a talk accepted at the annual UCISA Women in Tech (WiT) conference. I went to Newcastle for a day of talks, workshops and networking. I left with a better understanding of the WiT community , and a reinforced appreciation of the need for inclusivity in Higher Education.    

UCISA is an industry body supporting digital professionals working in the education sector. I have been actively involved in UCISA since 2022 when I helped set up the UCISA UX Group and became co-chair of this UK-wide community of practice. I’ve organised many UCISA UX events but had not attended one of UCISA’s flagship annual conferences, the Women in Tech event, until this year. My presentation about our project on staff profiles resonated with attendees, I learned a lot about diversity and representation in the sector from attending the other talks and I enjoyed connecting with other Higher Education professionals over shared inclusivity challenges. Here, I reflect on my highlights from an interesting day.

Sharing our staff profiles work piqued interest from other universities

As well as the clear focus on inclusivity, one of the themes of this year’s WiT was real-world applications and problem-solving. I felt our staff profiles project spoke to this theme, so I submitted a talk to share what we learned from research and the steps we have taken towards finding a new profiles solution.

My session was well received – perhaps unsurprisingly, colleagues from other institutions shared the same concerns and challenges in designing a profile solution that showcases staff in the best light, keeps them findable in searches, and yet remains easy for staff to update. I valued the chance to make new contacts, exchange ideas, and learn about other institutions’ diverse approaches to the ‘profiles problem’. I resolved to stay in touch as we take steps towards implementing a profiles solution at the University, recognising just how universal this need is across the Higher Education sector, and seeing an opportunity for meaningful collaboration.

Read more about the staff profiles project in the blog post series:

Collected blog posts about staff profiles project

Results of a 2025 WiT survey revealed risks and opportunities

One of the core activities of the UCISA WiT committee is to regularly collect data to understand diversity within IT departments across the FE/HE sector. At the conference, WiT committee co-chairs Christi Hopkinson and Katie Wilde shared a preview of the results of the 2025 survey, completed by more than 200 respondents from 66 institutions, with 74.5% of the respondents identifying as female. Several findings stood out from the preliminary report in terms of risks and opportunities.

There’s a risk of retention due to barriers to progression

Responses to a question about progression routes revealed significant proportions of respondents had started in IT in the following areas:

  • First/Second Line Support
  • Application Support
  • Business Analysis
  • Project Management
  • Web Development

Responses to a follow-up question about the roles respondents were currently working in showed continued representation in these areas, which indicated a degree of stasis when it came to progression in the sector. Areas where women were underrepresented included:

  • Infrastructure
  • Security
  • Enterprise Architecture
  • Senior Management.

The survey results showed a third of respondents had considered leaving their institutions or the sector, citing pay, workload and progression as popular reasons motivating them to think about moving on. Common blockers to progression included:

  • Lack of available higher-grade roles
  • Promotion structures tied only to management, not technical excellence
  • Career pathways not transparent
  • Women having to ‘prove more’ to progress

There’s potential to be gained by investing in non-technical skills

Most respondents cited the following skills as important for the roles they were currently in as well as for progression:

  • Problem solving
  • Communication
  • Analytical skills
  • Customer service
  • Business analysis
  • Strategic thinking

This spread of skills reinforced the value of focusing training and development on non-technical abilities to complement technical skills, and to ensure expertise was appropriately directed to deliver on broader institutional goals.

There’s room to improve on diversity, inclusion and discrimination

Responses to questions about inclusion and belonging revealed positives and negatives about the workplace respondents were part of.

On the positive side:

  • 79% felt valued as part of a team
  • 67% felt they were treated fairly and equitably

On the less-positive side:

  • Only 34% felt the leadership reflected diversity in the workforce
  • 41% felt there were opportunities for careers advancement
  • 46% felt their organisation supported under-represented groups
  • 47% were satisfied with their organisation’s diversity initiatives

The spread of these numbers provided a clear steer of areas to focus on to achieve less exclusive, and better-balanced IT workplace.

Achieving inclusivity starts with individuals and requires thinking beyond statistics

The survey data gave a snapshot of the current state of inclusivity in the sector, however, anecdotes from individual presenters painted a more vivid picture of what inclusivity could look like. The WiT programme included several women sharing stories of their induction into tech and reflecting on their individual progression routes. It was refreshing to see the diversity of pathways they had taken and interesting to hear about what they had learned along the way, and their tips for success.

Monica Jones, Chief Data Officer at the University of Leeds acknowledged that career progression paths rarely run smoothly, and advised setting personal goals and milestones to work towards, to be best-prepared for promotion opportunities when these came up. Julia Lloyd, College Manager – Business and Law, at the University of the West of England, emphasised the benefits of ‘quiet leadership’ and shared tips to create space for different voices – such as thoughtful structuring of meetings, design of communication channels and rewarding contributions over confidence. A joint talk ‘The Not-So IT Crowd’ from Catriona Blair, Joanna Addison and Sasha Titus from the University of Kent, and a session by Amber Mothersille from the University of Northampton emphasised the value of non-technical skills in technical roles – recognising the need for empathy, trust-building and adaptability to strengthen teams and build excellent digital services.

Breaking barriers requires breaking old biases and habits

A final takeaway from attending the WiT event was a call-to-action to question the way we work – specifically to foster inclusivity by making room for new ways of thinking and for fresh perspectives.

In an interactive exercise led by Katie Wilde, we considered five roles necessary for the operation of successful teams (the Navigator, the Connector, the Builder, the Challenger). In a period of honest reflection, we shared the roles we naturally adopted in team settings, and the roles we tended to overlook or disregard. Going through this exercise was a good leveller as well as a reminder to make room for diversity in everyday team settings instead of relying on familiarity.

The day closed with a thought-provoking talk on male fragility, delivered by Jake Dovey, a UCISA mentor. Drawing on personal anecdotes experienced through his involvement with UCISA, Jake’s talk described instances where men had overreacted defensively to being challenged and where women had inadvertently softened situations to avoid potential conflict and ‘keep the peace’. Jake challenged the women in the room to recognise these instances going forward, and prompted a call-to-action for all to recognise these harmful patterns and call them out to collectively help break the disruptive cycle.

Final thoughts – WiT26 was less about women and more about inclusivity

WiT26 delivered a packed programme which encouraged me to think outside my work in UX and more broadly about the joint responsibilities we all have in creating and fostering an inclusive work environment. I came away with recommendations of books to read and concepts to learn more about, and a heightened awareness of embedding inclusive practices in my day-to-day work and activities. I am keen to see the full results of the WiT 2025 survey and to remain part of the WiT community going forward.

 

❌
❌