← Back to work

Oracle · Management Cloud

Simplifying server resource utilization.

Oracle was building a Management Cloud platform with several domain applications. One of them helped users identify under-utilized and over-utilized server resources so IT infrastructure could be managed more efficiently.

Role
Lead Interaction Designer · Server Resource Analytics
Product
Oracle Management Cloud · IT Analytics service
Timeline
Jan 2016 — Mar 2016
Platform
Web · Enterprise SaaS
Server Resource Analytics — overview screen

My role

Lead Interaction Designer.

I led the design of Server Resource Analytics — owning the interaction model end-to-end and partnering closely with product, engineering, and domain experts.

Context & challenge

An integrated cloud, a very specific IT problem.

Oracle Management Cloud is an integrated cloud platform, and IT Analytics is one of its core services. Inside IT Analytics, Server Resource Analytics is the application capacity managers and system administrators rely on to manage their server estate — answering questions like "what's being wasted?" and "what's about to tip over?"

The data was rich and the use cases were dense. The challenge was turning a wall of metrics into something a busy admin could read in seconds and act on with confidence.

Oracle Management Cloud platform context

Getting familiar with the content

Three resources. Two that mattered most.

CPU, memory, and storage utilization were all in scope. But CPU and memory carried the most weight — their capacity constraints and usage patterns made them the metrics that most often drove real decisions. Letting that hierarchy show up in the design was an early, important call.

CPU, memory, and storage resources
CPU, memory, and storage resources.
Structure and information architecture
Structure and information architecture.

"Don't overwhelm the user with everything at once — reveal it in the order they actually need it."

— The principle that shaped every screen

Ideation

An inverted pyramid of information.

To keep a complex application from feeling overwhelming, I structured the experience around progressive disclosure — specifically, an inverted-pyramid approach with three stages:

  • The headline. A top-level read on resource health across the estate.
  • The breakdown. Pivots into the dimensions that matter — CPU, memory, time, group.
  • The detail. Server- and metric-level depth for the moment a decision actually has to be made.
Inverted pyramid approach
Inverted pyramid.
Design iterations
Design iterations.

Final designs

Wireframes that carried the structure through.

The wireframes evolved through several iteration rounds — but the underlying information architecture held all the way to final.

Final wireframes across the inverted-pyramid stages.
Server Resource Analytics — interaction in motion
The interaction in motion.

Impact

Well received — and quietly influential.

  1. Customer reception

    Landed with real server estates.

    The application was well received by customers managing large, messy server estates — the very audience the redesign was tuned for.

  2. Patterns beyond one app

    Adopted across the platform.

    Several interaction patterns from this work were adopted across the broader Oracle Management Cloud platform.

Reflections & design takeaways

Understand the content. The hardest part of this project wasn't the pixels — it was the vocabulary. To design a simple experience, I had to genuinely understand the use cases and the terminology underneath them. There's no shortcut for that.

Collaboration is the fastest path. On problems this technical, the quickest route to the right solution is tight collaboration with PMs, engineers, and domain experts. That partnership was the single biggest reason the experience landed where it did.

Get in touch

Have a complicated problem?
I'd love to hear about it.