
Automating Cash Management: A UX Case Study
Introduction
The Cash Management project was initiated to streamline and automate the cash operations within a Global retail chain, providing a unified solution for all cash-related activities.
Background
Previously, cash tracking operations in retail stores were entirely manual, with store employees recording cash amounts at each counter and deposits from full cash counters in spreadsheets. This process was not only time-consuming but also prone to human error. At the end of each day, employees would add the final cash count to the spreadsheet before submitting it to the finance team for record-keeping and review. This manual approach led to inefficiencies, inaccuracies, and delays in cash management, which could have significant implications for the store’s financial operations.
Problem Statement
The manual process of cash tracking and reporting in Apple retail stores was time-consuming and prone to errors. The challenge was to design an application that would automate these tasks, allowing store employees to efficiently manage cash operations, track variances, and ensure accurate end-of-day reconciliation, while providing supervisors with a clear overview of store activities.
My Role
- Sr UX Designer: Worked closely with the Lead Designer on the design and development of the Cash Management application.
- User Research: Collaborated with a User Researcher to conduct stakeholder interviews, surveys, and competitive analysis to gather insights and identify user needs.
- Task Analysis & User Flow: Developed detailed task analyses and user flows to ensure a seamless user experience.
- Wireframes & Prototypes: Created wireframes and interactive prototypes to visualize and test design concepts.
- Collaboration: Worked closely with product managers, developers, and stakeholders to iterate on designs and ensure alignment with business goals.
- Usability Testing: Conducted usability tests to refine the application’s interface and improve overall user satisfaction.

Stakeholder Interviews
To ensure the Cash Management application addressed the core needs of its users, I collaborated with the User Research team to conduct stakeholder interviews with store employees, managers, supervisors, and finance team members. These interviews revealed key pain points in the current manual cash tracking process, such as time-consuming spreadsheet updates, frequent discrepancies, and the lack of real-time monitoring.
Key Insights:
- Manual Process Challenges: Store employees and managers found the manual processes prone to errors and delays, especially during peak hours.
- Critical Requirements: Stakeholders emphasized the need for automated cash tracking, real-time variance alerts, and streamlined incident reporting to improve accuracy and efficiency.
- End-of-Day Verification: Both employees and managers highlighted the importance of a reliable end-of-day process to ensure accurate cash counts and timely store closing.
- Overall Store Monitoring: Supervisors needed an overview of cash operations across multiple stores to quickly identify and address recurring issues.
These insights guided the design of the Cash Control Management application, ensuring it would streamline cash operations, reduce errors, and improve overall efficiency in Apple retail stores.
Surveys and Questionnaires
To complement the insights gathered from stakeholder interviews, we conducted surveys and distributed questionnaires to a broader group of store employees, managers, and supervisors. The purpose of these surveys was to validate the findings from the interviews, quantify the frequency and severity of the issues identified, and gather additional feedback that might not have surfaced during one-on-one conversations.
Objectives:
- Identify Pain Points: Understand the specific challenges faced by users in managing cash operations.
- Evaluate Process Efficiency: Gauge the efficiency of the current manual processes and identify areas for improvement.
- Feature Prioritization: Determine which features users considered most critical for the new Cash Control Management application.
- User Expectations: Gather expectations and suggestions for the design and functionality of the application.
Sample Survey Questions and Responses:
Response:
- Very easy: 5%
- Easy: 10%
- Neutral: 20%
- Difficult: 35%
- Very difficult: 30%
Insight: 65% of respondents found manual cash tracking either difficult or very difficult, highlighting a need for automation.
Response:
- Every day: 25%
- Weekly: 40%
- Monthly: 20%
- Rarely: 10%
- Never: 5%
Insight: 65% of respondents encounter cash discrepancies at least once a week, indicating frequent issues with the current process.
Response:
- Automated cash tracking: 85%
- Real-time alerts for variances: 75%
- Easy incident reporting: 60%
- End-of-day reconciliation tool: 80%
- Multi-store monitoring: 50%
Insight: Automated tracking and end-of-day reconciliation are the most desired features, followed by real-time alerts.
Response:
- Less than 30 minutes: 15%
- 30 minutes to 1 hour: 45%
- 1 to 2 hours: 30%
- More than 2 hours: 10%
Insight: The reconciliation process is time-consuming for many, with 40% of respondents spending over an hour daily.
Response:
- Extremely important: 50%
- Very important: 30%
- Moderately important: 15%
- Slightly important: 5%
- Not important: 0%
Insight: A combined 80% of respondents view incident reporting as either extremely or very important, showing it’s a key feature.
Response:
- Yes: 20%
- No: 80%
Insight: The majority of respondents rely solely on spreadsheets, indicating an opportunity for a more advanced digital solution.

