As you start working with Claude, you'll likely encounter moments where the response isn't quite what you expected. This is normal—and it's an opportunity to refine your approach. Here are some of the most common challenges and how to address them.
By the end of this lesson, you'll be able to:
| Challenge | What's happening | Try this | |-----------|------------------|----------| | Claude's response is too generic | Your prompt didn't include enough context about your specific situation | Add details about your audience, role, or constraints. Instead of "Write an email about the project delay," try "Write an email to our enterprise client explaining that the software integration will be delayed by two weeks. They've been patient so far but this is the second delay. Keep it professional but apologetic." | | The response is too long (or too short) | Claude is guessing at appropriate length | Be explicit: "Give me a two-paragraph summary" or "Keep this under 100 words" or "I need a comprehensive analysis—length isn't a concern." | | Claude didn't follow my format | Claude understood what you want but not how you want it presented | Show, don't just tell. Provide an example of the format, or describe the structure explicitly: "Use bullet points with bold headers for each section." | | I got confident-sounding information that turned out to be wrong | Claude occasionally generates plausible but incorrect information, especially with specific facts or niche topics | For high-stakes work, verify key facts independently. Ask Claude to cite sources or indicate confidence level. Enable web search to ground responses in current information. | | The tone isn't right | Claude defaults to helpful and professional, which may not match your needs | Describe the tone in plain language: "Make this more conversational" or "This should sound authoritative and formal." Provide an example of writing in the style you want. |
One of the most important shifts when working with Claude is recognizing that your first prompt rarely produces a perfect result—and that's okay. Think of your initial prompt as the start of a conversation, not a one-shot request.
Effective Claude users:
Sign in to join the discussion
AI Fluency is the ability to collaborate effectively with AI tools—not just knowing which buttons to click, but developing the judgment to use AI well across different situations.
The 4D Framework for AI Fluency, developed through research collaboration between Professor Rick Dakan (Ringling College of Art and Design) and Professor Joseph Feller (University College Cork), identifies four core competencies that, when combined, can help you make the most of your AI interactions:
You've already been practicing these skills throughout this course. The prompt framework from Lesson 2 (setting the stage, defining the task, specifying rules) is rooted in Description. The troubleshooting techniques above draw on Discernment and Diligence.
As you start integrating Claude into more of your work, you might wonder: how do I know if Claude is actually good at this particular task?
This is where Discernment becomes essential. Evals (short for evaluations) are a way to develop intuition for assessing Claude's outputs on the tasks that matter to you. They're systematic ways to test how well Claude performs on specific types of tasks that matter to you.
Your work is unique. Claude might excel at drafting marketing copy but need more guidance for technical documentation in your specific domain. Running simple evals helps you:
You don't need complex infrastructure to evaluate Claude. Here's a practical approach:
Here's a practical example of how to evaluate Claude for data analysis:
The scenario: You're a program director who analyzes program attendance alongside employment outcomes every quarter.
Step 1: Identify a specific task. You want to delegate the data analysis part of your quarterly reporting.
Step 2: Find past data. Use last quarter's data where you already completed the analysis manually.
Step 3: Create test prompts. Start with: "I'm sharing attendance data and employment outcome data from our job training program last quarter. Please analyze the participation patterns across the three months and graph the correlations between attendance levels and employment success."
Step 4: Compare results. Check Claude's analysis against your known results. Did it identify the same patterns? What did it miss?
Step 5: Refine and test again. If Claude missed something, add more specific instructions: "Pay special attention to the program type when performing its analysis."
Step 6: Validate. If Claude can match your known results with the right description, you've built a validated approach you can use with new data.
This testing works for any analytical task: donor analysis, budget forecasting, survey synthesis, outcome tracking. Test first, validate what works, then apply with more confidence, or learn what you shouldn't delegate at all.
Before moving on, consider:
In the next lesson, you'll explore the Claude desktop app and the three ways you'll work with Claude there — turn by turn (Chat), handing work off (Cowork), and building software (Claude Code).