360° Feedback for Saudisation & Emiratisation Leadership Programmes

The short answer

To evidence a Saudisation or Emiratisation leadership programme, run a 360° feedback cycle on each participant at the start of the programme and a linked follow-up cycle after it. In each cycle, the leader's manager, peers, direct reports and (where useful) external raters describe observed behaviour against the same leadership competencies; the follow-up report then shows growth deltas per competency — self and others — against that leader's own baseline, not a norm table. Rolled up across the cohort, those deltas are the artefact a programme sponsor, HR committee or board actually asked for: which leadership behaviours moved, by how much, and for whom.

This matters because nationalisation programmes are usually reported in the wrong unit. Headcount placed, training days delivered and completion percentages all measure activity. A leadership programme's promise is behaviour change in specific, senior, visible people — and behaviour change is something only the people around a leader can attest to. That is precisely what a 360 measures and a completion certificate does not.

Why leadership development is the hard half of nationalisation

Saudisation, Emiratisation and the wider Gulf national-workforce agenda have two halves. The visible half is hiring: national talent recruited into roles, tracked in percentages. The decisive half is development — and its hardest case is leadership, because the programmes that matter most take high-potential national managers and prepare them for roles currently held by expatriates or newly created for them. These are expensive programmes, with sponsorship at board level, run on cohorts small enough that every individual outcome is visible.

The evidence problem follows directly. For technical capability there are exams and demonstrable skills; a measured baseline-and-re-measure loop handles it — we cover that loop in our guide to measuring national-workforce capability. But 'is she leading her team better than a year ago?' has no exam. Self-assessment inflates, sponsor impressions are anecdotes, and programme-satisfaction surveys measure the catering. The one source of evidence that scales and stands scrutiny is structured observation by the people who work with the leader every day — which is what a 360 is.

What a 360 measures that nothing else can

A 360° review asks a defined circle — self, manager, peers, direct reports, external raters — to score one person's observed behaviours against a competency model, and to describe those behaviours in writing. The self-versus-others gap analysis is where leadership development actually starts: confirmed strengths (self and others agree), hidden strengths (others rate higher than self — common in newly promoted managers), blind spots (self rates higher than others), and agreed development areas. On AssessAll, that gap read is computed by one arithmetic and shown in the report the subject sees, the preview the administrator reviews, and the cohort roll-up the programme office reads — so no two audiences can be looking at different numbers.

For a nationalisation cohort the instrument matters as much as the mechanics. Ready-made instruments cover leaders, managers and individual contributors, built from behaviourally worded competencies on a six-point labelled frequency scale — how often the behaviour is seen, not how much the rater likes the person. If the organisation has its own leadership framework tied to a Vision-programme capability model, the instrument can be composed to that framework instead: the requirement is only that the baseline and follow-up cycles use the same instrument, because the delta is the deliverable.

One design decision does disproportionate work in these cohorts: 'Not observed' is a first-class answer, excluded from every average, and every item carries an observed-count. A peer in another emirate who has never watched the participant run a difficult conversation can say so instead of guessing — and a score built on two observations reads as visibly thinner evidence than one built on nine. In small, distributed leadership circles this is the difference between data and noise.

The trust problem — and the mechanics that solve it

Every 360 lives or dies on rater candour, and the stakes are higher in workplaces where hierarchy is respected and professional circles are small. A direct report asked to describe their manager's behaviour — possibly a manager marked for promotion, in an organisation where everyone knows everyone — will hedge unless the anonymity is real and verifiable, not asserted in an invitation email. Hedged 360s are worse than none: they certify that a leader is ready when the people closest to the work quietly know otherwise.

Real anonymity is mechanical. On AssessAll, no anonymous rater group appears in any report until it has at least three completed responses — a floor the platform refuses to configure below. Groups under the threshold are merged into a combined 'others' view rather than dropped, and if even the combined view is too small, others-scores are withheld entirely with an explanation, rather than exposing a guessable two-person average. Written comments pass through an AI anonymisation step that removes names, titles, team and project references, dates and identifying incidents while keeping the behavioural substance — and the step fails safe: if it cannot run, comments stay out. The full mechanics, and the five questions to ask any vendor, are in our guide to 360 anonymity.

