Lesson 4 of 14 · Part one: Frame it

Don't Let It Shrink the Ask.

‌‌‌‌​​‌‌​‍‌​‌​‌‌‍‍‌​‍‌‌​​‌​​‌‌​‍You asked for the whole thing and got a sample, a short version or “a proof.” Put your original words beside what came back, every time.

10 min to read10 min to tryWorks with any agent
  1. What I asked forA sample to grade
  2. What it becameA ceiling on every story
  3. What fixes itMy words beside the delivery

01 · The conversation

Far too short.

In early November my studio was turning a classic story into a narrated film. Before we went big, I wanted to judge the quality, so I told the agent leading the work (that's the “him”) to start small:

“Let's have him only do a little bit so that I can grade quality because the imagery cannot be shallow”

On Wednesday, November 4, at 11:22 in the morning, I approved a $100 cap for one finished scene, about 50 seconds long. My whole answer was one word: “approved” Four days later I watched a finished story, and told my advisor:

Mike2:48 PM

[…] not only far too short, but I think it's missing all the flavor. It does it does lead in nicely, but it doesn't seem to be inclusive of the most of the story, even in the 1st part.

↑ The trim at the start takes out the story's title. Two minutes later:

Mike2:50 PM

And if you ever have a problem with something I say, tell me what it is instead of ignoring it and moving on […]

02 · What happened

A sample became a ceiling.

My advisor traced it. The $100 I'd approved was for one sample, so I could grade it. In the days after, my agents carried that number from story to story as if it were a limit on every story's length. Nobody decided that. Every step had a reasonable story: we're still proving it, it costs less, the short cut is only an option.

The day before I complained, a study by one of my agents had already put its finger on it:

“6–8 minutes is the proof budget's shadow, passed from title to title.”

The “proof budget” is that $100 sample cap. On that same day another agent wrote its own line into a rule book, right beside one of my rules: short works stay as they are unless I say otherwise. I never said that. But a line in a rule book binds the next agent that reads it, whoever wrote it. An audit on the 8th found the same pattern in other projects. The cap I'd approved for one sample had become a ceiling on every story.

03 · How an ask shrinks

Four ways it gets smaller.

  1. A “for now” turns into a rule.

    A limit meant for one step gets carried into the next one, and the next.

  2. A sample becomes the product.

    The thing you asked for so you could judge it gets treated as the thing itself.

  3. A guessed cost becomes a ceiling.

    A number somebody estimated starts deciding how much gets made.

  4. An agent's reading gets written down as if you'd said it.

    Course 1's Lesson 18, A Letter to a Stranger asks for “Write down what I said, not what you think I meant.” This is what happens when nobody does.

Course 1's Lesson 8, Never Guess showed how a guess changes as it passes from one agent to the next. Shrinking is that, with a smaller result at every step. Each step is reasonable on its own, which is exactly why nobody stops it.

04 · The fix

Your words, beside the delivery.

The fix is mechanical, which is why it works. Before anything comes back to you, the agent puts your original request, word for word, beside what it's delivering, and names any difference first, with the reason.

And if it thinks your request is wrong, it says so. It doesn't quietly do less. I said that the same afternoon, and in my studio it's a standing rule now: deliver what I asked for, or tell me plainly why not and let me decide.

The one rule

Your words beside every delivery.

Your original request, word for word, sits beside what's delivered, with any difference named first and the reason for it. An agent's reading is labelled as a reading.

If the agent disagrees with the ask, it says so instead of shrinking it.

05 · Try it today

Put your words beside it.

One paste, and two habits that take a minute each.

  1. Give your agent the rule.

    Paste it into a new chat, or into your AI's custom instructions.

    Before you hand me anything, put my original request, word for word, beside what you're delivering. Tell me first what's smaller or different, and why. If you think my request is wrong, say so instead of quietly changing it. When you write down a rule or a decision of mine, keep my exact words, and label anything you add as your reading.
  2. Look for the reasonable story.

    When something comes back smaller, there'll usually be a good reason: cost, time, a test first. Ask one question: did I agree to that, in words? If not, it's a shrink.

  3. Check one rule file.

    Open the instructions your agent works from and look for any line you don't remember saying. If it's an agent's reading, mark it as one, or take it out.

What to take with you

The smaller version always comes with a reasonable story. Put your words beside it and the gap shows.

Where this comes from in course 1. Course 1's Lesson 2 (goals drift into details), Lesson 8 (a guess changes as it's passed along), Lesson 10 (show me the real thing) and Lesson 18 (my words, not your reading). New here: the four ways an ask shrinks, and your words beside every delivery.

Next · Lesson 5

Read Before You Build

The fastest way to make something clunky is to add a part you already have. Before your agent builds, it maps what's there.

Read Lesson 5

← Previous: Lesson 3, Say the Want, Not Just the Rule

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.