Empathy-Based Training

Expanded Definition

Empathy-based training is a security awareness approach that corrects behaviour without shame, blame, or public embarrassment. Its boundary is important: it is not a softer version of policy enforcement, and it does not replace sanctions for deliberate misconduct. Instead, it changes how learning is delivered so that people are more likely to notice, report, and correct risky behaviour early. In security programmes, that usually means timely prompts, plain-language explanations, and context that matches the actual workflow rather than generic rules.

The term is often misunderstood as a culture-only idea, but its practical value comes from reducing the gap between what users understand and what security teams need them to do. That makes it relevant to phishing resistance, secure handling of data, and incident reporting. Guidance versus consensus is not strongly disputed here: most disagreement is about execution quality, not whether respectful training is useful. For broader behaviour-change design, the NCSC’s guidance on people-centred security is a useful external reference because it frames security outcomes around realistic human behaviour rather than idealised compliance.

Examples and Use Cases

Empathy-based training shows up in programmes that try to reduce repeat mistakes while keeping employees engaged. The common pattern is to explain why a risky action matters, then make the safer behaviour easier to repeat next time.

• A user clicks a phishing link and receives immediate coaching that explains the signs they missed, then a simple way to report similar messages faster.
• A finance team member shares data incorrectly and is shown the correct process in the context of the workflow they actually use, not in a generic policy slide.
• A help desk team runs short follow-up training after password or MFA mistakes, using examples drawn from the organisation’s own support tickets.
• A security team replaces public call-outs after unsafe actions with private, constructive feedback to avoid encouraging concealment or workarounds.
• A manager uses scenario-based refreshers that connect security behaviour to productivity, so the lesson feels operational rather than punitive.

The main tradeoff is that empathy-based training can be misread as leniency if expectations are not still clear. It works best when users understand that the organisation is being supportive about mistakes, but firm about repeated negligence or policy violations.

Security Implications

When training is punitive, people often hide mistakes, delay reporting, or stop engaging with awareness content altogether. That creates a measurable security problem even if the original error was minor, because late reporting can let phishing, misdirected data, or unsafe configuration choices persist longer than they should.

Empathy-based training reduces those failure modes by making disclosure and correction socially safer. The practical consequence is better visibility for security teams and less shadow behaviour from users who fear being blamed. It also improves the quality of lessons learned, because teams can see which workflows repeatedly lead to mistakes and adjust controls accordingly.

A common practitioner observation is that many so-called “user errors” are partly design errors: confusing prompts, unclear labels, or workflow pressure often contribute to the slip. Treating the event as an opportunity to improve both behaviour and process usually produces better outcomes than treating it as an individual failure.

Domain and Governance Relevance

In security governance, empathy-based training matters because awareness is not just a communications exercise. It influences incident reporting rates, employee trust in security functions, and whether control gaps are surfaced early enough to matter. A programme that drives silence may look disciplined, but it usually weakens detection and slows response.

The term has a clear operational place in cybersecurity culture, but it also affects governance decisions about how policy exceptions, repeat mistakes, and coaching are handled. The real issue is whether the organisation wants users to act as collaborators in risk reduction or as subjects of enforcement only. For identity and access teams, that difference can change how quickly people report suspicious MFA prompts, credential mishandling, or unusual access requests.

From an NHIMG perspective, the important shift is not that empathy-based training is an identity control, but that it can improve the human reporting layer around identity misuse and access anomalies. That makes it a supporting factor in broader assurance, even though its primary domain is behavioural security training rather than identity architecture.

Related resources from NHI Mgmt Group

• When should organisations move from completion-based SAT to behaviour-based training?
• What do security teams get wrong about reward-based model training?
• What breaks when user risk management is based only on awareness training and perimeter controls?
• What breaks when organisations rely on generic security awareness training instead of behaviour-based risk management?