There’s a balance to strike in architecture, no matter what methodology you use to create your software. In Agile contexts, that balance is often lost. And it usually leans to less over more. I think the most important acknowledgement or statement that we should all agree to early on in any architectural discussion is that we don’t know. Out of this level of openness and honesty comes the need for prototyping, discovery, and learning. It’s hard to do that if we don’t look each other in the eyes and say, “We don’t know, let’s find out.”