Strategic workforce planning in the GCC: a practical method

Most workforce plans I review in the GCC are budgets with a new name. They take last year's headcount, add the positions each department asked for, and apply a cost ceiling. That tells Finance what payroll will be next year. It says very little about whether the organisation will have the people and skills to deliver its strategy in three to five years.

This article sets out the method I use with HR teams to make workforce planning strategic in practice. It covers how to decide which roles deserve attention, how to model demand and supply without drowning in data, how to choose between building, buying, borrowing, redeploying and automating, and how to treat national workforce targets as a design input rather than a compliance afterthought.

Workforce planning and headcount budgeting are different jobs

Both are necessary. The problem starts when an organisation believes the budget process is its workforce plan. The two answer different questions, on different horizons, for different audiences.

A good strategic plan makes the budget easier. When the business already agrees which capabilities matter and how they will be sourced, the annual position requests become a check against the plan rather than a negotiation from scratch.

Start from the strategy and segment your roles

Workforce planning begins with a conversation about the strategy, not the organisation chart. I ask leadership a short set of questions. Which services or business lines will grow, shrink or appear? Which channels will shift to digital? Where will the organisation operate? What will be outsourced, privatised or moved to a shared service? Each answer has a workforce consequence, and it is HR's job to spell that consequence out.

Then segment your roles. Not every role needs the same planning effort, and trying to model every position is the fastest way to stall the exercise. I use four segments:

• Critical roles: high impact on the strategy and hard to replace, because the skills are scarce or take years to develop.
• Core roles: essential to daily operations but available in the market or quick to train.
• Support roles: necessary but standardised, often candidates for shared services, outsourcing or automation.
• Emerging roles: capabilities the organisation does not have yet but the strategy clearly needs.

Put most of your effort into critical and emerging roles. For many entities that means ten to fifteen job families, not hundreds of positions. The same list should feed your succession work; I cover how to identify these roles in critical roles, talent reviews and the leadership pipeline.

Model demand and supply at job-family level

The model does not need to be sophisticated. It needs to be honest about its assumptions and simple enough that leaders can challenge them.

Demand is driven by three things: volume (how much work there will be), productivity (how much each person can handle, including the effect of technology), and new capabilities the strategy introduces. Supply is your current workforce projected forward: attrition, retirements, internal moves and the pipeline of trainees and graduates already in progress.

A worked example

Say a 2,000-person semi-government entity plans to move most of its services online over four years. Two job families matter here: customer service (300 people today) and data and analytics (20 people today). The numbers below are illustrative assumptions for the example.

Customer service. Leadership expects service volume to grow by 60%. Digital channels and automated handling of routine enquiries are expected to raise productivity per person by 40%. Demand in year four is roughly 300 × 1.6 ÷ 1.4, or about 340 people. On supply, if annual attrition is 8% and nobody is replaced, about 215 of today's 300 remain after four years. The net growth looks modest at 40 people, but the real requirement is around 125 hires or redeployments.

Data and analytics. The strategy needs 60 people in year four. With 15% annual attrition in a scarce, well-paid market, about 10 of today's 20 remain. The gap is 50 people in a job family the market cannot supply quickly.

Two lessons come out of almost every model like this. First, attrition usually drives the gap more than growth does, and it is the number leaders forget. Second, the size of a gap matters less than how hard it is to close. Fifty analysts is a harder problem than 125 service staff.

Run at least three scenarios: a base case, a faster-growth case and a slower case. The purpose is to see which decisions hold across all three. Those are the ones to commit to now.

Closing the gap: build, buy, borrow, redeploy or automate

Once you know the gap, decide how to close it for each critical job family. Most organisations default to external hiring because it feels fastest. It is often the most expensive and the least reliable route for scarce skills.

Two options deserve more attention than they usually get.

