Tech skills crisis: three responses leaders can use now

Many teams assume the tech skills crisis can be solved by hiring more people. That response is understandable, but it rarely works on its own when the same skills are scarce across the market and the organisation has not changed how it develops, deploys, and retains capability.

The technology skills crisis refers to the gap between the digital capabilities organisations need and the skills they can reliably access through their current workforce, hiring market, and partner ecosystem. It is visible in cloud migration delays, cyber resilience gaps, overloaded data teams, stalled automation programmes, and software delivery backlogs that keep growing despite budget approval.

McKinsey’s research on the COVID-era acceleration of digital adoption remains a useful reference point. The firm reported that the share of digital or digitally enabled products in company portfolios accelerated by around seven years, based on responses from 899 C-level executives, and that many technology changes were expected to remain after the immediate crisis subsided. That finding still matters because it explains why the skills gap did not disappear when emergency transformation projects ended. Digital demand became part of normal operating expectations.

The result is a structural problem rather than a temporary recruitment inconvenience. Organisations now need software engineering, cloud operations, data, AI governance, cybersecurity, product management, and platform skills at the same time. Meanwhile, experienced people expect modern tooling, clear career paths, meaningful work, and flexibility. A salary increase may win a candidate, but it does not automatically create the internal conditions that make scarce talent productive or likely to stay.

The three practical responses: build, buy, and partner

Most leadership teams have three responses available. They can build capability by upskilling and reskilling employees, buy capability by hiring new permanent talent, or partner for capability through contractors, consultancies, managed service providers, and specialist vendors. The right answer is rarely one of the three in isolation. A stronger approach treats them as a portfolio, with each response solving a different timing and capability problem.

A useful decision framework has two axes: time-to-impact and strategic differentiation. Time-to-impact asks whether the organisation needs capacity in weeks, months, or several quarters. Strategic differentiation asks whether the skill is part of the organisation’s core advantage or a necessary but more standard capability. When work is urgent and relatively standard, partnering can provide fast relief. When a capability shapes core intellectual property, customer experience, risk posture, or operating model, building internal strength is usually more sustainable. When a missing senior role is blocking decisions, hiring may be the necessary move.

Building capability without turning training into theatre

Upskilling is the most sustainable response when the organisation already has capable people who understand the business but lack exposure to newer platforms, practices, or security requirements. It works especially well where the skills are close to existing roles: infrastructure teams moving into cloud operations, analysts adopting modern data tooling, developers learning secure delivery practices, or IT operations staff learning automation.

The hidden cost of building is not only course time. Teams experience a productivity dip while people learn, managers must protect time for practice, and delivery leaders need to connect learning to live work. If training sits outside the backlog, employees may pass an assessment yet return to the same tasks and behaviours. A stronger model links learning to active projects, labs, internal communities, architecture reviews, and measurable changes in delivery quality.

Useful metrics go beyond training hours or completion certificates. Leaders should look at time-to-productivity after learning, internal mobility into target roles, deployment frequency, lead time for change, defect trends, security incident patterns, cloud cost hygiene, and reduced reliance on a small number of specialists. The aim is not to prove that training happened; it is to show that the organisation can deliver and operate technology with less friction.

Readynez can support this kind of targeted capability building when certification-led learning is tied to real job outcomes rather than treated as a standalone achievement. The same principle applies regardless of provider: the programme should map skills to work, give learners hands-on practice, and make managers accountable for applying the capability after formal learning ends.

Buying talent where a missing role is blocking progress

Hiring is the right response when the organisation lacks a capability that cannot be developed quickly enough internally. This is often true for senior roles that set standards, design platforms, make security trade-offs, or coach multiple teams. A strong principal engineer, cloud architect, cyber lead, or data platform owner can unlock decisions that a broad training programme cannot resolve by itself.

The risk is that hiring plans are written as if new employees become productive immediately. In practice, senior technology hires need context: current architecture, risk appetite, business priorities, delivery constraints, vendor relationships, compliance obligations, and the informal decision-making culture. Without a deliberate onboarding plan, organisations can pay for scarce talent while leaving that talent unable to influence outcomes.

