A fintech startup CEO recently hired a CHRO from a Fortune 500 bank. Twenty years’ experience, managed 5,000+ employees, built award-winning programmes. Within six months, the company was drowning in approval hierarchies whilst competitors hired faster. The CEO was baffled. He’d hired brilliance. What went wrong?
Everything—because he’d hired credentials for the wrong context.
But it’s not just startup versus corporate. A manufacturing CHRO joining IT services faces similar failure. So does an IT CHRO joining BFSI. An e-commerce CHRO struggles in pharmaceuticals. A services CHRO flounders in product companies. HR expertise doesn’t transfer across contexts because the contexts demand fundamentally incompatible skills.
The statistics expose this confusion. Average CHRO tenure stands at just 4.5 years globally. In India’s BSE 100, it’s worse: 27 per cent appointed new CHROs in 2024 alone—three times the global average. More than half have changed jobs in the past 3.5 years. When 56 per cent of Indian appointments come externally versus 39 per cent globally, organisations are admitting they can’t develop the HR leadership they need. Yet they keep hiring the wrong profiles.
CEOs treat HR as transferable expertise when it’s actually context-specific capability. They’re making the same mistake repeatedly across every dimension of context that matters.
The industry blindspot
Consider what manufacturing HR actually does: managing 10,000 factory workers across shifts, negotiating with powerful unions, ensuring workplace safety compliance, coordinating with production schedules, handling blue-collar recruitment at scale. Success requires understanding shop-floor dynamics, labour law complexity, and industrial relations.
Now put that CHRO into IT services. Suddenly the challenges are: preventing 25 per cent annual attrition amongst knowledge workers, building talent pipelines for niche technical skills, managing billability and bench, creating career paths for engineers who don’t want management roles, competing with startups and global tech giants for the same talent pool.
These aren’t variations of the same job. They’re entirely different disciplines. The manufacturing CHRO tries to apply factory-floor thinking to knowledge workers. She implements attendance systems, creates rigid processes, focuses on compliance over enablement. Engineers leave. Projects suffer. The CEO wonders why someone so accomplished is failing so spectacularly.
The IT services CHRO joining manufacturing makes opposite mistakes. He tries to eliminate “bureaucratic” safety protocols, doesn’t understand why union negotiations can’t be “agile,” and implements performance systems designed for individual contributors in an environment requiring team coordination. Within months, he’s created compliance risks and labour unrest.
The regulatory mismatch
BFSI HR operates in one of the most regulated environments imaginable. Every hire undergoes background verification. Compensation structures follow strict guidelines. Risk management and compliance drive culture. Regulatory reporting is constant. Audits are frequent. The entire talent strategy revolves around risk mitigation and regulatory adherence.
An e-commerce company hiring a BFSI CHRO gets someone brilliant at compliance but terrible at speed. She implements verification processes that delay hiring by weeks. She creates approval hierarchies for routine decisions. She builds governance frameworks appropriate for banks but catastrophic for companies where speed determines survival. Competitors hire in days whilst she’s designing risk matrices.
The reverse fails differently. An e-commerce CHRO joining BFSI brings “move fast” thinking to an environment where moving fast creates regulatory violations. He streamlines processes that existed for legal reasons. He pushes hiring speed over verification rigour. He treats compliance as bureaucracy rather than necessity. The first regulatory audit reveals the disaster.
Pharmaceuticals present similar challenges. A pharma CHRO understands clinical trial recruitment, scientific talent assessment, regulatory affairs complexity, and the patience required for decade-long product development cycles. Moving to consumer goods, that same CHRO is lost—the pace is faster, the talent requirements completely different, the regulatory environment unrecognisable.
The business model dimension
Product companies and services companies require opposite HR approaches. Product companies need small teams of exceptional engineers building for years. Services companies need large teams of competent professionals delivering for months. Hiring, retention, development, and performance management differ fundamentally.
A product company CHRO focuses on finding rare technical talent, providing autonomy, enabling long-term thinking, and accepting that great engineers are expensive and worth it. A services company CHRO focuses on hiring at scale, managing utilisation, ensuring consistent delivery quality, and controlling costs because margins are thin.
Swap them, and both fail. The product CHRO joining services can’t hire fast enough, pays too much, gives too much autonomy, and destroys margins. The services CHRO joining products commoditises talent, implements utilisation tracking inappropriate for product development, and drives away the exceptional engineers the company needs.
The stage-and-scale trap
Then there’s the startup-to-corporate challenge everyone recognises but few solve. Startup HR is entrepreneurship: betting on raw talent, stripping away approvals, building trust without brand reputation. Corporate HR is systematic governance: managing executive egos, protecting culture at scale, balancing five-generation workforces.
The startup CHRO joining an established company tries to “inject energy” by eliminating processes she sees as bureaucratic, not recognising they exist because previous leaders learned expensive lessons. The corporate CHRO joining a startup implements frameworks that kill the speed making startups competitive.
Russell Reynolds found that 66 per cent of new CEOs replace their CHRO—not because the CHRO is incompetent, but because context changed. What the previous CEO needed differs from what the new one needs. When organisations shift from growth to profitability, from domestic to global, from product to platform, the HR requirements transform. The CHRO who was perfect for yesterday becomes liability for tomorrow.
The questions CEOs don’t ask
The hiring mistake stems from asking generic questions. CEOs interview asking about systems built and scale achieved. These reveal what someone did elsewhere—not whether they can succeed here.
For manufacturing, ask: How do you negotiate with unions who can shut down production? How do you ensure safety compliance across shifts? How do you recruit blue-collar workers at scale? IT services CHROs answer poorly because they’ve never faced these challenges.
For IT services, ask: How do you prevent attrition when engineers have five offers? How do you build bench without destroying margins? How do you create career paths for technical specialists? Manufacturing CHROs struggle because their experience is irrelevant.
For BFSI, ask: How do you hire under intense regulatory scrutiny? How do you build culture around risk management? How do you maintain compliance whilst enabling business? E-commerce CHROs have no reference point.
For startups, ask: How do you recruit against companies with ten times your budget? What rules did you break that others wouldn’t? Corporate CHROs can’t answer because they’ve never had to.
CEOs asking generic questions get generic answers that don’t reveal context fit. They hire impressive résumés that fail in practice.
What actually transfers (and what doesn’t)
Some capabilities do transfer: talent assessment, coaching senior leaders, managing executive conflicts, building compensation frameworks. These are foundational HR skills that work across contexts.
What doesn’t transfer: industry knowledge, regulatory expertise, business model understanding, cultural fluency, stakeholder networks, pace calibration. These are context-specific and take years to develop. A CHRO changing industries essentially starts over on these dimensions—they’re experienced HR professionals but context novices.
The tragedy is that CEOs hire for the transferable skills—”built talent function,” “managed large teams,” “implemented systems”—whilst ignoring the non-transferable ones that actually determine success. They optimise for credentials whilst missing context.
The expensive lesson
Failed CHRO hires cost more than salary. They cost competitive advantage when hiring slows in fast-moving industries. They cost culture when wrong processes get implemented. They cost compliance when regulations get misunderstood. They cost momentum when organisations get restructured for contexts that don’t exist.
A manufacturing company hiring IT services credentials wastes months implementing processes appropriate for knowledge workers in an environment requiring shift coordination. An IT services company hiring BFSI credentials creates approval hierarchies destroying the speed that made them competitive. A startup hiring corporate credentials builds governance strangling agility.
The irony: CEOs spend enormous time hiring other C-suite roles, recognising context matters. CFOs from retail struggle in SaaS. CTOs from product companies flounder in services. Sales leaders from enterprise fail at SMB. Everyone understands this—except for HR, where CEOs assume experience transfers regardless.
It doesn’t. The 4.5-year average tenure, the 27 per cent annual turnover in India’s BSE 100, the 56 per cent external hiring rate, the two-thirds replaced when CEOs change—these aren’t random statistics. They’re evidence of systematic misunderstanding.
The path forward
CEOs must stop hiring HR credentials and start hiring context fit. This requires acknowledging uncomfortable realities:
Someone brilliant at manufacturing HR will likely fail at IT services. Someone exceptional at BFSI will probably struggle at e-commerce. Someone perfect for startup phases becomes liability at scale. This isn’t criticism of their capabilities—it’s recognition that capabilities are context-dependent.
The solution isn’t avoiding external hires—it’s hiring for context match rather than impressive résumés. When contexts align—manufacturing to manufacturing, IT services to IT services, BFSI to BFSI—external experience transfers beautifully. When contexts diverge, credentials become irrelevant or actively harmful.
The smartest CEOs recognise this. They hire HR leaders who’ve succeeded in similar contexts rather than bigger ones. They value relevant experience over impressive scale. They understand that someone who built HR for a 500-person services company is better qualified for their 1,000-person services company than someone who ran HR for 10,000 people in manufacturing.
Until more CEOs understand this, they’ll keep making expensive mistakes, wondering why impressive credentials produced disappointing results. The answer is simple: credentials aren’t context. In HR leadership, context is everything.
1 Comment
Very well described! Thanks. Best Wishes-Alok