Is 90% of Software Bad? Why Planning Matters More Than Ever

80–90% of software may be poorly written, but is the real problem bad developers, or bad project planning? 00:00 - Is most software poorly written? 02:04 - The ideal project planning process 03:26 - How shortcuts create bad software 05:22 - Why implementation timelines get squeezed 08:38 - Requirements gathering is the real battleground 10:03 - The danger of “like-for-like” migrations 13:47 - AI can speed up builds, but not planning 15:08 - Why humans still need to be in the room In this video, I react to a discussion about legacy code, software shortcuts, and why so many systems end up bloated, fragile, or poorly matched to the business process they were supposed to support. Drawing from 15 years of professional services experience implementing call center software, I walk through how project timelines often get squeezed, why requirements gathering is usually the first thing to shrink, and how “like-for-like” migrations can create major problems in enterprise systems. I also look at how AI may speed up build and testing work, but why it should not replace the human project planning process. If anything, the planning phase may need to expand so teams can better understand business rules, user workflows, reporting needs, and real-world operational details before implementation begins. Support the channel and help keep the live lab running: 👉 https://ko-fi.com/sethoncall Sign-up for the SethOnCall newsletter "The Call Log" 📬 https://sethoncall.com/ #enterprisesoftware #professionalservices #callcentersoftware