Hiring also has opportunity costs. Recruitment takes management time, compensation expectations may create internal equity pressure, and poorly defined roles can attract candidates who are strong on paper but mismatched to the organisation’s maturity. Leaders should be especially cautious about hiring for every gap on a skills matrix. Some gaps are better handled by developing existing employees, simplifying platforms, or using specialist partners for a defined period.

Partnering for speed without losing internal control

Partnering is often the fastest way to bring in scarce expertise. It can help an organisation stabilise a cyber programme, accelerate a cloud migration, design a data platform, implement a managed service, or cover a short-term delivery surge. It is also useful where the capability is important but not differentiating enough to justify building a large internal team.

The main danger is unmanaged dependency. If partners hold the architecture knowledge, run the delivery cadence, own the tooling, and make key operational decisions, the organisation may appear to move faster while becoming less capable. Vendor lock-in can also emerge gradually through proprietary patterns, poorly documented configurations, or commercial arrangements that make future change expensive.

Effective partnering requires explicit knowledge transfer, clear ownership boundaries, and internal counterparts who work alongside the external team. Contracting for outcomes should not mean outsourcing understanding. Even when a managed service is the right long-term model, the organisation still needs enough internal capability to challenge decisions, assess risk, and steer priorities.

A first 90-day roadmap for leaders

The first 90 days should clarify the problem before committing heavily to one response. Many skills programmes fail because leaders begin with a preferred solution, such as a hiring campaign or a training catalogue, rather than a diagnosis of which capabilities matter most and how quickly they must improve.

Identify the few technology outcomes that are currently constrained by skills, such as delayed cloud migration, unresolved security risk, or slow product delivery.

Map the capabilities behind those constraints and separate missing knowledge from missing capacity, missing leadership, and unclear operating practices.

Classify each capability by time-to-impact and strategic differentiation so build, buy, and partner decisions are made consistently.

Select a small number of priority interventions, such as partner support for immediate delivery, hiring for one pivotal role, and targeted upskilling for adjacent internal teams.

Define outcome metrics before execution begins, including time-to-productivity, internal mobility, incident trends, defect trends, lead time, and partner dependency reduction.

Review progress with delivery, technology, HR, and finance together so the portfolio can be adjusted rather than defended as separate initiatives.

This roadmap also helps avoid common mistakes. A hiring-only strategy leaves the organisation exposed when recruitment slows or new hires cannot influence legacy ways of working. Generic training creates activity without capability if it is not connected to live backlog items. Unmanaged shadow vendors may deliver short-term output while fragmenting architecture and weakening internal accountability. Each risk has a practical correction: define onboarding, attach learning to work, and require partners to transfer knowledge as part of delivery.

How the portfolio approach looks in practice

Consider a mid-sized organisation migrating customer-facing services to the cloud while improving security monitoring. The immediate problem is delivery speed, but the deeper issue is that internal infrastructure teams have limited cloud operating experience, security engineers are overloaded, and product teams do not understand the new deployment model.

A balanced response would use a partner for the first wave of platform implementation and security configuration, hire one senior cloud platform lead to set internal standards, and build capability in existing operations and development teams through hands-on work tied to the migration backlog. The partner creates early momentum, the hire gives the organisation accountable technical leadership, and the upskilling effort makes the change sustainable after the first release.

The success measures would not be limited to whether the migration completed. Leaders would also review whether internal teams can operate the platform, whether incident response has improved, whether deployment lead times are falling, whether fewer decisions depend on the partner, and whether employees are moving into the target roles the organisation needs for the next phase.

Choosing a response that survives the next skills shortage

The tech skills crisis is unlikely to be solved by a single annual workforce plan. Digital demand changes too quickly, and the skills that matter most vary by strategy, architecture, regulation, and market pressure. Leaders therefore need a repeatable way to decide which capabilities to grow internally, which roles to hire for, and which work to entrust to partners.

The key takeaway is that build, buy, and partner are management levers, not competing slogans. Used together, they can relieve immediate pressure while improving long-term resilience. A practical next step is to assess the organisation’s most constrained technology outcomes, classify the skills behind them by urgency and strategic value, and use that diagnosis to shape a balanced capability plan; where structured learning is part of that plan, Readynez can help turn certification preparation into applied skills development that supports the wider workforce strategy.