Why do university IT systems drive staff round the bend?

Edinburgh’s finance chaos exposes deeper problems with the tools institutions rely on to function day-to-day

November 16, 2022
Man with tangled computer cables
Source: Alamy

The University of Edinburgh was recently brought to a near-standstill by a switchover to a new payments system, with PhD students going unpaid, contracts cancelled and the overseers of multimillion-pound research projects unable to order basic necessities such as paper.

While an extreme example, the case demonstrated what many who work in higher education have known for years: the systems universities rely on to function on a day-to-day basis are often apparently not fit for purpose.

It is feared that such endemic problems with digital infrastructure will now hamper the sector’s ambitions to pivot to offer more online and hybrid learning, with technologies unable to cope with expansion drives into areas such as microcredentials and lifelong learning. In a survey conducted last year by Jisc, the UK sector’s main technology agency, 82 per cent of staff reported experiencing technical problems while teaching online.

“Over the years universities have spent billions of pounds on the physical estate but the investment in digital infrastructure and the digital campus hasn’t been commensurate with that,” said Neil Mosley, an online education consultant who advises universities on their use of technology.

“In many universities there remains a patchwork of old legacy systems that don’t provide the kind of foundations needed to meet growing ambitions about the digital and online experience and that make it increasingly difficult to offer a modern user experience for staff and students.”

The autopsy over what went so wrong at Edinburgh is ongoing but the underlying issues that appeared to play a part will be familiar across the sector. In an attempt to streamline and centralise processes, a new expensive bespoke system was introduced but did not work as intended, with staff desperately left to try to pick up the pieces and find workarounds.

Similar themes were echoed in the responses to Times Higher Education’s recent work-life balance survey, in which higher education staff frequently blamed systems and processes that were ostensibly supposed to save them time for adding to their workload.

“A review of IT systems and positive change would greatly help,” was one common response from an HR professional when asked to make suggestions on what universities could do to relieve stress.

“The bureaucracy always increases,” said another respondent. “It doesn't help that we use several different IT systems that don’t talk to each other or aren’t fit for purpose so we have to create in-house solutions at dept level.”

One particularly disgruntled respondent was a lot blunter: “In the 1980s I worked in call centres. I was using better systems then than I use at the university now. It has reached the stage where I am actively looking for other jobs because of the poor IT system.”

Amanda White, deputy head of education at the University of Technology Sydney’s Business School, said many systems universities use were built to do highly specialised things with little thought as to how they connect together.

Pre-pandemic, people were relied upon to join up the dots, she said, but after job losses during the pandemic this administrative burden has been added to the workloads of those who are left, often stressed academics.

Mr Mosley said the sector has struggled to offer competitive pay to attract skilled IT professionals to lead on making improvements to digital infrastructure and there is only a “small talent pool of those that can support some of the old systems in use”.

To fix the problems, he said, “It’s going to take significant investment, effort and upheaval to metaphorically dig up the road to create a foundation for a modern digital campus.”

But a survey of chief technology officers at US institutions conducted by THE’s sister publication, Inside Higher Ed, recently found around half of those polled do not expect their total budget for central IT operations to increase next year. Less than half indicate that digital transformation is a “high priority” or “essential” for leaders at their institution.

Things might be changing, however. Sarah Knight, head of learning and teaching transformation at Jisc, said post-pandemic there had been a “huge shift” among university leaders and much more recognition that the next stage of a university’s development is going to require “robust infrastructure and staff who are digitally competent”.

“Most universities are very aware they need to get this right. Investment needs to continue in relation to building those systems and improving those platforms,” she said.

Dr White said while many universities have decided the investment is needed, uncertainties over future income are weighing heavily, forcing institutions to make difficult decisions over where to allocate scarce resources.

tom.williams@timeshighereducation.com

Register to continue

Why register?

  • Registration is free and only takes a moment
  • Once registered, you can read 3 articles a month
  • Sign up for our newsletter
Register
Please Login or Register to read this article.

Related articles

Five years ago, a THE poll painted a bleak picture of work-life balance in the academy. Has the subsequent rise of homeworking eased the pressure? Or are ever-increasing workloads outweighing any benefits of flexibility? Tom Williams reports on our survey of 1,200 university staff

10 November

Reader's comments (10)

