Just been thinking about the why of this. I think comes down to the details. It's those little details, the real weeds, where the complexity lies that makes s

Just been thinking about the why of this. I think comes down to the details. It's those little details, the real weeds, where the complexity lies that makes system implementations difficult. And, generally, management doesn't want to know, and often don't have the technical knowledge to understand those very details, no matter how well or deeply they're explained. The other side of that coin is the fact that on the technical knowledge side, if they know the details they have to consider, there's a kind of hubris that blinds them to the actual effort required to cater to those details. Not maliciously, but just by the fact it's considered a known rather than unknown it just may not get the pre-project attention necessary to determine time and effort required, and so it gets under-estimated. I think what I'm trying to say is that the tension between good, fast, and cheap is the fundamental reason, in my experience. Management tends to want all three, and so that's what's catered to to get the thing kicked off. Yes, it's irrational. Almost by necessity.