Scaling is much more than software
Architecture is about balance
From Scaling is much more than software comes this great little snippet about one of the ways to solve problems with your architecture.
What was the solution? Re-evaluating the business logic and requirements with the customer.
Whenever I'm talking to aspiring software architects about the role, I always find myself emphasising and re-emphasising that an architect must take both the functional and the non-functional requirements into account when designing a system. This reminds me of the previous question about business analysis - it's certainly part of the role and, as an architect, you shouldn't be afraid to question the customer's expectations, particularly if you feel that they are going to adversely affect other aspects of the development. Architecture, and it's success, is about balance.
