A security culture is tested in small, inconvenient moments. A member of staff notices an unsecured access point but assumes somebody else will deal with it. A supervisor receives a concern but does not feed back what happened next. A team sees unusual behaviour but hesitates because they are unsure whether it is worth reporting.

These are not usually failures of policy. They are failures of confidence, ownership and leadership. To improve security culture, an organisation must make the right actions clear, realistic and expected when time is short and pressure is high.

Security culture is what people do when no one is watching

Many organisations describe culture through values, posters or mandatory training completion. Those things may have a place, but they do not tell you whether people will recognise a concern, raise it promptly or make a proportionate decision when normal routines are disrupted.

Security culture is the shared understanding of what matters, what people are expected to do and how leaders respond when they do it. It appears in day to day decisions: whether staff challenge poor practice respectfully, whether managers deal with minor issues before they become normal, and whether teams learn from near misses rather than quietly moving on.

This is particularly relevant in public facing environments, critical infrastructure, construction, transport, events and hospitality. People working in these settings are balancing security with customer service, delivery deadlines, operational pressures and commercial demands. Telling them that security is everybody’s responsibility is not enough. They need to understand what that responsibility looks like in their role.

A good culture does not turn every employee into a security specialist. It gives them the awareness, authority and confidence to take sensible action within their competence, then pass information to the right person.

How to improve security culture where it counts

The starting point is not another campaign. It is an honest assessment of the gap between written expectations and normal behaviour.

Ask people simple questions. What would you report? Who would you report it to? What happens after you report it? What would stop you from acting? Their answers will reveal more than a training record. If people cannot explain the process in plain language, or believe nothing happens after they raise a concern, the culture is weaker than senior leaders may think.

Define the few behaviours that matter most

Security guidance often fails because it gives people too much to remember and too little help with judgement. Focus first on the behaviours that reduce real risk in your operating environment.

For one organisation, this may mean controlling visitor access and challenging unfamiliar people appropriately. For another, it may mean reporting suspicious activity, protecting sensitive information or escalating concerns about a deteriorating situation. The right priorities depend on the threat, vulnerability and operational context.

Be specific about the expected action. Replace vague instructions such as remain vigilant with practical direction. Explain what staff should notice, what they should do first, when they should seek support and what information is useful to pass on. This should be proportionate. People need enough structure to act, not a script that collapses as soon as circumstances differ.

Make leadership visible in ordinary decisions

Staff watch what managers tolerate. If a manager bypasses a control to save time, dismisses a concern as inconvenient or treats reporting as a nuisance, the message is immediate. Security becomes optional when operations are busy.

Leaders do not need to be security experts, but they must set the conditions for sound practice. They should ask sensible questions after an incident or concern, support staff who make a reasonable decision in good faith, and address repeated poor practice. Their language matters. When leaders describe security as a shared operational discipline rather than a compliance task, people understand that it affects the way work is done.

There is a trade off here. Constant intervention by managers can create dependency, while complete distance leaves staff uncertain. The aim is to give people clear boundaries and decision support, then allow them to exercise judgement within those boundaries.

Treat reporting as a conversation, not a one way process

Reporting systems fail when they feel bureaucratic, punitive or pointless. A person who reports a concern and hears nothing back is less likely to report the next one. Over time, teams begin to decide for themselves what is serious enough to mention. That is where valuable early warning is lost.

Give feedback wherever possible. It may be brief and it may not include every detail, but acknowledge the report, explain what was done and share any wider learning that is safe and useful to share. This closes the loop and proves that reporting has value.

The quality of reports also improves when staff know what good information looks like. Encourage clear observations rather than assumptions. What was seen, where and when did it happen, who was informed, and what action was taken? That approach supports better assessment without encouraging people to speculate or investigate beyond their role.

Train judgement, not just recall

Most staff can pass a short knowledge check immediately after training. That does not mean they can recognise a relevant concern six months later, while dealing with a queue, a contractor, a customer complaint or an equipment failure.

