Optimising the UX of Editing Dashboards & Widgets in an ATM Management System

My Role

UI/UX Designer

Timeline

March 2024 - April 2024 (4 weeks)

Business Model

(B2B) Business to Business

Tools Used

Figma, FigJam, Jira

OVERVIEW

The Organization -

ESQ Data Solutions is a global leader in financial services data analytics and ATM management solutions. Specializing in customized services, ESQ partners locally with clients to deliver tailored solutions that enhance market impact and operational efficiency. With a focus on financial services data analytics and ATM management, ESQ provides valuable insights and optimized performance to organizations worldwide.

The Product -

The Incident Management System (IMS) monitors the life cycle of incidents in the device environment. It serves as a unified point of contact for users to receive help in troubleshooting, answer queries, and address known issues. The Incident Manager enables users to effectively manage, resolve, and proactively monitor incidents in their business environment.

CHALLENGE

Making and editing widgets on the dashboard was frustrating for users. The controls were difficult to find, the instructions weren't clear, and changes were not reflected real-time. In some cases, data sources wouldn't work together, forcing users to start over. This created a clunky experience, and there was a need for more user-friendly and responsive interface.

The Data Analyzer dashboard, despite offering insightful data analytics, presented significant challenges in managing widgets. Users found it difficult to navigate the dashboard and edit widgets, encountering a cumbersome and unintuitive process. The system allowed users to add data sources only after creating widgets, and if a data source was incompatible, users had to restart the entire process.

The above scenario, A classic case of prioritizing functionality over usability.

RESEARCH & DISCOVERY

The approach I went with:

So, Why were the users struggling with the app?

Upon initial review, it became apparent that the app had several caveats that failed to address significant issues. And not to mention, the existing app appeared outdated, which was a key factor driving the need for a complete redesign. Turns out, the app was built directly by the development team as there weren’t proper product or design teams in place at the time.

The useful features were buried beneath the UI surface.