Framing the Foresight Question
A foresight study is only as good as the question it answers. Before any scanning, an analyst must fix three things: the decision the work serves, the time horizon it reaches to, and the boundary of the system under study. A badly framed question does not produce a weak forecast; it produces a confident answer to the wrong problem, and wastes the entire cycle.
By the end you can
- Explain why framing precedes scanning and sets the terms of the whole cycle.
- Distinguish the decision, the time horizon and the system boundary as the three framing choices.
- Recognise the common failures of a badly framed foresight question.
- Frame a question so that its outputs are decision-relevant rather than merely interesting.
Framing comes first
Analysts new to foresight reach for the tools: scanning, scenarios, forecasts. The experienced ones spend their first effort somewhere less glamorous, on the question itself. Framing is the act of deciding what the study is actually about, and it governs everything downstream. Scan without a frame and you drown in signals with no way to judge relevance. The discipline is to resist the pull toward activity and instead ask what decision this work exists to serve. Everything that follows inherits the quality, or the sloppiness, of that first choice.
Three choices that set the study
Good framing fixes three things. The first is the decision: who will act on this, and on what. Foresight that serves no decision is entertainment. The second is the time horizon: are we reasoning about eighteen months or fifteen years? The horizon changes which forces matter, because what is fixed over two years, such as installed infrastructure, is fluid over fifteen. The third is the system boundary: what is inside the study and what is treated as external context. Draw the boundary too tight and you miss the force that actually moves the system; draw it too wide and you cannot say anything specific. These three choices, decision, horizon and boundary, are the frame.
How a bad frame fails
A poorly framed question fails in recognisable ways. It answers a question no decision-maker asked, so the work is admired and shelved. It fixes a horizon that hides the relevant dynamics, forecasting next quarter when the client's exposure is a decade out. Or it draws a boundary that amputates the cause: a study of a firm's supply risk that stops at its direct suppliers will never see the upstream refinery where the real dependency sits. In each case the analysis can be rigorous and still worthless, because rigour applied to the wrong frame compounds the error rather than correcting it.
Framing in practice
DSI's Full Threat Surface discipline is, at root, a framing move: it insists the boundary be drawn wide enough to include the whole surface an adversary could reach, not just the assets a client happens to watch. That is a deliberate choice about the system boundary made before any scanning begins. The test of a good frame is simple and demanding: can you state, in one sentence, the decision this study serves, the horizon it reaches, and what lies inside its boundary? If you cannot, you are not ready to scan. Framing is where a foresight analyst earns their keep, because a well-set question makes the rest of the cycle tractable and a badly set one makes it futile.
Check your understanding
Answer each from memory. Your results are saved in this browser and count toward your readiness — sign in (account panel above) to keep them across devices.
Why must framing come before scanning in a foresight cycle?
Which three choices does framing fix?
A supply-risk study that stops at a firm's direct suppliers and misses the upstream refinery has failed at which framing choice?