AMX / LABS × TECH AT NITEFour-week experience

Winter Blitz / Four-week project studio

One useful project.
Four weeks to make it real.

Learn AI literacy and social cybersecurity by creating something your community can use. Build a little each week. Show your work. Make it better.

Beginners welcomeSolo or teams of 2–4About 3 hours each week

The challenge

Help your community make better digital decisions.

Create a guide, explainer, poster, short media piece, or simple webpage that helps a specific audience use AI thoughtfully or recognize online deception.

Finish with: a useful resource, a source log, a safety card, an evidence portfolio, and a short presentation.

A steady weekly rhythm

Learn. Build. Share.

  • 90-minute guided lab: 10-minute check-in, 15-minute demonstration, 50-minute build, 15-minute reflection.
  • 45-minute independent studio: improve your artifact and prepare evidence.
  • 45-minute showcase: demonstrate, get feedback, and choose a revision.

Suggested format. Hosts set dates, meeting links, and presentation order. No sessions are scheduled by this page.

Choose your project

Use a notebook, document, slide tool, or paper. No paid AI tool or headset is required. If you work with young people, the facilitator selects age-appropriate tools and sharing permissions.

Only use fictional or approved public examples. Learners can use the worked example if interviewing or testing with someone is not possible.

0 of 12 practice checks

Notes and self-checks stay in this browser; they are not submitted or synced.

0 of 12

Reset clears this program’s checks only; your notes stay. Export your notes before changing browsers or clearing browser data.

Week 1 · A problem worth solving

Discover & define

Who could we help, and what would a useful first version do?

Your outcome

Write a clear project brief and compare two AI-assisted drafts against real evidence.

Learn, then build

Start with A1 Understand AI, A2 Ask better, and A3 Check before sharing in the foundation course. Open the foundation course.

  1. Choose a real audience: a community group, a learning club, or a fictional local organization. Ask one consenting person about a need, or use the example brief below.
  2. Write a one-sentence problem, one intended user, and two success criteria you can observe. Keep the scope small enough to finish in four weeks.
  3. Draft a resource yourself or with an approved AI tool. Try two prompts that specify audience, purpose, constraints, and output format. Keep the prompts and describe what changed.
  4. Check at least two important claims using original sources. Record the source title, URL, date checked, and what the source actually supports. Label unknowns.
  5. Prepare a one-page brief with a rough sketch, two prompt versions, a source log, and a short explanation of the human decisions.

Bring to the showcase

  • One-page project brief with audience, problem, scope, and two success criteria
  • Two draft/prompt versions with a comparison
  • Evidence log for at least two claims; unknowns clearly marked

Weekly showcase

Idea & evidence pitch

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.

Worked example & practice prompt

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.

Your Week 1 notebook

Private to this browser. Keep passwords, personal records, and private links out of these notes.

My practice checks

Week 2 · Turn the idea into something useful

Make & test

Can someone else use our prototype without us explaining every step?

Your outcome

Build a small prototype and improve it after observing a user try a task.

Learn, then build

Revisit A2 and A3. Use any accessible tool you already have: paper, a document, slides, audio, or a simple webpage. Open the foundation course.

  1. Choose a format: a poster and checklist, a three-slide explainer, a captioned one-minute audio/video piece, or a simple webpage. A paper prototype counts.
  2. Build version 1 around your two success criteria. Add a clear title, one useful action, readable text, and source attribution.
  3. Prepare three tasks for a tester, such as finding the action, explaining a warning in their own words, and locating a source. Ask a consenting peer to try them; record observations without personal details.
  4. Separate what the tester did from your interpretation. Note confusing language, missing information, contrast, captions, and mobile readability where applicable.
  5. Make version 2. Record at least two changes and the evidence behind each. If no tester is available, run a self-walkthrough and label it as such.

Bring to the showcase

  • Working or paper prototype, version 1 and version 2
  • Three-task test sheet with observations and tester or self-review label
  • Revision log with at least two evidence-based changes

Weekly showcase

Prototype demo

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.

Worked example & practice prompt

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.

Your Week 2 notebook

Private to this browser. Keep passwords, personal records, and private links out of these notes.

My practice checks

