Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
AI Fluency Playbook
Getting Started
How to Use
Core Content
Five Pillars
Exercises
Concepts
Learning Profiles
Archetypes
Pathways
Reference
Resources
Glossary
Tools
Further Reading
GW AI Fluency Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
The Verification Checklist
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
''Build a personal AI verification checklist and stress-test it against real AI outputs. 25 minutes.'' <blockquote> '''One-liner:''' Build a personal AI verification system β a checklist you'll actually use β and stress-test it against real AI outputs to find its limits. </blockquote> ---- == π§ Jump in (Tinkerers start here) == You're going to build a verification checklist, then immediately try to break it. '''Step 1 β Generate something to verify.''' Ask AI to produce a piece of content you might actually use in your work: <blockquote> Write a '''[deliverable type β e.g., client email, project proposal, market analysis, technical recommendation]''' about '''[topic relevant to your work]'''. Make it detailed and specific. Include data points, recommendations, and reasoning. </blockquote> '''Step 2 β Build your checklist.''' Before reading the output carefully, write your own verification checklist. Start with these categories and add your own: | Check || Question || Pass/Fail | '''Factual claims''' || Are specific numbers, dates, or statistics verifiable? || | '''Sources''' || Could I find the original source for any cited information? || | '''Reasoning''' || Does the logic hold? Are there hidden assumptions? || | '''Completeness''' || What important perspective or consideration is missing? || | '''Tone/audience''' || Is the tone appropriate? Would the intended audience trust this? || | '''Actionability''' || Are the recommendations specific enough to actually follow? || | '''Your domain check''' || [Add a check specific to your field] || | '''Your domain check''' || [Add another check specific to your field] || '''Step 3 β Apply the checklist.''' Go through the AI output line by line using your checklist. Mark each check as pass or fail. For every fail, note what the issue is. '''Step 4 β Stress-test the checklist.''' Now deliberately ask AI to produce something harder to verify: <blockquote> Write the same type of '''[deliverable]''' but on a topic I'm less familiar with: '''[topic outside your expertise]'''. Make it equally detailed and authoritative. </blockquote> Apply your checklist again. Where does it fail to catch problems? What check do you need to add? '''Step 5 β Finalize.''' Update your checklist based on what you learned. Save it where you'll actually use it β bookmark it, pin it, print it, whatever works. ---- == π Plan first (Planners start here) == Here's what you're about to do: # '''Generate test content''' β Ask AI to produce a work-relevant deliverable. This gives you realistic material to verify. # '''Draft your checklist''' β Build a structured verification list covering factual accuracy, reasoning quality, completeness, tone, and domain-specific concerns. # '''Apply to familiar territory''' β Use the checklist on AI output about a topic you know. This lets you calibrate how well the checklist catches real errors. # '''Apply to unfamiliar territory''' β Use the checklist on AI output about a topic you ''don't'' know well. This exposes gaps in your process β the errors you can only catch with domain knowledge. # '''Iterate and save''' β Update the checklist based on what it missed. Save it in a format you'll actually reach for. '''"Done" looks like:''' A tested, refined verification checklist (8-12 items) saved in a usable format, with evidence of at least one error it caught and one gap you identified and fixed. ---- == π§ Why this matters (Strategists start here) == In [[The Fact-Check Habit|EP-Basic-01]], you built a simple 3-question verification prompt. Here, you're building a '''systematic process''' β a checklist that works regardless of topic, catches both factual and reasoning errors, and is tuned to your specific work context. The community's 75% Ethical Prompting score means most people ''intend'' to verify AI output but lack a consistent method. A checklist turns good intentions into reliable behavior. At the advanced level, you'll scale this into a governance framework for a team; this exercise builds the individual practice first. ---- == Reflection == * Which check caught the most problems? Which was least useful? * How did your verification experience change between the familiar topic and the unfamiliar one? * Is your checklist something you'd actually pull up before sending an AI-generated deliverable? What format makes it most likely you'll use it? * π¬ ''Trade checklists with a colleague. Have them apply yours to an AI output from their work β their feedback will reveal blind spots specific to your domain.'' (Social Learners) == β¬οΈ Level up == Ready for more? Try [[The AI Governance Playbook|EP-Advanced-01]] β where you'll design an AI governance framework for a team or project. Back to [[Pillars/Ethical Prompting|Ethical Prompting & Judgment]] [[Category:AI Fluency Playbook]] [[Category:Exercises]] [[Category:Ethical Prompting Exercises]]
Summary:
Please note that all contributions to GW AI Fluency Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
GW AI Fluency Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)