Overview
As a UX Designer at Oracle, I worked on updating design system for the Manage Services page in Oracle Primavera Cloud (OPC), a platform used by professionals in the construction and project management industries. The goal was to enhance clarity, consistency, and usability by aligning the interface with Oracle’s new Redwood Design System while addressing key user pain points.
Please note that due to information concerns and an NDA agreement, the critical details of the project and problem space can’t be disclosed, therefore the emphasis will be placed on the overall process work and deliverables
The Problem
The original Manage Services page was critical for users to monitor and manage background jobs, such as integrations, imports, exports, and metrics calculations. However, the experience was hindered by:
These issues contributed to frustration, especially when tasks were time-sensitive
Missing contextual information
Inconsistent design patterns
Redundant or unclear language
Difficulty locating specific jobs or statuses
These issues contributed to frustration, especially when tasks were time-sensitive
The Design Journey
I reviewed job logs, and analyzed usage data through Heap.io over a couple months, along with notes and reports from past stakeholder interviews, and usability tests for Manage Services.
Key Insights:
Primary Users:
Construction professionals and administrators.
Top Tasks:
View job status (Completed, Failed, In Progress)
Understand job context
Terminate or retry stuck jobs
View logs for debugging
Using the Shape of Data format, I gathered and organized the general usage and numbers for the page.
Quantitative Data:
~5.5k users on average/month
“Completed” filter used ~20x/week
“View Log” accessed ~25x/week
Failed jobs viewed 30–100 times/week
_Page_11.jpg)
Common Feedback:
Confusion between Manage Services, Inbox, and Notifications
Desire for more actionable context and better job filtering
Redundant or unclear terminology (“Invalid”, “Background Jobs”, etc.)
With the feedback and numbers I was able to search through the multiple page layouts within the Redwood Design System, and start with the wireframes.
The Solution
I redesigned the page using the rest of the preset Redwood Design System to bring consistency, clarity, and modern visual standards. I was able to use the...
Collection Detail Layout
Contest Switcher
The Smart Search
In-App Navigation
...presets to build out the Manage Services in the new design system
Key Changes:
Redesigned Job Cards: Clear hierarchy of job name, type, status, and date.
Simplified Filters: “All / Completed / Failed / In Progress” tabs with high visibility.
Expanded Job Logs: More context like user who triggered the job, associated project/workspace, and frequency.
Job Actions: Inline options like Retry, Terminate, and View Log placed where users expect them.
Search Improvements: Smart filtering for Job Type, Status, and Context.
Final Thoughts
This project helped me grow as a UX designer working within a large ecosystem. It showed me how even small interface changes can have a meaningful impact when rooted in user needs and backed by data. After this project I learned:
Data-driven design is essential—usage logs and user interviews helped prioritize features.
Design systems like Redwood improve scalability and cohesion across teams.
Enterprise UX often means solving for power users with high expectations and very specific workflows.
Collaboration with developers, QA, and PMs was critical to ensure feasibility and alignment.
_Page_08.jpg)
_Page_07.jpg)
_Page_09.jpg)