Feature Findability

[Image]

Feature findability directly affects how easily users can access critical financial tools within a platform. For product designers and managers, the challenge is ensuring that key actions, such as transferring money or managing accounts, are visible, intuitive, and consistent with user expectations.

Fintech Feature Findability Testing uses a design stack of UX metrics: success, effort, and satisfaction to measure how effectively users can locate and use important features. This approach replaces subjective opinions with measurable insights.

With these findings, designers and managers can make informed design decisions, prioritize improvements, and demonstrate the impact of changes on business outcomes. For example, testing Bank of America’s money sending features revealed high usefulness but weaker usability, showing where visibility and interaction design could be improved to reduce friction and improve task success.

---

Define Goals for Your Fintech Feature Findability Test

A fintech feature findability experience should balance user needs like clarity, guidance, and speed with business goals such as adoption, engagement, and satisfaction. Users want to easily locate and understand how to use key features like sending money or managing transfers, while businesses aim to ensure those tools are visible, intuitive, and delivering on their value. Measuring findability reveals whether essential features are discoverable and helping users succeed.

**Audience:**

This concept was tested with mobile banking consumers in the United States who explored the money sending and transfer features within Bank of America’s mobile app. Participants were asked to locate and use key transfer actions (e.g., Zelle, bill pay, or internal transfers) while sharing impressions of clarity, navigation, and confidence in finding what they needed.

User Needs
As a mobile banking customer trying to find and use key app features, the five most important needs would be:

1. Features should be easy to locate within menus or dashboards, without hidden steps (options should be Findable).

2. The organization and labeling of actions should match user expectations and mental models (usability should be Intuitive).

3. The features themselves should deliver clear value and solve real financial needs (options should feel Useful).

4. The interface should guide users with contextual cues or explanations for each option (features should feel Insightful).

5. The path from discovery to action should be quick and frictionless (interactions should be Efficient).

These five ensure features feel visible, understandable, and rewarding to use, helping users feel in control of their financial tools.

Business Goals
Here are the five most important business goals for fintech feature findability:

1. Increase Feature Adoption – Ensure users can easily discover and begin using core features like payments and transfers.

2. Maximize Engagement Frequency – Encourage recurring use by making important tools prominent and accessible.

3. Reduce Support Requests – Minimize confusion and help users self-serve through clearer navigation and guidance.

4. Highlight Competitive Advantages – Emphasize key features that distinguish the product from other banking apps.

5. Gather Behavioral Insights – Track which features users find or overlook to optimize design and feature placement.

These goals help the business increase adoption, strengthen user satisfaction, and optimize in-app experiences through clearer, more intuitive feature visibility.

---

Choose Metrics to Test Your Feature Findability

For Banko’s feature discovery experience, a design stack of four UX metrics was chosen to measure how effectively users can locate, understand, and act on new features within the platform. This stack — Usability, Engagement, Intent, and Satisfaction — was established by mapping user needs directly to measurable outcomes:

• Findable → Usability

  New features should be easy to locate within the interface. Usability measures whether participants can successfully find and access the feature without confusion or excessive searching.

• Intuitive & Efficient → Engagement

  Once discovered, the feature should naturally invite interaction. Engagement evaluates whether participants are drawn to explore or use the feature based on its visibility and clarity.

• Useful → Intent

  Users should recognize the value of using the feature. Intent measures whether participants express motivation to adopt or return to the feature after discovering it.

• Insightful → Satisfaction

  The experience should leave users feeling that the feature improved their workflow or understanding. Satisfaction captures whether participants describe the feature as helpful, meaningful, or worth using again.

---

Establish Hunches to Direct Your Testing

Feature discoverability in fintech apps is key to user satisfaction and retention. When users can easily locate tools like transfers, payments, or wires, they gain confidence in managing their money independently. Bank of America’s Pay & Transfer screen shows a clean layout that emphasizes clarity and hierarchy — yet subtle usability and expectation gaps may still emerge. These hunches help pinpoint how quickly and intuitively users locate and understand key actions.

