Selected work

Clarity for what comes next.

I help teams navigate unfamiliar product challenges—bringing clarity to complexity, aligning people around a direction, and turning innovation into products that can scale.

Selected projects

Products, systems, and teams I’ve helped move forward.

LionFinancial Merchant operations

A calmer operating system for merchant performance.

LionFinancial Merchant Management System brings the information behind a large merchant network into one connected experience, so teams can focus on decisions instead of wrangling disconnected tools.

LionFinancial merchant management dashboard displayed on a laptop

The challenge

The people responsible for merchant performance are often forced to make important decisions from scattered systems, disconnected reports, and partial information. Simple questions become stressful: Which merchants are healthy? Which need attention? Where are transactions slowing down? What needs to be approved, scheduled, reported, or fixed?

The design response

I designed LMMS to connect accounts, customers, transactions, approvals, scheduled payouts, and reporting in a clearer operating environment. The experience streamlines the work around the data, helping teams understand performance and act without reconstructing the story across multiple platforms.

1 / 6

LionFinancial merchant network dashboard

The merchant network as an operating view

A merchant list should do more than act as a directory. This view brings status, services, volume, recent activity, risk, approvals, onboarding, and network health together so platform teams can identify which businesses are growing and which need intervention without opening every record.

Representative outcome 30% greater efficiency in merchant review by making risk, activity, adoption, and volume visible at the list level.

LionFinancial payment methods and services interface

Service configuration meets adoption

Payment methods affect cash flow, friction, and revenue opportunity. I paired configuration with adoption so teams can see what is enabled, how many merchants use it, the volume and fees it drives, and where setup requests are waiting—shifting the question from “Is it on?” to “Is it creating value?”

Representative outcome A 15–20% improvement in the ease of driving service adoption, visibility, and conversion.

LionFinancial customer management view

Customer behavior as a merchant-health signal

Volume alone does not explain business health. Active customers, repeat purchase rate, payment preferences, lifetime value, support issues, and health scores reveal whether a merchant is retaining customers or beginning to lose momentum—and give platform teams a stronger basis for advising them.

Representative outcome A projected 35–60% improvement in merchant advisory conversations through clearer customer and payment-behavior signals.

LionFinancial payout scheduling workflow

Predictable future money movement

I reframed scheduled payments as a financial-operations tool supporting vendor payouts, platform fees, settlements, lease payments, payroll advances, insurance premiums, and merchant disbursements. Upcoming, successful, and failed activity remains visible alongside reusable templates because uncertainty is the enemy when users are responsible for money movement.

LionFinancial reports interface

Reporting without rebuilding the work

A report library, scheduled reports, saved views, quick exports, ownership, dates, and categories turn historical reporting into reusable operational knowledge. Teams can generate leadership summaries, monitor merchants and payouts, export what they need, and move on without repeatedly reconstructing the same analysis.

Representative outcome Approximately 80% less report-preparation time.

LionFinancial transaction management interface

From audit trail to pattern recognition

The transaction table covers payments, refunds, disputes, payouts, settlement timing, fees, methods, and status across merchants. Supporting views expose mix, volume by time of day, and settlement aging so users can move from “What happened?” to “What does this mean?” without exporting the data first.

Representative outcome A projected 50–75% reduction in manual transaction research and export dependency, depending on the business and user.

Global Payments Enterprise design system

A north star for product design across a global ecosystem.

All roads intersect at Vega—a shared foundation for software product design across three continents, numerous countries, and distributed product, design, and engineering teams.

Visit Vega
Vega enterprise design system shown across product interfaces

The opportunity

Our product ecosystem needed a stronger shared foundation—one that could make products more consistent, accessible, and thoughtfully designed without slowing teams down or preventing them from solving for their own product needs.

My leadership

As design system lead and product design manager, I kicked off and led Vega’s creation and evolution across reusable components, accessibility standards, design tokens, documentation, governance, and Figma-to-code alignment. I partnered closely with engineering to reduce rework and help teams build better software with greater speed and confidence.

1 / 6

Vega design system foundations and interface components

A foundation teams can share

Vega establishes common visual and interaction foundations so separate products can feel like parts of one ecosystem without erasing their individual requirements.

