I spent 25 years in a big company tolerating crappy software. Jason is absolutely 100% dead-on correct. The people who buy enterprise software aren’t the peop

I spent 25 years in a big company tolerating crappy software. Jason is absolutely 100% dead-on correct. The people who buy enterprise software aren’t the people who use enterprise software. ... [T]he software vendors are building for the buyers, not the users. The experience takes a back seat to the feature list, future promises, and buzz words. Enterprise software is bought on marketing bullet points, as long as the budget can bear it (cost and quality for enterprise software are totally uncorrelated). The buyers have no ability to judge the implementation of those bullet points, so a crappy implementation sells just as well as a good implementation. The other observation I would offer is that the level of effort required to initiate and carry through the purchase of a new software package is so high in a large company that nobody can afford to make a mistake (time/effort-wise, mentally, and career-wise). Thus, only "safe" choices are made. Ironically, what appears to be the safe choice very often is a mistake - crappy buggy implementations of huge bullet lists of mis-features. Sorry for venting. :-D I'm much happier in my new small company where we are willing to make several small, recoverable mistakes (base hits, bunts, sacrifice flies which advance the runner) to score a run rather than swinging for the fence and being out on a fly ball every time.