Private preview. Not published and not indexed.

Research opportunity · Organizational absorption: Why micro gains do not become macro outcomes

Where does the time saved with generative AI go?

Question

When workers save time with generative AI, how much of it goes to more of the same output, to new tasks, to checking AI output, to on-the-job leisure or to shorter hours, measured with time-use diaries or telemetry linked to the same workers' measured output?

Not yet measuredA PhD projectLow to medium costPartly addressed

Why it matters

Self-reported time savings come to 1.4% of US work hours, executives mostly report no productivity impact yet, and technical workers report speed gains larger than the value gains they report. A METR note shows why time saved on a shifted mix of tasks can overstate value. Whether saved time becomes output is the hinge between task gains and firm outcomes, and it is currently inferred from self-reports rather than measured.

The debate lists this among what we still do not know: Where does saved time go: more output, new tasks, checking, or leisure? No study follows saved time directly; Danish register data and one Korean survey come closest.

Evidence that motivates it

A possible design

Panel of workers in several organizations with staggered AI access (randomized timing where the employer agrees, otherwise the rollout schedule as a natural experiment). Before and after access, run two-week experience-sampling waves (several short prompts a day: what are you doing, is it AI-related, are you checking AI output, are you on a break) alongside consented application telemetry and recorded hours. Link to individual or team output records already kept by the employer. Decompose the change in time into more of the same output, new tasks, checking and oversight, on-the-job leisure and shorter hours.

Data needed

One or more employer partners with a staged rollout; an experience-sampling app; consented telemetry; output measures at the individual or team level; ethics approval for workplace monitoring.

Feasibility

A PhD project. Low to medium; experience-sampling software and participant incentives are modest, and the hard part is employer access and consent to link output data. Recording on-the-job leisure is sensitive. Opt-in consent, aggregate reporting and a written guarantee that the data are not used for performance management are needed, or participation and candour will drop.

Has this been done?

Partly done already: related work covers some of this question (first-pass screen of 15 October 2026; not yet checked in depth).

No study was found that follows the same workers' saved time with a time-use diary, experience sampling or telemetry and links it to measured output, so the proposed decomposition is untested. The nearest quantitative evidence is a cross-sectional, self-reported Korean survey that finds time savings almost uncorrelated with output changes and attributes the gap to on-the-job leisure. Danish register data show new tasks and no change in recorded hours or earnings but do not measure within-day time. Vendor-run telemetry measures time on specific tasks without tracing the freed time. An ethnographic study points the other way, to work that intensifies.

How strong this evidence is

Nearest work found

Search queries used
  • generative AI time savings time-use diary experience sampling what workers do with saved time
  • generative AI telemetry time saved reallocation tasks output linked administrative data workers study 2026
  • experience sampling study generative AI use workday time allocation oversight checking output knowledge workers
  • Ranganathan "AI doesn't reduce work" intensifies ethnography tech company generative AI workload
  • where does time saved by AI go measured output quantity call center or writers more tasks vs leisure field evidence hours worked Copilot

Provenance

RO-LD03-02 v1. Drafted by Claude (SocioLens Project Lead), AI-drafted from the LD-03 debate on 2026-10-15. Checked by an independent AI reviewer with fresh context (not a person), 15 October 2026 (review of PR #77): verdicts, query counts and 13 abstract-read labels checked; label slips corrected. Not yet reviewed by a domain expert. This is a research hypothesis, not a finding.

All research opportunities