Time-saving bias

Time-saving bias is misjudging how much time a change in speed actually saves, especially when comparing rates rather than durations.

Mechanism

How it works

Speed feels linear, but travel and processing time are reciprocal: time equals distance divided by speed. Moving from 20 to 40 km/h halves the time; moving from 80 to 100 km/h saves far less over the same distance. Intuition often notices the extra speed but not the denominator.

Examples

Where it shows up

  • On a 100 km trip, raising speed from 50 to 100 km/h saves an hour; raising it from 100 to 150 km/h saves only 20 minutes. The speed gains look similar, but the time gains are not.
  • A team pays to make a two-second page load one second faster while leaving a ten-minute manual approval unchanged.
  • A commuter chooses a faster route without checking whether its extra distance, congestion, or parking time erases the expected saving.
Consequences

What it can distort

  • People overpay for marginal speed and underinvest in removing the slowest, most repeated step.
  • In transport and operations, it can produce unsafe or expensive choices for a time benefit that is much smaller than it feels.
Countermeasures

How to work around it

  • Calculate end-to-end time in minutes, including waiting, setup, and handoffs; do not compare speeds alone.
  • For repeated work, multiply the measured saving by frequency, then compare it with the cost and risk of achieving it.
Caveats

Critiques and limits

A faster option can still be worth choosing for comfort, reliability, or safety. The bias concerns a numerical claim about minutes saved, not every preference for speed.

Taxonomy

Fields of impact

Evidence

How solid is the research?

Mixed — real but conditional

People often make predictable errors when estimating time saved from speed changes, although the size and direction of errors vary with presentation and task familiarity.

Research

Relevant papers

Case studies

Real-world patterns.

Real-world examples showing how Time-saving bias manifests in practice

Case study

Fixing the Login Screen, Ignoring the Discharge Bottleneck

A real-world example of Time-saving bias in action

Context

A 300-bed regional hospital sought to improve clinician productivity and reduce after-hours charting. Leadership prioritized IT projects based on perceived clinician frustration and visible daily pain points.

Situation

The IT director proposed purchasing a biometric single sign-on (SSO) solution to speed electronic health record (EHR) logins after several clinicians complained about authentication delays. At the same time, a small workflow team recommended automating parts of the discharge paperwork that currently required manual data entry and phone calls to coordinate community services.

The bias in action

Decision-makers fixated on the highly visible annoyance of login delays and estimated the SSO would save 90 seconds per login — a figure influenced by memorable complaints rather than measurement. That estimated saving was multiplied across the number of clinicians and logins to produce a large projected time-savings headline. The longer, less frequent discharge tasks felt less salient and their time-savings were dismissed as 'marginal' per patient. No formal time-motion study was commissioned; the team relied on gut estimates and anecdotal reports.

Outcome

The hospital approved a $240,000 budget for SSO and implemented it over three months. Post-deployment measurement found average time saved per login was only 8–12 seconds (clinicians still paused for patient context checks and other steps), so actual aggregated time savings were one-tenth of the projected amount. Meanwhile, the discharge automation pilot—deferred for budget reasons—remained undone. Over nine months the hospital experienced continued discharge delays, increased length of stay for patients awaiting community referrals, and recurring overtime for case managers.

What's inside the full case study

Unlock the deeper breakdown with real-world impact, measurable effects, lessons learned, better-approach recommendations, and relevant fields.

Real-world impact
Affected groups, timeframe, and measurable outcomes.
Lessons learned
Practical takeaways and a better path forward.
Full case breakdownEmail access

Want the full analysis?

Request access to the complete case study, including measurable impact, lessons learned, and the recommended better approach.

We'll use your email to follow up about case-study access.

Further reading

Recommended books

Related biases

Nearby patterns.

Study on Microcourse

Learn the wider pattern.

Dive deeper into Time-saving bias and related biases in Decision-Making and Risk Biaseswith structured lessons, examples, and practice exercises.

Practice

Test your knowledge.

Apply what you have learned and reinforce your understanding of Time-saving bias with a short quiz or self-assessment.

Entry last reviewed 2026-07-19 · sources verified against the published literature — methodology

Time-saving bias - The Bias Codex