Skip to content

CONCEPT Cited by 1 source

Timing-based information surfacing

Definition

Timing-based information surfacing is the UX discipline of showing information at the moment it becomes actionable, not at the moment it first becomes available. The underlying observation is that when a user sees a piece of information matters as much as whether they see it at all:

  • Too early — cognitive load; user dismisses, forgets, or can't act on it.
  • Too late — user has already fallen back on a worse strategy (ad-hoc text/call, wrong turn).
  • At the right moment — user acts on it with minimal interruption.

The driver-safety case

Lyft's 2026-04-23 write-up makes the case sharply for the driver app:

"They are likely navigating with eyes on the road — so a paragraph of gate instructions on their screen at the wrong moment is unhelpful and more importantly, unsafe. We designed the gate instructions to surface as a small, but obvious banner in the navigation screen at precisely the moment the driver approaches the gates."

Two principles compound:

  1. Information delivered too early is ignored — the driver sees it at trip start, forgets it by the time they need it.
  2. Information delivered in bulk at the wrong moment is dangerous — a wall of text in a moving car is a safety hazard, not a feature.

The fix is to engineer a timing anchor — something the system can subscribe to that fires at the right moment. Lyft's anchor is a virtual routing waypoint at the gate itself. When the driver approaches the waypoint, the banner appears.

Why this changes the architecture

Normal notification systems are keyed to state transitions (matched, arrived, picked up). Those are too coarse for context-of-approach information. The engineering move is: build or repurpose a system primitive (here, the routing graph) specifically so it produces the timing signal the UX needs. The routing change is small; the UX unlock is meaningful.

For this pattern to work the information itself must be:

  • Brief — a driver has seconds, not minutes.
  • Scannable — glance-sized, not paragraph-sized.
  • Safe to miss — if the driver doesn't see it, fallback (chat, call) is still possible.

Seen in

Last updated · 550 distilled / 1,221 read