The billion-dollar mistake of judging a new technology too soon
In 1984, when Apple introduced the Macintosh, Andrew Grove looked at it and saw a toy. It had no hard disk, at a time when every serious personal computer had one. It was slow. Its much-praised graphical interface, the little pictures and windows you clicked on instead of typing commands, struck him as more nuisance than advantage. He missed, by his own later admission, the far more important thing the Macintosh was demonstrating: that a graphical interface gives every program a shared, learnable structure, so that learning one piece of software teaches you the shape of all the others.
Grove calls this the trap of the first version, and he doesn't exempt himself from it. In 1991, when Apple began talking about hand-held computers called personal digital assistants, plenty of people, including many inside Intel, treated them as a coming 10X force, capable of doing to personal computers what personal computers had done to mainframes. Intel invested heavily to make sure it wouldn't be left out. Then Apple's Newton arrived in 1993 and was widely mocked for its failures.
Grove's point is not that hype should always be trusted, nor that it should always be dismissed. It's that the quality of a technology's first clumsy attempt tells you almost nothing about its long-term significance. The first commercial computer with a graphical interface sold poorly. The first version of Windows was, for years, dismissed as DOS with a pretty face. Both went on to reshape the industry. The first version of almost anything that later mattered was disappointing, because building something genuinely new takes several attempts to get right, while the underlying force behind it, once real, keeps growing regardless of how bad the first try looked.
Grove's suggested test is to imagine the thing ten times better, not as it stands. Picture a slow, clunky, half-built page loading on an early internet connection, then ask: what happens to this experience if the connection speed doubles? If professionals build the content instead of amateurs? If you can still shrug and say it wouldn't change anything for you, it's probably noise. If your gut says it would matter, you may be looking at the start of something real.
Next time you catch yourself dismissing something clunky and new, pause and ask whether you're really judging the idea itself or just its rough, unfinished first attempt. Try the ten-times test: picture the same thing significantly faster, cheaper, or better made, and notice whether your gut reaction changes once you do. Remember, too, how unimpressive your own first encounter with something you now can't live without probably was, and let that memory soften your certainty about the awkward newcomer in front of you. Stay skeptical of hype, because most of it never pans out, but don't let that skepticism turn into a habit of shutting your radar off entirely, because the very few things that do reshape everything usually looked disappointing before they did.
What You'll Achieve
The listener learns to withhold judgment about a genuinely new capability based on how rough its first version looks, and gains a simple mental test, imagining the thing ten times improved, for separating a real emerging force from a passing gadget.
Test the idea, not its clumsy first draft
Separate the execution from the force behind it.
When you dismiss a clunky new product or idea, ask whether you're judging the underlying capability or just its first rough attempt.
Run the ten-times test.
Imagine the same thing, but faster, cheaper, or better by an order of magnitude, and ask whether your reaction changes.
Remember your own history with new things.
Recall how unimpressive your first exposure to a technology you now depend on actually was, and let that temper your certainty about today's clumsy newcomer.
Stay skeptical of hype without shutting off your radar.
Most breathless claims about a new gadget don't pan out, but the ones that do usually looked disappointing at first too, so keep watching rather than dismissing outright.
Reflection Questions
- What new idea or product have you dismissed recently mostly because its first version was clumsy?
- If that same capability were ten times faster, cheaper, or better made, would your judgment of it change?
- What technology do you now depend on that you once thought was a toy or a gimmick?
- How do you tell the difference between healthy skepticism and simply refusing to look again?
Personalization Tips
- A shop owner dismisses an early version of an online ordering app because it's buggy and slow, then realizes the question isn't whether this version works, but what ordering looks like once it's fast and reliable.
- A manager who once mocked a colleague's clumsy first attempt at automating a report later admits the automation, once refined, saved the team hours every week.
Only the Paranoid Survive: How to Exploit the Crisis Points that Challenge Every Company and Career
Ready to Take Action?
Get the Mentorist app and turn insights like these into daily habits.