Competitive Analysis
We conducted a competitive analysis to understand the strengths and weaknesses of existing cash management solutions in the market. This helped us identify opportunities to differentiate the Cash Management application.
Key Findings:
- Complex Interfaces: Many competitors had feature-rich but complicated user interfaces, leading to a steep learning curve for users.
- Feature Gaps: Existing solutions often lacked real-time variance tracking, flexible cash counter management, and efficient end-of-day reconciliation tools.
- Cost and Accessibility: Several products were expensive and out of reach for smaller retailers, leaving a gap for a more affordable, user-friendly solution.
- Integration Needs: Competitors varied in how well they integrated with existing retail systems, highlighting the need for our application to offer strong integration capabilities.
These insights guided us in designing a simple, user-friendly application that meets the critical needs of retail stores, offering key features like real-time tracking, flexibility, and affordability.
Personas
To effectively design the Cash Management application, it was crucial to understand the needs, goals, and challenges of the different users who would interact with the system. Three key personas were identified based on the requirements: Store Employee, Store Manager, and Store Supervisor. Each persona represents a distinct user group with specific responsibilities and goals within the retail environment.

Store Employee
Role: Manages day-to-day store operations.
Goals:
- Open and manage cash counters.
- Monitor and evaluate cash amounts.
- Report discrepancies and assist in end-of-day reconciliation.
Challenges:
- Handling multiple tasks during busy periods.
- Ensuring accuracy while managing cash.

Store Manager
Role: Oversees overall store operations.
Goals:
- Verify cash amounts at the end of the day.
- Supervise store closing activities.
Challenges:
- Ensuring procedures are followed correctly.
- Managing unexpected discrepancies.

Store Supervisor
Role: Manages multiple stores.
Goals:
- Monitor cash operations across stores.
- Ensure consistency and resolve recurring issues.
Challenges:
- Overseeing multiple stores with varying needs.
- Balancing detailed analysis with quick decision-making.
User Tasks and Task Analysis
The Task Analysis for the Cash Management application breaks down the specific tasks that each user persona must perform to achieve their goals. This analysis provides insight into the workflow and interactions required by Store Employees, Store Managers, and Store Supervisors, ensuring that the application supports their needs effectively.
Store Employee
- Manage Store:
- Open Store: Set up and prepare cash counters for the day’s transactions.
- Close Store: Reconcile cash amounts and secure the store at the end of the day.
- Manage Cash Counter:
- Evaluate Cash Amount: Regularly check cash levels at each counter.
- Perform Cash Pickup: Secure cash from full counters for deposit.
- Verify Cash Amount: Ensure accuracy in cash amounts during store closing.
- Manage Incident:
- Raise an Incident: Report any discrepancies or issues with cash amounts.
- Deposit Cash Bag:
- Deposit Cash: Securely store cash for pickup by the finance team.
Store Manager
- Verify Cash Amount: Oversee and verify the accuracy of cash reconciliation at the end of the day.
Store Supervisor
- View Store Activity: Monitor cash operations across multiple stores.