Example: Bank of America Pay & Transfer Screen

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Hunch</p></th><th colspan="1" rowspan="1"><p>Question</p></th><th colspan="1" rowspan="1"><p>UX Metric</p></th></tr><tr><td colspan="1" rowspan="1"><p>The four primary actions (Transfer, Zelle®, Pay Bills, Wire) are clearly labeled and use recognizable icons, but users may hesitate between similar-sounding options like “Transfer” vs. “Zelle.”</p></td><td colspan="1" rowspan="1"><p>How confident were you that you selected the right option for the type of payment you wanted to make?</p></td><td colspan="1" rowspan="1"><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.helio.app/define/ux-metrics/behavioral-metrics/success">Success</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>The global navigation bar at the bottom (Accounts, Pay & Transfer, Deposit Checks, Invest) supports orientation, but users might miss the contextual depth of features available within each tab.</p></td><td colspan="1" rowspan="1"><p>How well did the tab names help you predict where to find different banking features?</p></td><td colspan="1" rowspan="1"><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.helio.app/define/ux-metrics/behavioral-metrics/comprehension">Comprehension</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>The activity section beneath the main tiles adds useful context, but it could compete visually with the primary action area, drawing users’ attention away from initiating a task.</p></td><td colspan="1" rowspan="1"><p>How easy was it to focus on starting a new action rather than reviewing past activity?</p></td><td colspan="1" rowspan="1"><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.helio.app/define/ux-metrics/behavioral-metrics/effort">Effort</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>The search bar with “Hi, I’m Erica” (the AI assistant) offers strong potential for guidance, but users might not realize it can help locate app features, assuming it’s only for support.</p></td><td colspan="1" rowspan="1"><p>How likely would you be to use the search bar to find a specific feature in the app?</p></td><td colspan="1" rowspan="1"><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.helio.app/define/ux-metrics/behavioral-metrics/intent">Intent</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>The layout consistency (white space, icon design, font hierarchy) promotes usability, but the abundance of options in other parts of the app may lead to decision fatigue when users don’t know where to start.</p></td><td colspan="1" rowspan="1"><p>How simple or overwhelming did this page feel when deciding what to do next?</p></td><td colspan="1" rowspan="1"><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://glare.helio.app/define/ux-metrics/attitudinal-metrics/sentiment">Sentiment</a></p></td></tr></tbody></table>

These hunches help determine whether Bank of America’s app effectively balances clarity, confidence, and guidance in its feature layout — ensuring users not only see what’s available, but know exactly where to go to complete a task.

---

Turn Hunches into Test Questions

Turning these metrics into participant questions transforms design assumptions into measurable signals. Each metric uses a specific question type paired with a clear example from Bank of America’s money-sending experience:

• Satisfaction **(Likert scale of satisfaction)**

  Question type: Satisfaction scale.

  Example: “Overall, how satisfied are you with the ease of finding and using the money-sending options in this app?”

[Image]

• Effort **(7-pt scale of difficulty)**

  Question type: Difficulty rating scale.

  Example: “How easy or difficult was it to find where to send money to another person?”
 (1 = Very Easy → 7 = Very Difficult)

[Image]

• Success **(Click test directive)**

  Question type: Task-based click test.

  Example: “Where would you tap to send money to someone using Zelle or another transfer method?”

[Image]

---

Calculate UX Metric Scores from User Feedback

For Bank of America’s mobile app money-sending experience, user feedback was analyzed to understand how easily people could locate and complete key financial actions such as sending funds or using Zelle. The design stack for this test included metrics that capture how intuitive the feature is to find, how rewarding the process feels, and how efficiently users can complete the task. Each score was calculated on a 0–100% scale using the following benchmarks:

• Very Good = 90% and above

• Good = 70%–89%

• Average = 50%–69%

• Poor = 30%–49%

• Very Poor = below 30%

