Channels📱:Web

Markets 🇬🇧: UK, IT

My role 🙍🏻‍♀️: Product Designer

Team 👥: POs, FE Devs, BE Devs, UX researcher, QA,

When 📅: Feb 2018 -Apr 2018

Status 🚦: live

✨ My Learnings ✨: The most difficult part of any problem is hiding the complexity away from the users. Sometimes when designing for this B2B product we had the tendency of treating everyone not just as a pro user, but as a lover of complexity. All I wanted to do with this one was turning that upside down.


The problem

The starting point an existing implemented feature which allows users to automatically transfer money from the company to the the user wallets. We had received some negative feedback about the implemented version's lack of clarity and not fitting some use cases, thus the decision was to improve and further develop this feature.

In this context, I started thinking about a possible re design of the existing feature that incorporated also a re organisation of other existing features and new ones. I began scouring for more information (going through Intercom chats and chatting with our UX researcher) and found out why the users were not satisfied with what was available.

Users and audience

The target audience were mostly the accountants or managers who set up the budget and expense limits of the employees. Having to handle dozens of people with different allowances and budgets the imperative was to make it as simple as possible to keep the situation under control.