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 a handful of products, Dashboard quietly became the primary surface customers used to onboard, launch, operate, and grow their businesses. The experience had not evolved alongside that shift. Customers were expected to navigate a growing platform largely on their own, with little guidance, context, or visibility into what mattered next.
Role & scope
I led design for Dashboard as its design lead, partnering with product and engineering to shape onboarding, launch, operational, and growth experiences across the platform. Over a multi-year effort, I helped establish the long-term vision for Dashboard as a customer platform rather than a collection of product-specific tools. My scope spanned customer-facing and partner-facing experiences, including onboarding, production access, launch, operational workflows, Home experiences, and platform foundations that enabled future expansion.
Approach
Rather than organize Dashboard around products and internal teams, I reframed it around the customer journey. Customers did not experience Plaid as a collection of APIs or product lines. They experienced it through a sequence of stages: signing up, testing, launching, operating, and eventually expanding into new products.
I led a cross-functional effort to map the lifecycle from acquisition through onboarding, launch, ongoing operations, and growth, creating a shared model for understanding customer needs at each stage. That work revealed a larger challenge: teams were often optimizing for individual products rather than the overall customer experience. To create consistency, I established a set of principles that guided Dashboard investments: prioritize relevance and simplicity, design for fast and intentional workflows, turn information into actionable insight, and create scalable patterns that new experiences could adopt. The lifecycle model and principles became a shared framework for prioritizing work across Dashboard.
Building lifecycle-driven experiences
Using the lifecycle model, we redesigned key moments throughout the customer journey. For new customers, Dashboard provided onboarding guidance and production-readiness workflows. For customers preparing to launch, we introduced Launch Center, helping teams complete implementation tasks and reach production faster. As customers matured, Dashboard shifted from guidance and setup toward operational insights, workflow management, compliance actions, troubleshooting, and product expansion opportunities. Home became a dynamic surface that adapted to a customer’s stage, products, and goals rather than serving the same static experience to everyone.
Creating a scalable foundation
As Plaid expanded, Home risked becoming a collection of bespoke experiences built independently by different teams. To avoid this, I worked with my team to establish a modular widget framework that allowed new products, workflows, and insights to integrate into Dashboard through shared patterns rather than custom homepage implementations. The framework supported multiple categories of experience, including lifecycle guidance, operational insights, workflow queues, compliance requirements, product recommendations, and platform communications. This allowed Home to evolve continuously while maintaining a coherent experience.
Scaling beyond the original use case
The widget framework became a foundation for future Dashboard investments. Teams were able to build new operational experiences, compliance workflows, partner experiences, and product-specific surfaces using shared patterns rather than reinventing the experience each time. Open Finance Overview and Bank Intelligence both leveraged the same foundational approach while serving entirely different customer needs.
Outcome
Dashboard evolved from a collection of developer utilities into the primary self-serve customer platform for Plaid. The new lifecycle-driven experiences improved customer engagement throughout the journey: first-time feature engagement increased 119%, customer re-engagement increased 350%, monthly active Dashboard customers increased 7%, support experiences deflected roughly 41% of tickets, and Launch Center increased launch rates by 32%. More broadly, Dashboard became the acquisition, activation, launch, operations, and expansion surface for Plaid’s growing self-serve business. During this period, self-serve revenue grew substantially as customers increasingly adopted and expanded their use of Plaid through Dashboard. The lifecycle framework and modular Home architecture also created a scalable foundation that enabled future experiences across Dashboard, Open Finance, compliance workflows, partner portals, and new products.