Skip to main content

Getting better results

📖 Lesson content

By the end of this lesson, you will be able to:

  • Recognize common challenges when starting out with AI and use troubleshooting techniques to overcome them
  • Define AI Fluency and know where to go to learn more about working with AI in a fluent way
  • Explain how you might set up evals to better understand how Claude might perform with your unique workflows

Estimated time: 15 minutes


Common challenges and how to fix them

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.

ChallengeWhat's happeningTry this
Claude's response is too genericYour prompt didn't include enough context about your specific situationAdd 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 lengthBe 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 formatClaude understood what you want but not how you want it presentedShow, 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 wrongClaude occasionally generates plausible but incorrect information, especially with specific facts or niche topicsFor 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 rightClaude defaults to helpful and professional, which may not match your needsDescribe 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.

The iteration mindset

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:

  • Treat first drafts as starting points. Review what Claude produces, identify what's working and what isn't, then refine.
  • Give specific feedback. "Make it shorter" is fine, but "Cut the first two paragraphs and make the conclusion more action-oriented" is better.
  • Know when to start fresh. If a conversation has gone off track, sometimes it's faster to open a new chat with a clearer prompt than to try to redirect.

What is AI Fluency?

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:

  • Delegation: Deciding on what work should be done by humans, what work should be done by AI, and how to distribute tasks between them. Includes understanding your goals, AI capabilities, and making strategic choices about collaboration.
  • Description: Effectively communicating with AI systems. Includes clearly defining outputs, guiding AI processes, and specifying desired AI behaviors and interactions.
  • Discernment: Thoughtfully and critically evaluating AI outputs, processes, behaviors and interactions. Includes assessing quality, accuracy, appropriateness, and determining areas for improvement.
  • Diligence: Using AI responsibly and ethically. Includes making thoughtful choices about AI systems and interactions, maintaining transparency, and taking accountability for AI-assisted work.

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.

To learn more, check out our free AI Fluency course that explore all four competencies in depth, with practical exercises and real-world applications.

Evaluating Claude for your workflows

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.

Why evals matter

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:

  • Understand where Claude adds the most value in your workflow
  • Identify tasks where you'll need to provide more context or examples
  • Build confidence in Claude's outputs for recurring tasks

A simple eval approach

You don't need complex infrastructure to evaluate Claude. Here's a practical approach:

  1. Gather examples. Collect 5-10 examples of a task you do regularly—emails you've written, reports you've created, analyses you've done.
  2. Create test prompts. Write prompts that would generate similar outputs. Include the context you'd naturally have when doing this work.
  3. Compare outputs. Run your prompts and compare Claude's responses to your examples. Ask yourself:
    • Does Claude capture the key information?
    • Is the tone and style appropriate?
    • What's missing or could be improved?
  4. Refine your approach. Based on what you learn, adjust your prompts, add examples to show Claude what good looks like, or identify where human review is essential.

iterate

1. Gather 5-10 past work examples

2. Create test prompts with context

3. Compare Claude output vs gold standard

4. Refine prompts, add examples

Build trust + intuition about Claude

Example: Using Claude for data analysis

The video above is taken from our AI Fluency for nonprofits course, but the example is relevant for anyone working with data in AI. To evaluate how Claude might work with your data:

  • Find a dataset you've manually analyzed
  • Create prompts that request Claude to do the analysis on your behalf
  • Compare Claude's results to your originals
  • Note patterns and refine your prompt accordingly: Maybe Claude gets the right numbers but misses the overall patterns

This kind of lightweight evaluation helps you develop intuition for how to work with Claude on tasks that matter to you—and where to focus your review and refinement energy.

Lesson reflection

Before moving on, consider:

  • Which of the common challenges have you already encountered? What techniques might you try next time?
  • Where in your work would a simple eval help you understand if Claude is a good fit for a recurring task?
  • How might the 4D Framework help you think about your collaboration with Claude?

What's next

In the next lesson, you'll explore the Claude desktop app and its three interaction modes: Chat, Cowork, and Code.

Feedback

As you progress through the course, we'd love to hear from you about how you are using concepts from the course in your work and any feedback you may have. Share your feedback here.

🎬 Video transcript

Source video: Zzn-g8lvLMA

📜 Click to expand transcript (cleaned + AI-translated)

Building Trust in AI through the Delegation Diligence Loop

In our last lesson, we dealt with data privacy and security—what you absolutely need to protect and how to do it. Now, let's address the question that has likely stopped you from using AI for data analysis in the first place: How can I trust the results?

