← All works

Case study

Dashboard

Turning scattered finance pages into one Payments screen managers can actually use.

Role
Product Designer
Platform
Desktop and Mobile web
Year
2024-Present
Team
Sole designer, partnered with product and engineering
Payments overview screen with funding balances, status tiles, and payout history

CreatorIQ is a creator marketing platform where brands and creators run campaigns end-to-end. The Payments section is where brand managers fund campaigns, approve creator payouts, and monitor transactions.

The section was spread across four disconnected pages with different labels and no shared state. I redesigned it as a single Payments screen that answers the three questions managers ask every day: Are we funded? What is blocking payouts? What should I approve today?

The finance UI was in disarray. Balances were in one place, approvals in another, and payout status somewhere else. Rails that made payments possible were hidden behind settings. Teams started each day collecting data from different sources, digging around to understand their financial picture, and putting the pieces together to determine what action to take.

  • No at-a-glance summary of the current financial picture
  • Blockers buried in UI: taxes/KYC, payment methods, currency mismatches
  • Approvals required context switching and lacked bulk actions
  • Payout tracking spread across multiple tables and terms

I began with a flow audit and a pass through support tickets, then desk calls with finance leads. The friction was more than UX — it was an overall structure that lacked cohesion. I reframed Payments around daily jobs: fund, approve, pay, configure. From there I defined shared statuses and summary patterns, prototyped the end-to-end experience, and instrumented it for a lightweight pilot.

  • One decision at a time
  • Every number is a doorway to a filtered view
  • Separate wallets by currency for clarity
  • Progress and status stay consistent across pages
  • Plain language in tiles, tables, and empty states
Payments overview screen

Overview

Managers land on Overview and see the full financial picture in one screen. Currency balances sit at the top so planning starts with reality. Status tiles surface Awaiting Funding, Scheduled Payouts, and Unpayable Creators, and each tile opens the exact filtered list underneath. Recent Payout History mirrors the columns used elsewhere, so drilling down feels consistent.

Key decisions

  • Separate wallets per currency instead of a single converted total. Managers plan against actual available funds, not approximations.
  • Status tiles as doorways, not dead ends. Every number links to the filtered list behind it, so spotting an issue and acting on it is one click.
  • Add Funds button on the Overview itself. Funding is the most common task after spotting a gap, and hiding it in Settings created unnecessary navigation.
Approvals queue screen

Approvals

Approvals is a focused list designed for speed and accountability. Items are grouped by what managers care about: campaign, method, and currency, with bulk approvals and rejections and inline explanations that write to an audit trail. Smart filters make clearing today's queue a five-minute task instead of a wild goose chase.

Key decisions

  • Grouping by campaign, method, and currency. Managers think in these three dimensions when clearing queues. Grouping by date or amount tested worse because it did not match how they batch their work.
  • Bulk actions with inline explanations. Approvals without an audit trail were a compliance risk. Requiring a separate explanation screen slowed the flow. Inline comments balance both.
  • Smart filters that remember state. Queue clearing is a repeated daily task. Filter state persistence cuts setup time on every return visit.
Payouts screen

Payouts

Payouts unifies Pending, Sent, and Failed payments into a single view. Solutions live next to problems, and filters let finance work a specific rail or currency without distraction. Status language is consistent across the platform, so nobody has to relearn terms between pages.

Key decisions

  • Unified Pending, Sent, and Failed in one view. Splitting these across tabs hid the most important signal: what is broken right now. A single table with status chips surfaces issues without tab-hopping.
  • Actions next to issues. Resend, cancel, and open receipt all live on the row itself. Previously these required opening a detail page, which added friction for a task that should be one click.
  • Consistent status language across the platform. Terms like "Pending" meant different things in different sections. Standardizing removed a learning step between pages.
Creators screen

Creators

Creators gives managers a focused view of payable and payment-ready creators across campaigns, so they can spot missing information and unblock payouts without opening a profile.

Key decisions

  • Payable status surfaced first. Managers audit Creators to unblock payouts. Leading with payable/not-payable status answers the first question in one glance.
  • Grouped by blocker, not by name. Creators with missing info cluster at the top so the most actionable rows get attention first.
  • Request Payment Info inline. The most common next step — nudging a creator for missing details — lives on the row itself instead of inside a creator profile.
  • From scattered finance pages to one Payments section with a clear total picture
  • From surprise blockers to early notifications with actionable solutions
  • From mixed currency totals to explicit per-currency balances and filters
  • From slow approvals to a focused queue with bulk actions and auditability

Currently in internal pilot with finance and ops teams at CreatorIQ. Early signals from testing:

  • Managers report the new Payments screen replaces 3 to 4 pages they used to check daily
  • Per-currency balances removed the most common class of finance support tickets
  • Bulk approvals cut queue-clearing time enough that finance leads flagged it unprompted

Full launch planned after pilot. Quantitative impact to follow once available.