When one person's departure almost cost us the account

The unplanned departure of a key contributor, combined with a remote service model for a fully in-person client, sank the account's metrics. A personal on-site intervention, plus an structural switch from a remote to a local position, reversed the trend and rebuilt trust.

The underlying mismatch: in-person on one side, remote on the other

A key contributor responsible for a complex South American banking account left unplanned. The client had a quirk that aggravated everything else: its work culture was 100% in-person — the client's team went to the office every day — while our service model for that account was remote, and the person we'd been preparing to take over didn't regularly visit the client's offices.

An emergency onboarding with the talent we had on hand

Out of urgency, we sent someone from Mexico to do the onboarding on site, with my remote support. The problem: that person was at technical level N1 — their client handling and advanced topics weren't the strongest we'd have wanted for a transition of this size.

Metrics sink: partial adoption, incomplete training, and real unfamiliarity

Metrics dropped considerably as soon as the new operation started. It wasn't a single factor — it was partial adoption, incomplete training, and genuine unfamiliarity with the tool and the processes, all at the same time.

Traveling: to train and to convey reassurance in person

I decided to travel personally. Not just to train — to convey reassurance to the client in person, something no remote call was going to achieve at that moment. During that visit I identified the real workload and the specific tasks driving the metric deviations — not the ones we assumed from afar, but the ones actually happening day to day.

The structural change: from remote to local

That led to the structural change: converting a remote position in Mexico, which served that account from afar, into a local L1 support position — the kind of work that consumed the most operational time and made the least sense to solve remotely for a client with that in-person culture.

Recovering the metrics and the trust

That visit, plus the plan to strengthen on-site support, was what let us recover the metrics and rebuild trust with the account. At the end of my involvement with that project, the client-side account lead said goodbye warmly and cordially, explicitly acknowledging my contribution.

The cost of lost knowledge, in data

The data that shows why this isn't a minor anecdote: according to recent research on organizational knowledge loss, 59% of companies report direct client impact after the departure of a key employee, and 30-40% of companies experience measurable deterioration in the account relationship after an account manager turns over. McKinsey estimates that, for roles with direct client contact or proprietary processes, rebuilding that knowledge costs 25-50% of the departed person's annual compensation — before even counting the account that might have been lost along the way.

The lesson

The lesson I take: when one person's departure threatens an account, the fix isn't just putting someone else in the seat — it's diagnosing, on the ground if needed, the exact combination of service model and talent level that specific client needs, and having the willingness to change the structure, not just the name on the org chart.

Data sources: recent research on organizational knowledge loss (59% of companies report direct client impact after a key employee's departure; 30-40% experience measurable deterioration in the account relationship after an account manager turns over); McKinsey — estimate that rebuilding knowledge costs 25-50% of the departed person's annual compensation, for roles with direct client contact or proprietary processes.