The one idea
Most of a video's quality is fixed before the camera is on.
Not most of the work — editing takes longer. Most of the outcome. A clear script recorded on a phone beats a vague script recorded on good equipment, every time, and it is not close.
Better gear improves a good plan by a few percent. It cannot rescue a bad one.
Write what you are going to say and in what order. That decides whether it works. Everything else is polish.
Objective, audience, one message, script, hook, shot list. Recording is execution of a plan, not exploration.
Pre-production determines structure, pacing and coverage. Post-production can tighten and reorder but cannot supply material that was never captured.
The order of decisions
| Stage | Decision | Skipping it costs |
|---|---|---|
| Idea | What is this about | A video with no point |
| Audience | Who is watching and what they know | Wrong level, wrong assumptions |
| Objective | What they should do or understand after | No way to tell if it worked |
| Script | The actual words, in order | Rambling, six takes |
| Hook | The first ten seconds | Nobody sees the rest |
| Storyboard | What is on screen at each moment | Talking head over nothing |
| Shot list | Every shot you need | Discovering a missing shot in editing |
| Sound | Mic, room, levels | Unwatchable, regardless of picture |
| Captions | Text of what is said | Excluding viewers and losing silent watchers |
| Thumbnail and title | What makes someone click | Good video, no audience |
The order matters. Each row depends on the ones above it. People start at "storyboard" or "shot list" because those feel like film-making, and then find the script contradicts them.
The script is 80% of it
A script is not a word-for-word recital. It is the decision about what you say and in what order. Some people write every word; others write a tight structure of beats. Either works. Neither is optional.
What a script fixes:
- The order. Most first drafts bury the point in the middle. Written down, you can see this and move it.
- The length. You will find that your five-minute idea is a ninety-second idea with three minutes of throat-clearing.
- The redundancy. Written down, you notice you make the same point twice.
- The number of takes. Knowing the next sentence is what stops the "so, um".
A two-minute product explainer. First draft: what the company does, then the problem, then the feature, then the benefit. Watched back, viewers leave in the first fifteen seconds — during the part about the company.
Reordered: the problem, in one sentence, first. Then the feature. Then the benefit. The company at the end, if at all. Same words, same recording quality, completely different retention. The edit was reordering a document, not re-shooting.
The hook
The first ten seconds decide whether the other ten minutes exist.
A hook is not a gimmick. It is the promise: why this is worth watching, stated immediately. Three that work:
- The problem, sharply. "Your Excel dates are showing as numbers and sorting wrong. Here is why, and the fix."
- The surprising claim. "Most of the time you spend formatting spreadsheets is spent undoing autocorrect."
- The result up front. "By the end of this you will have a working booking form. Here it is."
What does not work: introducing yourself, explaining what the video will cover, asking people to subscribe, or a long animated logo. All of these spend the only attention you are guaranteed on something the viewer did not come for.
Try this
Here is an opening. Rewrite it as a hook.
"Hi everyone, welcome back to the channel. Today we're going to be talking about something really important, which is how to handle version control in your projects. But before we get into that, let me quickly introduce myself..."
Storyboard and shot list
A storyboard is what is on screen at each moment. It does not need to be drawn well — boxes with words are fine. What it prevents is four minutes of a face talking over nothing while describing something visual.
A shot list is every distinct shot you need, so you capture them all in one session. Discovering in editing that you needed one more angle means setting everything up again.
B-roll is the supporting footage that plays over your narration: hands typing, the screen, the object being described. It does two jobs. It shows what you are describing, and it hides your edits — cutting from a talking head to a talking head is visible, cutting to B-roll is not.
Planning a short explainer
1 of 7Write the objective as a sentence about the viewer.
"After this, they can set up two browser profiles and know why they would want to." Not "explain browser profiles". The first is testable, the second is a topic.
Your challenge
Level 3 · IndependentPlan a two-minute video that teaches one thing you already know well. Do not record it.
Produce: the objective as a sentence about the viewer, the one message, three supporting points, a full script, a hook of no more than fifteen words, and a two-column storyboard where every section has something in the right column.
You have succeeded when someone else could take your plan and record the video without asking you a question. If they would have to ask, the plan is incomplete — and that gap is exactly what causes a fourth take.
What people usually get wrong
- Recording before writing. Six takes of an unplanned video is slower than twenty minutes of writing and one take.
- Introducing yourself first. Nobody has decided to care yet. Earn it, then introduce.
- Ignoring sound. The most common fatal flaw, and the cheapest to fix.
- No B-roll. A talking head for four minutes has nothing for the eye to do.
- Auto-captions left uncorrected. They break on precisely the words that matter.
- Explaining what the video will cover. Just do the thing. The overview is spent attention.
- One long take. Record in sections. A mistake costs you one section, not the whole video.
How someone experienced does it
Experienced video makers write the ending first. Knowing exactly where you are going makes every earlier decision easier, and it stops the video from meandering toward a conclusion the maker had not yet found.
They also record the same line three times in a row deliberately, then pick the best in editing. It costs twenty seconds during the shoot and eliminates the "that was almost right" re-shoot entirely.
And they watch their own videos with the sound off, and then with the picture off. Sound off tells you whether the visuals carry anything or are just a face. Picture off tells you whether the words stand alone. Most amateur video fails one of those two tests badly, and neither test costs anything to run.
When not to use this
Video is the wrong format when:
- The content is reference material. People need to scan, search and copy from instructions. A written page beats a video for anything someone will return to.
- It is dense with numbers or names. Viewers cannot pause and re-read comfortably. Write it.
- A screenshot would do. A thirty-second video of one setting is slower for the viewer than one annotated image.
- You are avoiding writing. Video does not remove the need to think clearly. It hides the lack of it for about ninety seconds.
Prove it
Make one two-minute video from a written plan. Then show the plan and the video to someone and ask two things: at what second did their attention drop, and could they state your one message afterwards.
If they cannot state the message, the script was the problem — which is the lesson, and it is much cheaper to learn on a two-minute video than a twenty.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned planning and scripting a short video. Assume I am intelligent but relatively new to this — treat me as intermediate level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood planning and scripting a short video. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at planning video before recording it — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.