Stop Listening and Start Watching If You Want To Understand User Needs 161
rsmiller510 writes "It would seem on its face that simply asking your users what they need in an app would be the easiest way to build one, but it turns out it's not quite that simple. People often don't know what they want or need or they can't articulate it in a way that's useful to you. They may say I want Google or Dropbox for the enterprise, but they don't get that developers can be so much more creative than that. And the best way to understand those users' needs is to watch what they do, then use your own skills to build apps to make their working lives better or easier."
But.. (Score:2, Funny)
Apple tells me what I need, thats the perfect scenario right?
Re:No shit? (Score:1, Funny)
I agree... Even if it's just purchasing a solution, you really don't know what the user's needs are until you take some time to figure out what they really do. {I mean beyond the broad over view you get when you ask them}
If I followed your advice I would be designing programs that alternates between showing fox news and browsing for porn with a spreadsheet simulator on a hot-key for when the boss shows up.
Re:No shit? (Score:4, Funny)
And your sales would be a lot better too.