Framework

Amara's Law

You overestimate new tech's short-run impact and underestimate its long-run impact — so ask if you're early, not whether it's working.

Amara's Law Find this on the mind-map

Introduction

Roy Amara, a researcher who went on to lead the Institute for the Future, put a name to a pattern he kept noticing: we tend to overestimate the effect of a new technology in the short run, and underestimate its effect in the long run.

Here's why it happens: expectation and capability move at different speeds, and they cross at a point almost nobody's watching for.

How It Works

Amara's Law diagram

The pattern runs in three phases:

Phase What expectations do What capability does
Hype Spike on announcement — "this changes everything, right now" Still early and rough
Trough Collapse as the real version disappoints, and people write it off Keeps improving, unnoticed
Quiet arrival Nobody's talking about it anymore Good enough that it's simply the default way of working

The iPod is a clean example. The promise was carrying your entire music collection everywhere. The first reality was skipping playback and a battery that died too fast — that's the trough. Storage, sync speed, and battery life kept improving generation after generation while most people had stopped paying attention, and at some point the thing stopped being a gadget and just became how you listened to music.

You'll see the same shape play out inside teams. Say a manager rolls out an AI coding assistant and adoption stalls — one engineer dismisses it as fancy autocomplete. The tools keep getting better, adoption picks up slowly and then quickly, and a year later the whole team is using AI assistants for coding, testing, documentation, and full spec-driven workflows. Nobody asks whether they should use it anymore, and nobody even remembers being skeptical. That forgetting is part of the pattern.

Amara's Law isn't a prediction machine — it doesn't say every hyped technology eventually arrives. What it says is that a single snapshot of a technology, taken at any one moment, is a bad basis for guessing where it's headed.

Why It Matters for Leaders

You can make two mistakes here, and they're the same mistake pointed in opposite directions.

The hype mistake is getting excited too early — telling a VP that AI will cut delivery time in half by next quarter, missing that target, and having every claim you make after that carry a credibility discount.

The dismissal mistake is writing something off too early — calling a tool "fancy autocomplete" and sitting it out, only to find a few months later that it's improved enough to be impossible to ignore, with your team now behind.

Both mistakes come from the same error: you looked at the technology once, at one point in time, and used that single look to decide where it was heading.

The dismissal mistake usually costs you more, because you pay for it under pressure. Picture an engineering manager who moves part of his team's infrastructure to the cloud, sees no efficiency gain and worse reliability after two months, and reverts to self-hosting. A year later the whole company moves to the cloud anyway, and he's restarting the migration from scratch — this time on someone else's timeline. That first migration wasn't a failed project. It just hadn't been given time to settle.

There's a version of this about people, too, not just tools. Say a principal engineer pushes to break a growing monolith into smaller services and gets outvoted — including by her own manager — on the grounds that it's too much work for too little payoff. Eighteen months later the codebase is hard enough to maintain that customer escalations are climbing and every fix takes days, and the team takes on that exact project anyway. The person telling you where things are heading is worth listening to, even when their timing is inconvenient.

The real value of this law is that it shows both patience and urgency can be the right call, depending on where you're standing. If you can't tell which one applies in a given moment, you'll default to whichever one matches your personality.

Your chat with Kyoshi about the Amara's Law framework

What to do next

Test your knowledge of Amara's Law

Take the quiz →

Practice Amara's Law

Apply Amara's Law to a real situation

Skills related to Amara's Law

Frameworks related to Amara's Law

Books related to Amara's Law