Totally agree on the tough balance. At best it's a trade off of different forms of technical, process, and business debt. Doing deep enough architectural thi

Totally agree on the tough balance. At best it's a trade off of different forms of technical, process, and business debt. Doing deep enough architectural thinking and planning at the start to focus on maintaining flexibility (which can be achieved in many ways) without premature optimization or engineering can go a long way. Basically, don't work yourself into a corner or concrete too quickly by trying to do too much, or too little is an approach I try to keep in mind. Technical and architectural debt comes with interest as well. One way to reduce the architectural risk is to make the first version a throwaway. It can burn through assumptions. Similar to design thinking, going broad and converging twice can help get a better sense of vector,