The stuff behind the scenes, such as the database, is simple and flexible, so I don't have to consider that. So this is all about what the users need, and that means what he needs in the GUI (it's a web application).

I know this is a very wide question. I could ask it much more specifically, but I think there has to be people out there, used to attack such problems, that have very general guidelines.

It could be great, if you have some resources for learning more, whatever your answer is.

closed as too broad by JohnGB Oct 25 '15 at 22:56

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Short answer: Please have a read of Indi Young's book Mental Models rosenfeldmedia.com/books/mental-models – nightning Sep 25 '15 at 16:49
  • It feels to me that if you are still trying to figure out what he needs in the UI (and if this is at the level I think you mean) then this means you might need to consider working with user stories. After you've scoped the problem with your user stories you can then start thinking of how you can fulfill those stories with your UI. After that you can start prototyping and doing some usability testing with your client. – Dont trust me Oct 25 '15 at 18:08

The job of a UX/UI expert is to figure out what the user needs in the UI. You can ask direct questions such as "What feature would you like to see on the home screen" and they'll look at you with a blank stare. Some of them will try and be helpful and give you answers, but you'll get half-truths. Most won't know what they need. They just know they need something simple and intuitive.

The best thing to do is dig down to the core and discover their true issues. What is failing with their current solution. Why is it inadequate. You'll get a bunch of useful info on what doesn't work. Your job is to take the info and for a hypothesis. Then test it (implement it in the software). Measure (A/B testing etc..) and refine.

Not the answer you're looking for? Browse other questions tagged or ask your own question.