Resources/12 min read
Best video production practices
The guidelines and techniques behind technical video that developers finish, and that signals the professionalism they expect from a tool.
- Production
- Quality
- Technical
01
Why production quality matters here
Developers are unusually sensitive to production quality, because it is a proxy for how seriously you take everything else. A badly lit, badly mixed video about your API says something about your API.
02
Core production principles
- 01
Pre-production planning
The work that decides whether the shoot is a day or a week.
- Detailed scripts and storyboards
- Technical demonstrations prepared and rehearsed in advance
- A clearly defined learning objective per video
- 02
Audio quality first
Audio matters more than video. People will abandon a beautiful picture over bad sound, and they will forgive a soft picture with clean sound.
- A real microphone (lavalier or shotgun)
- An acoustically treated room, not a glass meeting box
- Compression and EQ, not just a normalise pass
- 03
Lighting and visual clarity
The face should be readable and the screen should be legible. That is the whole brief.
- Three-point lighting for presenters
- High-resolution screen recordings
- Nothing distracting in frame
- 04
Pacing and structure
A clear opening, digestible segments, and space between concepts.
- Open with a concise introduction
- Break complex topics into segments
- Leave visual breathing room between ideas
03
How long it should be
Product demos
2–4 min
Key features, in context.
Tutorials
5–10 min
Step-by-step instruction.
Thought leadership
8–15 min
In-depth exploration.
04
Technical excellence on screen
- 01
Code clarity
Syntax highlighting, font sizes that survive a phone screen, zooms onto the line that matters, and annotations that point at it.
- 02
Screen recording
Professional capture at 60fps for smooth motion, with cursor highlighting so people can follow what you clicked.
- 03
Visual explanation
Animation and diagrams for the concepts that do not exist on screen: architecture, data flow, timing.
- 04
Technical accuracy
Developers lose trust the moment they spot an inaccuracy or an outdated approach. Have an engineer review before publication.
05
Do and don't
Do
- Use consistent branding throughout the series
- Invest in lighting and audio before cameras
- Caption everything, for accessibility and for silent viewing
- Test every demo before you record it
- Keep a visual style guide
Don't
- Rush the technical explanation
- Shoot code demos on a poor webcam
- Record in a noisy or echoey room
- Leave the mistakes and the long pauses in
- Ship low-resolution screen recordings
06
The kit
Audio
- Blue Yeti USB
- Rode Wireless Go II
- Audio-Technica ATR2100x-USB
Video
- Sony ZV-1 or ZV-E10
- Logitech Brio 4K
- Elgato Facecam
Lighting
- Elgato Key Light
- Neewer LED panel kit
- Lume Cube video kit