What motivated this project?

The registration process at smava ends with a feature encouraging customers to log into their bank accounts to verify their financial information and access exclusive benefits instantly. The first version of the implemented feature lacked optimizations for better communication and conversion. Customers felt we were stripping them down without us telling them why.

This feature offers both customers and the business great advantages. Customers can get far more accurate offers at better rates with less paperwork, as the banks will automatically verify the information from their bank account. The business can spend less on manual labor like calling people, advising them, or handling documents while growing at the same time the number of self-service customers. This feature unlocks a wide path of digitalization for us.

In the original implementation of the feature we relied on calling this feature a Tip, hoping customers would read the paragraphs and thus feel compelled to use their bank account login.

Testing visual communication changes

The first A/B test on this page introduced visual communication changes to the content surrounding the feature. We wanted to understand if making the feature more visually appealing and less verbose would increase the number of people logging in with their accounts.

The design was cleaned up with a new headline, a shorter paragraph, dividing the benefits in bullets, and adding an accordion at the bottom with additional information in case customers needed to know more. The radio buttons are also more prominent and in line with the style of the product.

We learned that more users clicked yes and had the intention to proceed with their bank accounts, however the final number of people actually doing it didn't increase enough to reach significance. There is potential, but we needed to dig deeper.

Side-by-side comparison of the tested designs. The redesign (right side) features conversion oriented elements like the icon list of benefits and a blue tag to highlight one of the radio buttons.

Afterwards, we ran a set of user tests on our platform. These tests confirmed that connecting to the bank account is too big of a commitment at this point in the customer journey, and we are not giving enough relevant information about this process to our users. We also learned that the login feature from our third-party provider has some additional steps we didn't know existed and needed to be considered.

I had also collected screenshots, videos, test results, and feedback about the feature from different sources. I cross-referenced our learnings to provide data- and knowledge-driven design solutions for the future tests, in addition to fundamental usability improvements.

Testing structural and flow changes

For the next test, I completely redesigned the page. We agreed on smoothing out the experience for our users while also pushing harder the bank login. With a design based on tabs, I placed users directly on the tab where the bank login is displayed and eliminated unnecessary conditional yes/no questions to display the login fields – reducing the journey by three interactions.

Both tabs request an IBAN number from the customer, however in the bank login tab there's additional content to persuade customers. Once they have introduced the IBAN number, the tab content is swapped for the bank login fields and reassurance elements like trust badges and privacy oriented USPs.

With the new designs I highlighted the path we wanted our users to take by making it the default state of the screen and turning the background light green.

What happens next?