The most effective feedback prompts assign Claude a specific role, explicitly request criticism over praise, and ask for output in a structured format. Vague prompts like “what do you think?” produce vague answers. Specific role-based prompts with clear output requirements produce the kind of direct, structured feedback that actually improves your course.
Why the Prompt Is Everything for Feedback Requests
Claude is a skilled communicator that naturally defaults to balanced, diplomatic language. That is useful in many situations but works against you when you need honest criticism of something you built. The prompt is the lever that changes Claude’s behavior from polite commentator to useful critic. Getting the prompt right is not a technical skill — it is a communication skill. You are briefing a contractor on exactly what job you need done.
Think of it like hiring a building inspector. You do not ask an inspector “what do you think of the house?” You ask them to check the foundation, the wiring, the plumbing, and the roof for anything that fails code. Specificity produces inspection. Vagueness produces opinion. The same principle applies to asking Claude to review your course.
The Proven Feedback Prompt Structure
Here is a prompt structure that consistently produces useful course feedback from Claude: “You are an experienced instructional designer who works with online educators and coaches. I am going to share my course outline. Your job is to give me honest, direct feedback — not a balanced review. Focus on what is wrong or could be stronger. Specifically look for: (1) concepts used before they are taught, (2) modules in the wrong sequence, (3) learning outcomes the content probably cannot deliver, (4) lessons that are too thin or too dense, (5) the point where students are most likely to lose momentum or drop off. Give me your findings as a numbered list, most serious problem first.”
After pasting that prompt, add your course outline. The role assignment (“experienced instructional designer”), the explicit bias toward criticism, and the specific numbered criteria together override Claude’s diplomatic defaults and produce structured, prioritised feedback you can act on immediately.
What This Means for Educators
Learning to prompt for useful feedback is a skill that pays dividends across everything you build — not just courses. The same structure works for reviewing your sales page copy, your welcome email sequence, your community onboarding flow, and your coaching framework. Any time you need genuine critical analysis rather than encouragement, the pattern is the same: assign a role, request criticism explicitly, define what to look for, and specify a structured output format.
Once you have a prompt that works, save it. Build a small library of feedback prompts for different assets. The next time you need a course review, a sales page critique, or a check on your community guidelines, you pull the right prompt rather than starting from scratch each time.
What to Do Next
Copy the prompt structure above, paste your current course outline after it, and run it through Claude today. Work through the numbered findings one by one. For each item, decide whether to fix it before launch, note it for the next version, or consciously dismiss it with a reason. The exercise takes under an hour and gives you a pre-launch quality check that most solo educators never have access to.