Make it simple
Banking app | restructure | Succesfull user testing
In order to have people use seemingly complex tooling, you need to make it match their use cases. And make it inuitive.
-
Organic growth had turned the NN Banking app into a structure lacking any rational architecture
-
As the app was being rebuilt in React, we had the opportunity to come up with a new structure. Future proof and user friendly.
-
Design a prototype featuring an intuitive architecture, to test whether this would resonate
-
Testresults were positive as all users understood the new approach and preferred it over the current
Analyse this āš».
You can only restructure once you understand what you're dealing with. What is the current structure? Classify all content. Dissect everything.
I would define the ideal structure of any digital service to focus on solving its most popular use cases. The challenge for NN was solving this with a lack of user insights as we had to rebuild the app without any available research. So we needed a form of information architecture that would support all content and services. One that users would understand - so on the longer run, we could address actual use cases.
With this many products getting lost would get very easy. Especially since the list of products shared so little - other than being financial. I applied a simple blueprint all content had to adhere to. This way, your way home was never difficult. The top layer features the full list; one level down is for an individual product and any funnel within this product would be on the third level. So wherever you are: two levels up and you're home.
The Test
We set up moderated usability tests and found all involved were able to move around. After this initial setup the app was built and user research started to find out what use cases we should be matching.