It's not really bugs vs design issues. It's more changeable vs unchangeable. Part of that is technical cost, but in my experience most is perceived risk, whic

It's not really bugs vs design issues. It's more changeable vs unchangeable. Part of that is technical cost, but in my experience most is perceived risk, which is largely a function of understanding and team (leader) confidence. The scariest things are existential: telling people the system they believe in has fatal flaws introduces a gap that can only be filled with a lot of confidence, which is typically lacking when growing fast or with new systems. The main remedy is to be sure you have an actual view and understanding of the system, and address things from that perspective. Otherwise, bugs are just make-work.