CyberPsychwith Connor
← About CyberPsych at Work

CyberPsych at Work · Sample package

The request changed. Did your checks?

Three everyday workplace decisions about familiar requests that suddenly change, followed by a new situation to try.

8 minutes, estimated · 3 short lessons · One new situation

Fictional teaching scenarios for a free product demonstration. This sample does not save answers or track employee completion.

Explore the employee lessons or manager kit. This free sample has no accounts or completion tracking.

Make the advice usable here

Try your team's instructions.

These optional fields update the briefing and reminder below. They stay in memory as you navigate this sample and are cleared on refresh. Use example details while reviewing.

A briefing for the person setting the tone

Make checking part of the job.

Make it easy to pause an unusual request, verify it through an established route, and get help when the normal contact is unavailable.

Reinforce this

  • Thank people for checking, including requests that turn out to be legitimate.
  • Apply the same payment checks when the request comes from leadership.
  • If someone has already acted, help them report promptly and follow the response process.

Make the process clear

  • Where are trusted supplier and employee contact details kept?
  • Who approves changes to payment destinations?
  • Who is the backup when the usual approver cannot be reached?
  • Where should an employee report a suspicious request or a mistaken payment?

Bring this to your next team conversation

A payment deadline is close and the usual approver is unavailable. What should a teammate do here?

Your team's process: To be confirmed with the business before employee use.

Reporting or help: To be confirmed with the business before employee use.

Completion records participation. A new application question gives limited evidence of understanding. Neither proves lower real-world risk. This prototype stores neither identities nor responses.

CyberPsych at Work · Your team

New payment details? Use an established check.

  1. Notice the change: destination, contact route, or approval process.
  2. Pause the change while you verify it.
  3. Use contact details obtained outside the request and follow the approved process.
  4. If verification is unavailable, use the agreed escalation route.

Our team process
Manager: add your approved process before sharing this reminder.

Reporting or help
Manager: add your team's reporting route before sharing.

A callback is one check, not a guarantee. Follow your organization's approval and incident-response procedures.

Sample package · Fictional scenarios · Version 1 · 2026-10-21

Practical guidance

FBI: Business Email Compromise
https://www.fbi.gov/how-we-can-help-you/common-frauds-and-scams/business-email-compromise

FBI: FBI Tech Tuesday: Building a Digital Defense Against Business E-Mail Compromise Scams
https://www.fbi.gov/contact-us/field-offices/portland/news/press-releases/fbi-tech-tuesday-building-a-digital-defense-against-business-email-compromise-scams

Evidence and interpretation

What supports this package?

The practical guidance is sourced below. The scenarios are invented; psychology explanations interpret the situations and make no claims about individual traits or measured outcomes.