A Short has about two seconds to earn the next ten. Viewers swipe on instinct, so the opening line decides whether the rest of your work gets seen. Developers often start with context ("So, recently there was a security issue in…"), which is exactly what makes people swipe.
This lesson is the structure I use for every Short and Reel on my channel. It works for any technical story: a bug, an outage, a strange JavaScript result, a WordPress fix.
The five beatsLink to this section
A 30–50 second Short has room for five beats, in this order:
| Beat | Time | Job |
|---|---|---|
| Hook | 0–2 s | A surprising, true statement. The danger or the paradox, first. |
| Setup | 2–12 s | The minimum context to understand what happens next. |
| Turn | 12–30 s | How it actually happened; the "wait, what?" moment. |
| Lesson | 30–40 s | One thing the viewer can do or remember. |
| Call to action | last 3 s | Where to go next: the long video, or a question to answer in the comments. |
If a beat runs long, cut words, not beats. A Short without a lesson feels like gossip; one without a turn feels like a lecture.
Writing the hookLink to this section
A good hook is a claim the viewer can't ignore and can't verify yet. Some patterns that work for technical stories:
- Paradox: "Updating WordPress is supposed to keep you safe. This week, the update was the way in."
- Number plus consequence: "1.5 million keys. One missing setting."
- Impossible result: "true + true + true equals 3. JavaScript isn't broken."
- Countdown: "In nine seconds, an AI deleted a company's production data."
Two rules keep hooks honest. First, the hook must be true as stated; the turn adds nuance, it doesn't contradict. Second, the hook is spoken and shown, because many people watch with the sound off.
Don't fake the stakes. "Your site is hacked!" over a story about a vulnerability that requires a narrow race condition is a lie, even if it gets clicks. Viewers who feel tricked don't subscribe, and the comments will say so.
The script tableLink to this section
Write every Short as a table with four columns. It forces you to think about what's on screen every few seconds, not just what's said:
| Time | Voice-over | On-screen text | Visual |
|---|---|---|---|
| 0:00–0:02 | "Updating WordPress is supposed to keep you safe." | UPDATE = SAFE? | A finger over a glowing "Update Now" button |
| 0:02–0:05 | "This week, the update was the way in." | THE UPDATE WAS THE HACK | Click; the screen flashes red |
| 0:05–0:11 | "While WordPress updates, it unzips a full copy of itself into a folder anyone can reach on the web." | /wp-content/upgrade/ |
The camera dives into a server; a second copy of the site appears |
| … | … | … | … |
| 0:39–0:42 | "Why 'Update Now' alone isn't enough: full story on the channel." | FULL STORY ↗ | Logo frame, 1.5 seconds |
A new visual every three to five seconds keeps the eye busy. On-screen text should be three to five words, in big type, and never a full sentence of the voice-over.
Write for the earLink to this section
Read each line out loud. Short sentences, active verbs, one idea per line. Replace jargon with what it does: "a file that holds your database password" before "wp-config.php". You can show the technical name on screen while the voice explains it.
Captions are part of the scriptLink to this section
Burned-in captions (or one-word captions in a punchy style) matter because a large share of viewers keep the sound off. Keep caption contrast high; the contrast checker works for caption colours as well as web text. Keep captions out of the bottom and right edges, where YouTube and Instagram place their own buttons.
Titles and thumbnailsLink to this section
For Shorts, the title is what people see in search, on your channel page and in the Shorts shelf. For long videos, the title and thumbnail are the click.
- Under about 55 characters, so the full title shows on a phone.
- Put the number or the surprise first: "13,095 Attacks in a Day. The Bug? Updating."
- Include one searchable word people actually type: WordPress, JavaScript, Next.js, the product name.
- One or two emoji at most, and one to three hashtags. Stuffed hashtags with double spaces look like spam.
For thumbnails on long videos, use two to four huge words that add to the title instead of repeating it, one face showing emotion or one clear object, and strong contrast. Upload two or three versions to YouTube's thumbnail test and let real data choose.
The call to actionLink to this section
End with one clear next step, not three. On a Short, that's usually the long video ("full story on the channel") or a question that invites comments ("Is your site on 7.1.4 yet?"). Then pin a comment that repeats the question, and set the long video as the Short's related video so the link appears on screen.
Your website belongs in the long video's description, not in the Short: a viewer who watched three minutes is the one who might click "hire".
A Hindi (or second-language) versionLink to this section
If your audience speaks two languages, a translated Short can reach a different group of viewers for almost no extra work. Keep it the same script table with the voice-over column translated. Keep technical names in English where that's how people actually say them ("update", "database", "admin"), so it sounds natural.
Checklist before you recordLink to this section
- ☐ The hook is true as stated and appears as text in the first two seconds.
- ☐ Five beats are present: hook, setup, turn, lesson, call to action.
- ☐ Every number and name on screen is in
sources.md. - ☐ A new visual at least every five seconds.
- ☐ On-screen text is three to five words, high contrast, clear of the platform buttons.
- ☐ Title under about 55 characters, with the number or surprise first.
- ☐ One call to action, plus a pinned comment.
In lesson 3 you'll see how the same script table becomes a prompt for an AI-assisted workflow, and how the finished video shows up on your website automatically.
Frequently asked questionsLink to this section
Should Shorts be 15, 30 or 60 seconds?Link to this section
For a story with a lesson, 30–50 seconds is a good range: long enough for a turn, short enough to rewatch. Cut anything that doesn't move the story forward.
Do I need to show my face?Link to this section
No. Screen recordings, simple diagrams and illustrated scenes work well for technical stories. What matters is a strong hook, steady pace and a clear voice.
Can AI write the script for me?Link to this section
It can draft one quickly, and it's good at variations of hooks and titles. You still own the facts, the voice and the final cut; treat AI drafts like a junior colleague's pull request.
Test yourself
3 quick questions on this lesson.
Finished this lesson?
Mark it complete to track your progress through the learning paths.