“The worst misunderstandings sometimes happen between different teams within the supposedly same ethnic group, particularly if they [come] from different locations or had different professional training (say, IT workers mingling with engineers)” – Gillian Tett

I have long been fascinated by differences in approach between engineers and Asset Management professionals – how AM is not just another variety of engineering. And, for that matter, why Operations managers don’t think like AMps, or how IT teams look at the world. For instance: what is it that motivates people in IT teams? (Not, I think, the pleasures of making users happy.)

In my own life, I seem to have sharply favoured working with maintenance, or ex-maintenance people, rather than Engineers with Capital E.  Because they were very different experiences.

It is not that there have not been engineers who are massively important to me, such as my brother, or my parents’ best friend Ed – but then again, they never acted like typical engineers, and were not very polite about such ‘grey men’ (Ed’s phrase) themselves. That engineering does have its own cultural norms, some quite odd, has been a question for me for many decades.

So my eye was caught by the review of a book by Financial Times editor Gillian Tett, Anthro-Vision: How Anthropology Can Explain Business and Life.  About trained anthropologists such as Tett who have found themselves working in businesses, such as Google or GM, or what they would advise governments on dealing with COVID-19.

She describes how anthropology is about both investigating what’s strange, other, exotic, and about the tools to see our own culture/s, to understand what is weird (or even WEIRD) about it. The book has plenty of interesting examples – about Kit Kats in Japan become an indispensable good luck charm for school exams, about dealing with Ebola or ‘CDOs’, as well as more effective advertising and work practices.

But it particularly made me think of how to understand the oddities of current engineering – why is so often tends towards the short term, to silos and uncoordinated stupidity, even resistance to data. Surely none of those attitudes are ‘logical’ – so what is really going on?  I take it as given that, like IT, there is a coherent motivation, a vision of what it means to be a good engineer.  So how come… that doesn’t play nice with Asset Management, so often?

And then again… what is the culture of Asset Management, developing before our eyes?

Because I also take it that if you don’t try to understand the water you swim in, you also don’t really understand what you are doing – how it might need to change or evolve – and why it gets up the nose of others who don’t share your basic values.

There is always culture, always weird to someone outside it, and managing infrastructure involves several different ones. So we must have anthropology in our Asset Management toolkits, too!

Next: Ethnographic approaches we might use in practice?