A common theme is limited or no budget for updating or expanding systems such that the go from "nice" to "acceptable" to "clunky" and then worse.

Politics also becomes an issue. That aged home rolled service might have a palpable price tag to fund a major update for, but once you do discovery and scope every specialized integration made for every department and reality sets in. Whatever path is chosen is going to burn a number of parties, and using a vendor provides a baseline for functionality and a convenient scapegoat

2 - see federated auth via shibboleth, or any number of incommon tech. Or even Kerberos

This stuff exists and often works well, but brings it's own operational maintenance challenges and required specialized skill sets.

3 - only a subset of these processes were handled on paper. expectations on both the timelines and breadth of services have gone up significantly since this was all on paper

Federal taxpayers underwrite unlimited amounts of money to the university’s customers. Why would the university’s leaders not take advantage of this and enlarge their kingdoms as much as possible? The bigger the budget, the bigger the university employees’ cut (incl the board).

2) See (1) and also because AI can't do it, so they can't handle.

3) Because paper kills trees, and brawndo contains electrolytes, duh.

I don't remember all the details, but this is what they used up til the mid-90s. By then, I could probably run something on my 486 home computer that would complete in half an hour. But there were decades of process and customization embedded in these systems.

When modernization happened, it was swift. My dad was lucky with the timing as he was retiring during the transition so even made bonus money coming back as a consultant. But you can imagine that even if the new software was pricey and not as customizable, the speed improvements and reduction in staff made sense.

Once the old staff was cleared out, there was no department of staff being paid to build computer services, only the lesser staff needed to maintain and use it. The issue was that hardware/Internet usage expanded too fast, the importance and reliance on tech grew and it became a selling point for unis to have the newest systems in place.

It makes sense now for the pendulum to swing in the other direction, as customization and cost are wildly out of balance with AI and the latent tech workforce available at every college.

I would say the blocker now is the same as what allowed creaky old systems to persist into the 90s - administration doesn't give a shit about any of this and it is only viewed as a cost center. Until differentiating through customization provides an obvious and immediate fiscal benefit to the admins themselves, most unis won't look at changing off their shitty landlord systems until they are basically forced to by the market.

1. They exist. However, writing a piece of software is not the same thing as supporting them, especially when it comes to dealing with core HR system. This is where SaaSs and similar platform offers lot of appeal.

2. Also difficult because everyone has different needs and at some point certain features get prioritized over others. I support a platform that was built in house before I was born. The guy who wrote it is no longer with us and it is cludgy. Any product decisions evolve years of committee meetings before any decision gets made (by which the it may be incorrect or not relevant.)

Every single time I worked for a company that said let’s hiring an engineering team to build a software that is already solved by a market offering, it has never gone well. The in house product never had the same capabilities or had the same sheen.

3. Can’t answer this one other than digitization efforts.

For transparency, a single software engineer budget is $670K+.

I mean students on their own go rogue and make tools for their peers to make it less painful to much fist shaking by the administration.

the kickbacks are too good.

Also, I wouldn’t put Palantir in the same bucket as Workday and ServiceNow. It’s expensive, but it does work.

Data Integration.

Workday is extremely good at integrating various different data sources and providing support to build integrations if they are not offered by them.

A private research university like WUSTL is a conglomeration of around 10 colleges all of which all have their own internal operations, a couple organizations dedicated to facilities maintenance, an entire community medical network dedicated to STL metro, a major sports program, housing for students and faculty, procurement, insurance, etc.

All of these are entire business units or functionally independent organizations. And in this complexity arises multiple different organically developed data stores, schemas, and practices. At that kind of scale, liability grows exponentially and you as an organization need a way to better understand what is happening.

That is why products like Workday are beloved by enterprises.

That doesn't quite make sense for a college. Students aren't employees, why are we trying to fit them into the same mold as an employee in this nonsense it feels like?

At the time the industry wisdom was that basically 80% of CRM projects fail to return value. And the customers knew that plainly, but the alternative was trying to keep some COBOL era system limping along. So even though they knew they were likely going to burn a huge pile of money, it felt like a necessity.

So a sort of stockholm syndrome mentality takes root where they just hope they can limit the bleeding as much as possible.

Also just HIPAA being in the mix adds non trivial complexities.

People drink the KoolAid and here we are. This is just the middle management disease that takes over everything unless people are very careful.

I mean, I’m not saying that $266m isn’t ridiculous and that Workday isn’t very expensive, but to pretend that UW can just use whatever your small company ended up with as a major ERP isn’t realistic. They need to track 35k staff (UW includes a full health system) and 50k students. There’s three total software packages you can take seriously on the market for this, and they all suck in their own way and are all ridiculously expensive and hard to implement.

Edit: wrong university. UWash is much smaller on both staff and students.

For a situation as bad as the one described here, though, the scope for an individual engineer - no matter how experienced - to turn things around is going to be limited. The core problem is almost certainly organisational and cultural rather than technical, so it needs to be addressed at the strategic management level.