Ask a relationship manager to describe a client’s experience and the answer may follow the visible relationship: enquiry, conversation, onboarding, regular reviews and trusted advice over time.
The client experiences all of that. They also experience the spaces where the relationship manager is absent: completing identity checks, locating a report, interpreting a communication, resetting access, changing a detail or waiting for a routine request to be processed.
Those interactions are distributed across operations, compliance, technology and external suppliers. No one person sees the whole journey, so a firm can deliver excellent advice and still make ordinary client tasks unnecessarily difficult.
The “journey nobody has mapped” is rarely completely unknown. Pieces of it exist in process diagrams, service tickets, portal analytics, complaints and the practical knowledge of employees. The work is to assemble those pieces from the client’s point of view.
Map what happens between the meetings
Relationship quality can mask digital and operational friction. A client who cannot retrieve a document may call an adviser who solves the problem helpfully. The call confirms the strength of the human relationship while hiding the failure of the service around it.
That distinction matters when leaders rely mainly on adviser feedback. Advisers see the recovery and may never see the failed login, confusing label or inaccessible report that caused it.
Start with observed behaviour:
- What are clients trying to accomplish between meetings?
- Which channels do they try first?
- Where do they abandon a task or ask an employee to complete it?
- Which interactions generate repeated calls, corrections or manual intervention?
- Where does the formal process differ from what people actually do?
Avoid assuming that every call is waste. Some clients value speaking with a person, and some requests require judgement or security checks. The goal is appropriate choice and reliable service, not maximum self-service.
Four areas where friction often concentrates
Onboarding and verification
Financial services onboarding can involve identity, suitability, financial crime controls, terms, consent, accessibility needs and the collection of sensitive information. The requirements vary by firm and service. A smoother journey cannot weaken the controls.
Map the client’s actions as well as the internal process. Do they know why each item is required? Can they pause and return? Are requests coordinated? Does the method work with assistive technology and on a suitable device? What happens when a document is rejected or an automated check fails?
A digital workflow may reduce duplication and provide useful status information. Paper, phone or supported routes may remain necessary for inclusion and exception handling. The best design is the one that meets the applicable obligations and works for the clients the firm actually serves.
Measure completion time, abandonment, repeat requests, support contacts, errors and exceptions. Segment the evidence so an acceptable average does not conceal a group that struggles.
Reports and access to information
Clients need different information at different moments. A regulatory or contractual report has a formal purpose. A client preparing for a review may want a concise explanation, current position or access to a previous document.
Do not assume a real-time dashboard is automatically better than a periodic report. Data latency, interpretation, market movement, service type and client vulnerability can all affect what is appropriate. Establish the client’s question, the source and status of the information, and the explanation or warning needed to use it responsibly.
Test the complete access journey on the devices and browsers clients use. A page that technically responds to a mobile screen may still contain unreadable charts or downloads designed only for print. Include authentication, session expiry, password recovery and support in the test.
Useful measures include successful retrieval, time to complete, repeated login failure, calls prompted by the report and client understanding. A download count by itself says little.
Communication and comprehension
Financial communications may need prescribed content, approvals and durable records. Those constraints do not require the surrounding explanation to be impenetrable.
Map the purpose of each communication, the action expected from the client and the questions it generates. Separate legally or regulatorily required language from internal convention. Qualified legal and compliance specialists should decide what can change; content designers and client teams can then improve hierarchy, explanation and channel within those boundaries.
Test comprehension with representative clients. Ask them to explain what the message means and what they would do next. Approval by an internal expert is evidence of technical accuracy, not evidence that a client can use it.
Accessibility, language, vulnerability and channel preference belong in this review. A message may be clear in isolation and fail because the client cannot access the attachment or obtain help.
Routine service and self-service
Address changes, document requests and updates to instructions can absorb employee time while giving the client little sense of value. They are sensible candidates for service redesign when demand is frequent and the task can be completed safely.
Use operational data to select candidates. For each request, map authentication, authority, fraud risk, processing, confirmation, records and exception handling. Some changes may require a conversation or additional evidence. The self-service route should make those boundaries clear.
Prioritise tasks that combine high client effort, high volume and avoidable internal work. A sophisticated portal with low-value features will deliver less than a simple, reliable route for a task clients perform regularly.
Combine people who see different parts of the truth
A useful mapping group includes relationship managers, operations, compliance, risk, complaints, digital or technology colleagues, and people who support accessibility or vulnerable clients where relevant. Supplier participation may help for outsourced steps.
Client-facing staff provide relationship context. Operations staff know the workarounds, exceptions and queues. Compliance specialists explain obligations and control intent. Technology colleagues can identify what the systems record and constrain. None has the complete view alone.
Include clients directly through interviews, observed tasks or co-design. Internal disagreement is a prompt to seek evidence. If an adviser believes onboarding is straightforward and operations receives repeated support calls, both may be describing different client groups or stages.
Build the map from evidence
Choose eight to twelve important interactions across the relationship rather than trying to document everything at once. For each interaction, capture:
- the client’s goal and context;
- the actions and decisions required from them;
- the visible people, messages and interfaces;
- the back-stage process, system and supplier activity;
- controls and applicable obligations;
- delays, handoffs, errors and workarounds;
- evidence from clients and operations;
- the owner and measure of service quality.
Mark assumptions clearly. A workshop produces hypotheses and connects evidence; it does not turn internal opinion into client research.
Look for “recovery masking”, where skilled employees repeatedly save a poor process. The recovery may generate appreciative feedback while consuming capacity and leaving the underlying friction intact.
Also look for channel switching. A client who starts online and finishes by phone may be expressing preference, responding to complexity or escaping a broken journey. Analytics and a brief follow-up can help distinguish them.
Prioritise by harm, effort and learning
Retention impact is important and difficult to attribute. Use a broader prioritisation:
- possible harm to clients or regulatory outcomes;
- client effort and accessibility;
- frequency and affected groups;
- internal effort, rework and control weakness;
- commercial importance;
- confidence in the diagnosis; and
- feasibility of a safe improvement.
Begin with a change that can produce evidence. This might be a coordinated onboarding request, a clearer explanation alongside a report, a reliable document-retrieval task or better status information for a routine request.
Set a baseline and monitor both client and control outcomes. Faster completion accompanied by more exceptions or weaker verification is not an improvement. Fewer calls may be positive, unless clients have simply stopped seeking help.
The map changes the management conversation
Journey mapping makes the distributed service visible. Leaders can see that a portal problem may begin in policy, a confusing letter may create operational demand, and a helpful adviser may be compensating for an unreliable process.
The map does not prove that clients will leave because of friction. It reveals where the firm is asking the relationship to carry avoidable strain and where evidence is missing.
Distinction runs a structured client journey mapping workshop for financial services firms, so we have a commercial interest in facilitated work. A firm can run the exercise internally if it brings together the right perspectives, tests assumptions with clients and gives the group authority to address what it finds.
We also provide a friction audit tool covering onboarding, information access, communication and routine service, with observable indicators and a priority matrix. Use it as an initial diagnostic. The most valuable output is still the shared, evidenced view of what clients do when their adviser is not there to help.
