Kotak Mahindra Bank

Compliance training is episodic, regulatory, and focused on prevention of known risks. A competency framework is continuous, developmental, and focused on building observable behaviours across every role in the organisation. Compliance training answers 'what must they know to stay compliant?' A competency framework answers 'what must they demonstrate to progress?' Both are needed. Only the second retains people.

Because the exit interviews at Kotak, as at most BFSI organisations, revealed that the top departure driver was not pay — it was the absence of a visible growth path. Once every role in a career family had a defined 4-level proficiency map, and once quarterly competency conversations replaced annual ratings, high-performers stopped leaving because they could now see the next six years of their career without leaving the organisation.

Three directly attributable metrics: (1) attrition reduction — 17-point drop at Kotak translated to ~₹12-18 crore annual retention savings based on replacement-cost benchmarks; (2) time-to-productivity — 5-week reduction per new hire across 2,000+ learners is a compounding productivity gain measured in quarterly output; (3) board-approved budget expansion — the 2.1x L&D budget increase the following FY was the commercial proof that the framework had moved from cost-centre artefact to capability infrastructure.

Yes — because the library is behavioural, not functional. IT engineers and branch relationship managers share more overlapping competencies (judgment under ambiguity, stakeholder communication, compliance discipline) than org charts suggest. The framework calibrates at the behavioural-family level and varies only at the role-specific application layer. One library, 8 role families, 263 validated statements, 4 proficiency levels — the architecture flexes across functions without fragmenting.