Pre-Lecture Prediction Questions for YouTube Videos (Prime Before Play)
Pre-lecture prediction questions for YouTube videos are written before playback so your brain has hypotheses to confirm or kill. This is related to pause-and-predict mid-video, but the timing differs: priming happens cold, using title, description, chapters, and syllabus context.
Students who skip priming watch passively; priming turns the first pass into a test of expectations.
Prediction vs pause-and-predict
| Pre-lecture prediction | Pause-and-predict |
|---|---|
| Before any play | During play at chosen pauses |
| Uses title/chapters/syllabus | Uses just-heard setup |
| Good for activating priors | Good for local inference |
Use both across a week; do not treat them as duplicates.
Pass 0 — Gather cold cues (3 minutes)
Without pressing play, skim:
- Title + description
- Chapter list (if any)
- Syllabus learning objective for this session
- Your last lecture’s exit ticket (what was left open)
Write 3–6 prediction questions that an exam might ask.
Examples:
- “I predict they define elasticity with %ΔQ/%ΔP—will they stress arc vs point?”
- “I expect a proof via induction—will the base case be trivial?”
- “Fieldwork ethics will appear—will consent be procedural or relational?”
Pass 1 — Watch to falsify (not to confirm)
Play at 1.25×–1.5× with your questions visible.
For each question mark:
C confirmed · R revised · X contradicted · M missing (not addressed)
Add timestamps when revised or contradicted—those are gold for study.
Pass 2 — Rewrite answers closed-player
Close the video. Answer each prediction question in ≤3 sentences from memory. Seek only R/X/M rows.
Pass 3 — Convert to durable cues
| Outcome | Card / note action |
|---|---|
| Confirmed | One short cue; do not over-note |
| Revised | Front: old belief; back: correction + time |
| Contradicted | “Why my prediction failed” because-answer |
| Missing | Park for office hours / next video; do not invent |
Pass 4 — Next-session handoff
End with one open prediction for the next lecture. Continuity beats starting from zero each time.
Worked mini-example (CS lecture)
Cold cues: title “Hash tables”; chapter “collisions.”
Predictions: (1) chaining vs open addressing tradeoff, (2) load factor threshold, (3) security aside on hashing passwords (maybe out of scope).
Watch → (3) missing; (2) revised threshold.
Closed answers + cards for (2); park (3).
Writing questions that are falsifiable
Weak prediction: “Will this be about photosynthesis?”
Strong prediction: “I expect they separate light-dependent vs Calvin cycle and emphasize ATP/NADPH roles—study skills structure only.”
Falsifiable predictions name distinctions, thresholds, or methods. If nothing could contradict your question, it will not steer attention.
Use stems:
- “I expect they will define X as… Will they exclude Y?”
- “I predict the proof strategy is… Alternative could be…”
- “I think the case study will illustrate bias Z—will they name a confound?”
Priming from syllabus language
Copy the learning objective wording into your prediction sheet, then write how you think the video will operationalize it. The gap between official objective and your prediction is often where you discover vocabulary holes before play—exactly when you can still look up a term without spoiling the whole lecture.
Group prediction protocol (20 minutes)
- Solo write 3 predictions (5 min).
- Share without debate (5 min).
- Watch agreed segment.
- Score C/R/X/M together (5 min).
- Each person writes one revised because-answer (5 min).
Groups that debate predictions before watching often contaminate priors; share, then watch.
After-action: belief change log
Keep a tiny log:
date — old belief — new belief — time — emotional surprise high/med/low
High-surprise revisions deserve flashcards. Low-surprise confirmations do not.
One-week experiment
For five videos, ban opening any summary or transcript before predictions are written. Track how many contradictions you catch. If you catch zero, your predictions are too vague—tighten stems.
Soft tool assist (optional)
Chapter lists on-page make cold priming faster. A short summary after your predictions (not before) can help you score C/R/X/M quickly. Study flashcards store revised beliefs well.
If you want summary, chapters, chat, and Study flashcards on the YouTube watch page, SummarizAI is a Chrome extension built for students. The free plan works as a student trial. Write predictions before opening any AI summary.
Pitfalls
- Writing 20 vague questions (“What is this about?”).
- Reading a full AI summary before predicting (destroys the prime).
- Only confirming and never logging revisions.
- Predicting topics not in the syllabus (scope creep).
- Skipping closed answers.
Frequently asked questions
What if there are no chapters?
Use the first 60 seconds + description + syllabus objective only.
How is this different from learning objectives?
Objectives are official targets; predictions are your hypotheses about how the video will hit them.
Can groups share predictions?
Yes—compare before play, then reconcile after. Do not copy answers before watching.
Does this slow me down?
Three minutes of priming often saves a full rewatch.
Should beginners skip this?
Especially beginners benefit: predictions reveal vocabulary gaps early.
Related guides
- Elaborative Interrogation After YouTube Lectures (Why → Because → Check)
- Blank-Sheet Recall After a YouTube Lecture (Closed-Player Retrieval)
- Active Recall From YouTube Lectures: A Practical Study Loop
- Night-Before Midterm: Triage Your YouTube Lectures in 90 Minutes
- How to Feynman-Technique a YouTube Lecture After Watching
- Concept Map From a YouTube Lecture for Exams (Nodes That Carry Propositions)
Try SummarizAI on your next lecture
SummarizAI is a Chrome extension that adds a summary, chapters, and Study flashcards on the YouTube watch page. The free plan is a student trial—no need to leave the lecture tab.
Start the free student trial