Who decides what counts and what gets counted?
When I first encountered Michel Foucault’s concept of veridictions several years ago, it was like having a new set of spectacles that caused me to look at the management processes, metrics and tools very differently.
I think that anyone studying or practicing management, or subjected to management processes, should familiarise themselves with the concept of veridictions. While the idea is not new and many will recognise veridictions within their work, it’s helpful to be reminded that the things we can often view as ‘truths’ within management, are usually socially constructed. And anything that is constructed, can be deconstructed, and reassembled another way.
What are veridictions?
A veridiction is something that holds truth according to a particular authority or worldview, rather than being independently or objectively true. Stories are veriditions - truths according to a perspective. The concept is intrinsically linked to the French philosopher, Michel Foucault, and his notion of ‘Regimes of Truth’. It’s been widely applied to political and social life, but veridictions also pervade the modern world of work. Verifications subtlety influence how we determine what we view as true or false, good or bad, or indeed acceptable and expected in work performance.
Management tools, such as metrics, evaluations, audits, procedures and performance goals contribute to what Foucault called managerial ‘truth telling’. They create define what we accept as true or false. If your role involves any form of evaluation, measurement, classification, prescription/proceduralisation, weighting/ranking, commensuration, assuring or verifying, then your work involves veridictions. We need these processes – in fact we cannot manage work without them. But we often overlook how subjective and arbitrary these processes are. Often we can be too close to them to recognise that what we’re looking at is not an absolute truth, but just a perspective. Foucault frames managements tools and processes through the lens of power/knowledge, subjectification and discipline, questioning who gets to decide what is measured, valued and rewarded.
Here's some common examples of verifications from the world of safety:
领英推荐
These are four very simplistic examples and there are many more. Indeed, almost all components of management systems are veridictions. ?
So what?
Of course, none of this is new and you’re probably wondering so what... My point is not to dismiss representations and veridictions that we rely on. We cannot be omnipresent or live in reality of frontline work; we need representations and veridictions to manage.
But as we increasingly use more digitalised processes, Big Data, algorithms and automated decision-making to manage safety and keep people safe and healthy, we can easily be fooled into believing that what we are seeing is reality and truth. Too often metrics, audits, criteria and management processes are applied as absolute truth and not questioned.
Foucault’s concept of veridiction is a useful reminder that often what we’re looking at not an absolute truth, but a perspective and an interpretation. The concept of veridicton acts as ‘pinch/grain of salt’, remining us that most activities in management systems, metrics and processes are not scientific facts, but someone’s interpretation of truth. Just recognising them as a veridiction and considering who gains, loses, is affected or discriminated can be enough to open the mind and explore different perspectives. And greater discussion and transparency is surely a good thing?
If you’re interested in learning more about Foucault’s regimes of truth, check out this paper: https://www.genealogy-critique.net/article/id/7026/
This site provides an overview of Foucault’s main thinking: https://michel-foucault.com/key-concepts/#:~:text=Foucault's%20entire%20philosophy%20is%20based,various%20points%20in%20his%20career.
The book ‘Management Tools: A Social Sciences Perspective’ by Eve Chiapello and Patrick Gilbert does a great job applying Foucault to the modern world of work.?
HM Principal Specialist Inspector | Chemicals, Explosives and Microbiological Hazards Division
1 年Thanks, James. Really useful to have a name to put to what’s bothering me about a fair amount of content in my feed just now!
Professional Process Safety Engineer
1 年Great article James Pomeroy. It is an interesting concept. Following incidents I sometimes hear "the HAZOP must have been poor because that scenario was missed". Do you think that the existence of a HAZOP allows the belief that a facility is "safe" to become an established "truth" (at least in some circles)? Would this make a HAZOP report be a veridiction? Or have I misinterpreted this article?
Non Executive Director @ the UK Flight Safety Committee (All views are mine)
1 年Many thanks James, for sharing this interesting concept which I hadn't heard of before. Regarding the question of who decides what counts and what gets counted, I used the attached slide in various presentations in the past. I also find this quote "what we measure shapes what we collectively strive to pursue – and what we pursue determines what we measure" from this report (https://ec.europa.eu/eurostat/documents/8131721/8131772/Stiglitz-Sen-Fitoussi-Commission-report.pdf) very true!
Cultivateur en organisation : Risque & Sécurité /Qualité
1 年Thanks James Pomeroy
Director of Environment, Health & Safety at Knight's Companies
1 年Great post and thoughts James! As you point out “incidents” are the tip of problem. I would a liken it to an iceberg, the KPI’s are the only visible, exposures part. What lays beneath the surface is rarely questioned. I believe mainly due to a lack of understanding as well as a lack of psychological safety in being able to voice the question “Why?”. I think you can attribute some colossal failures to the misdirection that can be caused when the KPI’s and reality are on a divergent course. With the digital, technological age, their is a ability to measure just about everything. While some of this can be interesting, mostly it creates additional noise. Our confirmation bias can lead us to see this as “supporting” data. We have heard in safety many times “the lack of one thing, doesn’t prove the presence of something else”, but I would also say the in this case the presence of something can easily be misinterpreted as something else. For instance the presense of productivity, doesn’t prove the presence of efficiency. For many organizations that want to be data driven, this is a subject that should be at the forefront of their attention.