8 ms·
Mistakes were made: ERP screwups
- wayoutthere 7y agoI don't think I've ever heard of an ERP implementation that wasn't an absolute clusterfuck. My impression is that while most folks from the integrators know their segment of the product pretty well, they don't have deep technical skills in a general sense or know much about other modules of the product. Also that the salespeople know almost nothing about the product and promise that it can do things it cannot. The customer eventually figures this out and ends up ripping out and re-implement tools from other vendors. It's a common joke for senior technology leaders at industrial companies to ask eachother "so what was the first ERP implementation you got fired for?"
- arethuza 7y agoHaving been through a few ERP projects (on the buying side) I'd say the scale runs from 'painful' to 'disastrous'. One large ERP project I worked on barely made it past the kick off meeting.... a number of us escalated that we were not happy with the implementation partner so our boss (bravely) recommended that the entire project get canned - which it did.
- jimnotgym 7y agoI have been on one that was pretty flawless. SAP at the time, with full costing/ manufacturing, multi-currency, multi- country. I should write a blog about that, shouldn't I? I only recall two minor faults.
- jmcalvay 7y agoYes, please
- nocubicles 7y agoI been on the system implementor side of the ERP for long time and done many ERP projects(SAP). I have also never seen ERP implementation that has gone smoothly and everybody involed has been 100% happy. I think implementing ERP is 98% change management project and 2% IT project or something like that. I recently also wrote my thoughts on what ERP is. Maybe its interesting to someone. https://www.integrated.ee/posts/the-erp-software/ https://www.integrated.ee/posts/the-erp-software/
- wayoutthere 7y agoOn the tech strategy side, we're moving everyone we can off of traditional ERPs and into cloud-based systems. Salesforce is largely taking their place as the CRM, with purpose-built solutions (often leveraging cloud-based ML models) for downstream functions. All the consulting companies have process maps, which are honestly where most of the value of traditional ERP comes in. TCO factoring in implementation costs is a fraction of a traditional ERP and is far easier to keep up to date. Most ERP implementations still have a lag of a month or so before data is consistent.
- jimnotgym 7y agoYou make some very broad statements here... Cloud ERPs stay up to day whether you are ready for the change or not, it is not all rosy when they break important things at critical times of year. Traditional ERPs often don't get upgraded because there is no need. It is simply not worth the testing for the new 'features'. Lots of managers value the stability. TCO is certainly not necessarily less, it is common for a company to move onto an ERP and stick with it for a decade or so. One off licensing can be much cheaper over this period than some cloud systems. I saw a system where TCO of was cheaper with the trad system after only 4 years. Cloud based ML models are a bit buzz-wordy for my tastes
- crispyambulance 7y agoI find it impossible to believe that an ERP implementation can ever "go smoothly". At best, even if the system does what it does perfectly, it's still a classic "diffusion of innovation" (1) problem where you have multiple stakeholders with wildly varying levels of acceptance. This is always challenging. As those of you who make a living at this stuff recommend, it's better to go 100% with the ERP's way and not customize. Well, that can be extremely difficult or impossible in an environment filled with stubborn beancounter/battle-axe personalities. Most importantly, however, the people who make the purchasing and sign-off decisions ARE NOT the ones who use the thing. There are going to be problems and those problems will not usually bubble back up to the consultant/vendor. People will just have their noses pushed to the grindstone until the job gets done-- never mind the tedium, never mind the countless little mistakes. New people don't get trained, they just get put in front of the the thing to hunt and peck through it, sometimes with the assistance of a surly veteran of the system, sometimes with no one to help them. There are thousands upon thousands of people sitting in cubicles right now using Oracle EBS with it's horrible grey java applet UI and ridiculous inscrutable query functionality. They've been sitting there suffering it since the 90's. Who listens to their screams? Not Oracle, not exec that bought the thing! Or maybe they're silent and they've resigned themselves to their fate? (1) https://en.wikipedia.org/wiki/Diffusion_of_innovations https://en.wikipedia.org/wiki/Diffusion_of_innovations
- wayoutthere 7y agoTotally agree! My clients are all ripping that crap out because nobody uses them correctly anyway. Most of the data in those systems is so error-ridden they're almost dangerous to use. Newer cloud-based systems offer a much more intuitive UI, which ultimately reduces bad data. Oracle and SAP are basically bad words at this point: you don't say them if you want to get hired.
- jimnotgym 7y agoThis is not necessarily true. I find accounts people who have grown up with these systems find Netsuite (a cloud system) slow, cumbersome and unintuitive. Fast repetitive data entry always seems faster in desktop clients. We are talking about professional full- time users, the initial easier learning curve soon loses its advantage once you have learnt the keystrokes. As for data integrity, I worked in very large SAP implementations without data integrity issues despite thousands of users. I have worked with cloud systems that are full of rubbish.
- mark-r 7y ago> "so what was the first ERP implementation you got fired for?" At my last job we underwent a transition from one ERP to another. Halfway through it my boss resigned and we got somebody new, mostly on the basis of his experience doing the same at another company. I heard a rumor later that this other company had nearly gone bankrupt because of the roughness of their transition. Things weren't looking good for ours either when I left.
- wayoutthere 7y agoThis is pretty much par for the course; corporate IT at the highest levels is a game of musical chairs where everyone fails up.
- cpeterso 7y agoThe article's actual title is "sMistakes [sic] Were Made". I can't tell if it is trying to be ironic or if a mistake was made. The article's URL has no extra s: "mistakes-were-made".
- danpalmer 7y agoI’m a software engineer and likely to be involved in implementing an ERP at the company I work for. Ignoring whether or not we should (we’ll put a lot of thought into this), does anyone have any tips on what to do or avoid to make a project like this a success?
- superbrane 7y ago- Make sure business stakeholders have realistic expectations about deployment, data migration, cost of working in parallel if another system exists, etc - stay away from customizations when possible. Each ERP comes with its own way of doing things. It's sometimes best to adjust the business to the ERP than the other way around :)
- gav 7y agoTo echo this point: in my experience, a lot of businesses seem to believe that their internal processes are unique for a reason and offer some competitive advantage instead of being that way because somebody made a decision years ago and that decision stuck. The more you customize your ERP, the worse off you are. The fastest, cheapest code is the code that's not written in the first place. The maintenance cost and difficulty upgrading down the road are many multiples of the sunk cost.
- arethuza 7y agoI'd recommend not getting involved in the 'technology' used to customize ERP products - this tend to be 'eccentric' at best. Personally I'd try and stay on the right side of a sensible API or database structure if you can find one.
- jimnotgym 7y agoNetsuite has a pretty handy javascript based internal system that is alright. But do insist on am API!
- jimnotgym 7y agoI have spent a lot of my career fixing botched implementations. And I have seen it go perfectly... Write your requirements for the system in plain English bullet points. Give this to vendors. Write a plan of what you would like to see on the demo. Btw you want to see the boring stuff, not the colourful charts. Book a whole day. Take a person from purchasing, accounts, sales. Get them to create a sku and a supplier, get them to buy it. Get them to receipt it, get them to show the accountant how that affected the ledgers. Move it sell it, collect the cash etc. Now you know something about whether it will fit and whether you rate the vendor. Could the company afford it costing twice what you planned? If not then maybe ERP is not for you. You need a test system. Allocate a lead person for every department. Let's call them the power user. At key check points the vendor should want you to do testing. Write a test plan for end to end transactions like my demo example. Get your power users to do the test, this gives you buy-in, sign off and critically, job specific user training. Allocate a huge sum of money for user training. Trainers are expensive. Job specific training is the only thing of value. There are often several ways to do something, only train in the one you have chosen. The trainers need to be on-site for all of go-live week. Budget for this. Don't train too early Go standard, don't customise, work the way the ERP wants On a phone but this feels like it would make a blog post!
- jon-wood 7y agoI'm not usually one to complain about the quality of an article, but this one seemed to be almost completely devoid of actual content. I was hoping for some actual analysis of why the projects mentioned failed, and instead didn't really get anything more than a brief explanation of what ERP and SAP are, and the fact they sometimes don't work out.
- chihuahua 7y agoTo be fair, the site that published the story is called "Tedium", their tagline is "the dull side of the internet", and at the end of the story it says "Your time was just wasted by Andrew Egan". So they are completely upfront about it, and they deliver what they promise.
- freshhawk 7y agoI looked around a bit thinking there must be an actual article starting on page 2 or something. This is like, 3 factoids from wikipedia stretched out with filler sentences.
- jrochkind1 7y agoI gave up 1/3rd of the way through and figured I'd check the HN comments and anyone would mention any highlights if they mattered. Feel proud that my BS detector is apparently functioning well!
- pessimizer 7y agoI found this article super-difficult to read (due to the weird layout), but as far as I can tell they didn't mention Levi Strauss & Co and Waste Management, which is weirder than the layout. https://www.zdnet.com/article/levi-strauss-sap-rollout-substantially-hurt-quarter/ https://www.zdnet.com/article/levi-strauss-sap-rollout-subst... https://www.computerworld.com/article/2536212/waste-management-sues-sap-over-erp-implementation.html https://www.computerworld.com/article/2536212/waste-manageme... Both $100MM+ boondoggles.
- IceDane 7y agoI recently got a job in the ERP industry(SAP), though my purpose is essentially to do stuff that is not SAP related. I don't think it should surprise anyone that SAP makes mistakes and/or that ERP systems are hard to implement. SAP in particular is an absolute monstrosity. I don't just mean in terms of size either. I can't help but think about that Nietzsche quote about the abyss. SAPs systems should become textbook examples of tech debt left to accumulate, of what happens when systems are allowed to grow in whatever direction is useful at the time without any thought for the future or proper design. This isn't very surprising either since I can't imagine that there is any group of human beings on Earth that is capable of understanding SAPs systems to the point where they could extend it safely. SAP also takes the NIH syndrome and makes it a core value. Everything they make is worse than that other technology that accomplishes the same. See UI5 - it's like they traveled back in time and hired a CS freshman in the late 90s to develop it. When they don't have the expertise to create a copy from scratch, they just use the competitors' solutions and wrap that in their own marketing. They want you to only use SAP stuff. The figures mentioned in the article about how important SAP is to the world's economy and logistics should scare the living shit out of anyone.
- jimnotgym 7y agoOn the other hand SAP is still by far my favourite ERP as a finance user. Interfaces that look like the green-screen dumb-terminals of the past are fantastically productive for data entry. Tab tab F9 I loved the rigour of the thing, I trusted it.
- jimnotgym 7y agoFurther than that, SAP Business One is pretty good to use too
- privateSFacct 7y agoHaha - so true. The first versions of some of the financial packages built on salesforce and elsewhere - so SLOW. Click, wait, dropdown -> wait for it to populate with the 1,500 items when devs probably only tested with 5 etc etc, then click, wait, click, wait. All much better now of course, but the early years were terrible.
- cdcarter 7y agoAs good of a time as any to remind people of Moonpig: https://blog.plover.com/prog/Moonpig.html https://blog.plover.com/prog/Moonpig.html.
- BMFXX 7y agoAs someone in the middle of an ERP integration to SAP. Its painful to say the least.
- shaneprrlt 7y agoI've done work integrating Shopify with ERP systems and let me tell you, I still get horrible anxiety whenever I hear the term.
- jotakami 7y agoI don’t think there’s anything special or unique about ERP screws ups: (1) ERP projects are typically large by their very nature (2) SAP projects are always built in waterfall fashion Seems like Fred Brooks’ original diagnosis would suffice here.
- nkoren 7y agoA botched SAP implementation played a significant role in the $2.1B implosion of Target Canada.[1] Can't belive it isn't mentioned here. 1: https://www.canadianbusiness.com/the-last-days-of-target-canada/ https://www.canadianbusiness.com/the-last-days-of-target-can...
- manicdee 7y agoNote to self: in this article, “ERP” means “Enterprise a Resource Planning” but uses it as a synonym for “SAP”. There was no Erotic Role Play involved. One thing that rings true in both worlds is that any system should be exactly as large and complicated as it absolutely needs to be, but no more.
- kens 7y ago> Xerox’s infamous decision to abandon the hardware computing industry in 1971 A minor correction: Xerox shut down its XDS computer division and sold it off to Honeywell in 1975, not 1971.
- deleted 7y ago[deleted]