Equally important is what is not anonymous, said honestly: the manager's view is attributed — one named rater cannot be hidden, and pretending otherwise teaches the whole cohort to distrust the protections that are real — and the manager is told this before writing a word. And nothing reaches any participant until a programme administrator has generated the report, reviewed exactly what the subject will see with every withholding rule already applied, and explicitly released it. In a cohort where participants are senior and visible, that human release gate is not bureaucracy; it is what lets the programme office stand behind every report it delivers.

Small rater circles: the Gulf cohort's practical constraint

A high-potential national manager two years into a leadership pipeline often has a thin rating circle: two or three direct reports, peers spread across functions or cities, and a chain of managers that has changed mid-programme. Naive 360 tools either block these participants or silently show tiny group averages. The merge-and-withhold rules above are the systematic answer — small groups fold into the combined view, and thin evidence is labelled thin rather than dressed up — but programme design can also widen the circle deliberately.

Each subject supports up to eight peers, up to ten direct reports and up to five external raters, alongside self and manager — and the external category is more useful in Gulf programmes than almost anywhere else: a client contact, a counterpart in a partner entity, a rotation-assignment supervisor, or a programme mentor all see leadership behaviour the org chart misses. Raters are invited by email, create no account, and are chased by built-in reminders — which matters when your raters include busy externals who will not register for anyone's platform. Rater participation is free; the per-subject price does not change with circle size, so widening a thin circle costs nothing but thought.

Running the cycle across a distributed cohort

Gulf leadership cohorts are distributed by default — participants across Riyadh, Jeddah, Dubai, Abu Dhabi and Doha, raters spread further. The operational shape that works: the programme office configures the instrument and rater circles per participant, invitations go out by email, completion is tracked per group with automatic reminders, and reports are generated, reviewed and released participant by participant as their circles clear the thresholds. Subjects read their report through a private link on any device, with no account to create.

The cohort roll-up is the programme office's own instrument: aggregate strengths and development areas across the cohort, which competencies are weakest programme-wide, and how self-versus-others gaps distribute. Read at baseline, it does a second job — it tells the training provider what the programme should emphasise before a single workshop is booked, turning the 360 from an evaluation afterthought into the programme's needs analysis. Providers running programmes for Gulf clients can operate all of this white-label, under their own brand, with client workspaces keeping each client's cohorts separate.

Before and after: the delta is the deliverable

Run the baseline cycle before the programme starts, or in its first weeks. From each baseline report, the participant and their coach record a development focus — the two or three competencies they commit to working on — stored against the report, so every subsequent conversation starts from a decision rather than a re-reading. Then, six to twelve months later, run a follow-up cycle linked to the original: same instrument, same competencies, refreshed rater circles where teams have changed.

The follow-up report shows growth deltas per competency — self and others, against the participant's own baseline. That framing is deliberate: a nationalisation programme's question is not whether a developing leader matches a global norm today, but whether the investment moved them — and by how much, in whose eyes. The anonymity rules travel with the comparison, so only aggregates releasable in the first cycle cross into the second; a group withheld at baseline cannot be reverse-engineered from the delta.

Across the cohort, the deltas roll up into the evidence a sponsor can put in front of a board or a national-programme committee: participants measured, competencies moved, self-awareness gaps closed, and the residual development areas that justify — or redirect — the next phase's budget. That is the difference between reporting that a leadership programme happened and reporting what it changed. One honest caveat belongs in every such report: a 360 measures observed behaviour, and behaviour is also moved by role changes, new managers and org shifts — which is why the delta is read per competency and per person, not waved at as a single programme score.

What it costs

AssessAll prices a 360 per subject at 50 credits — US$25 — charged only when that subject's report is released, which is the moment the value exists. Raters are free, however wide the circle; there are no seat licences, platform fees or annual contracts, and credit packs discount volume by up to 13%. A 25-participant leadership cohort therefore costs US$625 per cycle — US$1,250 for baseline plus follow-up — figures that disappear inside any Gulf leadership-programme budget, which is rather the point: the evidence layer should never be the line item that gets cut.

New organisations get 250 free credits — enough to run five subjects end to end and see the reports before paying anything. And because the 360 runs on the same platform as the rest of the nationalisation loop — TNA Studio baselines, Learning Journeys sequencing baseline/during/outcome waves, volume hiring screens, workplace English with AI-scored speaking — the leadership evidence and the capability evidence live in one system, in USD, readable side by side. AssessAll is an independent assessment platform: it has no affiliation with any GCC government programme or authority, and a 360 report is capability evidence for your own governance, not a government credential.