Redwood Design System

For each component project, I began with understanding business requirements from the project managers and product team leaders and designers. Based on those requirements, I work with stakeholders to determine the scope of design. As such, the levels of redesign can range from very small interaction changes to full-scale redesign. The components shown here were deemed for full redesign. For these components, I begin to understand user needs by doing secondary research of similar components in other products as well as gathering use cases and requirements from our customers.

How can we innovate these well-known components and the mental models behind them?

From there, I go into the design process by starting with explorations and ideation, focusing on addressing the unique requirements for Oracle products. These considerations include large data sets, user permissions and securities, and scalability. I follow an iterative process that involves working hand-in-hand with partners and sharing designs in feedback sessions. After these reviews and final sign off from direct stakeholders, I enter a delivery phase which involves sharing with other development organizations and publishing of the documentation into internal resource areas.

Below is a sample of some of those projects:

As a result of these component designs, we are able to redesign and add new components to the Redwood Design System component library. In addition, we were able to contribute to designing Oracle's other pillar products with an emphasis on creating a consistent and modern design language.