Scheme Flows
Trading app n26
The image above shows a workflow for design stages, precisely an 'involvement' workflow.
P - Product
B - Backend
Q - Quality Assurance
D - Data
M - Mobile of Front
In order to organise a team of 7 designers and established a clear involvement of different competency teams in design phases, as a team lead I came up with a simple workflow scheme.
Schemes are used in UX for multiple different purposes. From creating workflows as the one showed in the example above, to Information Architecture, Navigation Schemes, Interaction Schemes, etc.
Schemes play a crucial role in defining the information architecture of a digital product. This involves organizing content and features into a coherent structure, such as menus, categories, and hierarchies. By creating clear schemes for organizing information, users can easily navigate and find what they're looking for within the product.
This analytical approach brings clarity not only to final users but to people working on the product, makes communication with dev teams easier and outcomes more foreseeable.
In order to define features within the trading app, one approach considered competitor research. My role as a Head of Design was to lead in the research and ideation phases.
We set the Information Architecture of competitor Apps.
After the IA of competitors was done, we did the analysis, and with the product goals as a main pivot, considering the data availability we came up with the Information Architecture of the trading app.
Information Architecture artefact was used for creating UX Road Map, for creating wireframes and to divide work into smaller chunks as it provided a zoom out, over all view of the app.
The image below shows IA - Scheme Flows for One Scenario for the Trading App.
