top of page
Mac-Mockup.jpg

An UX and UI challenge

Auba is the payment solution that streamlines the process of settling multiple invoices for companies. Our challenge was to create a cohesive platform that encompassed all functionalities in a SaaS-style dashboard.

We focused on harmonizing payment complexity with ease of use. The result is an intuitive platform that enables companies to manage their financial obligations swiftly and effectively

Kick-off: I initiated the project with a kick-off meeting, setting the tone for the entire process. During this phase, I gathered key stakeholders and team members to align our goals, objectives, and expectations. This initial meeting helped establish a strong foundation for the project and ensured everyone was on the same page from the start.

Understanding the User: Next, I sought to understand our user base. By analysing existing data, I gained valuable insights into their needs, pain points and preferences. This stage was crucial in shaping the direction of the project, ensuring that the final product resonated with our target audience.

Julia Almeira - Finance Manager.png

User Journey: With a clear understanding of our users, I mapped out their journey. I visualized their interactions, emotions, and touchpoints with the product. This user journey map provided a comprehensive view of the user's experience, allowing me to identify opportunities for improvement and tailor the design to enhance user satisfaction.

Sitemap and Flowchart: To structure the project's information architecture, I created a system map that outlined the hierarchy of content and navigation. In addition, I developed flowcharts that illustrated the user's path through the platform, considering various scenarios and interactions. This stage ensured a logical and user-friendly layout for the final product.

FlowchartAuba.png

Design and Delivery: With an established base, I moved on to the design phase. Based on the insights gained earlier, I created wireframes and prototypes that were discussed with the client to understand whether they reflected the user's needs and the platform's functionalities. In close collaboration, we refined these designs into a visually appealing and intuitive interface.

Payment Dash

View multiple invoices
selected for payment

All Invoices - International several invoices.png
All Invoices - International invoices - Payment step1.png

Payment process

This is a representative screen of the multi-invoice payment flow

Responsiveness

Mobile representation of selected invoice screens as well as the payment flow

Group 463.png

Learnings and closing notes

Finishing this project taught me some valuable lessons. Seeing the client happy at the end confirmed that we were able to do a good job together.

One important thing was constant communication. We kept an open channel with the developers and the client, which allowed us to resolve problems quickly. This not only made everything faster, but also made the final product more unified and in line with what the client wanted.

I was also able to involve the client in different parts of the project, which allowed me to make adjustments based on what they liked and needed. This not only made the client happier, but also showed me the importance of keeping the focus on the user throughout the process.

Dealing with changes and adjustments was another point that became clear. Sometimes I had to change things because of new information or unexpected requests. The ability to be flexible and make changes without losing my way was something I had to apply in the process.

Finally, I can say that the success of this project wasn't just because the design looked good, but because we really achieved the business objectives and helped the end users.

man-and-woman-working-at-the-office-with-an-imac-template-a16265.png

Zelocode 

bottom of page