Useful
The audience and need are clear. A user can complete the intended task.
Winter Blitz / Facilitator edition
A practical delivery plan for AI Literacy & Social Cybersecurity 101.
Designed for beginner community learners, working solo or in teams of 2–4. Adapt reading level, tools, and permissions to the group. No paid AI tool is required.
How might we help a specific community make better digital decisions using a resource that is useful, evidence-based, and safer to share?
Offer a choice of guide, poster, short explainer, slide deck, or simple webpage. Keep one project through all four weeks so revisions are visible. Use the fictional event-invitation example when learners need a starting point.
Prerequisite: ability to read or listen to the materials and use a document or paper notebook. Begin with the six-station foundation course as needed; do not make tool accounts a barrier.
Independent studio: 45 minutes to finish the weekly deliverables and prepare a demo. If a learner misses a lab, send the weekly brief, offer a short check-in, and accept a written or recorded showcase.
Week 1 · A problem worth solving
Who could we help, and what would a useful first version do?
Write a clear project brief and compare two AI-assisted drafts against real evidence.
Start with A1 Understand AI, A2 Ask better, and A3 Check before sharing in the foundation course. Open the foundation course.
Weekly showcase
Show the need, a rough sketch, one improved prompt, and one claim you checked. Ask the audience: “Would this help the person we chose?”
Peer feedback: Peers name one strength, one unsupported assumption, and one manageable next step.
Revision goal: Choose one peer suggestion and explain how it changes your Week 2 build.
A neighborhood club needs a one-page guide for checking suspicious event invitations. Success: a new reader can name two checks in one minute and find the official event link.
Using this fictional neighborhood club, draft a 120-word event-verification checklist for beginners. Include a clear pause-and-check step. Do not invent event dates, official links, statistics, or quotes. Mark missing facts as [VERIFY].
An AI tool is optional. You can write and compare drafts yourself. Use fictional or approved public material.
Week 2 · Turn the idea into something useful
Can someone else use our prototype without us explaining every step?
Build a small prototype and improve it after observing a user try a task.
Revisit A2 and A3. Use any accessible tool you already have: paper, a document, slides, audio, or a simple webpage. Open the foundation course.
Weekly showcase
Demonstrate one task in version 2. Show a before/after change and the observation that caused it.
Peer feedback: Peers try one task, describe where they hesitated, and suggest one improvement.
Revision goal: Choose one usability issue and one trust question to investigate in Week 3.
The invitation checklist becomes a large-print poster and a phone-friendly document. A tester finds the official-link step but misses the warning about urgent messages, so the team moves that warning nearer the top.
Review this fictional checklist for clarity. Identify confusing phrases and suggest shorter alternatives. Do not add facts. Explain what a human tester should check.
An AI tool is optional. You can write and compare drafts yourself. Use fictional or approved public material.
Week 3 · Trust is part of the design
What could mislead or expose our audience, and how can we reduce that risk?
Produce a safety-reviewed prototype with a claim audit and a response checklist.
Complete B1 Defend accounts, B2 Spot the scam, and B3 Respond & recover. Practice with fictional messages and demonstrations. Open the foundation course.
Weekly showcase
Show one fictional risk, your verification path, and a change that makes the project safer. Explain a limitation you still have.
Peer feedback: Peers ask: “What is your evidence? What information is unnecessary? Where would I verify this independently?”
Revision goal: Resolve one high-priority issue before preparing the final presentation.
The team removes an unverified statistic, labels an AI-created illustration, and replaces a shortened link with a readable official destination. Its mock scenario uses invented names and no real login page.
For this fictional project, list possible confusion, privacy, or impersonation risks. Suggest questions a reviewer should ask. Do not generate a real phishing message, request credentials, or claim the project is secure.
An AI tool is optional. You can write and compare drafts yourself. Use fictional or approved public material.
Week 4 · Make your learning visible
Can we explain what we built, why it helps, and why others should trust it?
Present a finished community resource and an evidence-backed learning portfolio.
Review the foundation quiz and the project feedback. Choose one weak area to revisit before the showcase. Open the foundation course.
Weekly showcase
Use three minutes to explain the need, demonstrate the artifact, show evidence of improvement, and name one limitation. Take one minute of questions and one minute for your next step.
Peer feedback: Peers use the four-part rubric and describe a specific piece of evidence behind each rating.
Revision goal: Choose one follow-up improvement and keep a copy of your portfolio after the program.
The final showcase presents a two-page event-verification kit, a before/after poster, a three-task test result, and a short explanation of where AI suggestions were accepted or rejected.
Help me outline a three-minute presentation using only these project notes. Keep claims tied to evidence, identify missing information, and include a clear statement of human decisions and remaining limitations.
An AI tool is optional. You can write and compare drafts yourself. Use fictional or approved public material.
Showcase playbook
Use 45 minutes for up to six projects: 5-minute welcome, six 5-minute project slots, 7-minute reflection, and 3-minute close. Add parallel rooms or another session for larger groups.
Weeks 1–3: 2-minute demo, 2-minute feedback, 1-minute revision commitment. Week 4: 3-minute demo, 1-minute question, 1-minute next step. Teams divide the speaking roles; solo learners can ask the moderator to read questions.
Welcome to the Winter Blitz showcase. We are here to learn from the work and help the next version. Show what you made, the evidence behind a decision, and something you want feedback on. Ask before recording or sharing anyone’s work.
The audience and need are clear. A user can complete the intended task.
Important claims have sources. Changes are connected to observations, not just preferences.
Private information is removed. Asset permissions, AI assistance, verification routes, and limitations are explained.
The demo is understandable, readable or captioned, and includes a next step.
For each area, give 1: emerging (not yet shown), 2: developing (partly shown), or 3: demonstrated (supported by a concrete example). Add one evidence note and one next step. This is a feedback rubric, not a credential or security certification.
| Slot | Project / team alias | Presenter / format | Feedback focus |
|---|---|---|---|
| 1 | ________________ | ________________ | ________________ |
| 2 | ________________ | ________________ | ________________ |
| 3 | ________________ | ________________ | ________________ |
| 4 | ________________ | ________________ | ________________ |
| 5 | ________________ | ________________ | ________________ |
| 6 | ________________ | ________________ | ________________ |
Audience: ________ · Problem: ________ · Artifact: ________
Success criterion 1: ________ · Success criterion 2: ________
In scope: ________ · Out of scope: ________
Claim: ________
Original source title and URL: ________
Date checked: ________
What it supports / does not support: ________
Action: keep / correct / remove / mark unknown.
Task: ________ · Expected result: ________
Observed result: ________ · Test type: consenting peer / self-review.
Change made: ________ · Retest result: ________
I used [tool or manual drafting] to help with [task]. I checked [claims or outputs] using [sources or tests]. I changed or rejected [suggestion] because [reason]. I made the final decisions about [choices].
One strength: ________ · One question: ________
One revision: ________ · Evidence I will collect next: ________
No AI access: use manual drafts and the example prompts as a critique exercise. No peer tester: label a self-review. No internet: use this handbook and a paper artifact, then verify sources when connected. Storage unavailable: export notes before leaving the page. Showcase not accessible: accept a written or captioned alternative.
AI Literacy & Social Cybersecurity 101 includes the six learning stations, practice quiz, and source references. The program is educational practice, not a professional certification or a security audit.
Dates, enrollment, recording, submissions, and streaming are arranged by the host. This handbook does not activate those services.