Most people begin change from where they are.
That is understandable. The present is visible. It is noisy. It is urgent. It has meetings, budgets, anxieties, habits, obstacles and people asking for answers.
But beginning with the present has a cost. It encourages us to ask, “What can we do next?” before we have properly asked, “Where are we trying to get to?”
That small difference matters.
When we start from the present, we often inherit the assumptions of the present. We treat today’s problems as the frame within which tomorrow must be built. We improve processes that may no longer be necessary. We accelerate projects whose outcomes have not been clearly defined. We become busy before we become purposeful.
D4 begins somewhere else.
It begins with the future.
Not the future as a vague aspiration, nor the future as a prediction, but the future as a clearly described outcome. What do we want to be true? What would have changed? What would people be doing differently? What value would have been created? What would no longer be a problem?
Only when that future has been made clear does it make sense to work backwards.
Why working backwards changes the conversation
A future-backwards approach changes the quality of thinking.
Instead of asking:
“What actions should we take?”
we ask:
“What would need to be true for this outcome to exist?”
Instead of asking:
“How do we keep this project going?”
we ask:
“What result would make this project worth doing?”
Instead of asking:
“How do we manage the problem?”
we ask:
“What would it mean for the problem to have been removed?”
This is not a matter of wordplay. It changes where authority sits. The future outcome becomes the reference point. The work is judged by whether it moves us closer to that outcome, not by whether it follows an inherited sequence.
In real life, change rarely happens in a neat order. People do not experience organisations as flowcharts. Events overlap. Decisions interact. Obstacles appear. Opportunities appear. The path has to be recalculated as reality changes.
That is why I often think of the process as being closer to a route-finder than a railway timetable.
A timetable assumes the route is fixed.
A route-finder keeps asking: given where we are now, and given where we need to arrive, what is the smartest path from here?
The danger of confusing activity with progress
Organisations are very good at producing activity.
They can produce plans, reports, governance structures, meeting cycles, risk logs, dashboards and delivery updates. These things may be useful. Sometimes they are essential.
But they are not the same as progress.
Progress exists only in relation to an outcome.
A stalled project is often not stalled because people are lazy or incompetent. It may be stalled because the outcome is unclear, contested, unrealistic, unvalued, or not connected to the actual behaviour of the people who must make it happen.
A project can be perfectly managed and still fail to matter.
That is why the question of value is central. If an outcome is achieved, what changes? For whom? In what way? What is the cash value, the human value, the organisational value, or the public value of succeeding?
Without that, effort becomes detached from meaning.
Making change human
There is another reason to begin with the future: people need to see themselves in it.
A future that exists only as a board paper will not move anyone very far. A future has to become a story people can understand. They need to know what part they play, what will be different, and why the change is worth the discomfort of leaving the present.
This is where many formal change methods become too thin. They describe structure, but not experience. They describe governance, but not meaning. They describe implementation, but not belief.
People do not change simply because a plan exists.
They change when the future becomes tangible enough, valuable enough and credible enough for them to act differently now.
A useful question
If you are facing a personal, organisational or project problem, try asking this:
“What would have to be true for this problem no longer to exist?”
Then ask:
“What would we see, hear or measure if that future had happened?”
Then:
“What is the first thing that must be true before that can become true?”
These questions do not solve everything by themselves. But they often improve the starting point. They move the mind away from complaint and towards design.
The present is still important. It gives us the facts. It tells us what resources, constraints, people and obstacles exist. But it should not be allowed to define the limits of the future too early.
The future should pull the present into shape.
That, for me, is the heart of making change happen.
Interested in D4 or future-backwards thinking?
Alan is open to conversations about mentoring, presentations and training.
Leave a Reply