Expertise
Architecture of Information, Content Strategy, UI Design
Devices
Responsive
Deliverables
User Personas, Benchmarking, Wireframes, Architecture of Information, Interaction Design, Visual Design, Interative Prototype, Design System
Many times it is said that "here’s none worse shod than the shoemaker’s wife". In this case, the website of the Spanish visual artists' rights management did not correspond to the potential of its visual material and the disruption that is expected of a site like this.
Many times it is said that "here’s none worse shod than the shoemaker’s wife". In this case, the website of the Spanish visual artists' rights management did not correspond to the potential of its visual material and the disruption that is expected of a site like this.
Many times it is said that "here’s none worse shod than the shoemaker’s wife". In this case, the website of the Spanish visual artists' rights management did not correspond to the potential of its visual material and the disruption that is expected of a site like this.
On the other hand, the usability when managing any rights or searching for any type of information about it made any task feel like worse than pulling teeth. The initial meeting with the client was something like this:
On the other hand, the usability when managing any rights or searching for any type of information about it made any task feel like worse than pulling teeth. The initial meeting with the client was something like this:
On the other hand, the usability when managing any rights or searching for any type of information about it made any task feel like worse than pulling teeth. The initial meeting with the client was something like this:
Our website is horrible and our members are ashamed to be associated with it. Furthermore, we need to attract more members since they are put off every time they have to carry out any procedure through it...
So you want to design something that satisfies all current and future members.
Yes!
Ok, Who are your members?
From the very beginning, we worked hand in hand with the VEGAP team to create a coherent web structure with well-organized information. Thanks to their database, we were able to identify user profiles, which although quite broad in terms of age range and technological assimilation, allowed us to start working.
We quickly realized that this required two distinct areas: a public information section and a private section from which users could carry out transactions.
From the very beginning, we worked hand in hand with the VEGAP team to create a coherent web structure with well-organized information. Thanks to their database, we were able to identify user profiles, which although quite broad in terms of age range and technological assimilation, allowed us to start working.
We quickly realized that this required two distinct areas: a public information section and a private section from which users could carry out transactions.
From the very beginning, we worked hand in hand with the VEGAP team to create a coherent web structure with well-organized information. Thanks to their database, we were able to identify user profiles, which although quite broad in terms of age range and technological assimilation, allowed us to start working.
We quickly realized that this required two distinct areas: a public information section and a private section from which users could carry out transactions.
At this point, we encountered a major difficulty. Due to the client's fear of disrupting anything in the database, we had to propose that certain processes and management tasks have a manual part by VEGAP, which made some navigation flows overly complicated. Fortunately, we were able to solve all this by reaching a compromise to implement a digital solution for all of this in a V2.
Once all these issues were resolved, we were able to create wireframes and interactive prototypes as a preliminary step to the visual proposal that Óscar Tapia was going to make. Unfortunately, all this effort was interrupted, and we couldn't see it implemented in a final version as VEGAP decided to cancel the project. It's a shame; we would have liked to measure the impact of these changes. These things happen, but the work is there, and we had to show it.
At this point, we encountered a major difficulty. Due to the client's fear of disrupting anything in the database, we had to propose that certain processes and management tasks have a manual part by VEGAP, which made some navigation flows overly complicated. Fortunately, we were able to solve all this by reaching a compromise to implement a digital solution for all of this in a V2.
Once all these issues were resolved, we were able to create wireframes and interactive prototypes as a preliminary step to the visual proposal that Óscar Tapia was going to make. Unfortunately, all this effort was interrupted, and we couldn't see it implemented in a final version as VEGAP decided to cancel the project. It's a shame; we would have liked to measure the impact of these changes. These things happen, but the work is there, and we had to show it.
At this point, we encountered a major difficulty. Due to the client's fear of disrupting anything in the database, we had to propose that certain processes and management tasks have a manual part by VEGAP, which made some navigation flows overly complicated. Fortunately, we were able to solve all this by reaching a compromise to implement a digital solution for all of this in a V2.
Once all these issues were resolved, we were able to create wireframes and interactive prototypes as a preliminary step to the visual proposal that Óscar Tapia was going to make. Unfortunately, all this effort was interrupted, and we couldn't see it implemented in a final version as VEGAP decided to cancel the project. It's a shame; we would have liked to measure the impact of these changes. These things happen, but the work is there, and we had to show it.
