If you know you're cutting corners, the ability to change in the future should be the priority. It usually means that you need to consider how the "perfect" solution would look like, so you know where the possible refinements will come to play.
There is a bigger story about the project for "YayHappyFunTimesCorp" which included that difficult conversation - how to, instead of carrying on with designing new features quickly, slow down and make sure that everything that we hacked together is scalable. It's definitely not an easy one.
If you know you're cutting corners, the ability to change in the future should be the priority. It usually means that you need to consider how the "perfect" solution would look like, so you know where the possible refinements will come to play.