06-reference

tim urban 100 blocks a day

Thu May 07 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·status: stub-summary ·source: Wait But Why ·by Tim Urban
time-budgetingblocksfounder-cadenceattention-allocation

“100 Blocks a Day” — @waitbutwhy

Stub note — filed 2026-05-08 as part of WBW evergreen-content shortlist. Light WebFetch summary only; upgrade to deep assessment if cited heavily.

Why this is in the vault

Pairs directly with The Tail End (just filed today) for one-founder time discipline. 100 ten-minute blocks per day is the operational granularity for the Tail-End cost rubric.

Summary (≤200 words from WebFetch)

Each waking day breaks down into roughly 100 ten-minute blocks. Visualizing the day as a 10x10 grid forces an honest comparison: an intended grid (what you say you value) vs. an actual grid (where the blocks actually go). The exercise works because abstract time priorities are easy to deceive yourself about, but block-by-block accounting makes drift between stated values and real behavior visible and quantifiable. Urban prompts the reader to ask which blocks should be left intentionally blank — unallocated, unstructured, unscheduled — rather than fully optimized, recognizing that whitespace is itself a value choice.

Key frameworks named

Mapping against Ray Data Co

The Tail End converts a lifetime into countable units of remaining experiences (Christmases left, dinners with parents left). 100 Blocks is the daily-resolution version of the same technique — turn an abstract resource into a finite count and behavior gets honest. Direct application: Ray’s daily attention-allocation budget. With L4-going-on-L5 ambitions and one founder, every block routed to operational glue is a block not building toward agent capability. Useful as a check against the “I’m busy” feeling — busy with what blocks, exactly. Pairs with the Cook/Chef frame: Chefs spend blocks on first-principles work, Cooks spend them executing other people’s recipes.