01Concept · Notice the risk
Automation bias
A recommendation can feel more trustworthy because it comes from an automated system. Automation bias is the tendency to rely on that recommendation even when other evidence should make us question it.
- When it helps
- When a fluent AI draft, summary, or recommendation is about to become someone else's reference material.
- Try it
- Choose one factual claim in an AI-generated guide. Find the underlying source and compare the wording, exceptions, and date. Record any disagreement before accepting the claim.
- Watch out for
- Knowing the name of the bias does not eliminate it. A check is a review practice, not a guarantee against error.
Collected in the Knowledge Atlas. Research reference: Raja Parasuraman and Dietrich H. Manzey (2010). The guide-review activity is a Darronhold teaching adaptation. Read the research abstract.
02Method · Establish context
Facts & Expertise Primer
Before asking a model for an output, give it checked facts, the perspective it should work from, and a clear scope. Identify missing information instead of letting a plausible story fill the gaps.
- When it helps
- When drafting a resource that must reflect a particular service, audience, or situation.
- Try it
- For a workshop invitation, list the confirmed audience, duration, and activities on separate lines, with their sources. Mark unconfirmed details as unknown. Then request a draft limited to that information.
- Watch out for
- The model does not make a supplied fact true. Verify the inputs yourself and check that the draft has not introduced new claims.
Adapted from the Facts & Expertise Primer entry in Kyle Hobson's Knowledge Atlas / AI Glossary collection. The record does not identify an original external author; no origin claim is made. Open the collection entry.
03Method · Make the work manageable
Goal Breakdown
Prompt/Question Decomposition
Turn a complex goal into smaller questions and tasks that can be checked. The result should make the next action clearer, not simply produce a longer to-do list.
- When it helps
- When a team knows the outcome it wants but cannot yet tell what to do first.
- Try it
- Break 'prepare a volunteer orientation' into four outputs: confirmed audience needs, a short agenda, a practice activity, and a reviewed guide. Name what would show that each output is ready, then choose the first unresolved question.
- Watch out for
- A detailed plan can still rest on a wrong assumption. Check dependencies and unknowns before carrying out the steps.
Adapted from Goal Breakdown (Prompt/Question Decomposition) in Kyle Hobson's Knowledge Atlas / AI Glossary collection. The record does not identify an original external author; no origin claim is made. Open the collection entry.
04Framework · Review the result
RACCCA
Relevance · Accuracy · Completeness · Clarity · Coherence · Appropriateness
Use six lenses to review an AI-generated response. Instead of asking only whether a draft sounds good, look for the particular ways it succeeds or needs revision.
- When it helps
- When comparing drafts or preparing one for a specific audience.
- Try it
- Review a short response against the six criteria. Under each, note one observation and a concrete change. The worked example below shows this in practice.
- Watch out for
- Ratings are judgments, not objective measurements. Accuracy still needs evidence outside the response.
Andrew Maynard's RACCCA framework, developed for an Arizona State University prompt-engineering course; collected in Kyle Hobson's Knowledge Atlas. The example below is a new teaching adaptation. Read Maynard's framework.