Redeployment is sometimes called quiet hiring: filling a need by moving existing people rather than recruiting. It is fast and builds loyalty, but only if it is visible and fair. If stretch assignments always go to the same high performers, and nobody's grade or pay reflects the bigger role, you create burnout and resentment instead of capability.

Borrowing has become more practical as freelance licensing routes have opened in several GCC markets. Use contingent talent deliberately for work that is temporary or experimental. Do not use it to hide permanent capability gaps, and make sure someone owns the knowledge each engagement produces.

Automation now belongs in the same table as the human options. When part of the work will be done by AI agents, the planning logic changes, and I have written separately about workforce planning when part of the workforce is AI.

A workforce plan that cannot change a hiring, training or automation decision is a report, not a plan.

Build nationalisation into the model, by profession

Emiratisation in the UAE, Saudisation under Nitaqat in Saudi Arabia and similar programmes elsewhere are often handled by a separate team, reported separately, and met in whichever roles are easiest to fill. That is how organisations end up compliant on paper while their professional and leadership roles remain dependent on expatriate talent.

Put national workforce requirements into the model as a constraint on each job family: the national share today, the share required or targeted, and the realistic national pipeline. For professional and technical roles, that pipeline takes years to build, so the plan must trigger graduate programmes, sponsored degrees, apprenticeships and structured development well before the target bites.

What Saudi Arabia's national approach teaches individual employers

Saudi Arabia's Ministry of Human Resources and Social Development (MHRSD) plans the labour market at national level, and its approach offers useful lessons for a single organisation. Its Labour Market Strategy links workforce policy to the demand created by Vision 2030 sectors. Localisation decisions are increasingly issued profession by profession. Employers are brought into defining skill needs through sector skills councils, and workforce planning is connected to education and training through the Human Capability Development Program.

Four principles translate directly into an organisational plan:

1. Plan by occupation, not by department. Localisation rules and skills markets work at the level of professions, so your model should too.
2. Involve the business in defining skills. Line leaders, not HR alone, should say what capability a job family needs in four years.
3. Connect the plan to the learning pipeline. A gap that needs three years of development has to be funded this year.
4. Track a small set of indicators. A handful of measures reviewed regularly beats a large dashboard nobody reads.

There is also a practical point. Because localisation decisions can apply to specific professions, keep a view of your exposure by profession. A new decision can remove the "buy" option for a job family almost overnight, and you want to have seen that coming.

Use skills where they help, and keep ownership clear

Skills-based planning is useful, but I have seen it collapse into a multi-year taxonomy project that never reaches a decision. My position is to use job families as the planning unit and apply detailed skills analysis only where it pays back: in critical and emerging job families, and when matching people to redeployment opportunities.

Someone must own the skills framework and the data behind it. Larger organisations are creating dedicated roles for this, sometimes called skills architects (who design the framework) and skills engineers (who keep the data working across HR systems). In most GCC entities, these are better treated as clear responsibilities within the organisation development or workforce planning team than as new job titles.

Make it a cycle, not a project

A workforce plan built once and filed away loses value within a year. Refresh the full plan annually, timed so it feeds the budget rather than following it. Review critical job families quarterly. Agree in advance what triggers an off-cycle re-plan: a new strategy, a restructuring, a merger or a new localisation decision affecting your professions.

Ownership matters as much as timing. The plan works best when HR runs it, the business owns the demand assumptions, Finance validates the cost, and a senior executive, usually the CEO or COO, holds everyone to the decisions.

Where to start

1. Agree with leadership a list of ten to fifteen critical and emerging job families, using the four segments above.
2. Build a four-year demand and supply model for those families only, with three scenarios and written assumptions.
3. Choose a primary route for closing each gap using the build, buy, borrow, redeploy or automate table.
4. Map your national workforce exposure by profession and add the pipeline actions to the plan.
5. Put the plan's refresh date into the budget calendar so it drives next year's decisions.

If you want a partner to build the first version of that plan with your team and make it repeatable, that is exactly the kind of work we do at Humanyx.