Training should reflect the decisions people actually face. Use realistic scenarios that require them to identify priorities, choose an appropriate response and explain why. Discuss the limits of their role. Practise escalation and communication. Give immediate feedback that connects the decision to the consequence.

This is where many programmes fall short. They explain the threat but do not test whether learners can apply the information. A certificate confirms attendance or completion. It does not, by itself, confirm capability.

Short, repeated learning is usually more effective than a single annual session, particularly where staff turnover is high or responsibilities change. The format can vary between teams. A control room, a retail site and a project team will not need the same examples. The security standard should be consistent, but the learning must make sense in the environment where people work.

For organisations preparing for Martyn’s Law, this distinction matters. Requirements may drive attention towards plans, training records and procedures. These are necessary foundations. Yet the practical question remains: can the people on site make timely, proportionate decisions and work together when an incident creates uncertainty? Documentation cannot answer that question on its own.

Measure behaviour, not activity

A culture cannot be measured perfectly, but it can be assessed far better than many organisations attempt. Training completion, policy sign off and the number of communications issued are activity measures. They show that something was delivered, not whether it changed performance.

Look instead for evidence of capability. Are reports becoming clearer and more useful? Are recurring weaknesses being corrected? Can team leaders explain their responsibilities? Do exercises reveal quicker recognition, better escalation and stronger coordination? Are staff prepared to challenge unsafe practice appropriately, regardless of seniority?

Be careful with report volume as a metric. A rise in reporting may indicate increasing confidence and awareness, not deteriorating security. Equally, a low number of reports may reflect a quiet environment, but it can also signal resignation or fear of getting it wrong. Numbers need context.

Periodic capability assessments are valuable because they expose uneven understanding across roles and locations. They also identify where the problem is not knowledge but process, supervision, workload or unclear accountability. If people repeatedly make the same error, do not assume they simply need more training. Examine the conditions that make the error likely.

Stop rewarding appearance over readiness

There is an uncomfortable truth in security management. Some organisations are better at demonstrating assurance than building capability. They can show completed forms, completed modules and approved plans, yet their people remain uncertain about what to do in a live situation.

This happens when security is treated as a specialist function that produces paperwork for everyone else to follow. Protective security works differently. Specialists provide assessment, design, advice and oversight, but the organisation’s daily behaviour determines whether controls hold.

The most useful test is simple. Choose a realistic concern for your environment and ask a cross section of staff to talk through their response. Listen for uncertainty, assumptions and gaps between teams. Then fix what the discussion reveals. That is how security culture moves from stated intent to dependable action.

Why Mildot Group?

Built on Experience. Focused on Capability.

Mildot Group helps individuals and organisations build practical capability through professional learning, capability evaluations, premium publications and specialist consultancy. Every solution is designed to bridge the gap between theory and practical application, helping people and organisations perform with greater confidence in real-world environments.

Our Mission

Our mission is to help individuals and organisations build practical capability through professional learning, capability evaluations, expert guidance and real-world application. Everything we create is designed to bridge the gap between theory and practice, helping people make better decisions, strengthen resilience and perform with confidence.

Our Philosophy

We believe capability is developed through structured learning, practical application and continuous improvement, not simply by completing a course or meeting a compliance requirement. Every learning programme, capability evaluation, publication and consultancy engagement is designed to help individuals and organisations apply knowledge with confidence in real-world environments.

What Makes Mildot Group Different?

Real Operational Experience
Built on experience gained across military, corporate and international environments.

Practical Learning
Professional learning designed to develop skills that can be applied immediately.

Capability Focused
Building practical capability rather than simply delivering awareness or compliance.

Evidence-Based
Combining operational experience with research, proven frameworks and practical methods.

Individuals & Organisations
Supporting personal development, professional capability and organisational performance.

Continuous Development
A growing platform with new learning programmes, evaluations and professional publications added regularly.

Privacy Preference Center