In the classical building architecture less is more describes the minimalistic design, which is a whole school of architects that fundamentally stated with two different motivations. Ludwig Mies van der Rohe started with the minimalistic design as something driven by aesthetic, very much as anti statement to the cluttered architecture in existence. the other school of minimalism was driven from form and function and was one of the first area of productivity ( if you interested in more please see John Brockmann’s “The why, where and how of minimalism” from 1990 on one of the early conferences about system thinking (or system documentation).
Minimalistic architecture is actually key when you are paid on a deliverable value that will generate business and/or save costs, as all other architecture is driven by other reasons. I am even so bold as to postulate that theories of agile development and of minimal valuable products is caused by non minimalistic architecture. Minimalistic architecture can still be aesthetic such as a Japanese tradition, but it concentrates the factual and the spiritual on key elements. In the same way minimalistic IT or enterprise architecture should unlock the full potential in designs geared to a maximum positive outcome.