| Nothing like broad sweeping generalizations to make a good story. I have a few points to make : 1. End users have an incredible ability to complain that software doesn't meet their very specific and peculiar requirements at any point in time. "Why can't I print this expense report landscape on a5 paper, we have run out of normal paper" - "Why doesn't this expense report sub-total by supplier and week, but only in leap years?" 2. If the people using the software were the business owners I think they would sing a different tune, or go out of business because they spend so much money optimizing for user experience. 3. Enterprise software tends to be infinitely more complex than most Saas projects. It is hard to budget and focus on the user experience when you are processing billions of dollars in transactions, with complex business rules, complex tax rules, complex laws, integrating with legacy systems, changing business conditions and strategy. Most businesses will put compliance and accuracy ahead of user experience. 4. Non-enterprise developers seem to think they are shit-hot and have a chip on their shoulders about enterprise developers for some reason. So you get an endless stream of articles along these lines. |
I also remembered a new hardware product going out to a satellite office in $other_country, where the favourite sport of the sales staff was coming up with excuses for not meeting targets. This next-gen bit of hardware had everything they'd asked for and used as an excuse for not meeting those targets, and it was a nice bit of kit that would sell well (I'd previously worked in the industry it was targeted at and wished I'd had it then). Supplied with the first production model, they were asked for comments. The sole comment that was returned was "well, at least it's not green".
That company also gave me an insight to your #3. We had SAP-like software but the company treated us like shit so we were looking to replace them. It turns out there are (were as of 2009) no cheap options - they all failed at nested bills-of-material. A product might be a full box with manual and other parts. That product holds the assembled product and a couple of other assemblies. That assembled product holds several boards and subassemblies. Those subassemblies then require other parts. Rinse, repeat over several products and you have a system where there's nothing useful on offer at the cheap end of the spectrum (without heavy/clunky modification). Most of the cheap stuff was entertaining a retail mindset - "item A comes from supplier B/why would you need to ever put A and B in a kit?". Even the vaunted Salesforce needed customising to handle the idea of kits - and that is only a single level of nested BOMs.