Let that sink in for a moment...
How many times have you heard "well, it may be too complicated for a user", or "the users really could bind up the system if they don't know what they are doing"?
Let's consider these comments. Has no one learned that complicated software is crap? Has no one learned that complicated software has a slim chance of success? Complicated equals crap. Plain and simple truth.
Consider the below photo.
Although, this was built with a user in mind, it was most certainly built from the engineer's perspective, by a person who really understood the usability (um, yea...right). How many users could intuitively begin using this remote out of the box without help? A small percentage. Notice there is a help button on this remote! The design team knew they were delivering a crappy product!
Now consider the photo below.
This was built with users in mind. Most users are able to figure out how to use it right out of the box, with no help. That's a big difference from the first approach.
It takes a lot of patience to have a team work with a user community when developing a product. However, it makes no sense to ignore the very users you want to buy your product. Yet, we see it happen repeatedly, again, and again, and again.
Don't be like the Time Warner remote design team and proudly add a help button to your product. The only help your customer will be looking for is how to return your product and rant about it to their friends and the other 5 zillion people online.