Workplace Effectiveness · 7 October 2026
Skills-Based Hiring and Internal Mobility: Beyond the Rhetoric
Most internal mobility initiatives stall within a year because organisations hire for skills but still promote for tenure. Here is how to fix the structural disconnect.
The Learning Insights · 8 min read
Every major corporate talent summit over the past three years has featured at least one panel on the shift away from credentials toward capability. Chief human resource officers speak passionately about breaking down functional silos, cataloguing competencies, and deploying talent dynamically across projects. Yet walk through the corridors of almost any enterprise a year after they announce such an initiative, and the reality looks remarkably familiar. Companies loudly announce that they practise skills based hiring and internal mobility, and then quietly promote people based on tenure, visibility, and how inconvenient it would be for a department head to lose them.
This contradiction is why most internal talent marketplaces stall roughly twelve to eighteen months after launch. The software is purchased, job descriptions are stripped of arbitrary degree requirements, and employees are encouraged to tag their skills in a profile database. Then an opening appears for a critical product management role. An internal candidate from customer support who has spent two years teaching herself system architecture and writing technical documentation applies. The hiring manager glances at her resume, notes that she has never formally held a product manager title, and hires an external candidate who held that exact title at a competitor for three years. The internal mobility project dies not from lack of intent, but from an institutional refusal to trust skill evaluation when actual risk is on the line.
The fundamental misunderstanding of skills versus roles
To understand why capability-first mobility fails, one must examine how organisations historically defined work. For nearly a century, corporate progression was built on the logic of the bureaucratic container. A role was a fixed set of responsibilities, and progression meant moving from a smaller container to a larger one. Tenure served as a crude proxy for reliability. If someone survived four years as an analyst without incident, the organisation assumed they were ready for senior analyst duties, regardless of whether their underlying analytical capability had expanded or merely hardened into habit.
When organisations attempt to graft a capability model onto this container system without altering incentives, friction is inevitable. A skill is not a static credential. It is context-dependent, decays without application, and combines with temperament in ways that traditional job architectures cannot capture. Knowing Python in an academic context is very different from refactoring legacy code under production deadlines. When leadership teams treat capability as a checklist of keywords, they create an illusion of precision that crumbles the moment a manager needs a dependable outcome.
Furthermore, true career development requires cross-functional exposure, but middle management incentives actively penalise managers who export their best talent. If a regional operations director spends eighteen months coaching a high-performing associate, that director has zero incentive to release the associate to a strategy team. The current system rewards talent hoarding. Until performance metrics reward leaders for exporting capability to the rest of the business, skills-based internal mobility will remain an aspirational HR slide deck rather than an operating model.
Why tenure still wins the promotion argument
The persistence of tenure-based promotion is rarely driven by ignorance. It is driven by risk mitigation. When a leadership team must appoint someone to head a troubled business unit or steer a new client implementation, they look for predictable behaviour under pressure. Tenure provides a verifiable track record of organisational survival. It tells the decision-maker that the candidate understands the unspoken political landscape, knows who to call when systems fail, and can endure corporate ambiguity without resigning abruptly.
This dynamic explains why the first-time manager transition is so frequently mishandled. Companies routinely elevate the most tenured individual contributor to team lead, confusing operational endurance with the nuanced ability to coach, delegate, and resolve team conflict. When that individual struggles, the organisation blames leadership readiness rather than their own flawed selection criteria.
What conventional corporate talent models get wrong is the assumption that skill assessment is objective while tenure assessment is lazy. In truth, assessing actual behavioural capability is intellectually demanding and culturally uncomfortable. It forces managers to evaluate whether an employee possesses rigorous problem solving and decision making ability or simply a habit of deferring tough choices up the management chain. Tenure, by contrast, is indisputable. No one can argue about whether someone has sat in a seat for thirty-six months. It is safe, defensible, and disastrous for dynamic capability building.
The reality of internal mobility in practice
Consider what happens when a mature manufacturing firm attempts to pivot into digital industrial services. Leadership recognises that they need agile project managers who can bridge shop-floor engineering with cloud software development. Under a genuine skills-based regime, they would scan the organisation for individuals demonstrating systems thinking, cross-functional persuasion, and adaptability, regardless of their current business unit.
Instead, the initiative typically follows a predictable four-stage lifecycle:
To break this cycle, the focus must shift from cataloguing skills to restructuring how work is allocated and how managerial capability is built. If a company wants people to develop high-order competencies, it must provide environments where they can practise accountability and ownership on bounded, real-world assignments before asking them to make a high-stakes leap into an entirely new functional domain.
When an organisation claims to value adaptability but only rewards linear service, employees quickly learn that taking lateral development risks is a career liability.
- The Technology Phase: The organisation purchases a talent intelligence platform. Employees are asked to self-report their skills, resulting in a database filled with inflated self-assessments and outdated certifications.
- The Pilot Phase: A handful of visible lateral moves are orchestrated by executive sponsorship to demonstrate early success. These moves are celebrated in town halls as evidence that the new philosophy works.
- The Managerial Resistance: Frontline and mid-level managers realise that releasing strong performers leaves them understaffed, while accepting internal transfers from unfamiliar departments requires extensive onboarding time that their quarterly targets do not accommodate.
- The Quiet Reversion: Hiring managers bypass the internal platform entirely, posting requirements externally or choosing internal candidates who have simply waited their turn in the traditional hierarchy.
The distinction between operational skill and behavioural maturity
Much of the current industry noise conflates technical tasks with core behavioural capabilities. A candidate can master data visualisation software in three months of dedicated study. What takes far longer to develop is the contextual judgement required to understand what that data means for a sceptical board, or the emotional discipline required to handle intense interpersonal pushback during a restructuring.
As explored in our analysis of the skills to advance your career, the attributes that actually govern sustained career velocity are rarely technical competencies. They are interpersonal influence, commercial acumen, clarity of thought under stress, and resilience. A skills taxonomy that lists seventy technical proficiencies but ignores an individual's capacity for constructive collaboration is functionally useless for predicting performance in higher-complexity roles.
When evaluating readiness for internal progression, organisations must distinguish between three distinct layers of capability:
Most internal mobility platforms focus obsessively on the first layer because it is easy to codify. Yet lateral mobility almost always succeeds or fails based on the second and third layers. When an engineer moves into enterprise product marketing, their technical knowledge provides context, but their communication discipline determines their actual impact.
- Domain Expertise: The specific tools, methods, and operational knowledge required to execute immediate tasks within a specific department.
- Cognitive Agility: The capacity to parse ambiguous information, identify root causes, and structure solutions in unfamiliar operating environments.
- Relational Capability: The ability to build trust, navigate competing stakeholder interests, and communicate complex concepts without relying on formal authority.
What genuine capability-based progression requires
If an executive team genuinely wants to move past the rhetoric of skills based hiring and internal mobility, they must confront the structural realities of their organisation. First, they must dismantle the career ladder and replace it with a transparent project economy. High-potential talent should spend ten to fifteen percent of their time contributing to cross-functional problem-solving sprints outside their primary department. This provides proof of capability in action, eliminating the reliance on subjective manager recommendations or self-reported profile tags.
Second, performance reviews for people managers must include explicit metrics on talent export. A senior manager whose team members regularly advance into critical roles across the broader enterprise should be compensated and promoted ahead of a manager who delivers steady results by trapping high performers in repetitive tasks. This aligns managerial self-interest with organisational capability development.
Finally, the enterprise must invest in rigorous leadership development that trains managers how to assess human capability accurately. Evaluating whether a team member possesses genuine leadership potential requires structured observation, psychological safety, and meaningful feedback loops. It cannot be delegated to an algorithmic matchmaking engine.
The central question for modern organisations
The debate over skills versus tenure is ultimately a debate over organisational courage. Tenure is comfortable because it distributes responsibility across time. Skills-based progression is demanding because it forces leaders to take responsibility for evaluating human potential directly and building environments where talent can prove itself through work, not waiting.
If your organisation audited every promotion made across your senior business units over the past twenty-four months, would you find a map of where capability truly resides, or merely a list of who stayed long enough to avoid being passed over?