Skip to content
Two walk-in offices: Dubai Media City and Bur Dubai, Mon to Sat 9:00 to 19:00.Request an assessment
Blue glass artwork behind the page title

IT Support · guide

Running Phishing Simulation Without Wrecking Trust

A simulation programme that humiliates staff produces people who hide mistakes. That is the opposite of what you need when a real attack lands.

security-awarenessphishingtrainingdubaicybersecurity

Quick answer

A phishing simulation that humiliates staff produces people who hide mistakes, which is the opposite of what you need when a real attack lands. Run it fairly: tell people the programme exists, never publish individual results, make reporting effortless and praised, and treat a high click rate as a failure of your controls and training rather than of the person who clicked.
Get a quote
Written by
Azizi Technologies Team
Published
27 Aug 2026
Reading time
8 min
Category
IT Support
Reviewed in
Dubai

Phishing simulation works. Done carelessly it also teaches your staff that the security team is something to be avoided, which costs you the thing that actually matters during a real incident: someone telling you quickly.

The goal is reporting, not a low click rate

A business where nobody clicks but nobody reports is more dangerous than one where a few people click and everyone reports within minutes. Real attacks are not stopped by perfect staff. They are contained by fast reporting, and that is a behaviour you either encourage or suppress.

Lures we will not use

  • Salary changes, bonuses or payroll problems
  • Redundancy, restructuring or anything implying job insecurity
  • Health, family emergencies or bereavement
  • Anything impersonating a named colleague in a way that damages that person's standing
  • Visa, residency or immigration status, which in the UAE context is needlessly cruel

The argument for cruel lures is that real attackers use them. True, and irrelevant. The purpose of a simulation is to build a habit, not to prove people can be manipulated when distressed. You will get the same learning from a well-built invoice lure without the damage.

The HR test

If a simulation would upset someone enough to complain to HR, it is the wrong simulation regardless of how realistic it is.

Rules we agree before sending anything

  1. 1Difficulty starts moderate and escalates, rather than opening with something almost nobody would catch
  2. 2Results reported as team and organisation trends, never as a leaderboard of named individuals
  3. 3Anyone who clicks gets immediate, short, blame-free coaching showing the specific tells
  4. 4Anyone who reports gets acknowledged, including when the message turned out to be genuine
  5. 5Management agrees in advance that results will not be used in performance reviews
  6. 6Staff are told the programme exists, even if not when each test will arrive

The reporting button matters more than the training

Make reporting a suspicious email a single click in Outlook or Gmail. If reporting requires forwarding to an address nobody remembers, people will not do it. The easier reporting is, the faster your real incidents get contained, and that is the entire return on this programme.

What good looks like after a year

MetricWeak programmeWorking programme
Report rateLow and flatRising quarter on quarter
Time to first reportHours or neverMinutes
Repeat clickersSame names, unaddressedSmall, shrinking, supported
Staff attitudeSees IT as a trapReports genuine mail without fear of looking foolish
False reportsDiscouragedWelcomed, because over-reporting is the safe failure
IT Support

Setting up an awareness programme?

We run simulation programmes with the rules agreed with management up front, and report on the numbers that predict whether a real attack gets contained.

Security awareness trainingWhat to measure

Blue glass artwork

Frequently asked questions

Is phishing simulation fair to employees?
It can be, and it depends entirely on how it is run. Avoiding cruel lures, reporting trends rather than naming individuals, and coaching without blame make it feel like practice. Publishing a leaderboard of who clicked makes it feel like a trap, and people respond accordingly.
Should we name people who click?
No. Naming individuals produces staff who conceal mistakes, which is precisely what you cannot afford during a real incident. Report by team and by trend. If a specific person is repeatedly caught, support them privately rather than exposing them.
How often should we run simulations?
Frequently enough to build a habit and not so often that people become suspicious of all internal mail. Quarterly is a common rhythm, adjusted once you see how your teams respond. Short reinforcement training between simulations matters more than the frequency of the tests.
What if staff complain about being tested?
Usually that signals a problem with the lure or the communication rather than with testing itself. Tell staff the programme exists before it starts, avoid emotionally exploitative lures, and make sure the follow-up is coaching rather than criticism.
Do we tell staff when a test is coming?
Tell them the programme exists, not the timing of individual tests. Announcing each test defeats the purpose. Announcing the programme builds consent, and it is the difference between staff treating it as practice and treating it as entrapment.
About the author

Azizi Technologies Team · Editorial Team

Practical IT and digital marketing guidance from the Azizi Technologies team - an in-house team of certified engineers, SEO specialists, and digital marketers serving Dubai businesses since 2007.

Since 20074.9★ across 645 Google reviewsAbout the team