Jakob Nielsen called it:
“By the end of 2026, AI will likely perform tasks that take a human 39 hours which is more than a full work week when you account for meetings and other non-task activities.”
We find out by Dec 31, 2026. 126 days to go
Jakob Nielsen: “By the end of 2026, AI will likely perform tasks that take a human 39 hours which is more than a full work week when you account for meetings and other non-task activities.”
MET if A published time-horizon evaluation (METR or equivalent methodology) reports a frontier AI model autonomously completing tasks that require at least 39 hours of human expert time. Human-assisted or multi-step human-in-the-loop workflows do not count at any point, before 2026-12-31 23:59 (UTC).
Settles by documented review of public evidence against these locked criteria; the reviewer is named and the reasoning published.
Test details
Settled true if, on or before 2026-12-31, METR (or an equivalent published time-horizon evaluation) reports a frontier AI model able to autonomously complete tasks requiring at least 39 hours of human expert time. Otherwise false.
Quote verified against the source
Added by Thonest from a public source. The person quoted did not submit, approve, or endorse this record; the wording is verified against the source itself.
Read the original on Substack ↗
Reactions are about the record being worth keeping — never about whether the person was right. They are never counted for or against anyone, and never used to rank anything.
Discussion
Loading…
Prediction 1 ('Accelerating Relentless Change') in Nielsen's annual list of 18 predictions for 2026, extrapolating METR's AI task-duration horizon data.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x2307a94820c51b9030656ee3d143b3732677e38f5412a9efd100d7712d520fcc
- 0x78fa2a05830c0a6ecf76f287272ce7cb2b15de4fbae46889fcc0f8b7ec2603a3
batch #91 manifest · 4 entries
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
0xd3786fd9…dfb8b9 on block explorer
view the canonical capture · the page as served to us, kept verbatim and covered by the evidence hash
✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.
The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.
Disputes
No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.
Related