I have never personally experienced a project failing because of technical debt. I have experienced "the opposite" of that where there was such a focus on doing

I have never personally experienced a project failing because of technical debt. I have experienced "the opposite" of that where there was such a focus on doing things "the right way" it felt to me like development was slowed down by this. Our product iterations were slow and from my perspective it cost us valuable chances to test different product ideas. I'm using this definition of technical debt. Technical debt is a concept in programming that reflects the extra development work that arises when code that is easy to implement in the short run is used instead of applying the best overall solution.[1] [1] https://en.wikipedia.org/wiki/Technical_debt https://en.wikipedia.org/wiki/Technical_debt ##edit The project I am referring to was a consumer web project. No mission critical type data. In my experience (mostly consumer web, social media management for B2B) I have seen causes of failure to be heavily weighted towards product issues not engineering. The one big success I was a part of had the most technical debt. :) But that's probably because it lived the longest (and still lives today!). My experience is limited to being an employee at 4 different tech companies and several failed attempts of my own.