"The work wasn't hard." That is how Daniel Miessler opens a provocation aimed at anyone whose job mostly happens inside documents, dashboards and deliverables. His fuller version:

The work wasn't hard. What was hard was maintaining all this scaffolding. The workflows. The knowledge bases. And the output formats that make everything look professional.

His claim is that AI assistants have exposed something uncomfortable about knowledge work: the substance of the job — the analysis, the judgement, the decision — was often the smaller part of it. The larger part was the scaffolding: the workflows that route a task through five approvals, the knowledge bases that must be kept current, the templates and formats that make a two-paragraph finding look like a polished report. That scaffolding exists for real reasons — consistency, accountability, legibility to colleagues — but it is also where the hours go, and it is precisely the kind of work an assistant absorbs well. Formatting, structuring, summarising, reformatting for a different audience: these are exactly what the tools do reliably today.

If your day is consumed by process rather than substance, this is why using an assistant makes work feel lighter in a way that is hard to explain to someone who doesn't. You are not outsourcing your expertise. You are outsourcing the wrapper around it. The interesting follow-on, which Miessler's framing implies, is that the scaffolding may have been carrying more weight than anyone admitted — that a fair amount of what looked like rigour was actually presentation. If an assistant can produce the professional-looking output in seconds, the value of producing it slowly by hand drops toward zero, and what remains is the part only you can do: knowing what the output should say.

This is aimed squarely at knowledge workers — analysts, consultants, managers, ops people — whose roles are real but whose calendars are filled by the machinery around the role. It is not specifically a developer idea, though developers feel it too; scaffolding is arguably the defining feature of office work generally.

Some honesty about status: this is an idea, not a product or a measured finding. Miessler is naming a dynamic, not announcing a tool, and there is nothing here to buy or install. Nothing in it tells you how much of a given job is scaffolding versus substance, and that ratio presumably varies enormously — a regulatory filing and a status update are both "formatted output," but the consequences of getting them wrong are not the same. It also cuts both ways in a way worth sitting with: if the scaffolding was most of your job, an assistant absorbing it is a relief only if your judgement is visibly what remains. For roles where the scaffolding was the job, this observation is less comforting than liberating. And there is a limit the framing glosses over — scaffolding often encodes organisational memory and trust. Removing it may make work lighter and also make it harder for anyone else to check.

As a lens, though, it is a useful one this week. Look at what you actually spent your hours on. If most of it was maintaining the container rather than filling it, you now know which half an assistant is coming for.