Futurism Without Execution Is Storytelling.

I am a pragmatic futurist. I look for what regulation, infrastructure, incentives and human behavior make inevitable. Then I build toward it. Predictions are cheap. Deployable futures are expensive. They need licenses, distribution, teams and patience.

In 1994, few people trusted a browser with money. Joel Maske and I put stock quotes and personal finance on the web anyway, through a service called NETworth. The law was not ready either. In 1995, together with Vanguard and Fidelity, our small company went to the SEC for relief that would allow fund prospectuses to be delivered electronically. By October of that year, the SEC had issued formal guidance. It became legal.

Read the arc, not the headlines

Every platform shift I have built inside followed the same arc: infrastructure, consolidation, regulation, scale. A future becomes deployable at the regulation stage, when institutions can adopt it inside rules they understand. That is why I call regulation a feature, not a bug. A futurist who skips that step is telling a story.

My own board taught me this the hard way. I proposed that Galt become an online broker-dealer. The board said no. We would need licenses, and we did not have them. Decades later I understood that the licenses they feared were not only a barrier. They were a moat.

Foresight practice has moved the same way. The method many strategists now use is backcasting, a term from the Canadian researcher John B. Robinson: picture the future as done, then work backward to the steps that must be true to reach it. It is mission rehearsal run in reverse. It also guards against the trap Gates named: hype in the short run, neglect in the long run.

Turn a forecast into a build plan

1. List the forcesWrite what regulation, infrastructure, incentives and human behavior are already making inevitable in your market.
2. Find your stagePlace your market on the arc: infrastructure, consolidation, regulation or scale.
3. BackcastPicture the future as done. Work backward to the licenses, distribution, team and patience it will take.
4. Build before it is comfortableAsk what will still be needed if every current application fails. The answer is usually infrastructure. Start there.