The Process
I started by checking the targeted flows to do a quick evaluation, and making assumptions determining where are the issues. In such cases, I usually check recorded sessions using a session recording tool, this is very helpful to giving a quick indication for what is happening, but unfortunately, we don't have such tool installed.
After the evaluation I found obvious issues in the information architecture for the transfer types, UX writing, visual hierarchy. To back these findings up and get more insights, I conducted a usability session and quick interview after each session to collect their thoughts and expectations.
After the usability sessions and interviews we validated our assumptions and got more insights and defined the current pain points and the opportunities in the user flow.
After defining the pain points and opportunities and getting the expectations from the users, I run a brainstorming session and invited multiple members from different teams, in this step I highly recommend invite the backend engineers to this session, to validate our solutions early in brainstorming sessions which will save a lot of time and they can help optimizing solutions if we have limitations from the back-end side.
After that we started visualizing the solutions we came up in brainstorming sessions, then created low fidelity wireframes and a high fidelity prototypes for testing purposes.