Intro

Merchant Dashboard for Clip was a 6-month project to revamp the main platform clients use to manage payments and customers. The existing platform had issues that limited access to necessary information, usability problems, and design inconsistencies.

Problem

Business goals

User problem

Users struggled to find information and understand the status of their payments, leading to an increase in support inquiries.

‍

Target user

There are three main types of users on the platform, each with different purposes. I mapped out these user profiles to understand the specific information they need and how this will impact the roles and permissions features.

• Owner of the business
• Cashier/Seller

Information Architecture

To start the project, I first reviewed the current organization and labeling of information. I also conducted calls with key stakeholders to understand the rationale behind the existing structure and to identify any business rules that needed to be followed.

Current IA Insights

After several discussions and meetings with the team, I identified a few key points that needed to be considered for the new structure.

• Technical limitations: The Invoices and Security sections had technical constraints that needed to be addressed.‍
• Lack of a dedicated designer: The absence of a single designer led to inconsistent organization and design across the platform.‍
• Ad-hoc updates: Information was often added as new products emerged, resulting in a lack of hierarchy and frequent reorganization.‍
• Future-proofing: New ideas and products required the new architecture to be flexible and adaptable for future features.

‍

Research

Card sorting

To understand how users organize information, I created both offline and online exercises. These exercises helped me grasp the mental models of different user types and organize the information within the Merchant Dashboard accordingly.

Users

• Cashier: 6 users. 18-45 years.
• Owner: 6 users. 18-45 years
  ‍

Result of the research - New IA

After speaking with users, I identified common groupings and terminology, and noted that some labels like "Panel de control" were unclear. I proposed a new main navigation structure, shared it with the PM Lead, Head of Design, and stakeholders for feedback, and we agreed on the new menu, shown here.

Design & Results

Once I created the new sections, the team was able to launch some of the sections and assess how they were performing with the users.

Here are some of the results of the new revamp:

• Updated the styles with the new design system, establishing consistency throughout the merchant dashboard.
• Upgraded sections, allowing businesses to update their product information.
• Improved usability, especially for those sections that were old and hard to navigate.
• Decreased the number of client calls when the tech team and I started launching new changes.

I collaborated with the development team, project managers, and stakeholders to revamp the project. After a few months, I learned how to manage the project with multiple stakeholders, creating one or more workflows at the same time, and being flexible with priorities depending on the users' or business goals.

‍