Retention fell after a redesign of personal finance dashboard. Investigate the issue

Problem Statement Description

A personal finance dashboard was recently redesigned to help users better understand their accounts, spending patterns, budgets, balances, and financial health. After launch, retention declined. Your task is to investigate the drop as a Product Manager leading a root-cause analysis.

Assume this dashboard is used in a high-trust financial environment where users need confidence that their information is accurate, easy to interpret, and actionable. Support agents are also an important segment because they rely on the dashboard view and related user context to resolve customer questions about transactions, budgets, cash flow, or account insights.

You should frame the retention anomaly clearly, determine whether the redesign caused the decline, and identify where in the user journey the issue may be occurring. The focus is not to propose a full redesign, but to structure the investigation, isolate likely causes, validate them with data and qualitative evidence, and recommend immediate mitigation and longer-term prevention steps.

The experience should consider:

- How retention is defined, including the relevant time window, denominator, and comparison baseline before and after the redesign.

- Segmentation by user type, account maturity, financial behavior, platform, geography, accessibility needs, and support-agent-assisted users.

- Funnel and behavioral changes across key dashboard workflows such as viewing balances, checking transactions, reviewing budgets, understanding insights, and taking follow-up actions.

- Instrumentation checks to confirm whether the drop is real and not caused by tracking changes, event-name changes, logging gaps, or cohort misclassification after the redesign.

- Hypotheses related to usability, trust, information architecture, latency, data accuracy, missing features, visual hierarchy, or changes in user confidence.

- Evidence sources including analytics, session replays, customer support tickets, agent feedback, app reviews, surveys, and experiment or rollout data.

- Short-term mitigation options such as rollback, feature flags, targeted fixes, user education, or support-agent playbooks.

- Prevention mechanisms such as launch guardrails, retention monitoring, staged rollouts, QA checks, and post-launch user sentiment tracking.

The goal is to demonstrate a structured RCA approach that separates correlation from causation, protects user trust in a sensitive financial product, and leads to a clear decision on what to investigate, fix, monitor, or reverse.