Week 3 · Trust is part of the design

Check & protect

What could mislead or expose our audience, and how can we reduce that risk?

Your outcome

Produce a safety-reviewed prototype with a claim audit and a response checklist.

Learn, then build

Complete B1 Defend accounts, B2 Spot the scam, and B3 Respond & recover. Practice with fictional messages and demonstrations. Open the foundation course.

  1. Audit the prototype: check factual claims, source links, image/audio permissions, AI assistance disclosure, and information that should not be public.
  2. Map a simple trust problem: an impersonated organizer sends an urgent invitation. Identify who could be affected, what they might do, and what independent check would help.
  3. Run a tabletop exercise with a clearly fictional message. Discuss how a reader pauses, verifies through a known route, reports through the official service, and recovers if access is lost. Do not send deceptive messages or collect credentials.
  4. Write a one-page safety card: prevention habits, independent verification steps, official reporting/recovery routes, and a trusted support contact category. Use placeholders instead of private contact details.
  5. Revise the prototype and record what you removed or corrected. Re-test the user task from Week 2 and state any remaining limitations.

Bring to the showcase

  • Claim and privacy audit with corrections and remaining limits
  • One-page prevention, verification, and recovery safety card
  • Revised prototype and a short tabletop exercise reflection

Weekly showcase

Trust & safety clinic

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.

Worked example & practice prompt

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.

Your Week 3 notebook

Private to this browser. Keep passwords, personal records, and private links out of these notes.

My practice checks

Week 4 · Make your learning visible

Finish & showcase

Can we explain what we built, why it helps, and why others should trust it?

Your outcome

Present a finished community resource and an evidence-backed learning portfolio.

Learn, then build

Review the foundation quiz and the project feedback. Choose one weak area to revisit before the showcase. Open the foundation course.

  1. Finish the resource and run your two success criteria again. Record the outcome honestly, including anything not yet achieved.
  2. Assemble the portfolio: project brief, prompt/draft comparison, source log, prototype revisions, user-test notes, safety card, and final artifact.
  3. Prepare a five-slide story: need and audience; solution; evidence and revisions; safety and limitations; next step. Add captions or a transcript for recorded media.
  4. Rehearse a three-minute demo. Remove private names, account information, unapproved likenesses, and hidden answer keys from anything shown on screen.
  5. Present, collect feedback, and write a reflection: what I learned, what AI helped with, what I decided, and what I will improve next. Public sharing is optional and requires the group’s agreed permission.

Bring to the showcase

  • Finished artifact with sources and AI-use disclosure
  • Portfolio showing evidence, changes, safety review, and reflection
  • Three-minute demo or an accessible written/recorded alternative

Weekly showcase

Winter Blitz community 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.

Worked example & practice prompt

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.

Your Week 4 notebook

Private to this browser. Keep passwords, personal records, and private links out of these notes.

My practice checks

Every week, make the learning visible

Showcase with purpose.

A showcase is a work-in-progress conversation in Weeks 1–3 and a finished-project presentation in Week 4. Bring evidence, not just a polished picture.

45-minute agenda

  1. 5 minutes: welcome, access needs, and today’s feedback focus.
  2. 30 minutes: up to six project slots, five minutes each.
  3. 7 minutes: written reflection and revision commitments.
  4. 3 minutes: confirm next steps and the next meeting.

A five-minute project slot

Weeks 1–3: 2-minute demo, 2-minute peer feedback, 1-minute revision commitment.

Week 4: 3-minute demo, 1-minute audience question, 1-minute next step.

For more than six projects, use parallel rooms or two showcase sessions. Offer a written, audio, or captioned recording alternative.

Feedback that helps the next version

Useful

The audience and need are clear. A user can complete the intended task.

Evidence-based

Important claims have sources. Changes are connected to observations, not just preferences.

Responsible

Private information is removed. Asset permissions, AI assistance, verification routes, and limitations are explained.

Clear

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.

Showcases happen in your group’s chosen meeting space. This page does not upload projects, host calls, collect registrations, or publish learner work.

New to the basics?

The original six-station lesson remains available as the foundation for this program.

Open AI Literacy & Social Cybersecurity 101