Fintech UX Research Case Study

Discovery Research with Fintech Product Leaders and Developers for Vanguard

A team designing a new partner portal for Vanguard needed to understand how other companies evaluate and adopt a technology provider’s services. Marketade, a UX research firm, recruited and interviewed product leaders and software developers at fintech and financial services companies, then delivered a findings report with journey maps and portal requirements for each audience.

Candlestick chart of financial market prices on a trading screen

Last updated: November 17, 2026

Goals

Vanguard is one of the world’s largest investment managers, serving more than 50 million investors. Many financial firms now make their services available inside other companies’ products. A partner portal is where those companies learn what is on offer, judge whether it fits and begin building.

The team designing a new portal for Vanguard had 2 audiences in mind: the product leaders who decide whether to adopt a service, and the developers who integrate it. The team held several assumptions about both groups and wanted evidence before committing to a design direction.

The research set out to:

  • Understand how each audience evaluates a technology provider, and who makes the decision at each point
  • Learn what builds trust, and what people expect to see before they create an account
  • Identify pain points from past integrations that a new portal could avoid

‍

Approach

We ran the study as discovery research: UX research that comes before design starts, to learn about each audience's workflows and what they need. The core was 10 one-on-one interviews, split about evenly between product leaders and developers. The work followed 5 steps: discovery, recruiting, research, analysis and report.

1. Discovery

We started from the team’s research questions and its assumptions about the 2 audiences. We then added questions of our own about roles, responsibilities and how decisions differ from one organization to the next. This produced a research plan and an interview guide for each audience.

2. Recruiting fintech product leaders and developers

We led every stage of recruiting: sourcing, screening, selection, scheduling and incentive payments. Participants had to meet these criteria:

  • Product leaders: mid-level to senior managers with final responsibility for a product
  • Developers: software engineers and architects who had integrated third-party services, or worked from their technical documentation, in the past 3 months
  • Employer: a bank, fintech company, insurer or similar firm in the United States with 10 or more employees
  • No one employed by a direct competitor

We sourced candidates through LinkedIn ads and direct messages, Slack communities for product managers and developers, social media posts and research panels. Each candidate went through 2 rounds of screening: a web-based questionnaire, then a phone call.

Recruiting was the hard part of the project. Product decision-makers are difficult to reach in any industry, and financial services adds another layer. The biggest obstacle was finding people willing to speak openly about their own products and how their companies make decisions. Where a participant asked us to keep an employer’s name confidential, we did.

3. Research: one-on-one interviews

Each interview was a remote, moderated video session of about 45 minutes, and we recorded every session.

With product leaders, we asked how their companies decide whether to add a new capability, whether to build or buy it, and how they vet an outside provider. With developers, we asked about recent integrations, what separates good technical documentation from bad, and when they are brought into a decision.

Both groups described an integration that went well and one that went badly. They also told us what they would expect to see on a provider’s portal before logging in. Participants then clicked through portals and websites from other technology providers and talked through what worked for them.

Partway through the interviews, we shared an interim readout so the team could start using early findings.

4. Analysis

We did the synthesis ourselves. We organized what we heard along each audience’s path, from first identifying a need through ongoing use. At each stage, we listed the questions people ask and the information they look for.

Laying the 2 paths side by side showed where the audiences overlap and where they hand off to each other. We then sorted portal requirements into must-haves and additional features for each audience.

5. Report

The final report opened with an executive summary of key findings and recommendations, then covered each audience’s journey in detail. The later sections set out portal requirements, annotated examples from other providers’ portals and video clips from the sessions.

‍

Outputs

By the end of the project, the team had:

  • A findings report that distilled the interviews into 6 key findings, each paired with a recommendation, so the team could focus on what mattered most
  • 2 journey maps, 1 for each audience, each covering 5 stages from identifying a need to ongoing use
  • Must-have portal requirements for each audience, plus additional features to consider
  • Annotated examples from portals that participants pointed to as models
  • Video clips of participants describing what they need from a provider

Three examples show the kind of insight the research produced.

A single site for both audiences. The team expected 2 separate audiences with separate needs. Instead, product leaders and developers moved through similar stages and passed questions back and forth. The recommendation was a single site that serves both, with a clear path through to the technical documentation.

Key information before sign-up. Both audiences wanted to judge a provider before creating an account. They expected to see what the services do, example use cases, and security and legal information without logging in. Developers also wanted a test environment or trial before any payment. The recommendation was to keep this information public and offer a way to try before committing.

A technical overview for decision-makers. Product leaders said they need a high-level sense of how a service works and how hard it is to integrate before they can back it. The recommendation was a plain-language overview written for decision-makers, alongside the developer material.

‍

About the Project

  • Industry: Financial services
  • Platform: Web portal
  • Audience: Product leaders and software developers
  • Methods: Discovery research with one-on-one interviews
  • Stakeholder teams: UX and design
  • Company size: 20,000 employees

‍

More Case Studies

Marketade conducted mixed-methods discovery research to inform the product strategy of an AI software company serving 100,000+ local businesses.

Marketade interviewed B2B decision-makers at large organizations and led a 1-day workshop to explore new conceptual models for an enterprise security product.