Help ATS with a contribution via PayPal:
learn more

What is "forensic futurism"?

page: 1
0

log in

join

posted on Mar, 12 2012 @ 06:34 PM
link   
If there's a common trope about "futurism," it's that it gets everything wrong.

From jetpacks to vacations on the Moon, any discussion of futurism in broader culture very quickly turns into a listing of the various crazy things that "futurists" (whether or not they'd call themselves that) have said over the past century. Sometimes it's an easy one-off article, sometimes it's an entire book
or blog devoted the topic. Done well, it's a kind of indulgent ridicule: those futurists sure are whacky, but charmingly whacky.

Anyone who has read my stuff will know that I'm not really fond of being called a "futurist," although it's the most widely-recognized name for what I do. I don't make predictions, and I don't talk in certainties; I'm all about trying to illuminate surprising implications of present-day processes. I don't expect that the scenarios I offer will be right, but I do want them to be usefully provocative.

But that doesn't mean that I'm irritated by the focus on futurists being wrong (although I will admit to being tired of the "jetpack" trope; can't we come up with another stereotyped prediction?). I wrote a piece awhile back about "legacy futures," and pay close attention to the responsibility foresight professionals have to acknowledging when they get things wrong.

So when the term "forensic futurism" showed up today (see the extended entry for how & why), it hit me as something both useful and meaningful.

It's not enough simply to point and ridicule about whacky futurists. Those of us in the discipline really need to examine why serious forecasts can turn out to be terribly wrong. This takes two related forms:

Understanding why forecast X didn't happen as expected. Maybe we thought that certain drivers would continue to be important, or that other drivers wouldn't be important, or perhaps simply never expected a "Black Swan" event. This is a useful practice for all foresight professionals, in order to better understand (and ultimately to communicate) how reasonable expectations can go terribly wrong.
Understanding why X was forecast in the first place. This is the more difficult process, as it requires engaging in an objective, dispassionate look at how futurists came to their conclusions. Not simply what they looked at, the lines of evidence they selected as important, but why they chose those lines of evidence in the first place.
"Forensics" is a process involved in criminology, and I don't want to imply that futurists who get things wrong are doing something of dubious morality or legality. Instead, I'm riffing on the more popularized concept of the process, that of a strictly-evidence-based examination of a mysterious result. Leaping to conclusions, going only by hunches, and other subjective approaches are to be frowned upon; what we want to do is take a serious look at how we think about the future, in order to do so more usefully in the time to come.
It's a bit frustrating sometimes.
I'll be doing something innocuous -- reading a magazine, playing a game, something with a relatively low (but not zero) cognitive threshold, so that my brain is working but not focused -- and a phrase will pop into my head. It'll be novel (to me), typically a combination of terms that don't usually go together, yet seemingly something meaningful. I'll hop onto whatever digital device I have handy to see if someone else is already talking about the topic, to see if it's already a real thing. Often it is, and I can return to whatever I was doing. But sometimes, it's not -- it's a combination of terms that hasn't before been seen by the mighty eye of Google.

"Forensic Futurism" was today's term. And aside from a few pages including the two terms in an alphabetical listing, it's a term without a pre-existing presence. So the rest of my afternoon was spent trying to figure out what the hell forensic futurism might be, and why it sounded like it should mean something useful and/or important.

io9.com...






 
0

log in

join