The entire project had a deadline of three months to be implemented, with a design process deadline of two sprints (1 month).
Utilized Jira and an agile framework with a multidisciplinary scrum team of 7 members.
Roadmap
Card Sorting Session: Conducted virtual card sorting sessions to address information architecture issues. The most important insight was that the options must be divided into two profiles based on user personas.
Sketches: Designed main menus for each user persona.
Menu sketches
Mid-Fi Prototype: Validated categories within profiles.
Mid-fidelity sketches
(This image is a translation of the original interface since it is in Spanish.)
Usability Tests: Evaluated user perception of the new interface. Assessed term clarity and ease of performing common tasks. After the tests, incorporated user feedback to refine the design.
Findings:
- Clarifications needed for technical profiles.
- Text size concerns
- Understanding of terms
- All users mentioned the ease of finding their options in one place.
User's comments
Time Optimization: Up to 50% reduction in procedure time.
ATM Availability: 2-point increase in ATM availability for customers.
Error Reduction: 25% decrease in configuration errors.
The Power of User-Centric Design: This case study demonstrates how neglecting user needs in the initial design can lead to significant inefficiencies and delays. By prioritizing user-centric design the project achieved remarkable improvements. This highlights the importance of understanding users' workflows and pain points to create truly effective solutions.
Information Architecture Matters: Confusing navigation and organization can significantly hinder user performance. The card sorting session and focus on information architecture in this project show how optimizing the structure of information can dramatically improve ease of use and task completion time.
Real Hardware Verification Matters: While digital testing is crucial, don't forget the testing directly on ATM hardware in a lab environment, mimicking real-world user interactions. This emphasizes the importance of testing not just on screens, but on the actual hardware your users will encounter.