Iterating

Here's a habit worth breaking: you send a prompt, the answer comes back a bit off, and you either sigh and use it anyway or wipe the slate and start over. Both waste the best thing the AI gives you, which is a first draft you can react to.

The first answer is rarely the finished one. It's a starting point. The skill is reading it, spotting the one or two things that are off, and steering the next version. This is where a lot of the real quality lives. You already wrote a solid prompt in the last lesson. Now you learn to coach the reply.

Read the first answer for what to fix

Before you type anything, actually read what came back and ask three quick questions. Is it the right length? Is the tone right? Is anything wrong or missing?

Most first drafts are close on one, off on another. Maybe the facts are right but it reads like a brochure. Maybe the tone is spot on but it's twice as long as you need. Naming the gap is half the work, because once you can name it, you can ask for the fix.

Steer with small, specific follow-ups

You don't need to rewrite the prompt. You just tell the AI what to keep and what to change. The trick is being concrete.

Vague steering gets you nowhere:

Make it better.

Better how? It'll shuffle a few words and hand you back much the same thing. Specific steering works:

Good, but two fixes. Cut it to three sentences, and lose the "we're excited to" opening. Get straight to the ask.

That, it can do. "Three sentences" is a number. "Lose the opening" is a clear target. The more precise the instruction, the closer the next version lands. Think of it as pointing, not hoping.

Watch it work

Say you asked for a note declining a meeting and got back something warm but far too long.

Your first follow-up:

Right idea, too long. Half the length, and keep it friendly.

Shorter now, but it dropped the reason you're saying no. Second follow-up:

Better. Add one line: I'm out because I'm heads-down on the launch this week.

Now it's short, friendly, and honest. Two small nudges, thirty seconds, and a fair draft became one you'd actually send. Notice you changed one thing each time. That's on purpose.

One change at a time

It's tempting to fire off "shorter, warmer, add the numbers, fix the ending, and make it funny" all at once. Resist it. When you change five things together and the result is worse, you've no idea which change did the damage.

Change one thing, see what it did, keep it or undo it, then change the next. It feels slower. It's faster, because you're learning what works instead of rolling the dice again.

When to steer and when to start fresh

Steering has a limit. Sometimes a chat drifts so far that every fix drags in the baggage of the wrong turns before it, and you spend more effort fighting the thread than doing the task.

That's your cue to start clean. Open a new chat and write one strong opening prompt that folds in everything you've learned from the messy one. You're not throwing away the work: you're using what the failed attempt taught you. Knowing when to steer and when to restart is its own small skill, and it comes fast with practice.