The different target groups’ needs can vary dramatically. Thus if you want to design one product for all the different personas you should include the following insights in your development:
- offer multi-channel journeys
- personalize the UX
- promote financial literacy
During the very short Discover phase there was a huge pressure to have something feasible so the developers could start implementing. Nevertheless it was a very exciting and important time to be in the project.
- evaluation based on heuristic principles
- app reviews
• interviewing customer service
• workshops with mixed stakeholder set
• interviewing customer service
• workshops with mixed stakeholder set
- new fintech brands like Revolut
- swiss based established brands and products @UBS, @Postfinance etc.
- what do new successful fintech products provide
- what is the general trends for UX and UI patterns
We defined 2 aspects: 1) why and whom are we doing it for, 2) what is the technology we focus on
- interviewing customer service
- app evaluation based on heuristic principles
- app reviews
- 1st user testing interview
- Figma low-fidelity prototype with 3 use cases
- on site
- 1:1 situation with 4 observers in another room
- 6 tested persons
- aligning new product with predefined content scope
- aligning navigation and menu hierarchies according to defined personas and user journeys
- aligning due to tree testing insights
Based on what we have defined we designed a mobile prototype which we used for evaluation in a usability testing.Besides we did a quantitave tree testing remotely in order to evaluate our information architecture.
- interviewing customer service
- app evaluation based on heuristic principles
- app reviews
- 1st user testing interview
- persona & user journey validation
- Figma low-fidelity prototype with 3 use cases
- on site
- 1:1 situation with 4 observers in another room
- 6 tested persons
- Figma low-fidelity prototype with 3 use cases
- on site
- 1:1 situation with 4 observers in another room
- 6 tested persons
A structure was set up to have different stakeholders from business, engineering and design working with a common understanding. The design system provided not only the necessary artefacts for developers but was meant to educate all the stakholders.
Epics, features and user stories were told on a huge visual canvas and mirrored the whole Confluence documentation and its requirements.
- Key views
- Flows
- UI library
- Interaction patterns
- Design principles
- 2 weeks SCRUM intervals
- trying to chunk design process and its goals into the SMART goal setting
- working closely with business engineers on requirements and documentation