Task Flow
The Task Flow diagram illustrates the key steps involved in the daily operations of a Store Employee and Store Manager within the Cash Management application. The process is designed to ensure accurate cash handling and efficient store management, covering three primary steps:
-
Open Store:
- The Store Employee begins by opening the cash counters. If the expected cash amount is accurate, they submit it for verification, which is then reviewed and approved by the Store Manager. If there is a discrepancy in the expected cash amount, the Store Employee creates an incident (handled by a different application), and the process follows the same verification and approval flow.
-
Cash Pickup and Cash Deposit:
- During the day, if a cash counter reaches its capacity, the Store Employee performs a cash pickup and adds the cash to a deposit bag for secure storage.
-
Close Store:
- At the end of the day, the Store Employee verifies the cash details and closes the cash counters. The Store Manager then reviews and verifies all details before officially closing the store.
This task flow ensures a systematic approach to daily cash management, involving both the Store Employee and Store Manager, with clear steps for handling discrepancies, cash pickups, and store closing procedures. The flow is designed to minimize errors and ensure that all cash operations are accurately recorded and securely managed.
This task flow ensures a systematic approach to daily cash management, involving both the Store Employee and Store Manager, with clear steps for handling discrepancies, cash pickups, and store closing procedures. The flow is designed to minimize errors and ensure that all cash operations are accurately recorded and securely managed.
User Flow
The User Flow for the Cash Management application outlines how different user roles—Store Employee, Store Manager, and Store Supervisor—navigate through the application to perform their daily tasks. This flow ensures that each user can efficiently access and complete their required actions within the application, enhancing the overall user experience.
1. User Login and Dashboard Access
- Store Employee:
- Logs into the application with secure credentials.
- Directed to the Daily Operation Landing Page, where they can manage the day’s activities, such as opening cash counters and performing cash pickups.
- Store Manager:
- Logs into the application with secure credentials.
- Accesses a dashboard where they can oversee daily operations, verify cash amounts, and manage store closing activities.
- Store Supervisor:
- Logs into the application with secure credentials.
- Directed to a high-level dashboard where they can monitor overall store activity across multiple locations, review reports, and check on the status of various stores.
2. Daily Operations for Store Employee
- Manage Store:
- From the Daily Operation Landing Page, the Store Employee can:
- Open Store: Initiate the opening process by setting up and verifying cash counters.
- Close Store: At the end of the day, proceed to close the store by reconciling cash amounts and securing the counters.
- From the Daily Operation Landing Page, the Store Employee can:
- Manage Cash Counter:
- Navigate to the cash counter management section to:
- Evaluate Cash Amounts: Regularly check the cash levels at each counter.
- Perform Cash Pickup: If a cash counter is full, initiate the cash pickup process and add the cash to a deposit bag.
- Verify Cash Amount at End of Day: Ensure all cash counters are accurately reconciled before closing the store.
- Navigate to the cash counter management section to:
- Incident Reporting:
- When a discrepancy is found, the Store Employee is prompted to flag the issue, which is then reported (further management of the incident is handled by another application or process).
3. Store Manager Operations
- Manage Cash Counter:
- Access the cash counter management section to:
- Verify Cash Amount: Review and approve the cash amounts submitted by the Store Employee at the end of the day.
- Access the cash counter management section to:
- Close Store:
- Navigate to the store closing section to:
- Finalize Store Closing: After verifying all cash counters, the Store Manager ensures that the store is closed securely and that all financial data is submitted.
- Navigate to the store closing section to:
4. Store Supervisor Monitoring
- View Retail Store Activity:
- Access a high-level dashboard to:
- Monitor Store Operations: Review cash management reports and overall activity across multiple stores.
- Identify Issues: Detect patterns or recurring issues that may require attention, and communicate with Store Managers as needed.
- Access a high-level dashboard to:
5. Accessing Settings and Preferences
- Settings: All user roles can navigate to the settings section from their dashboards to adjust preferences, manage account details, or access help/support resources.
6. Generating Reports and Audits
- Report Generation:
- Store Managers and Store Supervisors can generate detailed reports from the application, summarizing daily cash operations, discrepancies, and incident resolutions.
Summary
This User Flow provides a comprehensive overview of how Store Employees, Store Managers, and Store Supervisors interact with the Cash Management application. It maps out the steps from logging in to managing daily operations, handling cash, closing the store, and generating reports. The flow also accounts for high-level monitoring by supervisors and access to settings and audit logs, ensuring that all users can navigate the application efficiently to accomplish their tasks.
Information Architecture
The Information Architecture (IA) for the Cash Management application is designed to provide a clear and intuitive structure that allows users to efficiently navigate through the system. The IA ensures that all user roles—Store Employees, Store Managers, and Store Supervisors—can easily access the tools and information they need to perform their daily tasks and monitor store activities.
1. Dashboard
- Purpose: The Dashboard serves as the central hub for users when they log into the application. It provides an overview of key metrics and quick access to essential tasks and notifications.
- Content:
- Displays summary information such as total cash, active incidents, and recent reports.
- Provides shortcuts to key sections like Daily Operation, Incidents, and Reports.
2. Daily Operation
- Purpose: This section is where Store Employees and Store Managers conduct their day-to-day cash management tasks.
- Subsections:
- Open: Start-of-day tasks, including opening cash counters and verifying initial cash amounts.
- Cash Pickup: Handles the process of picking up cash from full counters and preparing deposit bags.
- Deposit Bag: Manages the secure storage of cash in deposit bags until they are collected.
- Close: End-of-day tasks, including reconciling cash amounts and securely closing the store.
3. Incidents
- Purpose: This section allows users to manage and review incidents related to cash discrepancies or other issues.
- Subsections:
- Incident List: Displays a list of all reported incidents with the ability to perform an advanced search to filter and find specific cases.
- Incident Details: Provides detailed information about individual incidents, including status and resolution steps.
- Workflow: Outlines the steps and processes involved in resolving incidents, ensuring that all actions are tracked and completed.
4. Reports
- Purpose: The Reports section allows users to generate and view various reports related to cash operations, incidents, and overall store performance.
- Subsections:
- Report List: Displays a list of available reports, with an advanced search feature to filter reports by date, type, or other criteria.
- Report Details: Shows detailed information for selected reports, including options to export or print the report for offline use.

