Plan, record and caption a short, focused screencast that learners can use when they need it.
Why it matters
Short videos let learners revisit a demo when they actually need it: the first time they hit a merge conflict on their own, three weeks after the workshop. They are also easy to make badly: twenty-minute recordings of a trainer clicking around, with no plan and unreadable text. A few research findings and production habits make a big difference.
What the research says about length and style
Philip Guo, Juho Kim and Rob Rubin (2014) analyzed about 6.9 million video-watching sessions on edX. Engagement dropped off sharply for longer videos; the median time people watched topped out around six minutes regardless of how long the video was. Their recommendations: keep videos short, plan them for online viewing rather than chopping up lecture recordings, and talk fairly quickly and with enthusiasm. Tablet-style drawing ("Khan-style") and a personal tone engaged viewers more than polished studio slides.
Mayer's principles apply too:
- Segmenting: one task per video. "Resolve a merge conflict" is one video; "everything about Git" is not.
- Signaling: zoom or highlight where the viewer should look.
- Coherence: no intro music, no long logo animation, no tangents.
- Personalization: a conversational "you" and "we" tone beats formal language.
Planning a 3-minute screencast
Plan before you hit record. A simple script table works:
| Time | On screen | Narration |
|---|---|---|
| 0:00–0:15 | Terminal with conflict message | "You ran git merge and Git says there's a conflict. Here's how to fix it in under two minutes." |
| 0:15–1:00 | Open the file, conflict markers visible, zoomed | "The lines between <<<<<<< and ======= are yours. The lines below, up to >>>>>>>, came from the other branch." |
| 1:00–1:45 | Edit to keep the right lines, delete markers | "Decide what the final code should be, then delete all three marker lines." |
| 1:45–2:30 | git add, git commit, tests pass | "Stage the file to tell Git it's resolved, then commit. Run the tests to be sure." |
| 2:30–3:00 | Recap card with three steps | "Find the markers, choose the code, add and commit." |
A plan like this keeps the video under three minutes and tells you exactly which windows to have ready.
Recording setup
- Clean the screen: close other apps, turn on do-not-disturb, hide bookmarks and personal tabs, use a fresh practice repository with no real company code or secrets.
- Make text readable: increase terminal and editor font size (often 18–24 pt), use a high-contrast theme, and record at a resolution that will look sharp when scaled down (for example, a 1920×1080 area).
- Audio matters more than video: viewers forgive average video but not poor sound. Use any headset or USB microphone, record in a small soft room, and do a 10-second test first.
- Free tools: OBS Studio (free, open source, all platforms), the built-in recorders in Windows (Snipping Tool or Xbox Game Bar), macOS (Shift-Command-5) and many video-call apps. Paid tools such as Camtasia add easy editing.
Recording and editing
- Record in short takes, one segment at a time; it is easier to redo 40 seconds than three minutes.
- Pause between steps so you have clean cut points.
- Do not over-edit. Removing long pauses and mistakes is enough; a natural voice is fine.
- If you make a real mistake that learners will also make, consider keeping it and showing the fix.
Accessibility
- Captions: auto-generate them (YouTube, Microsoft Stream and many tools can) and then correct them, especially commands and technical terms.
- Describe what you do, not just "click here": say "open the Source Control panel on the left".
- Provide the commands as text below the video so learners can copy them.
- Avoid flashing content.
Where videos fit
A video is a resource, not a lesson by itself. Pair it with a task: "Watch the 3-minute video, then resolve the conflict in practice repo 2." Link it from the place people need it, such as the team wiki page on merging.
Common mistakes
- Recording a full live session and calling it a video course.
- Unreadable font sizes.
- A long introduction before the useful part.
- Showing real credentials, customer data or internal URLs on screen.
- No captions, or uncorrected auto-captions full of garbled commands.
Quick recap
- Short, focused, conversational videos hold attention better.
- Script the video against the screen before recording.
- Readable text and clear audio matter most.
- Correct the captions and give commands as text.
Try it
On the Do tab, plan and record a 3-minute screencast of one task you know well.