Posts Tagged ‘roadmap’
“They laughed at Columbus and they laughed at the Wright brothers. But they also laughed at Bozo the Clown.”*…

Most technologies that grow up to be important, Benedict Evans observes, start out looking like toys with little or no practical application.
Some of the most important things of the last 100 years or so looked like this. Aircraft, cars, telephones, mobile phones and personal computers were all dismissed as toys. “Well done Mr Wright – you flew over a few sand dunes. Why do we care?”
But on the other hand, plenty of things that looked like useless toys never did become anything more than that. The fact that people laughed at X and X then started working does not tell us that if people now laugh Y or Z, those will work too.
So, we have a pair of equal and opposite fallacies. There is no predictive value in saying ‘that doesn’t work’ or ‘that looks like a toy’, and there is also no predictive value in saying ‘people always say that.’ As [Wolfgang] Pauli put it, statements like this are ‘not even wrong’ – they give no insight into what will happen.
Instead, you have to go one level further. You need a theory for why this will get better, or why it won’t, and for why people will change their behaviour, or for why they won’t…
That’s to say, Evans suggests, you need to be able to envision a roadmap from “toy” to wide, practical use…
These roadmaps can come in steps. It took quite a few steps to get from the [Wright Flier, pictured above left] to something that made ocean liners obsolete, and each of those steps were useful. The PC also came in steps – from hobbyists to spreadsheets to web browsers. The same thing for mobile – we went from expensive analogue phones for a few people to cheap GSM phones for billions of people to smartphones that changed what mobile meant. But there was always a path. The Apple 1, Netscape and the iPhone all looked like impractical toys that ‘couldn’t be used for real work’, but there were obvious roadmaps to change that – not necessarily all the way to the future, but certainly to a useful next step.
Equally, sometimes the roadmap is ‘forget about this for 20 years’. The Newton or the IBM Simon were just too early, as was the first wave of VR in the 80s and 90s. You could have said, deterministically, that Moore’s Law would make VR or pocket computers useful at some point, so there was notionally a roadmap, but the roadmap told you to work on something else. This is different to the Rocket Belt [pictured above right], where there was no foreseeable future development that would make it work…
Much the same sort of questions apply to the other side of the problem – even if this did get very cheap and very good, who would use it? You can’t do a waterfall chart of an engineering roadmap here, but you can again ask questions – what would have to change? Are you proposing a change in human nature, or a different way of expressing it? What’s your theory of why things will change or why they won’t?
The thread through all of this is that we don’t know what will happen, but we do know what could happen – we don’t know the answer, but we can at least ask useful questions. The key challenge to any assertion about what will happen, I think, is to ask ‘well, what would have to change?’ Could this happen, and if it did, would it work? We’re always going to be wrong sometimes, but we can try to be wrong for the right reasons…
A practical approach to technology forecasting: “Not even wrong: predicting tech,” from @benedictevans.
* Carl Sagan
###
As we ponder prospects, we might send carefully-calculated birthday greetings to J. Presper Eckert; he was born on this date in 1919. An electrical engineer, he co-designed (with John Mauchly) the first general purpose computer, the ENIAC (see here and here) for the U.S. Army’s Ballistic Research Laboratory. He and Mauchy went on to found the Eckert–Mauchly Computer Corporation, at which they designed and built the first commercial computer in the U.S., the UNIVAC.

You must be logged in to post a comment.