Vega component library and design guidance

Components with intent

Reusable components pair visual consistency with behavioral guidance, helping designers and engineers understand not only what to use, but why and when to use it.

Vega reusable product patterns

Patterns for real product work

The system moves beyond isolated UI pieces into repeatable product patterns, giving teams a faster path through common workflows and complex states.

Vega accessibility and interaction standards

Accessibility built into the decision

Standards and usage guidance bring accessibility into component selection and interaction design from the beginning instead of treating it as a final audit.

Vega design tokens and implementation details

A durable bridge to code

Shared tokens and aligned naming reduce translation between Figma and engineering, protecting decisions as components move from design into production.

Vega documentation and component guidance

Documentation that supports adoption

Clear examples, governance, and contribution guidance make the system usable across distributed teams and give it a structure that can evolve with the organization.

AvenaPay Disputes management

Turning dispute complexity into actionable clarity.

A representative disputes analytics platform designed to help merchants manage high-volume chargebacks, understand what changed, identify what needs attention, and find the strongest recovery opportunities.

AvenaPay disputes management experience across desktop and mobile

The challenge

Merchants struggled to understand which disputes were worth defending, why cases were being lost, and how to recover more funds without relying on manual reports from support or client services. Complex dispute data needed to become easier to understand, filter, and act on.

My approach

I designed the dashboard strategy, information architecture, dispute-health KPIs, probability scoring, filtered queue shortcuts, case detail views, alerts, custom reports, and natural-language analytics. The interface, branding, data, and identifying details were recreated to protect confidential work while preserving the product’s complexity and design strategy.

1 / 6

AvenaPay outcomes dashboard with case metrics and trend visualization

Lead with outcomes

The primary dashboard reframes disputes around recovery, loss, and performance—giving merchants an immediate understanding of what changed and where attention matters.

AvenaPay dispute volume dashboard

Volume with meaningful context

Trends and comparisons help teams distinguish routine fluctuations from signals that require investigation, keeping raw case volume connected to business impact.

AvenaPay case detail workflow

Evidence where decisions happen

The case view brings status, value, evidence, timing, and recommended action into one workspace so merchants can move from analysis into resolution with confidence.

AvenaPay alerts and notifications interface

Attention, carefully directed

Alerts prioritize changes, deadlines, and high-value opportunities without turning every update into noise, helping teams intervene at the right moment.

AvenaPay executive disputes report

From operations to executive narrative

Custom reporting translates case activity into an outcome-oriented view leaders can use to understand performance, risk, and recovery over time.

AvenaPay AI-assisted case analysis interface

Natural-language analysis

A conversational layer lets users investigate their dispute data in familiar language, shortening the path from an emerging question to a useful answer.

Paladin UX framing kit

A shared language for solving complex product problems.

A reusable wireframing system that helps teams explore structure, workflow, content priorities, accessibility, and edge cases before visual polish gets in the way.

Paladin wireframing kit showing reusable product patterns

Why it was needed

Early product work gets messy when teams jump into high-fidelity design before understanding user needs, information hierarchy, workflow logic, interaction states, and edge cases. Paladin was designed to let that confusion melt away and bring the UX problem into focus.

The system

I created reusable, accessibility-minded components, established patterns, and annotation-friendly layouts for complex tables, reporting, payment workflows, and data-heavy products. The kit helps teams align earlier, uncover challenges sooner, reduce rework, and move more confidently into detailed design.

1 / 6

Paladin dashboard and data visualization wireframing components

Structure before styling

Dashboard and visualization frames help teams establish hierarchy, comparison, and decision priority before color or brand details influence the conversation.

Paladin table and data wireframing components

Dense data with a clear job

Table patterns account for scanning, filtering, bulk actions, pagination, status, and empty states so teams can solve the workflow around the data—not merely draw rows.

Paladin workflow and payment form wireframing components

Make consequential flows discussable

Payment and workflow frames expose steps, validation, decision points, and recovery states early, when changing the experience is still inexpensive.

Paladin reporting wireframing patterns

Reporting as a reusable pattern

Flexible reporting structures help teams test what should be summarized, compared, saved, scheduled, and exported before committing to a final interface.

Paladin buttons and toggles wireframing components

