Error Analysis Journal From YouTube STEM Lectures
An error analysis journal from YouTube STEM lectures tracks why a worked example or practice attempt failed—concept, setup, algebra/manipulation, units/signs, or misread—then links each miss to a timestamped repair. It is tighter than a general lecture mistake log: the unit of analysis is the problem attempt, not every confusing sentence.
This is study skills for course problem-solving—not professional engineering sign-off.
Error taxonomy (use consistently)
| Code | Meaning | Typical fix |
|---|---|---|
| C | Concept / principle wrong | Rewatch claim minute; write because |
| S | Setup / diagram / knowns | Redraw givens; list variables |
| A | Algebra / symbolic slip | Slow re-derive without video |
| U | Units / signs / dimensions | Dimensional check checklist |
| R | Misread question | Underline target; restate ask |
One primary code per miss. Secondary codes optional.
Pass 0 — Choose problems worth journaling
From each STEM lecture, pick 2–5 worked examples that match quiz style. Ignore novelty demos you will never be asked.
Pass 1 — Attempt before full solution reveal
When the professor sets up a problem, pause:
- Attempt for 3–8 minutes closed (or partially).
- Resume to compare.
- Journal every mismatch with a code + timestamp of the correct step.
If you only watch solutions, your journal will be empty and useless.
Pass 2 — Journal row template
date — course — problem label — code — what I did — correct move — time — rework ✓/✗
Keep “what I did” to one line. Ego essays waste the habit.
Pass 3 — Weekly pattern review
Every Sunday, tally codes:
| Code | Count | Action next week |
|---|---|---|
| C | … | Extra claim retrieval before problems |
| S | … | Forced diagram pass |
| A | … | 10-minute algebra warm-up |
| U | … | Units checklist tattooed on sheet |
| R | … | Restate-the-ask ritual |
Patterns beat isolated shame.
Pass 4 — Closed rework
For each journal row still ✗:
- Cover solution.
- Rework on blank paper.
- Seek timestamp only if stuck after the time box.
- Flip to ✓ only after a clean rework.
Relating to a general mistake log
- Mistake log: confusing claims, vocab, or lecture traps.
- Error analysis journal: graded/problem misses with taxonomy.
Keep both if you like; do not merge into one mushy list.
Worked mini-example (physics)
Problem: incline with friction.
You missed acceleration direction.
Code: S (setup) + U (sign).
Correct move timestamp 14:55 axes.
Rework next day with axes first; ✓.
Linking lecture claims to problem errors
When code = C (concept), do not only rework the problem—pull the claim timestamp into the journal row. Example: wrong energy conservation → seek the minute the professor stated the system boundary rule. Your journal then becomes a bridge between watching and practicing, not two parallel hobbies.
Create a reverse index weekly:
claim timestamp — problems that failed because of it
That index tells you which lecture minutes deserve second-pass review.
Time-boxing attempts (avoid solution addiction)
Rules of thumb:
- Easy quiz-style: 3–5 minutes attempt before reveal.
- Multi-step exam-style: 8–12 minutes.
- If you are still lost at the time box, peek only the next step, not the full solution; continue; journal the peek as a partial miss.
Full-solution staring teaches recognition of the professor’s handwriting, not your process.
Spreadsheet schema that scales
Columns that work: date, course, problem_id, code, secondary_code, note, lecture_time, rework_date, rework_ok, exam_tag.
Filter views: open reworks; C-heavy weeks; exam_tag=midterm. If your journal cannot filter, it will die by week four.
Emotional hygiene (so you keep writing)
Write codes, not insults. “A: dropped minus sign” beats “I’m terrible at calc.” The journal is a diagnostic instrument. Students who moralize every miss stop logging.
One-week experiment
In one STEM course, every watched worked example requires a pause-attempt + journal row. Count rows at week’s end. If you have fewer than the number of examples, you drifted into passive watching—reset the rule.
Soft tool assist (optional)
Chapters jump you to the example block. An on-page summary can list which examples exist so you do not scrub. Study flashcards can store “trap → code → first move” cues after you author them.
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. The journal entries must still be your errors.
Pitfalls
- Coding everything as C.
- Journaling without rework.
- Copying the professor’s solution into the “what I did” column.
- Tracking 20 problems per lecture (unsustainable).
- Never tallying weekly patterns.
Frequently asked questions
Is this only for physics?
No—calc, chem (study skills), CS algorithms, stats proofs all fit.
What if solutions are too fast?
Pause; journal the step you lost; slow re-derive that step only.
Should I include exam mistakes too?
Yes—same taxonomy; link to the lecture timestamp that covers the idea when you find it.
How is this different from Anki fails?
Anki tracks card memory; this journal tracks problem process errors.
Can I type it?
Yes. Spreadsheet tabs by course work well.
Related guides
- Turn Tonight's YouTube Lecture Into a Closed-Book Quiz
- Active Recall From YouTube Lectures: A Practical Study Loop
- YouTube Lecture to Flashcards: A Student Workflow That Sticks
- Elaborative Interrogation After YouTube Lectures (Why → Because → Check)
- Dual Coding Diagrams From YouTube Lectures (Words + Pictures That Stick)
- Blank-Sheet Recall After a YouTube Lecture (Closed-Player Retrieval)
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