Review Analyze and Complete the Chase Manhattan Bank Case Study on Page 339 of Your Textbook

Rather than aiming for perfection, information technology is more important to focus on continuous improvement for user experience (UX) for an existing production. In this article, we'll be exploring a heuristic evaluation example, particularly the exact procedure that nosotros're using to improve apps.

UX review is important to ensure that you're delivering the right solution that resonates with the audience. It ought to be carried out in products and services offered to ensure that customers are getting the best out of what your company offers.

Rather than glossing through the theories, nosotros're going to show how Heuristic evaluation is applied in a existent example: The Chase Mobile Cyberbanking App.

Chase For Business App Overview

The Chase business app allows users to easily connect and utilize the banking accounts and services provided past the JPMorgan Chase Banks. The Chase app offers the same financing features every bit the Chase.com website, including security, reports, and the ease of sending coin.

Users who already take a Chase.com account tin download the app and get started with the same credential. Alternatively, they can create a new account from the app itself.

Our UX Review Process

Now, let's go started on the UX review process of the Hunt business app.

Set objectives

Before starting the Heuristic evaluation for UX review, information technology is essential to establish the objectives of doing so. Ultimately, the process is intended to nautical chart a clear actionable path to amend the blueprint. The objectives may differ according to apps and organizations.
For instance, yous may want to review an app to find out ways to increase sign-upwards rates.

In our case, we're reviewing the Chase app to improve the app's user flow and streamline the user feel.

‍

Report behavior flows

User behavior reveals a great deal almost what'south working or defective in an app. It provides insights into bug like high user driblet offs, specially where and why it happens.

Our squad uses a few methods to study behavior flows on apps. We apply proto personas (as we have but assumptions, that we need to validate) to understand user needs and build empathy. Nosotros create an interactive user experience by combining the documented user journeying with business and user objectives.

Here's how our proto persona looks similar

An case of Customer Journey Map

In order to go a deeper insight into users' needs and validate our assumptions, nosotros also bear interviews.

The Chase App Heuristic Evaluation Example

Heuristic evaluation is a popular method to analyze user experience in a finished product. Information technology is based on a broad set of guidelines where a number of criteria are manually evaluated. The goal of the Heuristic evaluation is to pinpoint problems in a product and offer the right solutions.

In our review procedure of the Chase app, we're going to use Jakob Nielsen's 10 heuristics that are proven to be reliable in UX evaluation.

Permit's go through each benchmark with accompanying analysis, bug, and solutions for the existing app.

i. Visibility of organization status

Users ought to ever be aware of what they are doing in an app, particularly one that involves financial transactions.

Problem: No obvious elements (eolith)

Task: Put coin on deposit

Issue: Elements with the camera icon doesn't explain exactly what the users demand to do.

Recommendation: Add together a clarification or visually display what needs to be photographed.

‍

Good Points: Progress bar on the signup screen.

2. Friction match between organisation and the real globe

Apps are created by developers who are familiar with programming terminology. Nevertheless, users capeesh the information presented in languages and terms they are familiar with. The disparity in both leads to a bad user feel.

Problem #1: The icon doesn't brandish data about opening an business relationship.

Task: Open up an account.

Effect: The icon on the button doesn't correspond to the button'southward function.

Recommendation: Replace the icon with one that associates with a bank account.

Problem #2: The support push lacks a descriptive characterization.

Job: Contact support.

Consequence: The button's name isn't informative enough. It doesn't imply that the button is used to contact the back up manager.

Recommendation: Replace the text on the push with 'Contact Support"

‍

Good points: Information technology provides a convenient ATM search map.

3. User control and freedom

An app must conceptualize unpredictability in user behavior. For example, the user may brand mistakes and need to backtrace the navigational path. Or he/she needs to brand corrections to inputs on the app.

Problem: No issues were detected.

‍

4. Consistency and standards

Users are bound past habit and it will be bad for UX if the app does not show consistency in terminology, layout, and behavior. An app could be confusing for users if information technology fails to maintain a standard operating convention.

Problem #1: Inconsistent icon style.

Task: Access bank accounts info.

Consequence: The app icons are differing in mode. There are at least iii different types with mixed outlines, fills, and colors. Some icons bespeak to the aforementioned action simply are not uniformly designed on different screens.

Recommendation: Create a fix of consistent icons for the Chase app.

Trouble #ii: Navigational elements behave differently in different situations.

