Do less
Do less is an essay with four interactive demos, published in October 2026. Its argument is that most AI products wait to be asked, and that most people would rather have software that gets on with the work and brings them only the decision.
The argument
The usual assistant takes the middle of a job and hands both ends back. You notice the need, describe it, answer its questions, check what comes back and then carry it out yourself. The essay sets that against software that starts from an event rather than a prompt, already understands the process, prepares everything it can before you look, and brings you only the decisions that carry consequence or taste.
It gives five reasons the first kind dominates. The people who build these tools value capability for its own sake. A chat box is the cheapest general product to ship, while acting for someone means mapping their process end to end. Organisations set the chat box down beside work that carries on as before. Acting on someone's behalf carries risk that a draft does not. And products are measured on engagement, which a tool that does its job well should reduce.
What the reader does
Each demo runs the same job both ways, and the page keeps count. A ledger in the margin records how many things were asked of the reader and how many were done for them, and each demo has its own tally.
- Selling a cabinet: a chat assistant that asks seven questions and leaves the selling to you, beside an AI agent that asks for three photos and a choice between two buyers.
- A travel day with a flight delayed by three hours and forty minutes, on a timeline the reader can drag through or let play. Nothing is asked of them.
- An inbox in which the reply to an accountant has already been written, the invoice attached and the meeting time held, before the reader opens it. The one action left is to press Send.
- A policy consultation with 400 responses: an empty question box beside a version that read them as they came in, counted a campaign letter once, drafted replies to the points the paper already answers and left one question for the reader.
The essay ends with the reader's own totals, split into questions the software could have answered itself and decisions only the reader could make.
How it is built
The essay is one self-contained HTML file of about 85 KB, with the demos written and scripted inline. The demos are staged: none of them calls a model.
The look comes from the Board of Trade's Hints to business men visiting… booklets of 1969 and 1976: flat paper, one government blue, a bold grotesk, a ruled frame around the title and a date stamp. The demos are set in that system as modern AI software, with task rows that move from pending to running to done, an approval card for the one decision, and text that streams in behind a caret. Apart from the footer, nothing moves unless the reader acts or a piece of work finishes.
The illustrations were made with an image model in the style of the booklets. The footer plate, after Pieter Bruegel the Elder's The Harvesters (1565), shows a scythe mowing the wheat with nobody holding it while a man sleeps. It plays as a seamless 12-second loop, assembled frame by frame in Python and encoded as H.264 video at two sizes, for desktop and phone.
The site runs on a Cloudflare Worker serving static assets. Video requests go through a small byte-range handler so that Safari on the iPhone will play the loop, and a deploy script builds the site from exactly the files the page references.
Read it
The essay is at doless.charlesbee.org.