My Work

Design Principles

About Me

At a Glance

Problem: Design decisions often stall when requirements are unclear, stakeholders disagree, or constraints conflict.

Role: Senior UX Designer, responsible for making and guiding decisions under ambiguity.

Scope: Decision making, tradeoffs, collaboration, and alignment across complex products and internal systems.

Outcome: A clear set of principles that help teams move forward responsibly when the right answer isn’t obvious.

Yellow Flower

Timeline

Timeline

Summer 2024

Summer 2024

Tools

Tools

Figma, Figjam, Jira,

Figma, Figjam, Jira,

Why This System Mattered

Monthly rate adjustments were a core part of the business, but the system supporting them hadn’t kept pace with scale.

As volume increased, updates became harder to manage, errors were more costly, and operational risk grew. What had once been manageable became a bottleneck.

When the Tools Became the Bottleneck

The system technically worked, but only through workarounds and institutional knowledge.

There was no easy way to track rate changes, support historical pricing, or validate complex adjustments. As a result, updates were slow, fragile, and increasingly risky.

What the System Needed to Do

Users needed to manage thousands of rate tables quickly and confidently. Editing, filtering, and flexibility were critical to making that possible.

Understanding How the Work Actually Happens

I spent time with the team to understand how they actually manage rates day to day. Their workflow wasn’t linear, and the system needed to reflect that.


What Changed in Practice

What Changed in Practice

Updates became faster and more reliable, giving the team confidence in a high-impact system. The workflow now scales with the business instead of slowing it down.

75%

reduction in time spent on monthly rate updates

reduction in time spent on monthly rate updates

reduction in time spent on monthly rate updates

200+

hours saved every month by eliminating manual processes through creating simplified workflow

hours saved every month by eliminating manual processes through creating simplified workflow

hours saved every month by eliminating manual processes through creating simplified workflow

0 Hours

Multiple previously manual processes no longer require any manual intervention at all

Multiple previously manual processes no longer require any manual intervention at all

Multiple previously manual processes no longer require any manual intervention at all

Reshaping the Path Through Complexity

Reshaping the Path Through Complexity

The workflow needed to reduce friction without forcing rigid paths. The final structure allows users to move between adding and editing without losing context.

The workflow needed to reduce friction without forcing rigid paths. The final structure allows users to move between adding and editing without losing context.

Finding the Right Structure

Finding the Right Structure

I explored different layout directions to handle dense data without overwhelming users. This helped us find a balance between clarity and flexibility early.

I explored different layout directions to handle dense data without overwhelming users. This helped us find a balance between clarity and flexibility early.

A System Built for Scale and Precision

The final design focuses on clarity, hierarchy, and staying oriented through complex data. Consistent patterns make the system easier to use at scale.

A System Built for Scale and Precision

The final design focuses on clarity, hierarchy, and staying oriented through complex data. Consistent patterns make the system easier to use at scale.

Real-World Impact

The system significantly reduced time spent on monthly updates and removed several manual processes entirely. It became a reliable foundation for how the business manages pricing.

What This Project Reinforced

Designing for complex systems starts with understanding how work actually happens. Clear structure makes even dense workflows usable at scale.

Design Considerations

Designing for Specialized Users

This system is used by a small, highly specialized team responsible for one of the most sensitive operational processes in the company. The interface needed to support speed and accuracy without relying on training or tribal knowledge. Design decisions consistently favored clarity, predictable behavior, and guardrails that reduced the chance of costly mistakes. Rather than simplifying the problem, the goal was to make complexity manageable and visible in the right moments.

Designing for Specialized Users

Balancing Flexibility with Control