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.
This is not a failure of intelligence or of effort. It is what happens by 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 — which is uncomfortable, and is exactly the point.
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 does not remove the bet. It makes the bet 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 not the document. It is the 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. The honest version 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 the honest answer is that there is no live decision and the aim is to change how a group thinks, that is fine — but 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 toolkit.