❌

Normal view

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

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.

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.

 

❌
❌