Task: Navigating the app

Effect: The navigational elements are not confined to a single predictable behavior. There are several types of drop-downward and add together buttons. At least 2 types of tabs are institute in the app with one strikingly dissimilar from the generic background fashion.

Recommendation: Standardize the appearance and behavior of navigational elements.

Problem #iii: Different styles for similar elements.

Task: Decide the visual composition of buttons and elements on the screen.

Result: Too many font and button styles, including the placeholder for buttons.

Recommendation: Create a style and its variation for the same interface element.

Problem #four: Dropdowns wait different in various scenarios.

Task: Redesign dropdown elements

Outcome: There's a lack of consistency with dropdown arrows and behaviors. It'southward hard to conceptualize the behavior of dropdowns every bit like styles may result in different interaction beliefs. Also, dropdowns that exhibit the same beliefs sometimes take different colors.

Recommendation: Redesign dropdowns past making them visually consistent across similar types of interaction.

Trouble #5: Inconsistent 'More' button beliefs.

Task: Make the 'More' push consistent

Issue: The 'More' button opens different types of windows in different situations.

Recommendation: Review the information in the window and effigy out how to make the style of the windows consequent throughout the app.

5. Error prevention

Users are bound to make mistakes and it is the onus of the app to detect and prevent them from happening. Verification checks and error prompts are practiced features to prevent the app from taking in erroneous inputs.

Problem: Users are simply enlightened of errors after pressing the 'Go on' push button. The Chase app lacks preemptive error prevention.

Task: Improve error prevention.

Consequence: The app lacks preemptive error checks, which results in users spending more time correcting the mistakes and completing the course.

Recommendation: Add contextual field validation to check the information filled in spontaneously, and not after the user has submitted the form. Any input rules should be highlighted, whether they are fulfilled or not.

Good points: Field hints to brand form-filling easier and confirmation of pick for clarity.

6. Recognition rather than recall

Whatsoever data and educational activity deemed disquisitional in using the app should be fabricated visible to users. Users should not be burdened with memorizing the details as they navigate through the app. Such data should be visible, or easily accessible.

Trouble: Championship for 'Account'

Job: Add together navigation bar title

Result: The navigation bar championship is absent.

Recommendation: Review all pages to find out if the navigation bar title is missing elsewhere.

vii. Flexibility and efficiency of use

Both novice and experienced users expect the app to exist tailored to their preferences. Therefore, an app must allow personalization according to the user's level of experience. For example, advanced features are subconscious to prevent overwhelming novice users but accessible to experienced users.

Trouble #1: Can't copy an business relationship number.

Task: Add the possibility to re-create an account number.

Event: It takes also much effort to re-create an account number.

Recommendation: Enable account number copying by belongings the account number for a few seconds until the message 'Account number was copied' is shown in a small text field.

Problem #2: Button summit is less than 40 pixels.

Task: Check the clickable button zone.

Issue: The existing button height is not optimized for mobile. Information technology is besides pocket-sized for a 'touch' to exist made comfortably on the screen.

Recommendation: Review button and touch target heights. Ensure that the impact target pinnacle is at to the lowest degree 48 pixels or more than. A bear on target of this size results in concrete size of about 9mm regardless of screen size.

‍

Problem #three: Overloaded FAQ without a search role.

Task: Meliorate user interaction with information on the screen.

Issue: There are too many topics in the FAQ and it overwhelms users without the presence of a search bar.

Recommendation: Segregate FAQ to related topics to ensure users spend less time finding the right solution. Allow users to navigate the FAQ past categories. It's too a good idea to include a search bar, which lets users instantly locate a topic in the FAQ. Include a feedback form for users to suggest potential improvements.

Trouble #4: Overloaded screens

Task: Improve user interaction with information on the screen.

Issue: A large number of paragraphs and nested sections results in a cluttered interface. This may lead to an unpleasant user feel, particularly for advanced users.

Recommendation:

Rethink sections and iterate on nesting information. Brand on-screen navigation easier by adding sections. Transition to new screens and use overlays for separate contextual information.to reduce the burden on users.

Good Points

A lot of useful data without logging in/signing up to the app.
Easily-understandable navigation.
Users can make common transactions in a few clicks.

8. Artful and minimalist design

Less is often more in an app pattern. Adding more than data than required may overwhelm and confuse users. Instead, ask whether it is necessary before adding in elements, features, or information to the app. The app should exist strikingly uncomplicated, still allows users to easily achieve their purposes.

