Nice article. Now for the power users...
Speaking as a power user, in my workplace it's been an uphill battle ( but improving over the years ) to have user input inform design issues. This is more an awareness issue than actual desire to make things difficult.
I would suggest that a similar article about what power users want and need would be useful. I don't think they want / need the same things as the average user.
I can tell you, one thing power users want are simple ways to automate and schedule processes. They don't want to click, click, click ( dance, whatever ) their time away repetively to accomplish their end results. Living at the MS boundary where Access is too small, SSIS is restricted to the priesthood, and distributed queries is turned off is untenable. Ouch.
Once an Oracle person visited with a user automation tool that looked like the promised land. I guess it lives somewhere else, unfortunately. I guess it was too expensive to retool our shop.
I had simpler and easier to learn batch automation processes available to me in the 1970's than I have today.
Personally, I think MS wants sustain the IS priesthood ( I guess that would translate as "Developer Community" ) for profit reasons. This involves ensuring that users cannot automate too much. Part of the engineering mentality is to keep it complicated, or rather, not see why it's important to make it simpler.
Just want to give a suggestion for further discussion and exploration.