In my experience, a major problem is one that I helped to fix many years ago in a commercial role; those implementing the systems do not properly interview the users to see what they actually need. By designing a system based on such information, the difficulties are reduced. Of course, that is not "sexy" and may not line up with an ambitious IT manager's vision that they hope will lead to promotion and praise from the university hierarchy...
Linux and OpenSource - otherwise paying through the nose.
The key problem here is that IT cannot automate something that is neither optimised nor standard and many orgs do not want to do either of those as a fundamental cultural norm. They end up creating manual handovers, rework and duplicated effort and try to code their way out of it. Couple that with an unhealthy approach to not using partners and consultants means the reliance on in house to solve is problematic. Finally the lack of tech savvy leadership at the top level or the marzipan layer (more importantly) is tricky, most decisions are driven by the only common language people have … finance … rather than by understanding process and business. I recommend looking up Jeanne Ross (MIT) and Design for Digital … Btw according to her research 75% or organisations are in the same boat. This is not restricted to HE.
Investment will not go to IT services. I have talked to people working in that department and they are not so sure this investment will ever take place. The hours spent trying to work around inept tech systems, leads staff to despair.
Investment will not go to IT services. I have talked to people working in that department and they are not so sure this investment will ever take place. The hours spent trying to work around inept tech systems, leads staff to despair.
A common issue in the introduction of any new system is a failure to include end-users of that system from the very outset - design as well as implementation. Drawing on my own experience as a commercial developer I introduce Computer Science students to the concept of 'consultancy by walking around' that I used to use - spending time wandering around a client site talking to everybody about what they needed to do and how they wanted to do it, then designing computer systems around that. I have some good 'disaster stories' from when that wasn't done, too. By the time they come to their final year projects, it's interesting to see them prowling in search of prospective clients for whatever it is they are creating!
I'm in a university IT dept. In my opinion this article fails to consider or understand that universities need a vast number of systems to deal with the vast number of functions that modern universities undertake. The call centre that one of the sources mentioned probably had a very limited system portfolio. Probably a system to handle the telephony, one to record whatever they are selling or supporting, a system to handle payroll, maybe some networking. A university needs an enormous portfolio of systems, because universities are made up of a bewildering collection of faculties, schools, departments and teams which have some needs in common and a lot that are specific to themselves. So you have an ecosystem made up of some large third-party systems, a glut of smaller third-party systems, a bunch of bespoke systems, and a layer to make them talk to each other when they need to. Even the third-party systems often need customising as well, just to get them to work as the institution needs instead of as the supplier imagines a fictional standard university might need. Consultants are used all the time, in my opinion they are frequently not worth the huge sums we pay for them; they parachute in with limited knowledge or understanding of how a university works, do what they do, then leave and never have to face the consequences of what they leave behind in their wake. The IT department has to try and understand it all and make it all work with relatively few people There's no simple solution to this problem.
Yes it is exactly as above. Under resourced, poorly paid teams trying to support huge numbers of systems. Consultants who often just want to provide an easy off the peg solution whilst not fully understanding the business . Senior leaders who don't want to resource anything properly and have a tick box approach to IT . Ridiculous approvals frameworks and governance meaning solutions are often outdated before they've even been implemented. No resources devoted to experimentation or testing environments. Sheep mentality - just copying what the University next door has purchased. Stakeholders unwilling or unable to provide proper requirements. Unrealistic expectations of procured systems. No accountability or lesons learnt from failures. How can we expect things to be better working in this kind of environment ?
All older academics know that the administrative burden has increased hugely over the last 30 year. But fewer understand that while some of this is a result of scale - larger institutions - it is overwhelmingly driven by the increase in mandatory government reporting. Current IT systems are pressed into service to provide data that will satisfy government; everyone in the institution finds themselves playing the primary role of data provider to those systems. At the same time IT has provided a way to replace a lot of really low-value jobs - again, partly because we can now type our own papers for journals, timetable classes, manage the production and distribution of handouts. And in my experience, many academics love to moan about the lack of support, while being far too controlling ever to let go of any minor detail if you do offer support. So now we have added a huge amount of work, and shifted the balance of resources across the institution, but few institutions have the maturity to understand how much that is worth as a proportion of the total budget. They simply don't believe that it can cost that much to create and maintain effective systems, so they starve the IT people of resources, which then creates a downward spiral. Key systems are updated too late; keeping the old ones going costs too much (including opportunity costs for what might be done with that cash otherwise); everyone suffers as a consequence of the poor quality, and that creates further opportunity costs - which are of their nature hard to account for. As someone said, user needs are very important when designing systems, but particular the small and medium ones used by large numbers of non specialists. But even more important is for institutions to understand the demand, to know (and dream) of what IT might do for them, and to prioritise resource so that not all of it is spent keeping the old systems running, but enough goes into making sure the new systems are procured and work. It needs hard-headedness, the toughness to shut down high-maintenance low-value legacy systems, a willingness to consider off the shelf rather than bespoke, and capacity for a period of pain as you transition from one mode to another.
I recall starting at a Russell Group university as a Lecturer, a few years back, and within two months, I had 12 different logins to 12 different systems, none of which interconnected...

Sponsored