When the Bot Sounds Right but Is Not

Learners who can use a chatbot for simple tasks and now need to understand why plausible output still needs checking.

Audience

Learners who can use a chatbot for simple tasks and now need to understand why plausible output still needs checking.

What Do You Need

  • Time or session format: A short verification-practice session with examples of polished but flawed output.
  • Prior knowledge: Learners should have tried at least simple chatbot tasks or seen a facilitator demonstration.
  • Device, tool, or account needs: No account is required if sample outputs are provided; an approved chatbot can be used for optional live comparison.
  • Materials or examples: Confident AI answers with intentional issues, risk-level examples, and a verification checklist.
  • Privacy and safety boundaries: Do not use live high-stakes medical, legal, financial, employment, safety, or personal crisis questions as examples.
  • Participation options: Learners may mark up printed answers, work in pairs, discuss as a group, or compare against provided source material.

Purpose

Introduce AI failure modes through practical examples without making the tool feel useless or scary.

Learning Outcomes

By the end of this module, learners should be able to:

  1. Identify output that sounds confident but needs checking.
  2. Name common failure modes such as missing context, invented details, stale information, and overgeneralization.
  3. Decide what kind of verification an answer needs.

Core Ideas

  • Fluency is not accuracy.
  • Some mistakes are obvious; others are polished.
  • Verification depends on risk.
  • Learners can use AI while keeping judgment active.

Class Flow

  • Brief story or demonstration
  • Compare confident outputs
  • Identify what needs checking
  • Discuss verification levels
  • Take-home “sounds right” checklist

Hands-On Lab

  • Brain Dump to Memo gives learners a concrete transformation exercise: organize rough material without turning uncertainty into fact.

Learners review two or three confident AI-generated answers and mark what they would trust, revise, ignore, or verify.

Lab Materials

  • Sample AI answers with intentional issues
  • Verification checklist
  • Risk-level examples

Reflection Questions

  • What made the answer sound trustworthy?
  • What information was missing?
  • What claim would you check first?
  • What would be the consequence of using this answer without checking?

Take-Home Artifact

A “sounds right but check” worksheet for reviewing AI-generated answers, drafts, or recommendations.

Risks to Avoid

  • Overloading beginners with taxonomy.
  • Making learners distrust everything equally.
  • Using examples that require deep domain knowledge to spot.

Facilitator Notes

Choose examples where learners can identify risk through common sense and context clues, not specialized expertise.

Accessibility and Inclusion Notes

Offer plain-language examples. Use large-print comparison tables when possible. Let learners work in pairs.

Cross-Generation Potential

Maybe. This can support family learning if examples involve everyday information, purchases, travel, health-adjacent caution, or local services without giving professional advice.

  • Trust, but check.
  • Human ownership remains.
  • Friction is information.

Status Notes

Sketch ready for factuality and learning review. Needs sample outputs designed with clear teachable failure points.

Review status

  • Package lifecycle: Sketch
  • Learner availability: Planned
  • Review needs: Needs factuality review

Review this module


Source: modules/when-the-bot-sounds-right-but-is-not/module.md