The technical disciplines that keep heavy industry safe and productive, from geotechnical engineering to mining engineering and geology, are running short of people, and the shortage is the product of several causes compounding at once. Specialized university programs have thinned, a younger generation that values meaningful and flexible work is less drawn to the field, regulation has grown more stringent as executive tolerance for accidents has fallen, and a significant share of the existing workforce is expected to retire over the next five to ten years. Each pressure would be manageable alone; together they are draining the talent pool faster than it refills.
A second force runs underneath the first. The technologies introduced to manage technical risk do not reduce the demand for expertise; they raise it. When slope-stability radar arrived, it improved monitoring and simultaneously created a new set of demands the technical community had to meet for the tool to work at all. The result is that larger, more capable teams are needed precisely as they become harder to assemble, which makes a company's own development program more important than it has ever been.
Treat capability as a strategic enabler, not a training line item
The instinct in a downturn is to treat development as discretionary. The evidence points the other way. Organizations that prioritize and invest in skills are markedly more likely to anticipate and respond to change, to allocate talent where it is needed, to retain their high performers, and to innovate (Deloitte, 2022). Capability development, in other words, is not a welfare cost; it is one of the more reliable predictors of whether a technical function can keep pace with its own operating environment.
That reframing changes what a development program is for. The goal is not a library of courses but a structured way to understand the capabilities present in the business today and to build the skill sets it will need tomorrow, suitable for professionals at every level, region, and site, and balanced between those pursuing a technical career and those moving toward management.
"Many organizations continue to train and develop talent for the business of yesterday, while the competitive landscape for technical professionals becomes more intense and the gap in critical skills widens."
Decompose capability into skills, and skills into knowledge areas
Vague talk of "upskilling" fails because it never says what, precisely, is to be learned. We work from a simple taxonomy. A capability is the combination of people, processes, and technology that lets a company do what its strategy requires. A capability is made of skills, which are learned abilities, some technical and some interpersonal, that let a person accomplish a defined task. A skill, in turn, is made of knowledge areas, each of which can be taught in a classroom or learned on the job. Decomposing capability this way is demanding, because much of what an expert knows is tacit, but it is the step that makes everything downstream possible.
The decomposition is grounded in the work rather than in job titles. We define the deliverables a professional must produce to manage risk successfully, map those deliverables to the technical, business, and soft skills they require, and cross-reference the result against external sources so the final skills map is both complete and aligned with industry norms. A parallel exercise looks forward, anticipating how the work itself will change, through a pivot from in-field to remote operation, far broader data collection, real-time data-driven decisions, and scenario-based models to weigh uncertainty, and therefore which skills will matter most in the years ahead.
Build role profiles, then prioritize the skills that matter most
A large, global organization will carry a sprawl of role titles that obscures the underlying work. Grouping jobs by shared deliverables and skills collapses that sprawl into a manageable set of role profiles; in one program, well over a hundred distinct jobs reduced to six. Profiles describe responsibilities. A separate skills matrix then cross-references roles against skills and the proficiency each role requires, which is what turns the map into a tool for identifying training needs, assessing the workforce, and planning succession.
No organization can develop everything at once, so skills are prioritized on two axes: severity, the impact on the business if the skill is lacking, and scarcity, how rare the skill is across the organization. Plotting the two separates the primary skills that warrant purpose-built development from the secondary and tertiary ones that can wait, and a review by technical leadership keeps the priorities tied to the strategic needs of the business rather than to whichever gap is loudest.
Measure honestly, then teach through the right mix of methods
Proficiency is defined in explicit bands, foundational, intermediate, and advanced, each with the knowledge areas and behaviors that distinguish it, so that "advanced" means the same thing across the organization. A self-assessment tool lets each professional see the gap between their current and expected proficiency, compare confidentially against peers in the same role, and frame a development conversation with their leader around both their current role and the one they aspire to. The aggregate picture is often instructive in its own right: in one community, deep proficiency in long-standing safety skills sat alongside clear gaps in the future skills, such as coding, artificial intelligence, and machine learning, that emerging practice will demand, and in the business skills, such as trade-off analysis and cost estimation, that let technical staff make better decisions.
Closing those gaps draws on a deliberate mix of approaches rather than a default to classroom courses. Passive learning, through off-the-shelf or custom courses, suits codified knowledge. Active learning carries the rest: mentorship that transfers tacit expertise, job rotation that broadens exposure, secondment that builds outside perspective, and for the most demanding skills, a tutelage model in which a professional works through repeated review cycles under a senior lead. Not everything needs to be built in-house; much of the needed material already exists off the shelf, and the discipline is to curate thoughtfully, building only what is genuinely unique or critical and integrating the rest.
The lessons are clear: begin with the why and the jobs to be done before designing any module; embrace the complexity of decomposing tacit expertise rather than avoiding it; prioritize ruthlessly so the program equips people rather than overwhelming them; make learning accessible at the point of need; and design for pull, cultivating intrinsic motivation so participation is driven by demonstrated value rather than mandate. A program built this way produces a technical community that is more proficient, more resilient, and better aligned with where the work is going. Left unaddressed, the same gap surfaces as reduced design reliability, operational inefficiency, or a safety incident the lost expertise would have prevented.