Bible Network Crypto DeFi Onchain RWA AI Agent Stablecoin Chain SAFU CryptoTax DeFAI AGI Claude Me Claude Skill Claude Design Claude Cowork
Independent Media
Not affiliated with any project
Exploring the Frontier of AI Intelligence
claude-me.com
LATEST
Claude Haiku 5.5 Launches at $0.10 per Million Input Tokens, but Price Jumps 5x Past 100K: Do the Math Before You Migrate  ·  Claude Code Hooks Add onFailure: "block": A Mistyped Script Path No Longer Lets Your Policy Gate Silently Pass Everything  ·  Claude Code's Agent Tool Gets an effort Parameter: One Subagent Type, No More Separate Copies for Every Thinking Depth  ·  Claude Code Adds --max-findings: Stop Code Review From Dumping a Hundred Suggestions on You at Once  ·  Claude Code Adds Mods: Plugins Can Now Change Deeper Behavior, But Even Anthropic Hasn't Said How to Judge the Quality  ·  Barclays Scales Up Claude: Targeting 50% Developer Adoption of Claude Code by Year End, Sorting 120,000 Emails a Day
beginners

How to Tell Claude "That's Not Right, Try Again" in Conversation: The Art of Giving Effective Feedback

30-Second Version · For the impatient
The most effective format for Claude feedback isn't "wrong, redo" — it's "keep this, change that." Telling it what's right (what not to change) and what's wrong (what to change) is ten times more effective than just saying "not good."

Full Explanation +
01 · Why did this happen?

Core of giving effective feedback in Claude conversations: say "what's right and what's wrong," not just "wrong." Effective feedback has two elements: what to keep (so Claude knows what not to change) + what to change (specific direction for revision). This makes each conversation round a precise step forward rather than guessing from zero every time.

02 · What is the mechanism?

Why "wrong, redo" has poor results: Claude receiving vague negative feedback can only "re-guess what you want" — it doesn't know if tone is wrong, direction is wrong, or format is wrong, so it may repeat the same mistake. Each piece of unclear feedback is wasted time in an inefficient loop between you and Claude.

03 · How does it affect me?

Why examples outperform descriptions: human language is limited in its ability to describe style — "conversational" means A to you but Claude interprets it as B. A concrete text example eliminates this ambiguity: Claude sees the example and directly learns the target linguistic characteristics, sentence length, and vocabulary habits. This is especially effective for tasks with specific brand voice or personal writing style requirements.

04 · What should I do?

Practice exercise you can do now: find a previous Claude conversation where you felt output quality was insufficient, try giving explicit feedback using the "keep X, change Y" format, and see if the next output improves significantly. This exercise builds your intuition for "giving effective feedback" — the single most important Skill for getting consistently high-quality results from Claude.

Full Content +

Claude's first answer isn't quite what you wanted — totally normal. The problem is most people either give up, start a new conversation from scratch, or just say "not good, redo" without telling Claude what's wrong.

The right approach: learn to give effective feedback within the same conversation so each round brings output closer to what you need.

Most Important Principle: Say What's Wrong, Not Just "Wrong"

Least effective: "This isn't what I wanted, rewrite it" Most effective: "The direction is right but the tone is too formal — I need a more conversational version"

Good feedback contains two elements: what to keep ("the direction is right", "this example is good") and what to change ("make the tone conversational", "cut the length in half", "add a concrete number to support the argument").

Five Common "Wrong" Situations and What to Say

Wrong tone/style: Describe your target style with an adjective combination — "like talking to a friend, not writing a report; some personal opinion; shorter sentences."

Too long/short: Specify target length and explicitly say what to keep and what to cut.

Direction completely wrong: Explain what you actually wanted vs what Claude understood, with a concrete example.

Part right, part wrong: Explicitly name which parts to keep and which to revise.

Wrong format: Show the format you want, ideally with an actual example.

The Fastest Technique: "Here's an Example"

If you want a specific style, paste an example and say "write in this style." More accurate than any description — it directly shows "this is the feeling I want."

Ask a Question
Please enter at least 10 characters
Related Articles
Claude Cowork Honest Review: Three Months Later — What Actually Saved Time, What Made Me Regret Automating It
reviews · Jul 02
Using Claude for Competitive Analysis: A Complete Workflow from Information Gathering to Actionable Insights
practice · Jun 29
How to Set Up Claude Code's Screen Reader Mode: A Complete Guide for Blind and Low-Vision Developers
beginners · Sep 26
Claude Memory for Beginners: How Cross-Conversation Memory Works, and What About Sensitive Info?
beginners · Aug 29