4 ms·
Jason didn't dig deep enough on this one. Why is the buyer not the user? Because enterprise operations are too big and complex for any one person to do the jo
by dasil003 16y ago
Jason didn't dig deep enough on this one. Why is the buyer not the user? Because enterprise operations are too big and complex for any one person to do the job.
Likewise, there is no one person that understands how the processes work or even why they all exist. This makes the job of enterprise software development incredibly difficult, it also means that individual stakes are smaller, and the law of averages makes it much more difficult for anyone to rescue the project and pull it above the fray.
Now consider the demand for qualified software developers, the glut of incompetent developers, the difficulty of identifying which is which for the non-technical hiring manager, the variety of world-changing and otherwise sexy jobs available out there for quality engineers, and it's no wonder enterprise software isn't as good as small boutique software like Basecamp.
I'm happy for Fried and company that they were able to dodge the enterprise software world even more deftly than they maneuvered themselves free of a different scourge of the creative persuasion--client work--but this article is a bit too self-congratulatory without offering any real insight or potential solutions to the very real problems that large companies face.
- kenjackson 16y agoThis is exactly right. I actually was a user of enterprise software at the university and put together a list of my complaints about the software. Probably a list of ten items. To my utter surprise there were good reasons for why 9 of my items worked the way they did. And some of them were things like it actually being a law that you had to explicity retype a student's identification code. The problem with enterprise software, is less often the software, and more often the enterprise. I've seen expense reports that have had to go through 6 organizations, each with slightly different ways of handling various parts (some handle things for tax purposes, others of SarbOx, others for fraud detection, etc...). It's not as easy as an iPad sketch program.
- GFischer 16y agoI currently develop and maintain "enterprise software" for a large insurance corp. And laws are the enemy, I tell you :P (and the local equivalent of the IRS, and other regulatory organizations, and... you get the idea). Not to mention the UX isn't a high priority requiremente (I've been asking for UX help since I joined the company, I do what I can but it's not the same) For example: European regulations on data retention and local law means we have to ask for some billing information each time, an anti-terrorist law means we have to ask some really stupid information on every single form, IRS-equivalent regulation means we have to follow some archaic accounting practices, legal requirements mean that many documents which could have been happily emailed or otherwise electronically handled have to be faxed, etc, etc, etc ad infinitum
- pkaler 16y agoJason didn't dig deep enough on this one. Jason Fried didn't author this article. It's credited to Zubair Hamed.
- cromulent 16y agoYes. If you are looking to buy an ERP system to cover your South Korean, New Zealand, and Norwegian sales operations (as well as North America and your small but growing and complex Vietnamese operation) including support for all local tax laws, currencies, and languages (including double-byte right-to-left screen layouts), then how would you choose which of the users should make the buying decision? A vote? Should the sales users override the financial users, or should purchasing have the final say? Maybe it sucks because the buyer is not the user, but maybe it also sucks because it tries to solve awkward problems. Everything is relative. It doesn't try to be simple, but there is a market for complex software, like it or not.