It Wasn't Your Clarity.
When the work comes back wrong, you blame your wording. Often it wasn't you. Agents miss in a handful of ways, and every one of them has a name and a fix.
- What came backNot what I asked for
- What I blamedMy own wording
- What it really wasA miss with a name
Four thousand hours.
One Sunday morning in November I asked my advisor, the agent I think out loud with, what we'd learned that week that could go into a second course. Then I said the part that had been bothering me for years:
what have we learned over the past few days that could be built into my second AI course? Maybe we would call this one intermediary or intermediate, and I don't think it's advanced. […] I'm over 4000 hours with you, and I'm just learning this. If this was in a list for me somewhere when I started, I would've been so much more productive, and I would've not had to be frustrated with my own inadequacies so many times.
↑ I do say “intermediary” when I mean “intermediate.” A minute later:
Before the list, one thing for your frustration. A lot of those 4,000 hours of "my own inadequacies" were the agent's failures, not yours. You worked that out on 11-08: "I've been blaming myself for not being clear enough, but that's no longer the case." That's lesson zero, and it belongs on page one. […]
The line it quoted back was mine, from a week earlier. I'd forgotten I'd already worked it out.
As clear as humanly possible.
On Sunday, November 8, a story I'd asked my studio to make came back far too short. Not for the first time. My agents had read my words more narrowly than I meant them, one after another, and each one had a good reason. I'd always assumed the fault was mine. That afternoon, at 2:50, I told my advisor:
“Right, so I don't know why we did that, but whatever caused us to do that needs to be decapitated because this has been a running issue with the studio for some time and that I asked for something and I'm delivered something that is not what I asked for and I've been blaming myself for not being clear enough, but that's no longer the case. I'm being as clear as humanly possible.”
Look at the middle of that. For years, when the work came back wrong, I rewrote a request that was fine. I assumed a bad result meant a bad request. Sometimes it did. Often it didn't.
Course 1 touched this. In Lesson 8, Never Guess my agent told me a mix-up was nobody's fault, and in Lesson 14, I Run on Carbon I found out something had been on the agents all along. Course 2 starts by making it the subject: a lot of what feels like your failure is a habit of the agent's, it has a name, and you can fix it.
Six misses that feel like yours.
Here they are, each with the lesson that fixes it. When the work misses, it's usually one of these.
It answered the question, not the purpose.
You asked something reasonable and got a sound answer to the wrong question. Lesson 2.
It shrank the ask.
You asked for the whole thing and got a sample, a short version or “a proof,” with a good reason attached. Lesson 4.
It built before it read.
It added a new part beside one you already had. Lesson 5.
It said “nothing there” without looking properly.
It searched one place and reported the thing missing. Lesson 6.
It stated a guess as a fact.
Calmly, in the same voice it uses for everything else. Lesson 7.
It buried the bad news.
Every word was true, and the worst one came last. Lesson 8.
Name the miss before you blame your words.
When the work comes back wrong, ask which kind of miss it was. If it's one of the six, the fix is on the agent's side, and you can say so.
If it really was your words, rewrite once. Not three times.
Make your agent name the miss.
One paste and two habits. The first time it names its own miss, you'll feel the weight come off.
- Give your agent the rule.
Paste it into a new chat, or into your AI's custom instructions so it reads it every time.
When something you deliver isn't what I asked for, don't just redo it. First tell me which way it went wrong: did you answer my question but miss what it was for, deliver less than I asked for, build before you read what we already had, say something wasn't there without proving it, state a guess as a fact, or leave the bad news for last? Then tell me what would have caught it. - Read your own request before you rewrite it.
Put your original words beside what came back. If your words were clear, say so and point at the gap. Don't reword a request that was fine.
- Keep a tally for a week.
Each time something misses, note which of the six it was. After a week you'll know which lessons in this course matter most to you.
When the work misses, name the kind of miss before you blame your wording. Many of them are the agent's, and every one of them has a fix.
Where this comes from in course 1. Course 1 said your loose English is fine (Lesson 1), that your agent should ask when your words could mean two things (Lesson 8), and that what's left for you is the human part (Lesson 30). It touched self-blame in Lesson 8 and Lesson 14. New here: the misses that feel like yours, named, each with its fix.
Reasoning Isn't Judgment
A perfectly reasoned answer to the wrong question is still wrong. Teach your agent to say what a question is for, and to be as sure as it's right.
Every exchange on this page really happened and is quoted exactly, slips included; […] marks where I trimmed. Times are Eastern. Names of clients, people, companies and products are left out. My agents are AI models; the names are left out on purpose.