Pandemic Anytown

Pandemic Anytown

Reading Time: 3 minutes

Remember that song you learnt at school… “the knee bone’s connected to the leg bone“? Well, that song tells us to think of the body as a system of interconnected and interdependent components which work together to form a whole. Make a change somewhere and the repercussions of that will be felt elsewhere.

Other metaphors are available: The butterfly effect. The domino effect.

For a whole host of reasons though, we often focus more on components over systems; and it’s important we do that.

It’s important that when we plug something into an electrical socket or turn on a tap that what we are expecting comes out.

But we should ask ourselves why that is important. It’s important because, owing to our highly connected modern society, when a component fails the cascading impacts of that can be felt far and wide. It’s not just inconvenient, it can sometimes have direct safety implications.

When an earthquake struck northern Italy in 2013, the NHS in the UK had a supply issue with dialysis tubing.

We’re seeing similar right now with the COVID pandemic. It’s not just the impact of people who contract the disease, but the far-ranging impacts and knock-on effects of social distancing and isolation, reduced international travel and changing perceptions of risk.

I started the ANYTOWN project in 2013 as an attempt to better understand and describe how a partial or total failure of a network can impact on other connected networks. In some circumstances, this can lead to a much larger range of impacts than just the initiating incident.

Previous blog posts about ANYTOWN cover a bit more of the background of the project. But I’ve been attempting to apply the same model to describe what we are seeing (and may see in the coming months) with COVID.

There is very little ‘real science’ to this. Previous Anytown work was informed by extensive focus group research. However, as this is a highly dynamic situation this is primarily my musings. I shared it on LinkedIn over the last week and I’m indebted to those who have made suggestions and offered feedback.

This is is a work in progress. It is biased towards my own experiences as a middle-class white man in his thirties in London. I appreciate that other people’s experience of COVID will be different. I want to reflect that in future versions, but at the moment it is a limitation that I have noted.

Here’s version 1.2 for you to explore…

Starting in the centre is the initiating incident, in this case, the pandemic virus. Although there may be some specifics to COVID I suspect many of the cascading consequences would be relatively similar across different global pandemic threats.

The next ring out from the centre describes the ‘first-order’ impacts that are/have been observed across a range of different sectors. So some of the first impacts that would be anticipated (and have played out with COVID) are the introduction of social distancing measures, reduced public transport use and increased handwashing.

Second and third-order impacts for each sector are then captured as you move further from the centre. The diagram deliberately doesn’t indicate timescales; I intended this to help understand sequence, not timing.

This is a bit of a thought experiment to see if the model would work having previously been geared towards ‘hard infrastructure’ systems failure. I think it does, but it needs some development. I’m incredibly grateful to those who have made suggestions (I haven’t checked that it’s ok to specifically credit them so acknowledgements to feature in a future version!) or have commented that they have found it useful.

It’s not the answer to the problem. Not by any means.

But hopefully, it’s a useful tool to help us all to think about how our increasing interconnectedness. Normally this is super helpful, but it can sometimes work against us. At a time when there’s lots of uncertainty about lots of things, perhaps this offers a bit of a glimpse into the future to help us be prepared.

Comments are closed.
%d bloggers like this: