Every recession follows the same pattern. Hiring slows. Budgets get scrutinised. The phrase "doing more with less" appears in every leadership meeting. And HR teams are asked to find ways to keep delivering with the people they already have.

The instinct in those moments is often the wrong one: to look at headcount as a problem and morale as collateral. The better instinct is to look at capability - what your existing team can already do, and what they could do if you let them.

The skills you already have are almost always more than you think

In our experience working with organisations of all sizes, there is a consistent pattern: people massively under-report their skills. A police officer mentions "response driving" but not the leadership, public engagement, conflict resolution and incident command training that came with it. A car salesperson describes their job as "dealing with the public" without mentioning their negotiation, product knowledge or relationship management capabilities.

The reason is simple. People answer the question they are asked. Most performance reviews ask narrow, role-focused questions. So you get narrow, role-focused answers. The rest of what they can do never makes it onto any list, any system, or any conversation.

This matters even more during economic pressure, because the most expensive thing you can do is hire externally for a capability that already exists internally.

Three things to try before you post a job ad

1. Run a real skills conversation, not a form

Skills audits delivered as spreadsheets and tick-boxes consistently under-discover capability. People do not enjoy filling them in, so they rush. The questions are generic, so they get generic answers. And the format gives no opportunity to surface unexpected skills - the second language someone speaks at home, the volunteering they do on weekends, the tools they use in their hobbies.

In our own customer base, conversational discovery - whether human-led or AI-supported - consistently surfaces several times more skills per person than form-based approaches. The format invites people to elaborate, ask questions, and reveal context that a form would never capture.

2. Map skills to opportunities, not just jobs

Most skills systems are built around job titles. That is fine for hiring but useless for redeployment. When you need someone who can manage a project, run a workshop, mentor a graduate, or translate a customer call, you do not care what their job title says - you care whether they can do the thing.

The shift here is from "What is this person's role?" to "What can this person actually do?" Once you have that data, internal opportunities become visible in a way they were not before. The graduate who turns out to fluently speak Mandarin. The accountant who used to teach photography. The receptionist with a project management qualification. None of these would surface in a typical org chart.

3. Make development pathways concrete

One of the most common reasons good people leave during a downturn is not pay. It is the perception that there is nowhere to go. When promotion freezes happen, ambitious people start looking elsewhere - not because they want to leave, but because they cannot see a path.

You can change that without spending money. Map the actual capabilities required for the next role up. Show people exactly what skills they would need to develop. Connect them with mentors who have done the journey already. Even without a promotion budget, this conversation alone often retains people who would otherwise have updated their CV.

The mindset shift

The organisations that emerge strongest from periods of economic pressure are not the ones that cut deepest. They are the ones that took the time to truly understand what their existing teams could do - and gave them the chance to do it.

Talent shortages and budget pressure are real. But for most organisations, the talent shortage is mostly a visibility problem. The talent is there. It just is not being seen, deployed, or developed.

If you are facing a hiring freeze right now, before you write the business case for an exception, run the inventory. You may already have what you are looking for.