Redesign Core Data

Context

Every time a customer swipes their card, Capital One captures data tied to that transaction, account, and customer:

  • The account, the customer name, the card number, the dollar amount for the transaction
  • The merchant name, location, date, and point of sale
  • The status: authorized, cancelled, declined, pending, posted

Capital One receives all data, ~ 40 million transactions per day for millions of accounts and customers and through cleansing and categorization makes this data usable to internal teams

‍

Redesigning how that data was structured, surfaced, and prioritized became a strategic design opportunity.

Role

Service Designer

Team

  • 3 Product Managers
  • 3 Tech Teams
  • 12+ SME Teams
  • 1 Design Manager

TimeLine

8 Months

skills

Strategy Design
Service Design
User Research

Impact

450+
pain points collected across 50 subject matter experts
30
data elements prioritized for transactions, accounts and customers
2
quarters of VP-level product roadmaps informed
Core Data — Discover 1
Core Data — Discover 2
Core Data — Define 1
Core Data — Define 2
Core Data — Define 3
Core Data — Design 1
Core Data — Design 2
Core Data — Design 3
Core Data — Synthesize 1
Core Data — Synthesize 2
Core Data — Deliver 1
Core Data — Deliver 2

Discover

Capital One's middle-layer teams need to understand how internal platforms like EASE and Empath use data, so they can build a platform that meets current and future use cases, enabling new end customer experiences

‍

Help Capital One's core teams understand how data is used to build a platform and APIs that meet current and future customer needs.

‍

Contribution

Conducted user research, synthesized insights and provided strategic recommendations. Informed and helped align product and tech teams on roadmap and data architecture.

‍

Results

Interviewed 50 SME across 10 teams, collected 450+ pain points, prioritized 30 core data features. Influenced product roadmaps at the VP level that enabled new customer experiences.

Read Details
Core Data — Discover 1
Core Data — Discover 2

Define

Objective

Understand how consuming teams currently utilize Core data, identify pain points, opportunities and insights around the middle-layer data

Contribution

Collaborated on creating design brief. Assisted in participant recruitment and led interview activity for 10+ focus groups. Transcribed interviews and pulled relevant quotes

Result

Completed 3 research briefs for each workstream & 20 transcribed interviews with relevant insights, pain points, etc., highlighted for the research report

Project Brief
The project brief helped product teams outline the scope of the  initiative and for the design team, including myself to translate  

  • 1 The problem statement
  • 2 The research/ design approach

Moderator Guide & Activity

Since the team had to elicit feedback from many users and have detailed data requirements collected, I created a Google Slide with probing questions to facilitate conversations. Comments not directly captured in the activity, were also transcribed and annotated to ensure the team was recording all details

Read Details
Core Data — Define 1
Core Data — Define 2
Core Data — Define 3

Design

Objective

Synthesize interview insights into a list of prioritized platform capabilities and deliver a finalized research report

Contribution



Assisted in tagging, clustering  and summarizing notes. Collaborated with partners to refine themes and insights. Collaborated on research reports. Built a prioritization framework based on user research and product feasibility.

Throughout the research phase, I facilitated interviews, took notes, synthesized information, followed up with participants and sent out surveys (for teams to rank order needs)

Result

Delivered 3 reports to respective product and tech partners (Transactions, Accounts, Customer) and rank ordered 30 core data features

Read Details
Core Data — Design 1
Core Data — Design 2
Core Data — Design 3

Synthesize

Objective

Provide partners with qualitative and metric backed recommendations based on user research for middle-layer database architecture

Contribution

Collaborated in building a storytelling deck and crafting a roadmap based on feature prioritization. Mapped user research themes to product’s OKRs. Co-presented work to SLT

Result

Helped shape 2 quarters of design engagement and product work for the various middle-layerdata workstreams

‍

Read Details
Core Data — Synthesize 1
Core Data — Synthesize 2

Deliver

Design contribution helped shape the foundational understanding, strategic recommendations and the prioritized features for the middle-layer architecture
‍

  • Provide partners with qualitative and metric-backed recommendations for the middle-layer database architecture, and translate those recommendations into tangible customer experiences.
    ‍
  • Prototyped UI screens (demonstrative only) to represent the possible end customer experiences enabled by the underlying data and platform recommendations.
    ‍
  • The journey to Core modernization is set until 2025, several of the research findings are in production today, in the form of APIs that internal teams can leverage (Such as a Card Transactions API which allows any team building with customer data to pull the most relevant information)

Result

‍

Provided 30 short-term, long-term, and "nice to have" data features to the middle-layer teams for planning, validated through a follow-up survey ranking the data elements teams wanted most.

Read Details
Core Data — Deliver 1
Core Data — Deliver 2

Final product

Reflection

I'd pair the SME interviews with end-customer research to connect data needs to real experiences.

I'd set up a simple way to track which of the 30 prioritized features shipped as APIs.

Next, I'd re-run the prioritization survey as teams adopt the new APIs to keep the roadmap grounded.