- 1 Project manager
- 1 Solution architect
- 2 UX designers
- 1 UI designer
- 4 Developers
- Figma
- FigJam
- Google suite
- Microsoft Teams
- Agile workflow
Table of contents
Overview
Process
wireframing
wireframing
Customer Journey mapping
users
People that have never been Busso’s clients and never downloaded IoPago
customers
People that are Busso’s clients, but don’t know about IoPago app and services
customers
People that are Busso’s clients with qualified past payments
customers
People that downloaded IoPago but never made a payment
Mapping through segments revealed all the complexity for each type of user. Special importance was given to early stages of the CJ and how the already existing flow would integrate.
High level wireframes were embedded into the customer journeys to give tangible examples when sharing to all stakeholders (product owner, managers, developers) during extensive validation meetings, contextually finalizing the product’s specifications.
Lo-fi wireframing
Wireframes were jot down following all use case emerged from customer segments. All corner cases were covered, using a user flow-like representation that set out clearly conditions and error states.
Cyclical reviews were made in order for the design to respect back and front end limitations as much as meeting compliance requirements.
Hi-fi wireframing
What I learnt
Interacting with the whole team using an agile methodology was one of the key learning, as communicating regularly with developers. One important UX-related skill I learnt were tackling product complexity, creating clear product communication and overcome technical limitations.