Most organizations trying to improve DEI outcomes at the manager and above levels focus on the same levers: bias training, structured interview rubrics, diverse slates for open roles, sponsorship programs. These are not wrong interventions. But they operate at the point of the promotion or hiring decision — after candidates have already self-selected in or out based on whether the path to that role looked viable for them.
The earlier failure point is invisible in most talent management systems: qualified internal candidates never surface as candidates at all, because the systems that identify promotion readiness are built on job history and title trajectory rather than actual skill distribution. When you replace job-history matching with skill adjacency analysis, the candidate pool for growth paths changes — and for most organizations, it changes in ways that are directly relevant to DEI goals.
Why Job-History Matching Produces Homogeneous Candidate Pools
The traditional internal mobility logic is linear: to be considered for a Senior Product Manager role, you should currently be a Product Manager. To be considered for a Director of Engineering role, you should currently be a Senior Engineer or Engineering Manager. These title-to-title progressions feel logical because they're what has historically worked — for the subset of people who followed that exact trajectory.
The problem is that job-history-based promotion filtering encodes the existing demographic profile of those historical career paths. If the people who have historically moved from Engineer to Engineering Manager at your company are disproportionately from one demographic group, a system that identifies promotion candidates by "has this role title and this tenure" will disproportionately surface the same demographic profile. Not because of explicit bias in the system logic — because the data reflecting past career outcomes carries historical access disparities forward.
Skill adjacency analysis asks a structurally different question: which employees currently hold the skills that the target role requires, regardless of what title they hold now? This opens the search to employees in laterally related roles — customer success managers who have developed quantitative data analysis and stakeholder communication skills at the depth the product management role requires, or data analysts who have been building workflow automation systems that overlap significantly with the operational skills a product operations manager role needs.
What Skill Adjacency Actually Measures
Skill adjacency, in the context of promotion pipeline design, is a measure of the skill overlap between an employee's current assessed capability and the minimum proficiency requirements of a target role. An adjacency score above a threshold — say, 70% of required skills met at minimum proficiency or better — flags that employee as a viable candidate for a structured promotion pathway, regardless of their current title.
This is different from saying anyone with adjacent skills is ready for the role today. The adjacency score identifies that the remaining gap is bridgeable — that the employee has the foundation from which a defined reskilling path can close the delta without requiring a complete capability rebuild. A customer success lead with strong analytical skills, stakeholder management depth, and product sense who lacks formal roadmap prioritization experience has a fundamentally different and shorter path to a PM role than a first-year analyst with no adjacent skills at all.
The adjacency threshold matters and needs to be calibrated per role. Setting it too low creates false positives — candidates flagged who would need more development investment than the organization can practically provide. Setting it too high recreates the title-trajectory filtering it was designed to replace. For most managerial and senior individual contributor roles, 65–75% skill overlap at minimum proficiency tends to identify candidates for whom a 6–12 month structured pathway is realistic.
A Concrete Scenario
A growing financial services operations firm wanted to build a more diverse pipeline into their data analytics management roles. Their existing path was narrow: analysts hired into the data team, promoted to senior analyst, then considered for management. The demographic composition of that pipeline was heavily skewed toward candidates from quantitative academic backgrounds, which had its own demographic patterns.
When they ran skill adjacency analysis against the data analytics manager role-skill matrix — which required SQL proficiency, statistical analysis, stakeholder communication, project scoping, and team coordination — they identified a significant secondary cluster of candidates in their operations and compliance teams. These were people who had developed analytical skills through day-to-day work with regulatory data, built strong stakeholder communication skills through cross-functional compliance work, and had taken on informal coordination roles in multi-team projects. None of them were data analysts by title. Most of them had never been considered for the analytics management track.
The adjacency scores for this cluster showed 65–80% skill coverage of the role requirements. The gap skills — primarily SQL proficiency and formal statistical methods — were both learnable through structured programs. The firm ran a 9-month cohort program for 12 candidates from this pool. Seven completed the pathway within the target timeline. Three moved into data analytics manager or lead roles within 14 months of the program start.
We're not saying skill adjacency analysis is a complete DEI solution. Organizations still need to address bias in the promotion decision itself, retention factors, and the structural conditions that affect who develops which skills over time. But surfacing qualified candidates who were invisible under the old filtering logic is a necessary precondition for everything else to work.
Building the Adjacency Analysis Infrastructure
Running skill adjacency analysis at organizational scale requires two things that most HRIS systems don't natively provide: a role-skill matrix with proficiency thresholds for target roles, and assessed skill proficiency data for employees (not just self-declared skill presence).
The role-skill matrix work is the more tractable problem. For each role that is part of the target promotion pipeline, define 8–15 skills that are most critical for success at minimum proficiency. This definition work requires input from current role-holders and their managers, not just job descriptions — job descriptions systematically under-specify the actual skill requirements of senior roles.
The harder problem is proficiency data. Self-declared skills on HRIS profiles are not reliable enough to identify adjacency gaps with the precision needed for promotion path design. You need assessment signal: structured skills assessments, project contribution data, manager-validated ratings, or certification records. The quality of the adjacency analysis depends directly on the quality of this underlying data. Organizations that have been running structured skills assessments for 18 months or more have meaningfully better data quality than those starting from scratch — which is an argument for building the assessment infrastructure before the promotion pipeline design, not after.
What the Candidate Experience Looks Like
One operational consideration that often gets underweighted: how the identification process is communicated to employees matters for the program's effectiveness. Being told "our system has identified that you have skill adjacency to a role we think you should consider" is different from "we've been watching your career and believe you have untapped potential." The first framing is transparent about the methodology. The second is the vague sponsorship language that employees — particularly those who have been overlooked before — often greet with justified skepticism.
Programs that explain the adjacency methodology, show employees their skill coverage map against the target role, and provide a clear and specific account of the gap-to-close tend to generate higher candidate acceptance rates. The data visibility makes the offer feel concrete rather than aspirational. Employees can evaluate it themselves: "I can see I'm at 72% coverage, I can see the specific skills I'm missing, and I can evaluate whether that development path makes sense for me." That's a different decision than accepting an invitation to an ambiguous "leadership development opportunity."
The skill adjacency framing also changes the internal mobility conversation from a one-time promotion event to an ongoing question — which employees are building adjacency to roles they might want in 12 or 24 months, and are we structuring their current work and development to accelerate that adjacency? That shift from event to process is where the long-term pipeline improvement happens.
