← Back PactFi Funds Flow case study
Close

PACTFI · PRODUCT IMPROVEMENT · 16-DAY DELIVERY

Reducing Funds Flow Setup
from eight steps to five.

I turned one prioritized usability issue into a focused research, redesign, and validation cycle for a live private-credit platform.

  • Lead product design
  • Complex workflows
  • Product improvement
  • Interview-gated
Role
Lead Product Designer & UX Researcher
Product
Private-credit platform for deal operations
Scope
Research, redesign, validation, and delivery alignment
Reconstructed PactFi funds flow setup interface with a deal workspace, flow sequence, and setup details panel

Reconstructed interface shown for public-safe storytelling. Product names and visual details are adapted.

// AT A GLANCE

One focused redesign. Clear evidence of ownership.

I owned the Funds Flow Setup investigation and carried it from problem framing through redesign, validation, and delivery alignment.

01

8 → 5 steps

The shipped flow kept every required action inside one continuous setup sequence.

SHIPPED WORKFLOW
02

16 days

A focused cycle from issue framing and behavioral review through validation and delivery alignment.

END-TO-END OWNERSHIP
03

5 sessions

Individually moderated with partners from PM, Business Development, and Customer Support.

INTERNAL DOMAIN EXPERTS

// FROM INTAKE TO FOCUS

Delivery built momentum. Research was needed to sustain growth.

As client adoption, workflows, and operational complexity grew, BD and Customer Support consolidated eight important issues using client feedback and information from the support tool. I helped the six-person design team turn that intake into a coordinated research cycle without stopping active delivery.

  1. 01
    Platform intakeBD + Customer Support

    Eight separate client-reported issues across the product, not eight reports of one problem.

    INPUT
  2. 02
    Design-team prioritizationSix-person design team

    I helped prioritize six investigations, with one designer responsible for each selected issue.

    SCOPE
  3. 03
    My ownershipShared research framework

    I created the common research framework and owned Funds Flow Setup through the shipped redesign.

    DELIVERY

// INVESTIGATE → REDESIGN

Behavioral evidence narrowed the problem. Human review established what mattered.

I used Ask Galileo’s natural-language chat to generate focused charts, funnels, path analyses, and session playlists. I reviewed the resulting sessions directly, mapped the complete task, and redesigned the flow around continuity rather than isolated screens.

PactFi Transaction Review screen with an operations sidebar, work item queue, statuses, and a selected item inspector

// SHIPPED AND VALIDATED

I kept supporting work inside the primary task.

The shipped redesign reduced Funds Flow Setup from eight steps to five. Supporting entity work stayed inside the active Deal, existing entity information could be reused, and every required action remained in one continuous flow.

Reconstructed Funds Flow setup details showing the continuous flow, validation summaries, and setup inspector

Reconstructed details · five individual internal sessions · directional outcomes only · no externally verifiable baseline.

01

Five individual sessions

I moderated five separate sessions with partners from PM, Business Development, and Customer Support, each completing the full task individually.

INTERNAL DOMAIN EXPERTS
02

Task-level validation

I tested the complete sequence as one workflow, not a collection of screens, so continuity and return paths stayed visible.

END-TO-END TASK
03

Early signals after release

Post-release monitoring suggested smoother task completion, fewer support questions, and fewer errors or dead clicks. The short measurement window made these directional signals, not proof of causality.

DIRECTIONAL · NO CONTROLLED BASELINE

// REFLECTION

From reactive research to continuous product health

With more time and direct customer access, I would make the same loop more proactive, continuous, and closer to end users.

  1. 01
    Instrument critical journeys

    Track completion, friction, errors, and performance as ongoing product-health signals.

    Measure
  2. 02
    Create direct customer access

    Maintain a standing participant panel or design-partner program.

    Access
  3. 03
    Add continuous research capacity

    Pair designers’ end-to-end delivery with dedicated research support.

    Capacity
  4. 04
    Run hypothesis-driven experiments

    Use A/B testing selectively, only when it is the right method for the question.

    Experiment
  5. 05
    Automate product-health triage

    Let AI flag anomalies, with people reviewing context and deciding what matters.

    Triage