Talking-head Video Production Checklist ({{year}})

Sync with CHANGELOG.md, GitHub Releases, the Jira release ticket, and your OpenAPI or SDK diff to capture what changed, breaking behavior, flags, and precise version numbers.

Decide whether the video targets backend API consumers, frontend SDK users, or DevOps plugin users so your examples, code, and terminology match their workflow.

Choose one KPI such as docs CTR, SDK upgrade rate, or trial signups, then generate a UTM-coded link to the canonical doc, migration guide, or GitHub repo.

Write the "what changed, why it matters, and payoff" in one sentence, ideally with a measurable benefit like fewer lines of code or lower latency.

Assign a reviewer to approve commands, SDK calls, parameter names, and version strings to prevent re-shoots from accuracy errors.

Prepare a seed repo, sandbox account, fixture data, and feature flags; lock dependency versions in a Docker image to make the demo deterministic.

Use a test tenant, scrub customer names, and generate throwaway tokens; plan redaction overlays for any unavoidably visible secrets.

Structure as Hook, Context, Demo, CTA with time boxes for each segment so the update remains crisp and actionable for busy engineers.

Include cURL requests, Postman examples, and one language SDK snippet with copy-paste verified commands and expected responses.

Avoid network flakiness with local mocks, fixture payloads, and cached responses; keep the scenario to the smallest viable happy path.

Plan lower thirds for feature names, parameter highlights, and before-after diffs so viewers can visually scan the change in seconds.

Use the exact API names, SDK symbols, and GA or beta labels from documentation to prevent confusion and support-driven churn.

Draft SRT or VTT captions and a short glossary for acronyms; keep terms consistent with docs to aid non-native speakers and search.

Lead with verbs and technical nouns, for example "Add webhook retriers in Node in 90s", and reserve space for SDK versions on the thumbnail.

Use an XLR mic with an interface, 48 kHz sample rate, set peaks near -10 dBFS and average around -18 dBFS; add a pop filter and disable processing during capture.

Add soft furnishings or portable acoustic panels; keep mic 4-6 inches away and slightly off-axis to reduce plosives and room reverb.

Record 4K 30 fps at 1/60 shutter, f/2.8-4, ISO 100-400 with manual white balance at 5600K; maintain consistent profiles across shoots.

Use a 3-point setup with a 2:1 key-fill ratio and a subtle hair light; match lights to 5600K and avoid harsh monitor reflections.

Use a tablet prompter at 130-150 wpm with short, breathable lines so your eyes stay near the lens without sounding scripted.

Record a 4K canvas at 1x UI scale, bump editor fonts to 18-22pt, use a high-contrast theme, and lock frame rate at 30 fps for readability.

Turn on Do Not Disturb, hide menu bar and dock clutter, disable notifications and auto updates, and use a sanitized demo user profile.

Start each take with a clap and verbal slate, then capture 10 seconds of silence to build a noise profile for post-production cleanup.

Capture Hook, Context, Demo, and CTA in separate chunks with 2-3 safety takes each so editors can swap lines without jumpy cuts.

Record the terminal, IDE, or Postman separately using scripted keystrokes and consistent cursor motion; drop markers at each milestone.

Prepare a toggle for mocked endpoints, cached JSON, or a pre-recorded terminal session to avoid reshoots when the API misbehaves.

Use a demo tenant with scoped keys, mask tokens in env files, blur sensitive UI, and rotate all credentials immediately after recording.

Name the feature exactly, state GA or beta status and version numbers, and speak at 140-160 wpm while minimizing internal jargon.

Share an unlisted rough cut with engineering and docs, asking for timestamped notes within 24 hours to catch regressions and naming issues.

Trim filler words, maintain a beat before code reveals, and zoom on changed flags or params so developers can grasp changes quickly.

Apply a neutral Rec.709 LUT and balance skin tones near 65-75 IRE while preserving high contrast for code blocks and terminal text.

Target -16 LUFS for YouTube and -14 LUFS for social, cap true peak at -1 dBTP, and apply light de-essing and 3:1 compression.

Use lower thirds for feature names, SDK versions, and CLI flags; add brief code diff pop-ins and a compact end-screen CTA to docs.

Archive a 4K ProRes master, deliver 1080p H.264 landscape, and create 1080x1920 vertical edits with safe-area captions for shorts.

Write titles with concrete tech nouns and verbs, add descriptions linking to docs, GitHub, and changelogs with UTM tags, and include timestamps.

Monitor CTR, average view duration, SDK upgrade telemetry, and doc dwell time; summarize insights for the next sprint and update docs.