Speed matters when the thing being built is isolated.
If you're building a new feature/product whatever, and the business views that both as a standalone feature, but also as a stepping stone to support another product or feature then the code you get when writing quickly is going to slow you down in that next step.
Scale that up a few levels and you end up with 'enterprise code' that no one wants to touch for fear of breaking all the parts that depend on the pieces below it.
So write code quickly when its isolated and not planned for use in additional products, features, capabilities.
It is very difficult to convince management to prioritize tech debt and the only successful way is in the frame of enabling additional product capabilities.
If you're building a stepping stone, you still have to figure out how to make it isolated in a way then do it quickly. Like if it's a software service, spend the extra time figuring out a good API then speed through the initial implementation.
If you're building a new feature/product whatever, and the business views that both as a standalone feature, but also as a stepping stone to support another product or feature then the code you get when writing quickly is going to slow you down in that next step.
Scale that up a few levels and you end up with 'enterprise code' that no one wants to touch for fear of breaking all the parts that depend on the pieces below it.
So write code quickly when its isolated and not planned for use in additional products, features, capabilities.
It is very difficult to convince management to prioritize tech debt and the only successful way is in the frame of enabling additional product capabilities.