this is a disgusting amount of money for this
Workday project at Washington University hits $266M
31–40 of 106 posts
Re: Workday project at Washington University hits $266M
#32I guess I have three questions here. 1) What happened to the days when universities published their own software, like pine from UW? It seems like Washington of St Louis, which offers a PhD in computer science, should have some students capable of writing a database to run the university. 2) Why have universities not collaborated to develop a modular, expandable system for running a university, instead of putting the…
> At what point did the university so lose its organizational competence that the filing system (that's what a database is) ate the budget?
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).
Re: Workday project at Washington University hits $266M
#33Was wondering how Workday a managed to sponsor so much stuff
Re: Workday project at Washington University hits $266M
#34workday is VERY expensive, probably one of the most, my company (150 employees) can't afford it, we ended up using something else, cheaper, and quite frankly, it does the same stuff.
You might want to share with the class?
Re: Workday project at Washington University hits $266M
#35How organizations would pay for Workday baffles me. It is the worst company software I've ever used. It would regularly lose data that managers would input so the best practice amongst EMs was to never put data directly into Workday but instead keep copies elsewhere and only input it into Workday at the last moment. Then if Workday decided to drop your performance feedback you could just paste it again. It must be re…
My guess is that it's the IBM or React of HR. Everyone knows it, everyone knows how to use it.
Re: Workday project at Washington University hits $266M
#36I've always thought it would be interesting to be the guy called in to clean up these messes. That's where I'd love my career to go... being called in to turn around a sinking ship.
Technology projects have a habit of going wildly off the rails, especially if you're not at ${bigTechCo} with a really mature software factory pumping out large projects consistently, so it seems like there'd be no shortage of mess to clean up around the industry.
The idea of building something greenfield isn't as interesting as fixing a badly broken machine to me. Call it a fixer complex :)
Re: Workday project at Washington University hits $266M
#37Workday, Palantir, ServiceNow - a new generation of Accenture/Oracle et al 'consulting' parasites that wine and dine their way into organisations (and governments) and then bleed them dry. There's a reason software spending endlessly goes up but productivity has flatlined.
ServiceNow is so terrible I genuinely wonder how it is ever deployed anywhere. Seriously, do the purchasers never look at it? Is there no product demo at all during the purchase process? Do the sales people actively hide it or something?
> ServiceNow is so terrible I genuinely wonder how it is ever deployed anywhere. Seriously, do the purchasers never look at it?
When I first saw ServiceNow, I was impressed - because my point of comparison (I worked for a university at the time) was BMC Remedy, which was terrible. And some years later I did some consulting for a major bank which was using some 3270-based IBM solution (Tivoli something… I believe it has finally been discontinued) and ServiceNow is light years ahead of that too.
Re: Workday project at Washington University hits $266M
#38Spending roughly $38M per year (as per the Register article) for HRM, EPM, IBP, and CRM in an organization with roughly 22,000 employees [0] and 16,000 students [1] is a fair amount. HNers really underestimate the complexity of software projects in organizations as divided as a large private research university that is also a major healthcare network [2]. [0] - https://governmentrelations.wustl.edu/economic-impact-st…
I worked for a CRM reseller for a bit when I was younger.
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.
Re: Workday project at Washington University hits $266M
#39Spending roughly $38M per year (as per the Register article) for HRM, EPM, IBP, and CRM in an organization with roughly 22,000 employees [0] and 16,000 students [1] is a fair amount. HNers really underestimate the complexity of software projects in organizations as divided as a large private research university that is also a major healthcare network [2]. [0] - https://governmentrelations.wustl.edu/economic-impact-st…
I worked for a CRM reseller for a bit when I was younger. 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…
> Also just HIPAA being in the mix adds non trivial complexities
Yep, and WUSTL - like most Universities - is a major medical network in it's region. Ime, the bulk of the costs that arose from Higher Ed contracts I dealt with were due to the fact that most Higher Ed institutions were also medical networks.
But the issue is, medical PHI is important, and outages can lead to liability and potentially patient risk.
> 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
Pretty much, because the TCO for a Cobol system limping along would eventually become unsustainable - especially if you had dozens of BUs with their own internal data practices.
Re: Workday project at Washington University hits $266M
#40With that amount of money I’d suspect corruption unless explicitly proved otherwise.