My Work

Design Principles

About Me

At a Glance

At a Glance

Problem: Every invoice was treated as high risk, creating manual effort, delays, and operational bottlenecks

Role: Senior UX Designer

Scope: Internal enterprise tooling, auditing workflows, risk evaluation logic

Outcome: Reduced manual review, faster funding decisions, and improved operational efficiency without increasing financial risk

Pink Flower
Pink Flower

Timeline

Timeline

2025-Present

2025-Present

Tools

Tools

Figma, Lucid, Jira

Figma, Lucid, Jira

What This System Is Responsible For

This system supports invoice auditing for funding decisions, helping teams decide when manual review is necessary and when invoices can safely move forward automatically.

Before this work, auditors treated nearly every invoice as high risk. While this reduced exposure, it created significant operational drag and slowed funding decisions across the business.

Why Manual Review Was No Longer Sustainable

Invoice volume continued to grow, but the auditing process didn’t evolve with it. Auditors spent time reviewing invoices that posed little to no risk, leaving less capacity for cases that actually required investigation.

What worked at lower volume became increasingly difficult to sustain as the business scaled.

When Everything Became High Risk

By default, every invoice enters the same review path, regardless of context. Invoices tied to long-standing relationships or predictable patterns were handled with the same scrutiny as true edge cases. Over time, auditing shifted from risk management to process maintenance.

Reframing Automation Around Confidence

Rather than asking which invoices could be fully automated, we reframed the problem around risk confidence. Automation wasn’t about removing people from the process. It was about identifying when confidence was high enough to proceed without review, and when uncertainty justified human intervention.

Letting Risk Signals Do the Heavy Lifting

Letting Risk Signals Do the Heavy Lifting

This work required moving from a one-size-fits-all review model to a selective, signal-driven approach. Early discovery focused on how auditors assess risk today and which factors consistently lead to meaningful intervention. Grounding the system in existing judgment patterns allowed automation without introducing unfamiliar logic or reducing trust. The goal was not to remove oversight, but to apply it more intentionally where it matters most.

This work required moving from a one-size-fits-all review model to a selective, signal-driven approach. Early discovery focused on how auditors assess risk today and which factors consistently lead to meaningful intervention. Grounding the system in existing judgment patterns allowed automation without introducing unfamiliar logic or reducing trust. The goal was not to remove oversight, but to apply it more intentionally where it matters most.

Defining meaningful risk signals clarified where automation could safely replace routine review.

Automation is paired with visibility and clear intervention paths to maintain user confidence.

Automation is paired with visibility and clear intervention paths to maintain user confidence.

Making Automated Decisions Understandable and Trustworthy

Making Automated Decisions Understandable and Trustworthy

The workflow was designed to make automated decisions clear and defensible. Instead of simply advancing invoices, the experience surfaces why an invoice qualifies for automatic funding while preserving clear escalation paths. Each interaction supports a single, focused task with relevant context close at hand. This reduces cognitive load while keeping manual intervention fast and accessible.

The workflow was designed to make automated decisions clear and defensible. Instead of simply advancing invoices, the experience surfaces why an invoice qualifies for automatic funding while preserving clear escalation paths. Each interaction supports a single, focused task with relevant context close at hand. This reduces cognitive load while keeping manual intervention fast and accessible.

Choosing Clarity Over Coverage

Early concepts explored more configurability than the first release could support. Working closely with Product and Engineering, the design was narrowed to prioritize clarity, auditability, and delivery feasibility. Non-essential features were documented for future iterations rather than forced into the initial build. This ensured a strong foundation without unnecessary complexity.

Choosing Clarity Over Coverage

Early concepts explored more configurability than the first release could support. Working closely with Product and Engineering, the design was narrowed to prioritize clarity, auditability, and delivery feasibility. Non-essential features were documented for future iterations rather than forced into the initial build. This ensured a strong foundation without unnecessary complexity.

Deliberate tradeoffs balanced flexibility, clarity, and delivery constraints.

What Changed in Practice

After launch, the impact was clear. Manual reviews dropped significantly for low-risk invoices, funding decisions moved faster without increasing exposure, and auditors were able to focus on genuinely high-risk cases.

Reflections & Impact

This work changed how the organization approached auditing. By shifting from blanket review to confidence-based evaluation, teams were able to move faster without sacrificing financial control.

The biggest impact wasn’t just efficiency; it was clarity.

Additional Design Considerations

Balancing Automation with Trust

Automating a financial decision requires more than confidence in the data, it requires confidence from the people responsible for the outcome. A major focus of this project was ensuring users could understand why an invoice moved forward automatically and when they should step in. By making risk signals visible and escalation paths clear, the system reinforces trust rather than replacing judgment.

Balancing Automation with Trust

Automating a financial decision requires more than confidence in the data, it requires confidence from the people responsible for the outcome. A major focus of this project was ensuring users could understand why an invoice moved forward automatically and when they should step in. By making risk signals visible and escalation paths clear, the system reinforces trust rather than replacing judgment.

Balancing Automation with Trust

Automating a financial decision requires more than confidence in the data, it requires confidence from the people responsible for the outcome. A major focus of this project was ensuring users could understand why an invoice moved forward automatically and when they should step in. By making risk signals visible and escalation paths clear, the system reinforces trust rather than replacing judgment.

Balancing Automation with Trust

Designing for Edge Cases Without Slowing the Happy Path

Designing for Edge Cases Without Slowing the Happy Path

Designing for Edge Cases Without Slowing the Happy Path

Designing for Edge Cases Without Slowing the Happy Path

Scaling a Shared Internal Platform

Scaling a Shared Internal Platform

Scaling a Shared Internal Platform

Scaling a Shared Internal Platform

The secondary verification workflow is triggered when additional review is required beyond the initial audit

Selecting a secondary workflow from the initial stage to progress the invoice