Iterate prompts to improve output quality

Refine with specific, actionable feedback in the same conversation, and say what must not change.

Key ideas

Be specific

“Cut to about 150 words, use a conversational tone, keep the three key dates” works. “Make it better” doesn't.

Protect what's right

State what to keep exactly (figures, dates, regulatory wording) so a style edit doesn't break the facts.

Stay in the conversation

Iterating in context keeps everything Claude has already learned about the task. Starting over usually reproduces the same problems.

Change one thing when diagnosing

If you don't know why output is off, adjust one element at a time so you can see what helped.

Save the winner

Once a prompt works, keep it as a template or Project instruction so you don't rediscover it every week.

Worked example

An internal announcement draft is accurate but too long and formal.

Why: It names the change, the target, what to preserve and the desired ending.

Common traps

• Resending the identical prompt in a new chat and hoping for a different result.
• Switching model tiers before fixing an unclear prompt.
• Accepting a draft that is accurate but unusable for its audience.