You are making assumptions about both the premise and the conclusion :) Designing and building for scalability, flexibility, availability, etc does not mean go

You are making assumptions about both the premise and the conclusion :) Designing and building for scalability, flexibility, availability, etc does not mean going all out to boil the ocean and then find that you attempted to boil the wrong ocean. If that did happen, you got the wrong team :)