Summary
This Information Architecture provides a logical and organized structure for the Cash Management application, ensuring that users can easily navigate between the Dashboard, Daily Operations, Incidents, and Reports. Each section is designed with clear subsections that cater to the specific needs of the user roles, whether they are managing daily tasks, handling incidents, or reviewing reports. The IA supports an efficient workflow, allowing users to focus on their tasks without unnecessary complexity, ultimately contributing to a seamless user experience.
Low-Fidelity Wireframes
The Low-Fidelity Wireframes serve as the initial visual representation of the Cash Management application’s interface. These wireframes focus on the layout, structure, and functionality of the application without getting into detailed design elements like colors, typography, or images. By creating multiple sketches, I explored different approaches to how users would interact with the application, ensuring that the layout was intuitive and aligned with the needs identified in the previous stages of the project.
Exploration of Different Layouts
During the wireframing process, I developed multiple sketches for key screens, including the Dashboard, Daily Operation, Incidents, and Reports sections. Each sketch explored different ways to present information, organize content, and streamline user interactions:
- Dashboard Layouts: Focused on how to present key metrics and shortcuts to essential tasks in a way that would be immediately useful to users.
- Daily Operation Screens: Considered different layouts for the sequence of tasks such as opening the store, managing cash pickups, and closing the store, ensuring that users could move seamlessly between these tasks.
- Incident Management Layouts: Explored how to best present a list of incidents, incident details, and workflow steps, aiming for clarity and ease of navigation.
- Reports Section: Sketched out various ways to organize report lists, with clear options for searching, exporting, and printing detailed reports.
Usability Testing and Feedback Integration
To validate the initial wireframes, we conducted a usability test by showing the low-fidelity screens to a selected group of users and stakeholders, including store managers and business users. The feedback gathered from these sessions was invaluable in fine-tuning the wireframes to better meet user needs.
Key Feedback and Adjustments:
- Variance Display: Store managers expressed a desire to see cash variances categorized by known and unknown reasons. This led to the addition of filters in the variance reports, allowing users to easily differentiate between these categories.
- Store Performance Information: Business users requested the inclusion of data showing the top-performing and least-performing stores in terms of cash variance, as well as the duration for store open and close timings. In response, we added a summary section on the Dashboard highlighting this information, making it readily accessible for decision-making.
These adjustments ensured that the wireframes were not only aligned with the intended user flow but also addressed specific needs and preferences of the users who would interact with the application daily.
Selection of the Final Wireframe
After evaluating the different sketches and incorporating feedback from the usability tests, I selected the wireframes that best balanced usability, functionality, and clarity. The chosen wireframes were those that:
- Supported the User Flow: The selected layouts ensured a smooth flow from one task to the next, minimizing user effort and reducing the potential for errors.
- Highlighted Key Features: The wireframes effectively showcased the application’s core features, such as cash management, incident reporting, and report generation.
- Simplified Navigation: The selected designs offered a clean and intuitive navigation structure, making it easy for users to find what they needed without confusion.
These low-fidelity wireframes were then refined and tested to ensure they met the needs of the different user roles (Store Employee, Store Manager, Store Supervisor) before moving on to higher fidelity mockups and prototypes.
By uploading multiple sketches, I am able to provide a clear view of the design process, showing the evolution of the application’s interface from initial concepts to the selected final wireframes. This iterative approach ensured that the final design was both user-centered and effective in addressing the goals of the Cash Control Management application.
High-Fidelity Wireframes
After finalizing the low-fidelity wireframes and incorporating feedback from usability testing, the next step was to develop high-fidelity wireframes. These high-fidelity wireframes are a more polished and detailed representation of the Cash Management application, reflecting the final design elements that users will interact with.
Purpose of High-Fidelity Wireframes
The high-fidelity wireframes serve several important purposes:- Visual Design: They incorporate visual elements such as colors, typography, branding, and detailed layouts. This brings the design closer to the final product, allowing stakeholders to see a more accurate representation of how the application will look and feel.
- Interaction Details: These wireframes also include specific interaction elements, such as buttons, dropdowns, and input fields, with their states clearly defined (e.g., hover, active, disabled).
- Usability Testing: With a more refined design, the high-fidelity wireframes are used for further usability testing, ensuring that the visual design and interaction details enhance, rather than detract from, the user experience.
Key Design Enhancements
- Visual Consistency: We applied a consistent color scheme and typography throughout the application to ensure a cohesive user experience. This involved using the company’s brand guidelines to select colors, fonts, and icons that align with the brand identity.
- Detailed Layouts: The layout of each screen was refined to optimize space and improve readability. This included careful attention to alignment, spacing, and hierarchy to guide users naturally through their tasks.
- Enhanced Navigation: We improved the navigation structure to make it more intuitive. Clear visual indicators and consistent placement of navigation elements help users easily find their way around the application.
- Interactive Elements: All interactive components, such as buttons, forms, and links, were styled to be visually distinct and easy to interact with. States such as hover, focus, and active were clearly defined to provide feedback to users as they interact with the interface.
Usability Testing and Refinements
The high-fidelity wireframes were tested with a small group of users to validate the design choices. Feedback from these sessions led to several refinements:- Increased Visibility of Key Actions: Based on user feedback, we adjusted the prominence of certain buttons and actions, ensuring that important tasks like submitting a report or raising an incident were easily accessible.
- Improved Readability: Font sizes and contrast were adjusted to improve readability, especially in areas where users needed to read large amounts of data, such as reports or detailed incident logs.
- Streamlined Workflows: Some workflows were further streamlined to reduce the number of steps required for common tasks, based on user feedback that highlighted areas where the process could be more efficient.
Interactive Prototype and Usability Testing
After completing the high-fidelity wireframes, we developed an interactive prototype to simulate the user experience. This prototype allowed users to navigate through the application, interact with key elements, and perform tasks as they would in the final product.
Usability Testing
We used an internal tool to share the interactive prototype with a larger group of users for usability testing. This round of testing aimed to validate the design and ensure it met user needs across various roles.
Key Outcomes:
- Positive Feedback: Users found the prototype intuitive and easy to navigate, confirming that the design aligned well with their expectations.
- Minor Suggestions: A few minor adjustments were suggested, primarily related to improving the flow and displaying more information where needed, ensuring users could access critical details more easily.
- No Major Issues: The testing revealed no significant issues, indicating that the design was robust and ready for the next phase.
With the prototype validated and minor refinements made, we are now ready to proceed to the final handoff to the development team, ensuring a smooth transition into the development phase.
Challenges Faced and Solutions
During the development of the Cash Management application, several challenges arose, each requiring thoughtful solutions to ensure the final product met user needs and business goals.
1. Complex User Flows
- Challenge: One of the primary challenges was managing the complexity of user flows, particularly for Store Employees and Store Managers who needed to navigate multiple tasks, such as opening and closing the store, managing cash pickups, and reporting incidents. Ensuring these flows were intuitive and efficient, without overwhelming users, was crucial.
- Solution: We addressed this by breaking down the user flows into smaller, manageable steps. Each task was clearly defined and logically connected to the next, with visual cues and navigation aids added to guide users. We also conducted usability testing with low-fidelity wireframes to gather feedback, allowing us to refine the flows before moving to high-fidelity designs.
2. Balancing Detailed Information with Usability
- Challenge: Another significant challenge was balancing the need to display detailed information, such as cash variances and incident reports, with maintaining a clean, user-friendly interface. Users required access to extensive data, but too much information could easily clutter the interface and hinder usability.
- Solution: We implemented a layered information approach, where high-level summaries were displayed upfront, with options to drill down into more detailed views as needed. This allowed users to access the information they required without being overwhelmed by data on the main screens. Feedback from usability testing helped us fine-tune this balance, ensuring that critical information was easily accessible while keeping the interface clean and organized.
3. Integrating Feedback from Diverse User Roles
- Challenge: With multiple user roles (Store Employee, Store Manager, Store Supervisor), each with different needs and priorities, integrating feedback from all these groups into a cohesive design was challenging. For example, store managers wanted to see specific variance details, while business users requested broader performance metrics.
- Solution: We created customizable dashboards and reports that catered to the specific needs of each user role. This flexibility allowed us to address the unique requirements of different users without compromising the overall design. By involving representatives from each user group in the usability testing phase, we ensured that the final design met the diverse needs of all stakeholders.
4. Ensuring Smooth Navigation Across Sections
- Challenge: Navigating between the different sections of the application—such as Daily Operations, Incident Management, and Reports—needed to be seamless. However, the varied nature of tasks and the amount of data presented in each section made it difficult to maintain smooth navigation.
- Solution: We implemented a consistent navigation structure across all sections, with clear labels and easy access to primary tasks. A breadcrumb trail and contextual navigation options were also added to help users understand their location within the application and move between related tasks easily. This consistency in navigation reduced cognitive load and made the application easier to use.
Impact
The implementation of the Cash Management application resulted in significant positive outcomes for the retail operations. Here are some of the key impacts:
Enhanced User Satisfaction
Dramatic reduction in time required for daily cash management tasks.
Reduction in Errors
Significant decrease in manual errors, leading to more accurate financial records.
Improvement in Incident Resolution
Faster resolution of cash discrepancies with streamlined workflows.
Enhanced User Satisfaction
Increased satisfaction due to an intuitive interface and improved workflows.
These metrics were derived from a combination of user feedback, system data analysis, and performance comparisons before and after the implementation of the “Cash Management” application.