Today's lesson is about the Delegation Diligence Loop. Specifically, it is about building confidence in AI's analytical capabilities for your specific work by systematically testing it against data you already understand. By doing this, you can better understand how AI will support your specific circumstances.

The Process of Delegation

The process starts with delegation. Here is how this works:

  1. Identify a specific analytical task you do regularly that you want to delegate to AI.
  2. Find past data where you have already completed the analysis.
  3. Work with AI to reproduce what you did, evaluating what works and what doesn't.
  4. Refine your approach and test again.

If AI can match your known results, you know how to use it and trust it for similar future tasks. If not, you have learned that this specific task is something you should not delegate.

Case Study: Practical Application in Program Management

To see what this looks like in practice, let's look at Rio, the program director at Valley Veterans Services. Every quarter, he analyzes program attendance alongside employment outcomes, calculating participation rates, tracking monthly changes, and determining whether attendance correlates with job placement success. This analysis consistently takes him hours.

Setting Up the Test Case

Considering delegation, Rio knows he wants to continue using the results of this analysis to improve his program. He wants to interpret the results himself, but he could do without the data cleaning and formula mayhem he usually finds himself in.

To test whether AI is appropriate, he evaluates it using last quarter's data. He knows exactly what this data showed after he analyzed it without AI, and he has the raw, messy data from before he started. This is his test case.

Executing the Diligence Loop

Rio uploads the data and starts to work with AI, using description and discernment to perform his analysis. Each time the AI responds, Rio checks the results against what he knows to be true and jots down potential gaps in AI's reasoning.

  • Refining Description: Sometimes additional description helps AI get the outcome he is looking for. In these cases, Rio knows he must include that kind of information for future tasks.
  • Identifying Capability Gaps: Other times, Rio might find legitimate capability gaps. This diligence changes what he chooses to delegate in the future.

Iterative Testing and Refinement

Rio's first attempt might look like this: "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."

AI responds with a summary, but rather than assuming this is fact, Rio checks it against his records. He notices that while AI correctly identified the correlation, it missed a critical insight regarding the combined housing assistance and job placement program.

Rio refines his description, asking AI to try again but pay special attention to the program type. This time, AI catches its mistake. Rio notes that for future quarters, he will need to specifically request the AI to consider the program type.

Next, he tests something harder: "Can you also look at this based on when participants enrolled?" Rio observes that despite not having the enrollment data explicitly formatted, AI could help extract it. He makes a note to cross-reference these results later.

Validated Confidence vs. Guesswork

By going through this process, Rio has systematically validated what AI can and cannot do for his quarterly reporting. He has learned that with the right description, AI can accurately reproduce manual analysis. However, he has also identified clear limitations:

  • AI needs explicit enrollment dates to do cohort analysis; otherwise, it tries to infer them inaccurately.
  • He now has a tested approach and clear notes on what context he needs to add himself.

When Rio uses this validated approach with new data, his diligence continues. He checks whether numbers make sense, takes accountability for the final report, and remains transparent about AI's role. He is now working from validated confidence, not guesswork.

Framework for Data Delegation

If you want to apply this yourself, follow this framework:

  1. Identify a specific analytical task that you want to delegate. Be precise about what you need.
  2. Find past data where you already completed that analysis. You need the right answers to evaluate whether AI can arrive at them.
  3. Work with AI to reproduce your past analysis and systematically evaluate the results.
    • What did AI produce?
    • How did it approach the task?
    • How did it communicate findings?
  4. Identify gaps, refine your delegation, and test again.

If you can validate that AI produces correct results, you have built an approach you can use on new data. If you cannot get there after several refinements, you have learned that this is not a task you should delegate.

Support for Non-Data Experts

What if you are not comfortable with data to begin with? AI can still be a useful tool to brainstorm and implement solutions. Because AI models are uniquely good at coding, they can help with:

  • Writing Excel formulas.
  • Reformatting messy data.
  • Explaining complex data concepts.

In these cases, bring your question to AI and ask for help understanding what a solution could look like, just as you would work with a data analyst on your team. Ask for clarifications and explanations so you can follow the process and understand the final output.

Final Principles of AI Analysis

Validation builds confidence, but it does not eliminate responsibility. You are still accountable for checking that results make sense and being transparent about AI's role in your analysis process.

This testing works for any analytical task:

  • Donor analysis.
  • Budget forecasting.
  • Survey synthesis.
  • Outcome tracking.

Test first, validate what works, and then apply with confidence—or learn what you shouldn't delegate at all.

🔁 Related lessons

📚 Source & attribution

Was this lesson helpful?

Feedback / ReportSpotted an issue or have an improvement idea?