Is It Better to Know?

Is it always better to know how long it’ll take you to get somewhere? If not, what are examples of times when it would be better not to know?

Your phone says thirty-seven minutes. You can settle into the ride, or you can watch the number, and every red light becomes a personal insult.

Key concepts

Cost Versus Experience: Time you are enduring and time you are living are different goods. A commute is a cost, so putting a bound on it helps; a hike is the experience itself, so measuring it shrinks it.

+ 1 more concept inside

Every work — at a glance

The Psychology of Waiting Lines — David Maister, 1985 (paper)

The 1985 paper that named why waits hurt: an uncertain wait feels longer than a known one, and an unexplained wait longer than an explained one.

+ 2 more works explained inside

What to know

01
The rule is what the time is for. Knowing helps when time is a cost you are trying to bound — a commute, a queue, a wait you cannot shorten anyway. Knowing hurts when the time is the experience, because a clock you keep checking is a clock you are watching instead of living.

+ 1 more insight inside

Across subjects

Hitchcock made the opposite case for film. Show the audience the bomb under the table and tell the characters nothing, and you buy fifteen minutes of suspense;

Theme connection

"Are We There Yet?"

The question is a demand to know — and the demand is not always wise. One side says information is a gift: you can choose to ignore a clock, but you cannot un-ignore one you never had. The other says surprise, immersion and wonder all die under a countdown.

Practice — a sample

SOCAlways knowing exactly how long something will take, the likely cost is —

A More anxiety
B A longer wait
C Worse planning
D Higher expectations
E No surprise left

Keep reading the full lesson

The remaining insights, works, and practice come with full access — $9.99/month or $29.99/season.

Unlock full access →

New here? Create a free account to read the free section.