Home / Guides / Design critique lecture notes

Design Critique YouTube Lecture Notes That Capture Feedback

Published 2026-09-18 · Francesco Masciopinto

Design students watch critique lectures, live studio uploads, and “redline this UI” breakdowns on YouTube—then close the tab with a feeling and zero actionable notes. Useful design critique YouTube lecture notes capture criteria, observations tied to goals, and next experiments, not a transcript of someone’s taste.

Decide what “notes” must enable

If your notes only say “make it cleaner,” you captured a vibe, not feedback.

Pass 1 — Map the critique session

Tags for first watch:

time — segment — tag (context / goal / critique / principle / demo fix / Q&A)

Example for a UI critique lecture:

• 00:00–06:00 — Project brief restated (goal)
• 06:00–14:20 — Success criteria / rubric (principle)
• 14:20–38:00 — Walkthrough critiques on example screens (critique)
• 38:00–49:30 — Live revision moves (demo fix)
• 49:30–end — Student questions / edge cases (Q&A)

Watch at 1× when they point at UI details; you can go slightly faster on logistics.

Done check: write the success criteria in your own words without the video.

Pass 2 — Capture critique as structured claims

For each substantial critique moment, use a fixed template:

Weak: “Navbar is bad.”
Strong: Navbar — Observation: 5 equal-weight items compete. Goal conflict: “primary task = search.” Principle: visual hierarchy. Experiment: one primary + overflow. 22:15.

Stay descriptive. Critique notes that insult the designer (even yourself) waste working memory.

Pass 3 — Build a personal rubric glossary

Critique lectures reuse words—“hierarchy,” “alignment,” “cognitive load,” “affordance,” “gestalt,” “type ramp.” Maintain a one-page glossary:

• Term (course spelling)
• One-sentence meaning as used in this class/video
• Thumbnail example timestamp
• Non-example (what people mis-call by this name)

When terms stay fuzzy, your notes become synonym soup.

Pass 4 — Turn notes into revision experiments

Feedback that does not change a file is unfinished. Same day:

1. Pick your own project (or a practice redesign).
2. Apply one experiment from the lecture’s highest-severity pattern.
3. Record before/after and which criterion improved.
4. If the experiment fails, note what you learned—do not silently revert and forget.

For lecture study without a live project, redesign a public screenshot under the lecturer’s rubric and write a 5-bullet self-critique.

Studio / exam / portfolio week uses

• Studio: bring your structured claims; speak observation → criterion → experiment.
• Design exams / quizzes: principle definitions + “what’s wrong / why / fix” items map cleanly to your claim table.
• Portfolio case studies: decision logs from critique notes become process narrative (problem → options → choice).

Pitfalls

• Taste cosplay — copying a YouTuber’s aesthetic without criteria.
• Note maximalism — fifty nitpicks, zero experiments.
• Ignoring constraints the brief stated (time, brand, accessibility requirements as taught).
• Tool talk instead of critique (“just use Auto Layout”) when the issue is informational hierarchy.
• Accessibility handwaving—if the lecture teaches specific checks, capture them as criteria, not vibes; follow your course and relevant standards coursework for graded work.

Self-critique checklist cloned from the lecture

After you capture the lecturer’s rubric language, clone it into a short checklist you run on your own work weekly:

1. Goal / user / constraint restated in one line
2. Top three screens or spreads against hierarchy criteria
3. One accessibility or clarity check as taught in that video/course
4. One experiment scheduled with a deadline

Critique YouTube without self-application becomes entertainment. The checklist makes design critique YouTube lecture notes operational. Keep the checklist short enough to finish; a 30-item moral inventory will not get used.

Note template you can copy per video

Brief/goal (1 line):
Rubric criteria (bullets):
Critique claims (table rows):
Experiments queued (3 max):
Glossary terms added:
Self-critique date:

Fill it once per critique lecture. The constraint of three experiments max prevents infinite nitpick lists. Over a term, these templates become a searchable log of principles you actually practiced—stronger evidence in a portfolio process section than a folder of unwatched critique VODs.

Separating craft notes from product notes

Critique videos often mix visual craft (type, color, layout) with product thinking (job-to-be-done, funnel, empty states). In your claim table, tag each row craft or product. When you revise, pick experiments from the tag your brief actually prioritizes this week. Mixing tags without labeling is how students “fix spacing” when the real issue was unclear primary action.

Optional on-page panel

An on-page YouTube panel helps you chapter-mark critique beats, summarize the rubric, chat “what principle did they invoke at 22:15?”, and make Study flashcards for principle definitions and “spot the issue” prompts. Use AI as a drafting aid; your eyes still need to verify against the frame.

If you want summary, chapters, chat, and Study flashcards on the watch page, SummarizAI is a Chrome extension for students studying from YouTube lectures. The free plan works as a student trial. A paper claim table is enough if you actually run experiments.

Frequently asked questions

Related guides

• How to Take Notes From YouTube Lectures (A Workflow That Sticks)
• YouTube timestamp notes: a repeatable workflow
• How to Study From YouTube Lectures Without Rewatching the Whole Video
• How to Convert a Lecture Video Into a Study Guide Students Actually Use
• How to extract key points from a YouTube video
• How to Retain Information From Video Lectures (Beyond Rewatching)