Wholesale eSign

Estimated read time: 10 mins
Dec. 2021–Mar. 2022, Professional Project

Project Overview

A seamless eSign journey containing document management.
‍

My role

UX/UI designer

Keywords

B2E, Tablet design, Shared eSign journey, Supporting document management, System integration, Pattern alognment

Background

Wholesale eSign (on tablet) supports Business Relationship Manager to conduct eSign journey with customers shoulder by shoulder during Insurance, Business Loan, Mortgage application journey and etc.

In the past, there was a lack of order in system management. Depending on the type of business, users had to rely on multiple different outdated systems and even paper form to perform the same functionalities. Now, we have integrated the old systems into a shared platform that can be utilized by different business segments, promoting collaboration and efficiency.

Design opportunities

This system update enhance the sales users productivity in interacting with the customer through digital way.

Meet requirements different business line.
Establish a unified process.
Combine Document managment, Take photo, Signing into one application.

Design Process

Design process

When customer comes to Business Relationship Manager and ask for relevant services, the customer and manager will go as:

High-level architecture

This high-level flow encompasses the desired functionalities to be implemented within the user journey through integrating the requirements put forward by the business stakeholders.

Instead of starting over and completely redesigning the entire user journey, the ultimate goal of this design iteration is to consolidate the functionalities scattered across different systems into a unified entry point, like eSign, Photo taking component, etc.

UX Flow

Pattern Alignment

Since there are similar instances in other user journeys where multiple operations are performed on files, this project Wholesale eSign serves as a pilot to establish a commonly used design alignment.

Let us first divide this issue into two levels for the purpose of discussion. The first level is the information display aspect, and the second level is the action aspect.

Information Display

In most cases, these documents that need to be processed require the display of supplementary information, for example, document update time, document status.

By using tables to hold the files and their supplementary information, we could effectively display them all at once.

Action Placement

Actions towards individual file

Using table can also neatly list out specific actions towards each file.

Using representative file names as clickable text links serves as the entry to access and view the files at a read-only state.

Actions towards file group

Some actions, such as uploading files and taking photos, have an impact on the entire file group. These actions will be placed close to the file group, but outside of it.

Pattern Layout