The Work You Need to Keep

Last week, while editing an essay about the danger of accepting AI output without evaluating it, I accepted AI output without evaluating it.

I had sent a draft out for review and one of the models in my editorial pipeline returned a gap analysis: structured, specific, confident, professionally formatted. I passed it to the next stage without reading it. The next reader caught the problem in under a minute — it was a detailed, well-argued critique of the wrong essay, a piece that had already shipped months earlier. Every surface property said rigorous. The formatting was clean, the section references were precise, the tone was authoritative. The only thing that could have caught it was evaluation, and evaluation was the step I had skipped. While editing the essay arguing that this is the failure that matters.

I’m starting there because the public conversation about AI-generated work is busy looking somewhere else. Much of the conversation about AI-generated writing has become a detection exercise — em dashes, uncanny smoothness, the tells — as if the presence of a model were the thing to catch. But that gap analysis would have passed any detector and every style check. The dangerous artifact isn’t the one that looks like AI. It’s the one that looks finished. What’s worth detecting is the absence of thinking, and the absence of thinking reliably produces exactly the polished, plausible output that sails through.

A lot of workplace AI use is transactional: prompt in, answer out, accept unless obviously wrong. Some is evaluative: the output is where the work begins, not where it ends — it gets interrogated, reframed, partially rejected, made to defend itself. The distinction isn’t about skill or virtue, and it isn’t about how the interaction looks from outside. It’s about whether anything was decided.

Here is the distinction I had been missing, and the one my own incident finally made plain. There are two ways to not evaluate an output. The first is triage: a deliberate call that the stakes don’t warrant the cost — this is a formatting pass, a transcription, a list of options I’ll judge later, and I am choosing to let it through. Triage is itself judgment. Senior people do it constantly and correctly; delegation would be impossible without it. The second is drift: the output goes through and no call was ever made. Not “I decided this was low-stakes” but “deciding didn’t happen.” From the outside, triage and drift are indistinguishable. From the inside, only one of them involved you.

My gap-analysis moment was drift. I hadn’t judged the artifact low-stakes — it was headed into the revision of a piece I cared about. I hadn’t judged anything. The confidence of the output substituted for the call I didn’t make, which is precisely the trade the transactional mode offers: the artifact arrives wearing the appearance of having been evaluated, and accepting the appearance is always cheaper than performing the evaluation. Part of why it’s cheaper is that polish reads as completion — a fluent, finished-looking artifact quietly discharges the very alert that would have prompted the check.

This also answers the question the title raises. What you can offload is generous: transformation, formatting, summarization, option generation, first-pass drafts in many domains. What you keep is narrow and non-negotiable: the framing of the problem, the tradeoffs, the rationale, the ability to explain why this and not that — and above all the triage call itself, the moment of deciding what this output is and what it deserves. That call is small, fast, and constant, and it is the entire difference between using the tool and being processed by it.

The cost of drift is cumulative rather than immediate, which is what makes it easy to live with. Judgment is maintained through repetition — through the unglamorous reps of evaluating, rejecting, explaining. An educator, Dr. Alexa Trifilo, once reframed this for me in terms of how children learn arithmetic: the tool comes after number sense, not instead of it, and the test was never whether a resource was used — it’s whether the choices can be explained. Every output accepted in drift is a rep not taken. One costs nothing. A year of them is enough to notice the edge getting dull, and nothing in any individual transaction will have flagged it.

That’s the deceptive part. Smooth, fast, efficient use feels like productivity, and often is. But speed and ease are also what drift feels like from the inside, and often the transaction won’t tell you whether you’re thinking more or deciding less. One reliable sign that the call is still being made is friction — the moments that sound like that’s not wrong, but it isn’t what I expected, or this is elegant and it’s missing something I can’t name yet. Friction isn’t proof of judgment; sometimes it’s just a bad prompt. But its complete absence over a long stretch of supposedly complex work is worth treating as a signal, because hard problems don’t usually go quietly. Anyone who leads people shapes this directly: teams learn what friction is worth from the stories their leaders tell about their own work, and a steady diet of smooth-output stories teaches that friction is waste — right up until the nuance disappears and the risk surfaces late.

Structurally, the point is simple: the triage call is a control point, and for the person whose name goes on the work, it is the one control point that cannot be absent. It can be handed to another accountable person — that’s delegation, and it’s fine — but it cannot vanish into the tool, because an output that confers its own acceptance is an output nobody judged. The same shape appears in autonomous systems: constraints stated in prose are merely input to a reasoning loop, and real control has to live somewhere the loop can’t negotiate with it. Drift doesn’t remove your judgment in any dramatic way. It relocates one small decision at a time into the tool, each relocation invisible, none of them chosen.

So the standard I’m adopting is Trifilo’s, transferred to my own work. Not whether the tool was used — it was, it will be, that question is over. Whether I can explain what I kept, what I rejected, and why. The week I can’t is the week the essay was about me again. That explanation — the kept things, the rejected things, the reasons — is the work, and it doesn’t go in the prompt.