Gerald Ajam

Foresight exists to loosen the grip of the present.

That is all futuring is good for, and it is worth more than it sounds. Left alone, every planning conversation assumes tomorrow will be today with better hardware. A plan built on that assumption is a defence of current arrangements wearing the costume of a strategy.

The Atlas & Loom framework

Why it matters

The failure this strand exists to prevent is quiet and extremely common. A team sits down to plan for the next five years, and without anyone deciding to, they plan for the present with the numbers adjusted. Enrolment goes up or down a little. The devices get faster. The timetable stays a timetable. Nothing in the room forces anyone to ask what happens if the shape of the thing changes rather than its size.

Clever, hard-working teams do it too. It is the default, because the present is the only thing anyone has direct evidence about, and evidence is what careful people reach for. Foresight is the discipline of deliberately reasoning from something other than evidence about now. That is uncomfortable by design.

For education the stakes are unusually high, because the lag is unusually long. A child entering school this year leaves the system more than a decade later, into working conditions nobody in the building can describe. Every curriculum decision is therefore already a bet about the future, whether or not anyone admits it. Futuring leaves the bet in place and makes it visible enough to argue about.

What I have come to believe

Foresight is not prediction, and the largest single cause of it being done badly is people quietly hoping it is. The moment a group starts asking which scenario is most likely, the exercise has reverted to forecasting and the other scenarios become decoration. I now say this out loud at the start of any session, and I still have to say it again halfway through.

The output that matters is a changed capacity to recognise a situation. Someone who has spent a day inhabiting four futures will, two years later, notice the early shape of one of them arriving and name it faster than a colleague who has not. That recognition is the actual product, and it is close to unmeasurable, which is a real problem for justifying the work.

Foresight has a horizon problem that most of its literature is coy about. The timescale that makes scanning worthwhile is longer than the timescale most teams are accountable for. A department planning next year cannot act on a 15-year signal, and pretending otherwise produces a well-received document and no change. A sound exercise either connects a long signal to a decision that is live now, or admits it is doing sensitisation rather than planning. Both are legitimate. Confusing them is not.

The methods are also less exotic than the field likes to present them. Scanning is structured reading with a discipline about what gets discarded. Scenarios are a 2×2 with better writing. Backcasting is working a plan in reverse. The value is almost entirely in the rigour of the doing, and almost none of it is in the novelty of the technique.

How I approach it

I start by asking what decision the exercise is meant to touch, and I refuse to start without an answer. Foresight with no decision attached becomes a pleasant away-day that produces a deck. If there is no live decision and the aim is to change how a group thinks, that is fine. It is a different exercise with different success criteria, and it should be named as such on day one.

Then I spend more time than people expect on the uncertainties rather than on the futures. A scenario set is only as good as the two things it chose to be uncertain about. Choose badly and you get four descriptions of the same world in different hats, and no amount of good writing afterwards will rescue it.

And I try to leave the group with something they can run again without me. A scenario set that only the facilitator can use has failed at the thing this strand is supposed to contribute to the framework.

Limits

Where it stops being useful

Every method in the framework has a failure mode, and teaching the tool without teaching its failure mode is how a method becomes a ritual. These are futuring’s.

  • When the group wants a forecast. If the decision genuinely requires knowing what will happen, foresight is the wrong instrument and saying so is the useful contribution.
  • When the horizon is shorter than a year. Below that, the future is mostly the present with known events in it, and ordinary planning is better and cheaper.
  • When nobody in the room can act. Foresight run with people who have no decision rights produces frustration dressed as engagement.
  • When the scenarios harden into names. Six months on, people reason from the label rather than the description underneath it, and a memorable name becomes a substitute for the thinking it was meant to carry.

Unsettled

What I would still argue about

The part of this page I would defend least confidently.

  • Whether the recognition capacity I claim as the real output actually exists, or whether I believe in it because it is the one claim that cannot be falsified.
  • How much of the value is in the scenarios and how much is in the arguing. My read is that the people who argued hardest about the axes got the most out of it, and they might have got that from any well-run disagreement.
  • Whether foresight can be taught to a school team in a day, which is usually all the time there is, or whether a day only ever produces the feeling of having done it.
  • How to keep a scan alive. A horizon scan is a photograph and it starts ageing immediately. I do not know what maintaining one costs, or who should do it.
Singapore