Designing User Experience
UX is not UI but UI is UX
First, we’ll review existing contents and trim the inefficient (outdated, unsuccessful, inappropriate to the goals/audience…) ones. Of course we’ll also keep those who the keep the job done. By doing this, we’ll be able to see what’s missing as content and what needs to be created according to brainstorming sessions with project stakeholders, eventually coupled with an « on field » crowdsourcing phasis. These methods will allow us to stick to the actual usability principles for the upcoming designing steps.
Having a complete overview of project in terms of content, we’ll sort them into appropriated categories which be useful later on to create navigation bars, wordings and interfaces.
Mapping the project
We’ll now map the different categories of content in a diagram to represent the macrostructure of the project which is beginning to become a visible, comprehensible information system.
After having designed the general structure, we’ll now work on the microstructure of the pages by making detailed wireframes : laying out the content components on the mockup regarding their priority level.
As you can see, all these elements are figuring efficiently the structural aspect of the system to come and its affiliated sections. Far from being superficial, UX actually allows you to prevent potential bugs and unfruitful use or incomprehension from the users ; which can simply lead them to lose interest in your app or website. By giving you the chance to understand how users could comprehend and navigate into your information system, UX is a lever helping you identify problems to come and permitting to work on their solutions in a preventive way.