KYC remediation is where financial crime programmes go to test their change-management maturity. The pattern is familiar: a gap is found, a population is scoped, a big number is announced, and eighteen months later the programme is at 40% completion with the deadline three months away.

Why remediations stall

The root cause is almost never analyst productivity. It is upstream: unstable requirements ('what does good look like for a trust?' being answered differently in month one and month nine), poor data quality that turns each file into an investigation, and outreach processes that assume customers respond to letters. Fix the requirement stability and the data enrichment first; throwing analysts at an unstable process just produces rework.

Segment ruthlessly

Treating a remediation population as one queue is the most expensive mistake available. Straight-through segments — where existing data already meets the standard — can often clear 30–40% of the population with quality assurance sampling rather than full review. Genuine high-risk files need senior reviewers from day one, not after the backlog is discovered. The middle deserves a standardised playbook with clear escalation triggers.

Measure completion honestly

A file is not remediated because it was touched; it is remediated because it now meets the standard and the evidence is retrievable. Programmes that report 'files actioned' discover the difference during independent review, at the worst possible moment. Build quality assurance into the run rate from the start and report completion net of QA failures.

The change-management core

Remediation is a delivery discipline. Weekly cadence, a single empowered decision-maker for requirement questions, visible burn-down against a realistic baseline, and early escalation of blockers. None of this is novel — which makes it striking how often it is missing.