Safety culture, because of its lack of conceptual clarity, can be turned toward increased abstraction or to increased specificity. So we have discussions about the importance of, say, values and trust to ensure safety. We also have discussions that focus on really-existing practices–formal, informal and irrespective of stated values, beliefs and objectives–that perform safely in these but not those contexts.
Like others, I feel I am being productive when talking about what is trust like what is liberty or domination. But the part of me that is a policy analyst looks downwards to events, situations and contexts where actionable granularity exists (if at all). How so? There, safety is more an adverb and less a noun. To act safely means to act according to these practices and not others. The policy analyst then asks: Does that work, right here and right now?
The benefits in doing so are not just pragmatic; they’re also conceptual. First, when looking downwards and adverbially, it is “safely with-respect-to what failure or accident scenario during what stage of infrastructure operations (normal, disrupted, failed, recovered or new normal)”. No floating signifier about “risk,” “trust,” or “success,” in the face of what must be differentiated accomplishments at more grounded levels of analysis and action.
Second, we’re so used to thinking that holism requires an inter-system perspective that we fail to see its analogue at a more granular and less abstract level, namely: the real-time interconnections between and among different critical infrastructures mandated to perform safely even during turbulent times. Indeed, a conceptual shortfall in some past table tops organized around accident scenarios for any one infrastructure has been the failure to consider these wider (manifest and latent) interconnectivities when scenarioizing.