> Remember, the number one cause of software product failure is having barriers to entry that are too low. Is there any consensus for this? Or are you being sa

> Remember, the number one cause of software product failure is having barriers to entry that are too low. Is there any consensus for this? Or are you being sarcastic? I don't know anything about these things so I googled it: https://www.google.com/search?client=firefox-b-1-d&q=the+number+one+cause+of+software+product+failure+is https://www.google.com/search?client=firefox-b-1-d&q=the+num... The top box says >> The No. 1 Cause of IT Failure: Complexity. ... According to software architect Roger Sessions, the primary cause of software project failures is complexity. Complexity can create delays, cost overruns and systems that don't meet business needs, according to Sessions, who is chief technology officer at ObjectWatch Inc.Dec 21, 2009 Another question below mentions these points: Software Management Common Software Failure Causes Lack of user participation. Changing requirements. Unrealistic or unarticulated project goals. Inaccurate estimates of needed resources. Badly defined system requirements. Poor reporting of the project's status. Lack of resources. Unmanaged risks. It doesn't make sense to me why barrier to entry being too low would be a problem. Am I missing something? The one thing that comes to mind is javascript but it isn't really a failure if the metric is user adoption.