Small controls, explicit behavior

Foundational controls include interaction and state considerations so accessibility and behavioral consistency enter the discussion alongside layout.

Paladin ecommerce wireframing patterns

Breadth without prescription

Commerce patterns demonstrate how the kit adapts to distinct product domains while remaining neutral enough for teams to explore their own content and business rules.

LedgerFlow Payments and invoicing

One understandable flow from invoice to payment.

A modern fintech experience for businesses that need a clearer, calmer way to manage invoices, payments, customers, reminders, reporting, and mobile collection.

LedgerFlow invoicing, payment, and collections product overview

The goal

Getting paid should feel organized, trustworthy, and easy to act on—not scattered across disconnected tools or buried in confusing financial workflows. LedgerFlow needed to preserve the depth businesses rely on while making everyday financial work feel manageable.

My approach

I designed the core desktop and mobile flows, including the dashboard, reporting, invoice creation, payment links, customer billing, reminders, and payment collection. I focused on hierarchy, clarity, status visibility, and reusable patterns so users could quickly see what needed attention, what was handled, and where money was moving.

1 / 6

LedgerFlow dashboard and financial workflow overview

An actionable financial overview

The dashboard prioritizes status, movement, and exceptions so users can understand what needs attention before entering a detailed workflow.

LedgerFlow reporting experience

Reporting connected to the work

Financial summaries remain close to the underlying activity, helping businesses understand performance without moving between disconnected reporting tools.

LedgerFlow invoice management interface

Invoices organized by state

Clear status, value, customer, and due-date signals let users distinguish what is moving normally from what needs a reminder or intervention.

LedgerFlow invoice creation workflow

Create with confidence

The invoice flow uses progressive structure and immediate context to make a detailed financial task feel guided without removing the control businesses need.

LedgerFlow payment and collections interface

Collections without the chaos

Payment links, reminders, and collection activity share a common language, making the next action legible while preserving a complete record of what has happened.

LedgerFlow mobile payment experience

The same clarity on mobile

The mobile experience focuses the product around quick checks and high-value actions, extending the system without forcing a desktop interface into a smaller frame.

Northstar Commerce Conversion strategy

A clearer path from first impression to confident conversion.

A conversion-focused commerce experience that helps small business owners understand the offer, compare payment products and rates, and choose the right setup for how they sell.

Northstar Commerce landing page displayed on a transparent desktop screen

The opportunity

The page needed to feel more approachable than a typical fintech experience while still communicating legitimacy, trust, and business value. Product choices and competitive rates had to become easier to evaluate without making the experience feel pushy or overbuilt.

My approach

I designed the landing-page structure, visual direction, product presentation, CTA strategy, trust-building sections, responsive direction, and supporting brand elements. Color, spacing, and progressive information reduce cognitive load while guiding visitors through a clear conversion path.

1 / 6

Northstar Commerce landing-page introduction

Make the offer immediately legible

The opening establishes audience, value, and next action quickly, using approachable product presentation to make a fintech decision feel less intimidating.

Northstar Commerce business benefits section

Translate features into business value

The narrative moves from the product promise into recognizable small-business needs, helping visitors see how the platform fits the way they already sell.

Northstar Commerce product comparison content

Make comparison feel manageable

Product options are structured around meaningful differences so visitors can evaluate fit without decoding a dense matrix or leaving the conversion path.

Northstar Commerce rates and pricing content

Use transparency to build trust

Pricing and rates are introduced with enough context to support evaluation, balancing clarity with the nuance required for different business models.

Northstar Commerce trust and support content

Reduce risk before asking for commitment

Support, proof, and trust signals answer the doubts that naturally appear late in consideration, strengthening confidence without relying on aggressive persuasion.

Northstar Commerce final conversion section

End with a clear next step

The final invitation resolves the story into a focused action, preserving the page’s friendly tone while making the path forward unmistakable.

The throughline

Every challenge is different. Progress starts with clarity.

Across platforms, systems, and teams, my role is consistent: make complexity understandable, create the structure people need to move together, and turn ambitious product decisions into work that can scale.

What comes next

If your team is entering unfamiliar product territory, let’s create a clear path forward together.

See more in Figma Start a conversation