Whether we want it or not, we, as software (solution) architects have to specialize in a bounded business domain and a bounded array of technologies. The required depth of knowledge depends on the type of architecture work you do.
While finding the "golden balance" is an obvious observation, a helpful reminder for you is to review your "golden balance" once every quarter and don't be afraid to re-define what you mean by your balance. It's natural for people to change - some become more specialized and technical, others pull up and specialize in a macro view. If you move a lot between low level and high level architecture you'll experience "turbulence" - and that may be OK if that's how you define your balance.