Silvia Gomera Boné

Redefining Flows


Analyzing Data-Driven Personas


— PROJECT NAME

Analyzing Data-Driven Personas: Redefining Flows


— ROLE

UX Designer


— DATE

June 2025

Led Data-Driven Persona research that detected refund/chargeback ratio discrepancies (caused by incorrect family unit counting), driving the redefinition of the service request Flow from individual to family unit.

Executive Summary & Problem


Business Problem: A UX Research for data driven Personas, detected that more than 20% of the data base records were from minors who obviously weren’t the users who interacted with the system. Discrepancies in key financial metrics (refund and chargeback ratios) were uncovered. The figures did not reflect the reality of the business, which made decision-making difficult.


UX Objective: Apply research to detect the root cause of the KPI discrepancy and redefine the user flow to reflect actual user behavior.


Key Result (Strategic Impact): Redefinition of the application flow from individual to family unit, achieving accurate business metrics and improving the experience for the family user segment.

Research and Discovery


Key Methods: UX Research, Data-Driven Persona Research, Database Analysis , and cross-referencing data with financial reports.


Critical Finding: Persona research revealed that 20% of records corresponded to non-user family members (e.g., children), meaning that a single family transaction resulted in multiple individual records.


Problem Conclusion: If a family requested 5 services and asked for 1 refund, the system counted 5 refunds, inflating the refund ratio and distorting the health of the business.


Inital Flow: request by individual

Requirements and Flow Definition



Strategic Requirement: Users needed to be able to make services requirements for multiple family members. So, the system had to stop treating users as isolated individuals and recognize the “family unit” as the unit of service and billing.


Flow Definition: Creation of a new user flow that would allow the primary applicant (parent) to manage and add family members before finalizing the service request.


Decision: Redefinition of the service/transaction at the family unit level rather than the individual level.

New Flow: request by family unit

Design & Prototyping


Design Deliverables: Detailed user flow maps for the new process. Low- or medium-fidelity wireframes for the new family management interface and the adapted application form.


Design Approach: Ensure that the new information architecture was intuitive for the primary user (head of household).

Wireframing for the new flow by family unit

Outcomes and metrics

Business Impact: Refund and chargeback diminished to acceptable ranges, providing management with reliable metrics for financial planning.


User Experience Impact: Friction was eliminated for the family segment (which represented a significant portion of the database), simplifying the management of multiple requests under a single account.