Once the individual UX metric scores are calculated, the average of those scores are used to determine the overall score for the user experience.

Bank of America’s Results

• Success (93% / 85% — Very Good & Good): Across two key directives, most users located and completed the send-money features with minimal confusion. The iconography and task flow were described as “clear” and “predictable,” though some wanted shortcuts for repeat transfers.

• Satisfaction (96% — Very Good): Participants were highly satisfied with the ease and reliability of the experience. The familiar design language and simple confirmation steps made users feel confident and in control.

• Effort (93% — Very Good): The process required few steps, resulting in strong efficiency and low cognitive load. Users appreciated how both transfer and Zelle actions were consolidated within a single, visible card interface.

[Image]

Together these results produced an overall test score of 92% — Very Good, showing that Bank of America’s money-sending flow delivers exceptional usability and satisfaction. The clear labeling and quick completion time demonstrate best-in-class feature findability within a financial app. Future optimizations could focus on personalizing frequent transfer options or automating repeat actions to further enhance efficiency.

Click here to check out the raw survey data and UX metric scores for Bank of America’s money sending features.

---

Draw Signals from Your Design Stack

Here’s how signals were surfaced from the Bank of America mobile features test results by following these five steps:

1. Focus on poorly scoring metrics

[Image]

Bank of America’s feature findability test achieved a Very Good overall score of 92%, performing strongly in Success (93%), Satisfaction (96%), and Effort (93%), but dropping to Good (85%) for the second success task — using Zelle after reaching the Pay & Transfer page. This dip indicates that while users easily locate the main hub for transactions, task clarity decreases when moving into secondary flows like peer-to-peer payments. The key signal: strong feature visibility, weaker task comprehension within sub-flows.

2. Identify patterns across metrics

[Image]

The consistently high satisfaction and effort scores show that users find the experience polished, reliable, and smooth, suggesting strong UI execution. However, the split success rates expose a moment of cognitive friction — users understand where to go but not what happens next. This suggests Bank of America’s feature hierarchy is clear, but its feature differentiation (Pay vs. Zelle) isn’t fully intuitive.

3. Determine if user needs are being met

[Image]

• Findable: Exceeded — users quickly identified the main transfer section.

• Intuitive: Partially met — users hesitated when distinguishing between transfer options.

• Useful: Met — core functionality aligns with expected financial goals.

• Insightful: Partially met — lack of contextual cues made Zelle’s role less obvious.

• Efficient: Exceeded — minimal effort and fast task completion once the correct path was known.

4. Compare outcomes to your business goals

• Increase Feature Adoption: Partially met — discovery is excellent, but completion within Zelle flow needs support.

• Maximize Engagement Frequency: Achieved — easy access encourages repeat usage of main transaction tools.

• Reduce Support Requests: Supported — high clarity on initial pages minimizes user confusion.

• Highlight Competitive Advantages: Missed — Zelle’s ease-of-use advantage isn’t surfaced through microcopy or onboarding cues.

• Gather Behavioral Insights: Achieved — clear evidence of friction between discovery and sub-feature comprehension.

5. Surface signals & establish a direction
**
Signals derived from the data:**

1. Feature findability is excellent, reinforcing strong IA and visual clarity.

2. Feature differentiation lacks clarity, especially between transfer pathways.

3. High satisfaction hides subtle confusion, suggesting users are content but not confident when branching into advanced tools.

**Direction based on business context:**

To align with Bank of America’s goals of increasing adoption and emphasizing competitive advantages, next steps should focus on:

• Adding contextual prompts (e.g., “Send money instantly with Zelle—no extra setup required”).

• Highlighting visual distinctions between internal transfers and peer payments.

• Providing a guided tooltip or mini onboarding for first-time Zelle users.

Based on the signals and design direction, we created an updated version of the design with the expected UX metric improvement:

[Image]

The signal is clear: users easily find transfer tools but lose momentum in sub-flows. Providing more context will turn awareness into confident action.