FXStreet is the leading provider of information and resources for Forex traders. Created in the year 2000, FXStreet offers tools to help traders take more informed decisions when entering the market, through an objective view of the market.
Job Description: Heuristic Analysis, Information architecture, Prototiping, User Testing.
Duration: June 2015 / August 2015
UX Designer tools: User research, Axure, Tree testing, Paper, Pencil, Survey tools
Solve the architecture and hierarchy problem in the platform header
In collaboration with Dolors Pou (UX Expert), we worked on the architecture of the website header, my function was to implement a Benchmarking analisys and extract the main weaknesses and strengths of the competition, with the idea of analize and improve the header. Later to raise a hierarchy of the components and determine a space close to minimalism in the header.
On the other hand Dolors was dedicated to more research work and information architecture to determine the content that would contain the different levels and also in charge to implement and create the visual design.
The header of the Fxstreet website did not have a defined hierarchy of components. With studies of heat maps, we detected that the user spent a lot of time in the header trying to allocate the elements, the mental map problem was evident.
Another problem we encountered was the problem of navigation scalability.
With a new design, an approach of minimalism, could solve the a lack of redistribution of elements and improve the scalability.
The first step was to meet with stakeholders and listen to their needs, also to analyze the comments we had so far.
The information was based on the vision of the stakeholders where they analyzed the architecture.
A co creation session was designed, implementing a design thinking method for a week.
To evaluate the hypothetical hypotheses so far, perform a guerrilla user test and evaluate the results.
The header of the site belonging to the company Fxstreet had been created with the idea of containing the most important components in a narrow architecture.
The Hierarchy was created so that the elements coexisted together and correctly organized in a space that breathed very little. This caused a scalability problem and the possible incorporation of sublevels. With the growth in levels and possible new functionalities, the hierarchy defined until that moment ran a serious risk of facing the problems of interfering in the possible mental maps that the user could generate.
After iterating through several ideas and sketches, the following architecture was reached:
The main idea was to generate a new hierarchy of the components and to create a minimalist design with the idea of facilitating the mental map that the user generates in his head when he tries to define the location of the components. The elements were grouped by similarity, order in the hierarchy and their functionality. With this architecture, the scalability in the amount of navigation elements was improved.
The main idea was to hierarchize the content and to facilitate the mental map that the user generates in his head when trying to define the location of the components.The elements were grouped to facilitate the user through similarity, the order in the hierarchy and its functionality.
With this architecture it was improved the scalability in the number of navigation elements.