Time-Saving Bias

The glitch, explained plainly.

Imagine you're walking really slowly and you start jogging—you'd get there way faster. But if you're already sprinting and you try to sprint even harder, you barely save any time at all. Our brains think the opposite: that speeding up when you're already fast helps a lot, and speeding up when you're slow doesn't help much. It's like thinking adding another scoop of ice cream to a huge sundae matters more than adding one scoop to an empty bowl.

The time-saving bias describes people's inability to grasp the curvilinear (inverse) relationship between speed and travel time. When increasing from a low speed, the actual time saved is much larger than people intuit, and when increasing from an already high speed, the actual time saved is much smaller than people believe. This occurs because people tend to use a proportion or difference heuristic—judging time saved based on the ratio or gap between speeds—rather than applying the correct mathematical formula. The bias extends beyond driving to any domain where output rate affects completion time, including healthcare staffing, manufacturing productivity, and project planning.

Where it shows up.

1. 01 A city transport planner must choose between two road improvement projects: Plan A increases average speed on a suburban road from 30 km/h to 40 km/h, while Plan B increases average speed on a highway from 80 km/h to 120 km/h. Both roads cover the same distance. She confidently recommends Plan B, believing the larger absolute speed increase will save commuters more time, even though the math shows Plan A saves significantly more.
2. 02 A hospital administrator is deciding whether to add a physician to a slow rural clinic that sees 8 patients per hour or to a fast urban clinic that sees 25 patients per hour. He allocates the new physician to the urban clinic, reasoning the larger throughput boost there will reduce patient wait times more dramatically, not realizing the rural clinic would see a much greater proportional reduction in wait times.
3. 03 A factory manager is reviewing two proposals to reduce production time: Option 1 increases assembly line speed from 30 to 60 units per hour, and Option 2 increases a different line from 90 to 150 units per hour. She picks Option 2 because the absolute gain of 60 extra units per hour seems more impressive, overlooking that Option 1 actually frees up far more production time per unit.
4. 04 Marco is running late for a flight and is already driving 110 km/h on the motorway. He decides to push to 140 km/h, convinced this will shave critical minutes off his 50 km remaining drive. In reality, the increase saves him less than 4 minutes while dramatically increasing his accident risk.
5. 05 A software engineering lead is deciding which microservice to optimize. Service A handles 200 requests per second and could be improved to 300, while Service B handles 20 requests per second and could be improved to 40. She prioritizes Service A because the 100 req/s gain feels larger, not realizing that Service B's improvement would halve its response latency—a far greater time saving per request.

Where it shows up at work.

The same glitch looks different depending on the terrain. Finance, medicine, a relationship, a team — same mechanism, different costume.

In history.

• Road safety policy debates in multiple countries where speed limit increases on highways were preferred over urban traffic flow improvements, despite mathematical evidence that the latter would save more aggregate commute time.
• Sweden's road improvement planning studies (Svenson 2008) where respondents consistently chose to increase highway speeds from 70 to 110 km/h over increasing urban speeds from 30 to 40 km/h, despite the urban improvement saving more time.