Defragmenting You

Defragmenting You

or, When a bank asks for the same information because each team sees a different version of the customer

or, When a bank asks for the same information because each team sees a different version of the customer

Role

Service Design Principal

Discipline

Design Research · Service Design

Focus

Customer understanding and KYC service architecture

Approach

Interviews, journey mapping and service blueprinting

I led customer research and service design for HSBC’s corporate KYC programme, working across relationship management, operations, risk, quality control, and technology.

Periodic reviews crossed multiple teams, systems, and customer relationships. Mapping the service made that fragmentation visible before establishing a connected direction for KYC.

The existing KYC service blueprint across teams and customer touchpoints

The challenge was not simply to collect more customer information, but to make what HSBC knew available wherever the relationship moved.

Scattered Knowledge

HSBC was not short of people who understood its customers. The problem was that knowledge did not move reliably between them.

Knowledge existed across Relationship Managers, operational teams, systems, documents, and previous reviews. People were performing their individual roles inside a fragmented service, while the resulting effort was passed outwards to customers.

Customers asked again across contacts, departments and changing relationships
The proposed journey: use existing knowledge before asking customers for information

Before asking the customer, HSBC needed to ask itself.

The proposed journey gathered existing information first, identified genuine gaps, aligned the teams involved, and checked the request before making a formal information ask.

k-04A Data
K-04B Team
K-04C E2E

The Correction Loop

Quality checks could identify that something was wrong. But unclear feedback left customers to interpret what needed fixing.

Relationship Manager and customer views of feedback attached to requested information

Feedback travelled with the information it referred to.

Customer information moved through RM, CDD, and QC review. When something needed correcting, the feedback returned with the case rather than becoming another disconnected request.

K-06 Loop
K-07 E2E

Change Is a Constant

Customer knowledge lived partly in systems, but also in the relationships employees built over time. When those relationships changed hands, that knowledge did not always travel with them.

K-08 Aaron

Aaron’s company opened new accounts for individual productions. Recognising the customer meant understanding that repeated requests and delays had direct business consequences.

K-09 James

James had worked with his previous Relationship Manager for seven years. When the relationship changed hands, much of that understanding had to be rebuilt.

K-10A Data
K-10B Team

Knowing the customer meant preserving both the record and the relationship.

K-11 Illustration

One Connected Service

The project connected those fragments into a shared direction for KYC—across data, teams, workflow, quality, and customer relationships.

1

Connected service

5

Experience principles

6

Service strategies

21

Capabilities

K-12 Arch
K-13A Journey
K13B Improve
K-13C Reduce