I read something the other day that I think captures the "razor's edge" that must be navigated in terms of finding the balance between Power and Simplicity when building new technology solutions for non-technical users:
Option 1: Hide the Complexity. Downside - That means users have less control.
Option 2: Provide Maximum Configurability. Downside - That means more complexity, and less inherent usability.
Option 3: Productize Training and Support. Downside - Training takes time, dollars, repetition and organizational "religion."
These are not mutually exclusive constructs, but they do provide framing for thinking about Users, Usability and Utilization.