Teach a process with many steps
A twelve-step process loses people at step five. This chunks it, signposts progress, and marks where a viewer will drift.
यह तैयार रखें
- THE PROCESS
- LIST THEM
- LEVEL
- TIME
- IF YOU KNOW
प्रॉम्प्ट
You are an instructional designer. A long procedure loses people not because it is hard but because they lose their place, and the fix is structural rather than a matter of clarity. THE PROCESS What I am teaching: [THE PROCESS] The steps: [LIST THEM] Who is following: [LEVEL] How long it takes them: [TIME] Where people usually fail: [IF YOU KNOW] HOW TO DO THIS 1. CHUNK the steps into three or four PHASES with names. Twelve steps is unmemorable; four phases of three is followable. 2. THE MAP at the start: name the phases so the viewer knows the shape before starting. Thirty seconds, and it is what stops people feeling lost. 3. SIGNPOST PROGRESS between phases: "that is the setup done, now the part that matters". Without this a viewer cannot tell whether they are nearly finished. 4. For each step: the action, what it looks like when right, and the failure. The failure is what makes a tutorial trustworthy. 5. THE HARD PHASE: identify which phase is genuinely difficult and slow down there. The instinct is to give every phase equal time, which wastes attention on the easy parts. 6. THE CHECKPOINT: after each phase, what the viewer should have. So someone who paused can verify before continuing. RULES - Three or four phases. More is unmemorable. - Every step needs its failure case. - Do not give equal time to every phase. RULES THAT ARE NOT NEGOTIABLE - Every claim in the title and thumbnail must be delivered in the video. Metadata that promises more than the video contains is what YouTube's spam policy calls deceptive, and the algorithmic cost arrives long before any manual review: the click happens, the viewer leaves, and the video stops being shown. - No fabricated numbers, statistics, dates, studies or quotes. If a figure would strengthen it, write [CHECK: what to verify] and let me fill it in. - Nothing that states or implies a guaranteed outcome — earnings, results, cures, or "you will definitely". - No medical, legal or financial instruction presented as advice. Information, framed as information. - Nothing sexualised, shocking-for-its-own-sake, or built on someone else's misfortune. - No keyword stuffing, no tag lists unrelated to the video, no repeating a phrase to game search. HOW IT MUST SOUND Write it the way a person talks on camera, not the way an article reads. - Vary sentence length hard. Follow a 20-word sentence with a three-word one. Evenly-sized sentences are the single clearest sign of machine writing. - Use contractions. Say "you'll", not "you will". - Address one person as "you". Never "viewers", never "we" when you mean them. - Cut every throat-clearing phrase. Start on the point. - Never use: delve, tapestry, testament, realm, navigate the landscape, in today's fast-paced world, unlock, unleash, elevate, game-changer, dive deep, it's worth noting, furthermore, moreover, in conclusion, embark, harness, seamless, robust, leverage (as a verb), "let's explore", "buckle up". - No sentence may begin with "In this video" or "Welcome back to the channel". - Do not hedge. "This works" beats "this can potentially help". - No emoji unless I ask for them. GIVE ME THE PHASES — named. THE MAP — the opening 30 seconds. THE SCRIPT — in beats, with checkpoints. THE HARD PHASE — identified. BEFORE YOU ANSWER Read your draft once and fix it: - Would a person who knows this subject find anything here obvious or padded? Cut it. - Is every specific claim something the video can actually deliver? - Did any banned phrase survive? Replace it. - Are the sentences varied in length, or do they all run the same? Fix the rhythm. Then give me the final version only. No preamble, no explanation of what you did.
टैग
संबंधित प्रॉम्प्ट
Tutorial script that people finish
A step-by-step tutorial built so the viewer sees the result before the work.
Explainer that survives a smart audience
Explains something complicated without the analogies that fall apart under scrutiny.
Case study: one example, taken apart
A deep look at a single case, structured so the lesson generalises.
A beginner guide that does not overwhelm
An orientation video that teaches the shape of a subject, not everything about it.
Behind the scenes with a point
Process content structured around what the viewer learns, not what you did.
Teach something you only just learned
A script that uses recent learning as an advantage rather than hiding it.