What to test for, what to train, and why retention is a management problem.
7 min read · His Word Business Support Services
Most offshore engagements that fail do not fail because the talent was weak. They fail because the hiring process tested the wrong things, or because nobody managed the role once it started. Both are fixable, and both are decided before anyone’s first day.
Tool familiarity is the easiest thing to screen for and the least predictive. Someone who has never used your helpdesk will learn it in a week. Someone who cannot judge when to escalate will cost you customers for a year.
For support and admin roles, the useful test is a written scenario: an awkward customer email, an ambiguous instruction, a conflict between two priorities. You are not looking for a perfect answer. You are looking for whether they identify what is actually being asked, notice what is missing, and ask rather than guess.
For specialist roles — bookkeeping, CRM, media buying — give a small, real task with deliberately incomplete information. The strongest candidates come back with questions before they come back with work.
Written and spoken fluency are different skills, and roles need them in different proportions. A media buyer who writes clear weekly reports may rarely speak to a client. A customer service representative on phones needs conversational ease, comfort with interruption, and the ability to sound calm when a caller is not.
Test the one the role actually needs. A written test for a phone role tells you very little.
The first three weeks set the pattern. A new team member who spends them guessing — unsure what good looks like, unsure who to ask — either becomes cautious and slow or confident and wrong. Neither is recoverable cheaply.
Document the role before the first day, not during the first month.
A workable onboarding pack is short: the tasks, the tools and access, the standards, the escalation path, and five examples of finished work done well. That last item does more than any written instruction. People calibrate against examples.
Offshore roles turn over for predictable reasons: no path forward, no feedback, unclear expectations, and being treated as a resource rather than a colleague. Pay matters, but it is rarely first on the list when people explain why they left.
What holds: regular feedback that is specific, work that grows, a manager who is reachable, and being included in the context around the work. A team member who understands why a report matters produces a better report.
This is the part clients often expect a provider to handle entirely. A provider can and should handle employment, supervision, and development — but inclusion is yours to give. A weekly fifteen-minute call from the person whose work it supports changes retention more than most incentives.
Every role needs a trained backup and a documented process, from the start. Not when someone gives notice — by then it is too late, and you will spend the notice period extracting knowledge instead of transferring it.
The test is simple: if this person were unavailable tomorrow, could someone else pick up the work from what is written down? If not, the role is a single point of failure regardless of how good the individual is.
Agree up front what gets reviewed, how often, and against what. Weekly for the first month, then monthly, is a reasonable default. Review output against the scope, not against a feeling about how things are going.
Roles reviewed regularly stay aligned. Roles reviewed only when something goes wrong teach the team member that attention means trouble — which is the fastest way to stop hearing about problems early.
By the end of the first quarter, a well-hired and well-managed role should be operating without daily direction, escalating the right things, and producing work that matches the examples they were given. If that is not the case, the cause is usually traceable to the scope, the onboarding, or the review cadence — not the hire.
A discovery call turns the general principles here into a scoped role for your operation.
