INTERNET BANKING
Vizir Software Studio
Project Overview
A leading cosmetics company buys primary commodities from riverside sellers, who faced constant thefts due to cash transactions, while the internal finance sector lacked a personalized tool, causing complexity and insecurity. Our mission was to provide digital security to the communities living along the Amazonas riverside.
Tags
Bringing Clarity Through Visual flows
I joined this ongoing project to design an approval flow feature. After reviewing previous meeting recordings, I noticed the team lacked clarity on the requirements. To address this, I created visual information architecture flows based on available documentation and used them to validate requirements with key stakeholders. This brought clarity to the team and established a solid foundation for the solution.
Connecting User Journeys in Complex Approval Workflows
The goal was to enable clients to create personalized approval flows for different needs. The solution required four key elements: registering users, creating profiles with custom permissions, assigning users to profiles, and setting up approval flows with parameters.
Understanding the personas was crucial. The complexity of connecting different journeys revealed an important challenge - three main personas with complementary roles needed to interact seamlessly. This meant the solution also required a notification system tailored to each persona’s journey.
User Personas
SYSTEM ADMIN
T.I. Person
Will create the approval flow accordingly the business needs, create new users and give them profile and permissions.
JOBS TO BE DONE
- Add users
- Create profiles with parameters
- Setup personalized approval flows
OPERATIONAL
Person from financial sector
Include new payment requests, they can be cooperatives represented or financial that pay bills.
JOBS TO BE DONE
- Create requests
- Follow the request approval answer
APPROVER
Chief financial officer
People who have the permission to review requests, usually in high positions.
JOBS TO BE DONE
- Review requests, approving or denying
- Write a motive in case of denial
A holistic view of a payment request journey with notification system.
User research
To validate our assumptions, the Product Owner and I conducted usability testing with 9 operational users using prototypes. The research uncovered critical issues that needed resolution before launch.
Key findings:
Users expected payments and transfers to be separated, reflecting their daily workflow. We restructured the side navigation to accommodate this mental model.
A major pain point emerged during request reviews—missing context made approvals difficult. We added a description field to the existing request feature to provide necessary details.
Users instinctively looked to the center of the interface for their most frequent tasks, but no dashboard existed. As one participant noted: “It’s always good to have a shortcut… it’s important because it’s a daily activity.” This insight led us to design a centralized dashboard for core workflows.
Creating a payment approval flow
Solution used by the System admin persona to create and manage multiple payment approval flows.
Screen that centralize active payment approval flow.
