Yeah, this is why I kind of like project ownership even though it's now considered out of fashion. If you create technical debt, you own it and it's your future productivity that takes the hit. Eventually your productivity grinds to a halt as you fix problems in the crap you wrote before.

I look at it as technically informed product ownership - merging business and technical domain knowledge to make the right tradeoffs. How else can you execute effectively?