Trouble #1: Not enough dissimilarity betwixt important elements and descriptions.

Job: Adjust and structure the information based on bureaucracy and priority.

Effect: At that place is a lack of contrast between of import graphics and texts. The poor choice of colors and typographies results in the failure of displaying the information vividly to the users.

Recommendation: Highlight the differences between primary and secondary data with the right dissimilarity. Use the right color, size, and typography to display information unambiguously. Keep information simple and reduce unnecessary elements to simplify user navigation.

Problem #2: Unnecessary contour on the internal screen

Task: Define where the profile information ought to be shown in the awarding architecture.

Effect: The profile call icon is displayed in random and non-obvious places, making it hard for users to admission contour information.

Recommendation: Define the architectural mapping of the profile in the application, i.e. in the carte du jour or settings. Decide the level of the profile to be displayed.

Problem #three: Unlike features overloading the chief screen.

Task: Organize and construction data on the main screen based on bureaucracy and priority.

Issue: The principal screen is overloaded with different features which cause overlapping and confusion. Some information in the dialogue is suppressed by others, making them insignificant.

Recommendation: Create a minimalist pattern without unnecessary elements that could disrupt the user feel. Reduce uncertainty by removing redundant content and redistribute functionality past reducing on-screen content.

Problem #4: Overloaded Account Page, which does non split up 'Profile Settings" and "Profile Information"

Task: Restructure the overloaded account page.

Issue: The profile screen contains besides many items that are non relevant in context.

Recommendation: Change the application's structure past adding an additional 'Settings" carte du jour particular. Place related contextual items in the new carte item.

Problem #five: Lack of visual hierarchy

Task: Review and edit phone details in Contour Settings

Issue: Information technology's difficult to define how the information is categorized. Too, there are issues with duplicate information.

Recommendation: Plant an business relationship visual hierarchy and restructure the data around information technology to provide clarity.

Problem #6: Too many similar information

Task: Choose the correct Account settings field to interact with.

Issue: Also much information that belongs to different parts are strikingly like.

Recommendation: Divide information on the 'User Profile & Settings and "Aid & Support" section. Rather than having them on the same list, keep the information on split up screens.

Trouble #7: Complicated navigation for this screen.

Task: To detect activity data.

Consequence: Navigation on this screen is an arduous process due to its complicated multi-level structure.

Recommendation: Restructure the information past decreasing the nesting levels and taking clarity into account.

Problem #8: Like style for icons and graphic elements

Task: To choose the right variant of back up for solving some issues.

Issue: Users are unable to distinguish between the icons as they look similar. As a event, users wasted time in reading through all the descriptions.

Recommendation:

Solution i: Delete similar icons.

Solution 2: Create a single mode for all icons and graphic elements to aid users recognize the features intuitively.

Problem #9: Visualization charts lack clarity

Task: To observe stats and contempo activity

Issue: The charts and graphs lack clarity, and in some cases, parts of the screens are empty and not purposeful.

Recommendation: Fix and amend how charts and graphs are visualized. Helpful details can be included in the empty areas.

‍

9. Assistance users recognize, diagnose, and recover from errors.

An app should have the intelligence to observe and help users to recover from errors. Instead of displaying error codes, the dialog should provide details and instructions intelligible to non-technical users.

Skilful points: The Chase app provides hints everywhere and includes field validations.

10. Help and documentation

Ideally, you'll want to build an app that intuitively lets users navigate through. Even so, in that location are some cases where users got stuck and in need of help. In such cases, help and documentation will come in handy, particularly those that are unproblematic and direct.

Good points: Users can easily access the documentation and support on the Hunt app.

Fixing Problems After UX Review

As you conduct a UX review, you could potentially observe more issues than our heuristic evaluation example. It will be prudent to employ an touch on/value map to determine which issues should y'all focus on.

Typically, you'll want to focus on issues that deliver high bear upon when they are stock-still. Based on this affect/value chart, we'll advise working issues that are to a higher place the line.

Summary

Delivering a seamless user experience is key to attracting and retaining users on your app. Nosotros've shown how to apply Heuristic evaluation with the Hunt app as an example in this article. With the same process, y'all're able to hone in on UX issues on your app.

brysongirese1941.blogspot.com

Source: https://www.uptech.team/blog/heuristics-analysis