The Frosting Problem

Why spreading AI over the top of human ceremony holds you back — and what it looks like to collapse the ceremony instead. A field note by Mark Statkus.

Every tool you use at work is full of ceremony. Forms. Tickets. Approval chains. Status meetings. Dashboards you check. Buttons you click in a particular order. None of it is the work itself — it's the procedure around the work. And here's the part almost nobody says out loud: all of that ceremony was invented to work around human limitations.

We hold meetings because humans can't share what's in their heads any other way. We write tickets because humans forget. We build dashboards because a human can't watch forty systems at once. We design point-and-click interfaces because humans have eyes and a mouse, not the ability to read raw data. Every layer of process is a prosthetic — a crutch for something people genuinely couldn't do.

That was fine. It was the price of coordinating humans. But something changed: we now have software that can hold the whole context, can watch everything at once, can read the raw data directly, and doesn't forget. And what is the industry doing with it?

Frosting. They're spreading a thin layer of AI over the top of the exact same stack of ceremony. AI that writes your ticket for you. AI that summarizes the meeting you still held. AI that clicks through the point-and-click interface on your behalf. The ceremony survives untouched — it just gets performed faster.

Ceremony is a prosthetic

Here's the mental model, no jargon required. Imagine you taped a photo of the inside of your fridge to the fridge door, so you wouldn't have to open it to know what's inside. That's clever — if opening the fridge is expensive. But the photo goes stale the moment anyone takes something out. Now you need a procedure for updating the photo. And a rule about who's allowed to update it. And a meeting when the photo disagrees with the fridge.

An enormous amount of professional software is fridge photos. State files that describe your cloud infrastructure because the tooling can't just look at your cloud infrastructure. Status reports that describe what your team is doing because you can't just see what they're doing. Saved click-sequences in a GUI because the software can't just read the instructions and go.

Every one of those made sense when a human — or dumb, non-perceiving software — was the one doing the work. The photo was a prosthetic for an actor who couldn't open the fridge. An AI agent can open the fridge. It can perceive live state, hold the full context, and act directly. Hand the same job to that kind of actor, and the prosthetic doesn't become quaint — it becomes drag. You're maintaining a photo of a thing the worker can simply look at.

So the honest question to ask of any process, any tool, any "workflow" is not "can AI do this step for me?" It's: "did this step ever exist for any reason other than a human limitation — and does my new worker still have that limitation?" If the answer is no and no, the step is dead ceremony. Collapse it.

What collapsing actually looks like

This isn't a thought experiment. Below is the stack I build and run — each tool exists because I asked that question about a piece of ceremony everyone treats as permanent, and the answer came back dead. It goes deeper than the dev stack — a personal agent quietly tends the mail, the calendar, the home network, even the house battery, and says something in Slack only when it matters — but the receipts below are the public half. The map reads left to right: the project, the ceremony it deletes, and the live mechanism that remains.

* The honest asterisk: you collapse ceremony you own. Ceremony that's load-bearing for someone else — a client, a team, a compliance regime — you bridge instead, and you stay honest that it's a bridge. Roadie exists so agents can operate inside the incumbent world without pretending the incumbent world is the destination.

What survives the collapse

This is not an argument for deleting all process — and here the distinction gets sharp. Two things survive the collapse, and noticing which two is the whole discipline.

First: the paper survives — but it changes jobs. Not every document is a fridge photo. A photo caches reality: the status report, the state file, the wiki page describing what production looks like. Those die, because an agent can look at reality directly. But a document that declares intent — a spec, a plan, a design — can't be perceived from the world, because it doesn't exist in the world yet. Someone has to author it. I still design in Markdown. Every project above started life as a spec in plain text, because plain text is the one format both a human mind and an agent fleet can read, argue with, and execute against. The difference from the old world is the direction of sync: nobody maintains the document to match reality. Reality gets brought into line with the document. The Markdown stops being paperwork and becomes the steering wheel.

Second: the gates survive — re-aimed at the new worker's weakness. An agent's characteristic failure isn't forgetting, it's confident wrongness at speed. So the checkpoints that matter move upstream of the speed. In practice the loop looks like this: review the spec before it becomes a plan. Review the plan before it becomes work. Then an adversarial review — a second mind whose only job is to attack the plan and find where it's confidently wrong. Only after the plan survives that does it fan out to subagents for parallel execution, with one last gate in front of anything irreversible. The meetings die; the review checkpoints concentrate.

The frosting test

  1. Did a layer disappear? Is there a form you no longer fill out, a meeting that no longer happens, a dashboard you no longer watch? If every old step survived and got a sparkle icon, it's frosting.
  2. Does it perceive, or does it read the photo? Is the AI looking at the live thing — your real data, your real systems — or at a stale copy someone still has to maintain?
  3. Where did the human attention go? Collapse frees you to do judgment work. Frosting reassigns you to supervising the ritual: reviewing AI-written tickets, correcting AI-filled forms, attending the meeting about the AI summary of the meeting.
  4. Are the gates on the right things? The process that should survive is narrow and precise: review of the intent before machine-speed execution, and a gate on anything irreversible. If the approvals guard trivia while the plan goes unreviewed and the dangerous button has no gate, the ceremony was never about safety.

The frustrating truth is that frosting will always be easier to sell. It doesn't threaten anyone's org chart, anyone's tool budget, anyone's ritual. Collapse asks a harder question: which parts of how we work were only ever workarounds for being human? The organizations — and individuals — willing to answer honestly will simply move at a different speed than the ones licking frosting off the same old cake.

And what replaces the ceremony isn't another artifact. It's the conversation. Status is whatever you ask, answered from the live thing. The summary takes your shape — your question, your depth, this moment — instead of a wall of text already drifting from the reality it describes.

The work was always under there. The ceremony was scaffolding. Take it down.