Why Claude’s Answers Feel Off — It’s Almost Always One of These 5 Mistakes

EDIBLOG · CLAUDE 101 · PART 2 / 5

Why Claude’s Answers Feel Off — It’s Almost Always One of These 5 Mistakes

Hi, I’m Eddie. After using Claude daily for over a year, the question I get asked most is “why does the answer feel off?” I’ve found the answer is almost always one of 5 mistakes. Avoid these and your output quality jumps immediately.

TOP 5 MISTAKES ONE-LINE FIX BEGINNER 5-MIN READ

01 · WHYBad answers are almost always a user-side problem

Bottom line. If Claude’s answer is too long, off-topic, or awkward, it’s usually not the model. It traces back to one of 5 mistakes in how the question was phrased.

I see this every day — tweak the same question slightly and the output changes completely. The model can’t read your mind. You just have to tell it.

02 · TOP 5These five are the usual suspects

Bottom line. You don’t need to memorize all five. Just remember “context · format · iterate · role · refine.” Five words.

MISTAKE 1

Asking too briefly — missing context

BAD

Write me a marketing strategy.

GOOD

Write a 1-month Instagram marketing strategy for eco-friendly cosmetics targeting women in their 20s. Budget: $800.

TIP

Just nail who · what · under which constraints and the answer gets dramatically better.

MISTAKE 2

Not specifying the format you want

BAD

Tell me the pros and cons.

GOOD

Give me pros and cons as a table. 3 of each.

TIP

Specify table · numbered list · 3-line summary and it follows exactly.

MISTAKE 3

Cutting the conversation short — starting a new chat

BAD

First answer felt off → start a new chat → re-explain everything from scratch

GOOD

Stay in the same chat: more specific · more casual tone · add an example and keep going

TIP

The same chat remembers context. New chat = back to square one.

MISTAKE 4

Skipping the role assignment

BAD

Explain this code.

GOOD

As a senior backend engineer, point out the performance issues in this code. or Explain it so a 5th grader could understand.

TIP

Role shifts both tone and depth. Just pick one — expert · beginner · friend.

MISTAKE 5

Using the first answer as-is

BAD

Treat the first answer as final and copy-paste straight out

GOOD

Refine once or twice: make it shorter · simplify the jargon · friendlier tone

TIP

The first answer is a starting point, not the final draft. One or two passes of refinement is the real output.

03 · FIX FLOWYou don’t have to fix all five at once — add one line at a time

Bottom line. Trying to nail all five in one shot feels overwhelming. Adding one line at a time flows much more naturally.

A real refinement flow · starting from “Write me an email”

PASS 1 (no context)

Write me an email.

PASS 2 (add context)

Write an email to a coworker letting them know the meeting time has changed.

PASS 3 (add format)

Keep it to 3 lines, polite tone.

PASS 4 (refine)

Make it a little friendlier. Add a one-line apology at the end.

I don’t think you need to jump from pass 1 to pass 4 immediately. Adding one line at a time is actually faster overall.

CODAIf I had to nail it in one line

Claude’s answer quality isn’t decided by the model — it’s decided by the person asking. Context · format · iterate · role · refine — just remember those five words.

— Eddie · Claude 101 Series, Part 2

Eddie’s noteAfter a year of using Claude, I’ve never actually memorized all five. When an answer feels off, I just run through them in my head — “which of the five was it this time?” That’s how you build the muscle. Next post: 7 copy-paste prompts for everyday work and life.

SERIES · CLAUDE 101 · 5 PARTS

  • Part 1 · Sign up to first chat in 5 minutes
  • Part 2 · Why answers feel off — it’s almost always one of these 5 (you are here)
  • Part 3 · Practical prompts ① everyday & work
  • Part 4 · Practical prompts ② dev & coding
  • Part 5 · How far does the free plan get you? Full plan breakdown

SOURCES · REFERENCES

Primary Data

  • Ediblog · 1 year of daily Claude use, personal log (author)

Disclaimer: Accurate as of 2026-05. Models and features may change. No ads, no affiliates.


This post is part of an English mirror of a Korean dev experiments blog. Cross-posted for the global developer audience.




Leave a Comment