The AI slop nobody logs: the 20-page doc that makes its problem your problem. There's a hidden tax on teams right now: polished AI output that shifts the thinking onto whoever opens it. The real skill was never volume. It's what you cut.
My assistant created the same task three days running. The fix has a name: idempotency. A tiny automation bug taught the same lesson payment systems learned years ago: the question isn't whether it runs, it's what happens when it runs again.
A context window is working memory, not a hard drive. Feel that, and you manage AI differently. The AI doesn't remember everything you've told it. It has working memory, and it's finite — here's the cheap trick I use to hear it filling up, and the fix when it does.
The real test of a system is whether the work moves when you've left the desk. A week away, not too many meetings, and the clients' work kept moving — because the mechanical parts run on their own. On building systems that outlast your presence, and the judgement that can't be automated.