1/39
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai |
|---|
No analytics yet
Send a link to your students to track their progress
Which framing clarifies the need and your response?
Problem-solution
Signposting helps by:
Previewing what you'll cover and in what order to keep audiences engaged
T/F: Capture feedback in a decision log and submit v2 changes clearly.
True
A pitch deck is best defined as:
Slides supporting a short persuasive presentation for decision-making
Including specs and constraints demonstrates that you followed the brief.
True
Use the method: repeat the question → bottom-line answer → evidence during Q&A.
True
A *styleframe* is:
A polished still that shows the intended final look of a key shot
Which tip helps translate vague goals into measurable outcomes?
Map adjectives to visual choices (palette, type, motion rules)
Which item belongs to *motion language*?
Rules for movement (easing, pacing, transition style, camera feel)
An *MVP (Minimum Viable Project)* means:
The minimal scope that still meets the brief's requirements
T/F: A shared "Requirements Checklist" is discouraged because it slows teams down.
False
T/F: Success criteria should define how the client will judge whether the work meets goals (measurable outcomes).
True
T/F: Starting with highest-risk shots early can prevent last-minute failure.
True
What are *constraints* in a client brief?
Non-negotiables like specs, platform, style rules, deadline, resources
T/F: A pitch is a decision tool, not a production diary.
True
A scope slide should:
Clarify what you will produce and what you will not produce
T/F: Every team member should avoid speaking to prevent confusion.
False
A client brief typically includes which of the following elements?
Goals, audience, deliverables, and constraints
T/F: The key message is a single sentence that states what the audience should remember or feel.
True
T/F: Highlighting every non-negotiable (resolution, fps, segmenting, submission rules) helps avoid rework.
True
In a *VFX breakdown*, you should:
List shot-by-shot tasks (keying, tracking, roto, typography, color, export)
A risk slide should present:
Top risks and mitigation plans
T/F: Q&A is where you prove feasibility; iteration after feedback is expected.
True
T/F: Problem-solution slides are optional and add little value to clarity.
False
Practical presentation tips include:
One idea per slide; show evidence early; include specs/constraints
T/F: The ask should align with client needs (e.g., approval of concept and plan).
True
Which definition best describes *deliverables* in a brief?
Required outputs like duration, format, resolution, fps, segments
A *moodboard* is best described as:
A set of reference visuals showing tone, color, texture, inspiration
T/F: Define the key message in one sentence and repeat it in intro and conclusion.
True
Proof of feasibility can include:
Styleframes, prototype test, breakdown, schedule
Misreading a requirement in the brief (e.g., duration or naming) primarily leads to:
Rework and late-stage failure
T/F: Dependencies are tasks that must happen before another task can proceed.
True
T/F: Adding 10-20% buffers for revisions and rendering is recommended.
True
The *ask* in a pitch refers to:
What you want approved/provided next (greenlight, assets, feedback, timeline)
The *key message* should be:
One sentence—the main takeaway for the client
During delivery and Q&A, a clear intro-body-conclusion and rehearsal primarily serve to:
Support comprehension, protect time for Q&A, and reduce filler
T/F: Rehearsal helps pacing and leaves time for Q&A.
True
T/F: Motion rules are unnecessary when multiple editors work on the same project.
False
T/F: Quality checks include legible text, stable tracking, clean edges, and consistent color.
True
T/F: Styleframes reduce revisions by aligning expectations before production
True