Capital One Card Alerts: Designing a One-Screen Setup for Instant Notifications

Quick Overview

A product improvement question about consolidating the multi-screen setup for Capital One's instant push notifications into a single view. It tests reasoning about why customers want real-time card alerts, which settings to show or default, when to offer the setup, and how to measure success with guardrails and an A/B test.

Capital One Card Alerts: Designing a One-Screen Setup for Instant Notifications

Company: Capital One

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You own the redesign of Capital One's instant push notifications (IPN). The experience customers use to turn on and manage these alerts currently spans multiple screens and is being consolidated into one view. How would you make that experience better? ```hint List the decisions first Before laying anything out, write down every choice the current screens ask a customer to make. For each one, ask whether the customer needs to decide it during setup at all, or whether a sensible default would do. ``` ### Clarifying Questions - Which alerts does the view cover: purchase alerts only, or every card and account notification? - Where do customers reach it: during card activation, from settings, or from a prompt elsewhere in the app, and on mobile, web or both? - Which goal matters most: more customers turning alerts on, fewer people abandoning setup, or faster fraud reports and fewer support calls? - Is moving to one view already decided, or should I also judge whether a single view is the right call? ### What a Strong Answer Covers - Why customers want instant alerts and what the bank gains, and how that shapes what the single view must do - Which settings appear on the view, which become defaults, and how the layout keeps one screen from feeling crowded - When and where customers are offered the setup, since timing affects whether they finish it - Success metrics with guardrails, and an A/B test against the current flow - Edge cases such as notifications blocked in the phone's settings, several cards on one profile, and accessibility ### Follow-up Questions - In the A/B test the single view lifts setup completion, but more customers in that arm switch alerts off within a month. What do you conclude, and what would you change? - How would you test the best moment to offer alert setup, and which results would you read beyond tap-through rate? - Another team you depend on to deliver the redesign has no capacity to help for six months. How would you run your first meeting with them to win their support?

Overview: A product improvement question about consolidating the multi-screen setup for Capital One's instant push notifications into a single view. It tests reasoning about why customers want real-time card alerts, which settings to show or default, when to offer the setup, and how to measure success with guardrails and an A/B test.

Capital One logo
Capital One
Feb 14, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You own the redesign of Capital One's instant push notifications (IPN). The experience customers use to turn on and manage these alerts currently spans multiple screens and is being consolidated into one view. How would you make that experience better?

Clarifying Questions Guidance

  • Which alerts does the view cover: purchase alerts only, or every card and account notification?
  • Where do customers reach it: during card activation, from settings, or from a prompt elsewhere in the app, and on mobile, web or both?
  • Which goal matters most: more customers turning alerts on, fewer people abandoning setup, or faster fraud reports and fewer support calls?
  • Is moving to one view already decided, or should I also judge whether a single view is the right call?

What a Strong Answer Covers Guidance

  • Why customers want instant alerts and what the bank gains, and how that shapes what the single view must do
  • Which settings appear on the view, which become defaults, and how the layout keeps one screen from feeling crowded
  • When and where customers are offered the setup, since timing affects whether they finish it
  • Success metrics with guardrails, and an A/B test against the current flow
  • Edge cases such as notifications blocked in the phone's settings, several cards on one profile, and accessibility

Follow-up Questions Guidance

  • In the A/B test the single view lifts setup completion, but more customers in that arm switch alerts off within a month. What do you conclude, and what would you change?
  • How would you test the best moment to offer alert setup, and which results would you read beyond tap-through rate?
  • Another team you depend on to deliver the redesign has no capacity to help for six months. How would you run your first meeting with them to win their support?