Most first programs fail for the same reason: they start with a tool and a test, and only later ask what they are trying to change. Start the other way round. Decide on the behaviours, get people on side, and the tooling becomes the easy part.
1. Decide which behaviours you want
"Be more secure" cannot be measured. Pick four or five concrete behaviours that would have stopped the incidents you worry about. Common first choices:
- Report a suspicious email with the reporting button or address, rather than deleting it.
- Check any request to change bank details or make an urgent payment through a second channel.
- Never enter a work password on a page reached from an email link.
- Lock the screen when leaving the desk.
- Use the company password manager and multi-factor authentication.
Everything that follows, content, tests and metrics, should map back to this list.
2. Get agreement in writing
Phishing tests touch employee trust, so agree the ground rules before the first email goes out. Write a one-page charter that answers:
- Who sponsors it. A senior leader who will back the program when someone complains.
- Who is in scope. All staff, including leadership. Exemptions undermine credibility.
- What is recorded. Opens, clicks, reports, and whether data was typed into a page.
- How results are used. To teach and to measure the program, not to discipline individuals.
- Who has seen it. HR, legal, and the works council or employee representatives where they exist.
Also tell your IT and mail team, so they allow the simulation sender through filters and do not escalate the test as a real incident.
3. Give awareness a home
People need one place to find the security policy, the "how do I report this" page, and short guides. If it is spread across an intranet, a shared drive and old emails, nobody will look. A dedicated awareness portal with policies, topics, courses and tests solves this, and gives every phishing test a page to send people to afterwards.
4. Run a baseline phishing test
The first test is a measurement, not a lesson. Send one realistic but fair email to everyone so you know where you start. Guidelines for a fair test:
- Imitate the kind of email your company really receives, such as a shared document or a delivery notice.
- Avoid lures that cause real distress or false hope: bonuses, layoffs, health results, family emergencies.
- Never collect real passwords or payment details. If a page has a form, do not store what is typed.
- Spread sending over a few hours so the first people to click do not warn everyone else.
- Send anyone who clicks to a short page that shows the clues they missed and how to report next time.
5. Train in small, regular pieces
An hour once a year meets an obligation and is forgotten by the next quarter. Short modules of a few minutes, released every month or quarter and each followed by a quick test, keep security in mind without getting in the way of work. Explain one concept at a time, use examples from your own company, and drop the jargon.
Make the content relevant to life outside work too. People who understand why a scam text to their personal phone works will spot the work version faster.
6. Measure the right things
Track a few numbers per campaign and watch the trend across campaigns, not one result on its own:
- Report rate. The share of recipients who reported the email. This is the number to grow.
- Click rate. The share who clicked. It should fall, but it also depends on how hard the lure was.
- Time to first report. How quickly your security team would have heard about a real attack.
- Repeat clickers. People who click in several campaigns, who need a conversation and extra help.
- Course completion and test scores. Whether the training is reaching people.
Compare like with like. A harder lure will raise the click rate even when people have improved, so note the difficulty of each campaign next to its results.
7. A first 90-day plan
| When | What to do |
|---|---|
| Weeks 1 to 2 | Write the one-page charter, get sign-off from leadership, HR and legal. Pick the four or five behaviours you will focus on. |
| Weeks 3 to 4 | Publish policies and the first awareness content in your portal. Tell employees the program exists and that tests will happen. |
| Weeks 5 to 6 | Run the baseline phishing test on everyone, with a landing page that explains what they missed. Record click and report rates. |
| Weeks 7 to 9 | Release the first course module with a short test, focused on the weakest behaviour from the baseline. |
| Weeks 10 to 12 | Run a second campaign with a different lure. Compare against the baseline and send leadership a one-page summary. |
After the first quarter, settle into a rhythm: one module and one campaign each month or each quarter, and a short report to leadership every quarter.
8. Mistakes to avoid
- Naming and shaming. Publishing who clicked teaches people to hide mistakes, including real ones.
- Only testing, never teaching. Every test needs a lesson attached, or it only measures.
- Making every lure impossible. Tests people can never pass breed resentment, not skill.
- Ignoring the reporters. Thank people who report. It is the behaviour you want to spread.
- Forgetting leadership. Executives are targeted most and must be tested too.
9. Choosing a tool
You need three things: somewhere to publish content and policies, a way to send simulated phishing, and results you can export. If you have someone who can run a PHP application and you want to keep data on your own server, Awora covers all three for free. If you would rather not host anything, or need voice and SMS simulations, a managed platform such as PhishGrid fits better. The comparison sets out the trade-offs.