Dashboard

Evolving the developer dashboard into a lifecycle-driven customer platform

Mature customer Overview showing metrics, compliance actions, workflow queues, product adoption opportunities, and operational insights

Problem

The Dashboard began as a transactional utility. Developers came to grab API keys, check logs, submit support tickets, and leave.

As Plaid expanded beyond read-only API products, the Dashboard became the primary surface customers used to onboard, launch, operate, and grow their businesses. The experience had not evolved alongside that shift, requiring customers to navigate a growing platform with little guidance.

The Dashboard Home before the redesign: generic utility cards and a support ticket table, unchanged as the platform scaled

Role & scope

I led design for the Dashboard, partnering with product and engineering to shape onboarding, launch, operations, and growth experiences across the platform. Over a multi-year effort, I helped establish the long-term vision for the Dashboard as a unified platform for customer-facing and partner-facing experiences.

Approach

To make the Dashboard useful to customers at every stage of their journey, I led a cross-functional effort to map the lifecycle from acquisition through onboarding, launch, ongoing operations, and growth, creating a shared model for customer needs at each stage.

Customer journey map spanning Acquire through Grow and Retain, showing Dashboard's role across the full customer lifecycle

This work revealed a larger challenge: teams were optimizing for individual products rather than the overall customer experience. The goal was to provide a self-serve experience that would help customers succeed across their journey. However, with very limited front-end engineering capacity, design had to be strategic about where it invested, favoring reusable patterns that could be built once and scale.

Adapting Home to the lifecycle

Home was a priority because it was the one surface customers returned to at every stage of their journey. The same page had to open as a first-time experience, guide onboarding and compliance, surface implementation tasks through Launch Center, and mature into an operational hub for established customers. Rather than build a separate Home for each stage, we made it respond to the customer’s position in their lifecycle, surfacing the guidance, insights, and actions relevant to that moment.

Launch Center guiding a new customer through production-readiness tasks, an early lifecycle-driven experience

Building a scalable framework

A surface that adapts to every stage runs the risk of becoming a collection of bespoke experiences built independently by different teams. To prevent that, I worked with my team to establish a modular widget framework. Operational product tasks, key metrics, and communications could be surfaced on Home without custom builds, composing into an experience shaped to a customer’s stage and the products they used. For example, an established customer using Plaid’s Payment solution saw a Home with ACH Transfer KPIs in addition to core conversion metrics.

Widget taxonomy for the new Home: categories spanning overview metrics, product-specific metrics, communications, platform features, and task queues

A customer Home composed from the framework, tuned to the products they used and their stage in the journey

Serving different user types

This modular foundation helped scale the Dashboard beyond customer-facing experiences. Open Finance and Bank Intelligence experiences, built for data partners, reused the shared patterns to display data-network insights. And the exchange ran both ways: data visualization widgets built for partner surfaces fed back into customer experiences, so investment in one area compounded across the others.

The widget framework extended to a data-partner surface, reusing shared patterns for an entirely different user

Bank Intelligence, a distinct Open Finance product built on the same modular Home foundation

Outcome

Dashboard evolved from a collection of developer utilities into Plaid’s primary self-serve customer platform. The lifecycle-driven experiences improved engagement across the journey: first-time feature engagement increased 119%, launch rates increased 32%, re-engagement increased 350%, and support tickets dropped by roughly 41%.

It became the surface where customers onboarded, launched, operated, and grew their use of Plaid, directly driving substantial growth in Plaid’s product-led revenue as customers adopted and expanded on their own.