Understanding the people behind everyday banking experiences.
Digital banking has made financial services more accessible, but accessibility alone doesn't guarantee a good user experience. People still need to understand where to go, what actions to take, and whether they can confidently complete important financial tasks.
I was engaged as a UX Researcher on a digital banking experience improvement project for a financial services organization.
My responsibility was to plan and execute research that would help the product team better understand users' behaviours, expectations, and experiences when interacting with digital banking services.
I led the research process, from developing the research plan and gathering user perspectives to synthesizing evidence and presenting recommendations to stakeholders.
Confidentiality note: This case study documents my research process and professional responsibilities. The client's identity, proprietary research findings, participant information, internal documentation, and specific product recommendations have been omitted in accordance with confidentiality obligations.
How do you improve an experience without losing sight of the people using it?
Digital banking products support important everyday activities, often involving people's money, time, and trust.
Improving these experiences requires more than identifying interface problems. It requires understanding how people approach financial tasks, what they expect from their banking applications, and how those expectations influence their interactions.
The engagement sought to develop a clearer understanding of user behaviour and identify opportunities to inform future experience improvements.
The research needed to consider both existing customer experiences and broader expectations shaped by other digital banking products.
Research objectives
The research was structured around four objectives:
Understand user behaviour: Explore how people approach and interact with common digital banking activities.
Identify experience challenges: Investigate where users encounter difficulty, uncertainty, or unnecessary effort.
Understand expectations: Explore what users value in digital financial experiences and how they evaluate different banking applications.
Inform product decisions: Translate research evidence into actionable guidance for future product and experience design work.
The central question guiding my approach was:
How can we better understand people's banking behaviours and expectations to inform a more intuitive digital experience?
Image 1 Image 2 Image 3 My approach My Approach Combining what people say with how they experience banking.
I adopted a mixed-methods research approach, combining qualitative research with quantitative survey analysis.
This allowed me to explore individual experiences in depth while examining patterns across a broader group of respondents.
The work was organized into four stages.
Stage 01 — Research planning
Before conducting the research, I developed a structured research plan outlining the objectives, methodology, participant considerations, research activities, and expected deliverables.
I also reviewed available background information to understand the project's context and identify where additional user evidence would be most valuable.
This helped establish a clear direction for the engagement and align the research activities with the questions stakeholders needed answered.
Stage 02 — Qualitative research
8 user interviews · 3 field studies
I conducted eight user interviews to explore participants' banking habits, expectations, and experiences.
The interviews provided opportunities to ask follow-up questions, understand the context behind participants' responses, and explore how they described their interactions with digital banking services.
I also conducted three field studies to gain additional context about how people experience banking activities.
Together, these methods helped me examine user experiences beyond isolated opinions or assumptions.
Stage 03 — Quantitative research
102 survey respondents
Alongside the qualitative research, I analyzed survey responses from 102 participants.
The survey provided a broader perspective on banking behaviours and user-reported experiences.
I examined the responses for recurring themes and compared them with the qualitative evidence.
The goal was not to treat every survey response as a definitive conclusion, but to understand how different sources of evidence could contribute to a more complete picture.
Stage 04 — Research synthesis
After completing the research activities, I organized and analyzed the collected evidence.
I reviewed interview notes, field observations, and survey responses to identify recurring themes and areas requiring further attention.
I then translated the research into a structured presentation of findings and recommendations for stakeholders.
This final stage was particularly important because research is only useful to a product team when the evidence can be understood and considered in decision-making.
Key Research Decisions Making deliberate choices about how to gather and interpret evidence.
Several decisions shaped how I approached the engagement.
01. Using multiple research methods
I chose to combine interviews, field studies, and survey analysis rather than relying on a single method.
Each provided a different perspective: interviews offered depth, field studies added context, and the survey offered broader directional evidence.
Using these methods together created opportunities to compare observations rather than depending on one source.
02. Focusing on behaviour, not just preferences
I wanted the research to go beyond asking participants what they liked or disliked about banking applications.
Understanding how people approach tasks, interpret information, and describe their experiences was equally important.
This helped keep the research grounded in user behaviour and context.
03. Separating evidence from interpretation
During synthesis, I considered the distinction between what participants reported, what I observed, and what those observations might suggest.
This distinction matters because research recommendations should be supported by evidence rather than presented as unquestionable facts.
04. Making the research useful to stakeholders
The final deliverable needed to communicate more than a collection of interview notes or survey responses.
I organized the research into a report and presentation format intended to help stakeholders understand the work, evaluate the evidence, and consider implications for future product decisions
Evidence of Work Evidence of Work From research questions to a structured body of evidence.
My contributions to the engagement included:
Research planning Developing the research approach, objectives, methodology, and execution plan.
User interviews Conducting eight interviews and documenting participants' experiences.
Field research Carrying out three field studies to gather contextual evidence.
Survey analysis Reviewing responses from 102 participants and examining broader patterns.
Research synthesis Organizing qualitative and quantitative evidence into a coherent research narrative.
Stakeholder communication Preparing a research report and presentation of findings and recommendations.
The original research materials, participant records, findings, and stakeholder deliverables are confidential and are not reproduced here.
Image 4 Outcome and Reflection 06 / Outcome & Reflection Turning research into a foundation for better product decisions.
The engagement concluded with a structured body of UX research and a set of recommendations presented to the client.
The research brought together evidence from interviews, field studies, and survey responses into a format intended to support future product and experience design discussions.
Because the work was conducted under a confidentiality agreement, I cannot publicly share the specific findings, recommendations, internal decisions, or subsequent product outcomes.
However, the project strengthened my understanding of how research contributes to product development.
What I learned
Research begins with asking better questions.
A well-defined research plan helps keep activities focused on the decisions a team needs to make, rather than collecting information without a clear purpose.
Different methods reveal different perspectives.
Interviews, field observations, and surveys each have strengths and limitations. Combining them requires careful interpretation, especially when the evidence is directional rather than statistically representative.
Good research requires judgment.
Collecting evidence is only one part of the work. Deciding how to organize it, distinguish observations from assumptions, and communicate its significance is equally important.
Research is part of product thinking.
This engagement reinforced my interest in the relationship between user needs, business priorities, and product decisions.
It also contributed to my growing focus on product management: understanding problems clearly, evaluating evidence, and helping teams make more informed decisions.
Closing thought
Better product experiences begin with a better understanding of the people using them.
This project reminded me that the most valuable contribution of UX research isn't simply identifying problems. It's helping teams approach product decisions with greater clarity, context, and evidence.
Confidential client project · UX Research · 2026
Your workspace has used all of its available credits.
