Skip to main content

SENIOR PRODUCT DESIGNER // REGULATED FINANCE

Clarity where a wrong click costs money.

High risk, many roles, strict rules: I make the path through it clear and put every decision on record. I prototype in code with AI and check the output.

TERMINAL 01 // highlights

about 8% to less than 1%

ORDERS RETURNED FOR ERRORS AFTER THE SUBSCRIPTION WORKFLOW REDESIGN

DESIGN THROUGHPUTUP about 50%

ADMIN REVIEWDOWN about 30%

SUPPORT CALLSDOWN about 4X

  • MULTI-ROLE WORKFLOWS
  • B2B FINTECH
  • USER RESEARCH
  • RAPID HI-FI PROTOTYPING
  • CODED PROTOTYPES
  • DESIGN SYSTEMS
  • STAKEHOLDER MANAGEMENT
  • DESIGN OPS
  • ACCESSIBILITY

[01] CASES

The decisions behind the numbers.

  1. 01ALTERNATIVE INVESTMENTS / B2B / WORKFLOW DESIGN / COMPLIANCE

    From about 8% to under 1%: redesigning a multi-role subscription workflow

    Subscriptions list showing each order's status, with a progress tracker on the open order.

    CONTEXT

    One review action asked for a small fix. Another erased every signature already collected. Nothing made them look different.

    DECISION

    Three releases made the difference explicit, surfaced status in the list, and named what was missing before it blocked.

    RESULT

    • less than 1%

      ORDERS RETURNED FOR ERRORS, FROM about 8%

    • about +20%

      USER ADOPTION IN A YEAR

    • about 4x

      FEWER SUPPORT CALLS

    VIEW CASE STUDY

    9 MIN READ · PASSWORD

  2. 02ALTERNATIVE INVESTMENTS / MOBILE / SPEC / COMPLIANCE

    Investors couldn't see where their money stood: a mobile spec for status and alerts

    Mobile dashboard with an overdue capital call banner and a list of required actions, each with its due date.
    Account page with an overdue capital call alert, account totals, and tabs for investments, subscriptions and documents.
    Pending capital call notice with the amount due, its due date, and Acknowledge and Manage buttons.

    CONTEXT

    Investors on an alternative-investments platform couldn't see the status of their account or their positions, and weren't told when something changed.

    DECISION

    This self-initiated spec puts status and alerts on mobile. Anything that moves money stays on desktop behind re-authentication, so a lost phone can't move it.

    RESULT

    • 21

      SCREENS SPECIFIED

    • 9

      EDGE CASES DEFINED

    • 4

      MOBILE-NATIVE JOBS

    VIEW CASE STUDY

    6 MIN READ · PASSWORD

  3. 03AI DESIGN-BUILD / DESIGN SYSTEM / HYPOTHESIS TESTING

    Abyssal Pioneer: live in 3 days, hypothesis disproved in 1

    A scene from Abyssal Pioneer: an engineering manager's message beside his portrait, with the scene's steps listed on the left.

    CONTEXT

    The first launch was a deep-ocean exploration concept site, shipped over a weekend to test for interest. A few months live brought zero calls and zero outreach.

    DECISION

    Keep the rails, change the product. I audited and extended the design system and put a long-held idea on the same codebase: a game that immerses non-native English speakers in a US corporate office. It went live in three days. Real users disproved the hypothesis within a day: AI tools and a short $10 online course already do the job better.

    RESULT

    • 3

      DAYS TO GO LIVE

    • 6

      SCENES

    • 1

      DAY TO DISPROVE THE HYPOTHESIS

[02] ABOUT

From buildings to flows

Both break the same way.

Anton Lebedev with swept-back hair in a dark jacket and open-collar shirt, resting his chin on his hand.
ANTON LEBEDEVSENIOR PRODUCT DESIGNER // WILMINGTON, DE

Ten years in construction taught me to get owners, engineers and inspectors working from one plan, and to turn building codes into steps contractors could execute. I moved into UX in 2020, with a PhD in economics behind me.

From 2022 I led design at an alternative-investments startup: a team of three, design ops for 10 to 15 tickets a month, and a design system rebuilt to match engineering's components. Design throughput rose about 50%.

My job is done when the system runs without my help.

[03] CONTACT

Complex flows, real stakes? Let’s talk.

Give me the workflow everyone avoids: the most roles, the strictest rules, the most support tickets. I'll untangle it.