I think one of the most common scenarios I’ve seen in the industry is the upper management team(s) putting pressure on devs to deliver faster and the developers saying they’re going too fast and are piling up tech debt but no one listens and then time is later wasted fixing a bunch of bugs. I don’t have the perfect solution but I know the problem well.
I think tech/team leads/PO need to be added to the list also. I've worked with tech leads that trusted me/team and ones that didn't trust me/team.<p>The one who trusted us always asked "why did you do it this way" and he'd would open it up as a discussion.<p>While the one who didn't, would basically say "no that's wrong. It needs to be done this way".... 2 weeks later after we would make all the changes that he wanted. He'd say "no this is also wrong, why aren't we doing this [insert implementation that we did initially]".
Between (a) building the thing right and (b) building the right thing, I've personally seen a) go wrong sometimes and b) go wrong most of the time.<p>My personal feelings are that developers have far less influence on b).