Scheduler

As a UX/UI Designer at Oracle, I focused on shaping the Collection Processor – Scheduler feature into a seamless, intuitive workflow for enterprise users. Beyond wireframes and mockups, I leveraged user research, testing, and iterative design to create an engaging, consistent user journey—empowering finance teams and operations personnel to efficiently schedule and manage automated collection activities.

Challenges Faced

• Cloud Support teams were too dependent on manual entry input and its accuracy to be able to locate the customer’s account.
• Once the customer’s account was found, cloud support teams had difficulties viewer the list of databases and hardware devices associated with it.
• Cloud Support teams were only limited to one time scheduled scan and weren’t able to have a recurring scan.

Solutions

• Schedule Options - One Time or Recurring Collection.
• Collection Type - EXAchk or Diagcollect.
• Automate the Search Process - Include various ways to search for a customer’s account and their related Eng Sys or Racks.
• Streamline the Schedule Process - pre-fill information based on customer profile and allow the user to properly schedule collections and on what specific clusters.
• Properly display a review step to a user to allow them to review and make changes before scheduling a collection.

Users

• Proactive Cloud Support Team - focuses on diagnostic collection results, troubleshooting. Want to prevent any issues with the database or server performance.
• Reactive Cloud Support Team - Use EXAchk reports to determine the overall health of the environment for a specifc timeframe not big picture.
• Patching Team - Team that is responsible for implementing solutions based on the reports collected and solutions shipped.
• MAA Reporting Team - Generate Reports based on EXAchk collections scheduled and successfully ran.

Key Learnings

• Streamlining the search functionality with auto-complete and smart defaults significantly reduced user friction - showing that small UX improvements can have major impact on daily workflows.
• The iterative design process with cloud support teams revealed that a clear review step was essential for mission-critical scheduling tasks, leading to a more confident user experience.
• Designing for different user roles (Proactive, Reactive, Patching, and MAA teams) taught me the importance of creating flexible interfaces that serve multiple user personas while maintaining consistency.