Lessons From 70 Triathlons About Why Enterprise Software Projects Fail

Most enterprise software projects fail—and the reason is surprisingly simple: the organization routes around any solution that doesn't fit its actual experience. That provocative insight comes from an unlikely source: a veteran of 70 triathlons writing for Forbes. The human body, the author argues, instinctively bypasses strategies that ignore its true condition. The same, he says, is true of enterprises. The message is clear: no matter how elegant the technology, if it doesn't match the organization's pain points, it will be ignored, worked around, or abandoned.

For decades, the Standish Group's CHAOS Report has pinned the failure rate of enterprise software projects at roughly 31%, with another 52% considered “challenged” (over budget, over deadline, or missing features). That is an extraordinary waste—trillions of dollars globally each year. Traditional explanations point to scope creep, unclear requirements, poor communication, and lack of executive sponsorship. The triathlon analogy adds a new layer: organizational resistance is not just a process failure—it is a biological-like response to a misfit solution.

The author draws from personal experience: over 70 triathlons, he learned that pushing against the body's signals leads to injury and failure. A triathlete who insists on a rigid pacing plan despite fatigue will crash. Similarly, a company that rolls out a new CRM system without aligning with how sales teams actually work will see the system bypassed in favor of spreadsheets and sticky notes. “The body, whether human or organizational, routes around solutions that do not match its actual experience of the problem,” he writes. This principle explains why enterprise software project failures so often stem from a gap between design and reality.

Key data points underscore the scale of the problem. The Standish Group found that 45% of features in a typical enterprise software product are never used. Another 19% are rarely used. That means almost two-thirds of development effort is wasted on functionality that employees actively avoid. Companies like Hewlett-Packard, Nike, and the UK's National Health Service have all suffered high-profile project failures costing hundreds of millions. Common threads: a disconnect between IT and business teams, and a failure to understand the messy, human workflows that software is supposed to support.

Why do enterprise software projects fail so often? The analysis points to a cultural gap. Developers and project managers often focus on technical specifications rather than the lived experience of end users. A solution that “should work” on paper can be entirely unsuitable in practice. The triathlon lesson is that success requires empathy: listen to the body—or the organization—before prescribing a remedy. Informed observers like Dr. Robert Austin, a professor at Ivey Business School, argue that the most successful digital transformations treat employees as co-creators, not obstacles. The metaphor of routing around a mismatch reinforces that the real problem is rarely the software itself, but the assumptions baked into its design.

Looking ahead, the growing adoption of low-code platforms and agile methodologies may help close the gap. By involving end users early and iterating quickly, organizations can test whether a solution fits before investing heavily. Another milestone to watch is the rise of outcome-based metrics that measure actual usage patterns rather than just deployment milestones. The triathlete’s advice for enterprise software project failures: stop pushing the plan and start listening. The organization will show you where it needs to adapt. Smart project leaders will follow those signals—or risk being routed around themselves.