A framework for making sense of challenges that won’t hold still.
Educational change often fails before implementation begins. We inherit assumptions from the present. We simplify systems that don’t behave simply. We reach for familiar categories before checking whether they still fit.
Most frameworks for change look one way. Foresight looks ahead. Systems thinking looks across. Design method looks for the next step. Each is useful, and each misses what the others catch.
This is my attempt to hold three of them together: futuring, complexity and ways of thinking, joined tightly enough to make sense of a challenge that is uncertain, tangled and possibly framed wrong, all at once. That describes most of the challenges worth working on right now. I haven’t found the three combined this way elsewhere. That’s why I think it’s worth building, and why I’m building it in public.
Each of the three interrupts one of the habits that sink change before it starts:
- Futuring expands what could be.
- Complexity improves how we understand interaction and change.
- Ways of thinking change how a situation can be framed.
The three stay separate disciplines.
What I’m after is the practical moves that improve judgement when the future is uncertain, the system is complex and the problem itself may need reframing.
Atlas reads the terrain at different scales. Loom shows how the threads hold together and what moves when one is pulled. A challenge that won’t hold still needs both, so the framework carries both names.
Why these three
Futuring
Foresight methods are good at one specific thing: taking seriously a future that isn’t an extrapolation of now. Scanning, scenarios and back-casting all exist to break the assumption that tomorrow is today with better hardware. Without them, planning quietly turns into defending current arrangements.
Read the strandComplexity
Complexity thinking takes as its object what the other strands assume away: a situation’s capacity to change, including in response to being analysed. It earns its place as a diagnostic and an overlay. It says when the other tools’ assumptions hold, and it adds seven checks to whatever tool a team already uses.
Read the strandWays of thinking
Design method, systems mapping, critical questioning and the rest turn an insight into something a team can do again next Tuesday without you in the room. They’re the most portable of the three, and the most easily hollowed out into a workshop with sticky notes and no argument.
Read the strandTen questions
The common unit
Each question, asked on purpose, changes what a situation looks like. Each comes from one strand, and all of them work on the same kind of problem. Inside each strand, four moves turn the thinking into a method you can run with a group.
- Futuring · 3
- Complexity · 3
- Ways of thinking · 4
- 01Ways of thinking
Surface the assumption
What must currently be believed for the present arrangement to make sense? - 02Complexity
Change the boundary
What happens when we include actors, effects, or timescales currently treated as outside the problem? - 03Ways of thinking
Change the scale
Does the problem look different at the learner, classroom, school, system, or societal level? - 04Ways of thinking
Find the feedback
What consequence of an action later changes the conditions that produced the action? - 05Complexity
Read the disposition
What is this situation already inclined to do, without us? - 06Futuring
Work backwards
If a preferable future existed, what conditions would need to have become true before it? - 07Futuring
Introduce discontinuity
What happens if a condition currently treated as stable changes abruptly? - 08Ways of thinking
Reverse the obvious
What would the opposite assumption reveal? - 09Complexity
Audit the options
Which options is this plan spending, and did anyone decide to spend them? - 10Futuring
Ask what persists
If the intervention disappeared tomorrow, what capability, practice, or knowledge would remain?
Tension
Where they conflict
The three strands disagree in places. Naming the conflict is more useful than pretending they agree.
Foresight wants scenarios, complexity resists prediction
FuturingDescribe futures to plan against
pulls against ComplexityEmergence resists forecast
Where I hold itScenarios as rehearsal, anchored in what the present is already disposed to do, with each scenario linked to a probe.
Scenario work asks you to describe several coherent futures in enough detail to plan against. Complexity says the interesting behaviour of a system is emergent and not reliably forecastable, and that confident description is exactly the error. Both are right about something. The reconciliation I can defend is to use scenarios as rehearsal. They build the capacity to recognise a situation when it arrives. They can’t tell you which one will. The complexity strand sharpens this. Futures work should grow out of what the present is already disposed to do, and each scenario should point to something small the school can try now and learn from.
Thinking frameworks want tractability, complexity refuses it
Ways of thinkingSimple enough to hold under pressure
pulls against ComplexityFaithful to a situation that isn’t simple
Where I hold itIt doesn’t dissolve. Name it, and teach the failure mode with the tool.
A framework earns its keep by being simple enough to hold in your head under pressure. Complexity earns its keep by insisting the situation isn’t that simple. A framework made complex enough to be faithful is no longer usable, and a framework usable enough to teach has already thrown away most of what complexity was pointing at. I don’t think this dissolves. You name it, and you teach people the tool’s failure mode along with the tool.
Ways of thinking choose a frame; complexity asks whether it will hold still
Ways of thinkingPick the frame that fits
pulls against ComplexityThe frame changes what it frames
Where I hold itChoose a frame, hold it as partial, and write down the trigger for switching.
The ways-of-thinking strand asks a team to notice its frame and choose one deliberately. Complexity asks whether any frame holds still long enough to be chosen, because the act of framing, measuring and acting changes the situation being framed. Both are right. The working answer is provisional commitment: choose a frame on stated grounds, treat it as one partial view among several, and decide in advance what you would need to see to switch.
Futuring is expansive, practice is bounded
FuturingA 15-year signal
pulls against PracticeAccountable for next year
Where I hold itTie the long signal to a live decision, or admit it’s sensitisation.
The horizon that makes foresight worthwhile is longer than the horizon most teams are accountable for. A department planning next year can’t act on a 15-year signal, and pretending otherwise produces a nice document and no change. The useful version connects the long signal to a decision that’s live now, or admits it’s doing sensitisation rather than planning.
Structure
The shape so far
The three strands meet on one situation. That much holds. How they fit together beyond that is still being worked out, and the questions below are where I’m stuck.
Unsettled
What is still open
- How few questions it can have and still be worth calling a framework. My instinct is that the ceiling is around seven, and I have ten.
- Whether it should be sequenced or modular. Sequence makes it teachable. Modularity makes it usable. I haven’t found a version that’s both.
- What the entry point is for someone with no background in any of the three. Every draft so far assumes more familiarity with systems vocabulary than is fair.
- How to tell whether it worked. The outcome I care about is a changed decision, months later, made by someone who no longer remembers where the idea came from. That’s close to unmeasurable.
- Whether complexity belongs in it at all. I have half an answer now. Complexity works as a diagnostic and an overlay: it says when the other tools’ assumptions hold, and adds seven checks to them. What still worries me is the evidence. Most complexity tools have many case studies and few controlled evaluations.
Where next
Follow this idea
Evidence
Complexity educationLibrary shelf
Operationalise it
Ten questions for thinking about educational changeTool
Related argument
The designed conditions of learningDomain
See it in practice
One problem, four ways of seeing itTool
Follow the concept
Concept indexPage
To take away
Try one question on a real problem before you agree with any of this.
I’d rather talk to someone who has tried to teach this and found it hard than to someone who agrees with me. If you’re building something in the same territory (foresight for schools, systems literacy, design method for educators, or any of it outside education), I’d like to hear how you handled the tensions above, especially the second one.