Cheap Production That Looks Fine: Record With What You Have

Thursday, 14:10, at Redbrook Engineering. Owen, four months on the desk, has brought Farah a list: a camera, a lamp on a stand, a desk microphone, an editing package. He also wants "a few days to get up to speed with it", all before the first video. Farah asks what the first video is. "Connecting a laptop to the meeting-room screen. We get it every week." She asks him to record it now, on his own laptop, with the screen recorder that is already on it. She asks him to film the cable end with the phone in his pocket. He is back at 14:40 with a seventy-second clip that starts on the laptop's display settings and ends on the room's screen lighting up. It looks fine. It looks, in fact, exactly like a video made by someone who knew what they were doing, which is the only thing "professional" has ever meant.

Cheap production is making a how-to video or photograph with equipment you already own, in a way that looks competent because nothing in it draws attention to itself. "Looks fine" is the target. "Looks professional" is a target that produces a budget request, a procurement cycle and no videos. The things that make a help video look amateurish all cost nothing to leave out. These are a shaky cursor, a cluttered screen, a notification sliding in, music, a logo animation. This article is part of our Visual & Video Guides series. It is about pressing the record button well.

It covers what you already have and why it is enough, then setting the screen up before you press record. Next come recording the window rather than the monitor, a steady, slow cursor, and sound, meaning narration or silence and never music. Then come filming a physical thing with the phone, where the file lives, which is beside the article, and naming the file. A short war story and the production checklist to copy finish the article, in that order.

What You Already Have Is Enough

Every workstation already has a way to record its own screen, either built into the operating system or inside the meeting tool. The meeting tool can record a shared screen with narration as readily as it records a meeting. Every phone records video and takes photographs good enough to show a lever. The headset you take calls on is a microphone that already sits the right distance from your mouth. That is the full kit. The equipment list for a usable how-to video is the equipment list for an ordinary Tuesday.

What makes a video look good is stillness and clarity, not gear. A still frame with large readable text and one cursor moving slowly to one place looks assured. The same content shot with a camera on a stand, lit by a lamp and edited with transitions looks like a corporate training film. That is a thing people have learned to stop watching. The reader does not notice production quality when it is adequate; they notice it only when it fails, and it fails in ways that are free to prevent. The table below is the whole inventory, with the one setting on each that is worth checking.

Buy something only when a specific recording has failed for lack of it, and you can name the failure. A microphone is justified when the headset's audio, tested and listened back, is genuinely unusable. A stand is justified when the phone propped on a mug keeps falling over. Nothing is justified in advance of the first video, because the first video is where you find out what, if anything, is missing. Usually it is nothing. Occasionally it is a mug.

Set the Screen Up Before You Press Record

The recording is only as clean as the screen was when you started, and cleaning the screen afterwards is editing, which this series avoids. Before the take: close every window except the one being shown. Turn on do-not-disturb so no message, calendar reminder or update prompt slides into the corner at the wrong moment. Clear the desktop of files if any of it will appear. Hide the bookmarks bar in the browser, and close every tab but one. Use the default theme and colours, because the reader's screen uses them. A dark theme in the video and a light theme on their machine makes every control look like it has moved.

Use a test account. A screen recorded from your own account has your name in the corner and your mail in the background. It has your open tickets in another tab, and whatever the last customer wrote in the search history. A test account has none of that, and it has the same permissions the reader will have, so the menus match. The things that must never appear in anything the public can see, names, addresses, ticket subjects, internal hostnames, are the subject of What Must Never Be in the User Document. A video is a user document that shows the whole screen, so the list applies to every frame.

Make the text big. The video will be watched at a third of the width it was recorded at, often on a phone. Text that is comfortable on a large monitor becomes unreadable there. Raise the display scaling or the application's zoom until the text looks slightly too large to you; that is the right size for the reader. Then put the screen into the start state from the script sheet, the exact view the reader sees before the first action, and only then press record. The start state is not "the desktop". It is the first frame the reader needs.

Record the Window, Not the Monitor

A whole widescreen monitor, shrunk to fit a video player, turns the dialog that matters into a postage stamp in one corner with acres of empty desktop around it. Record the application window, or a region drawn around the part of the screen the task uses, and the dialog fills the frame. Most screen recorders offer the choice; the meeting tool's shared-window option does the same thing. If the only option is the full screen, shrink the window to a modest size in the middle of the screen. Make it the only thing visible, and accept that the reader will see some desktop.

Choose the region before recording rather than cropping after, because cropping afterwards costs an editor and a second pass. The region you choose also settles the text size argument at the same time. A window recorded at a sensible size, with the zoom raised, is readable on a phone without anyone doing anything else. A full monitor cropped afterwards is readable only if someone spends twenty minutes making it so. The twenty minutes are the reason the video never gets re-recorded when the screen changes.

Keep the window still. Do not resize it, move it or switch to another application during the take. If the task genuinely crosses two applications, that is usually two tasks and two clips, or a region large enough to hold both. The frame the reader is looking at should be the frame the reader has in front of them. A window that lurches across the screen is a window the reader cannot map onto their own.

A Steady, Slow Cursor

The cursor is the pointer, and everything it does is an instruction. Move it in a straight line from where it is to the control. Pause for a beat so the reader sees where it stopped. Click once, and pause again so the reader sees what happened. That rhythm, move, pause, click, pause, is the whole technique, and it is slower than the pace you use when nobody is watching. Record at the pace of someone following along on a second device, which is roughly half your normal speed.

Do not circle. Waving the cursor around a button to draw attention to it does the opposite. The eye follows the motion, not the target, and the reader sees a blur where the button is. One straight movement and a stop points at a thing. A cursor that circles a button three times before clicking it is not emphasis; it is a cursor that has lost its nerve. Likewise avoid dragging the cursor along text as you read it aloud, which turns the narration into a karaoke and hides the text behind the pointer.

Keep the cursor at the system default size, or one notch larger if the recording will be watched on phones. Switch off any effect the recorder offers beyond a small, plain click indicator. A quiet circle that appears for a moment on each click is helpful, because the reader otherwise cannot tell a click from a pause. A large coloured blob that pulses on every click, a trail, or a spotlight that darkens the rest of the screen is decoration. Decoration ages a video faster than anything except music.

Type at reading pace, and say what you type as you type it. For anything long, a path or an address, paste it from the script sheet rather than typing. Say where the reader gets it from: "Paste the server address from the article below." The reader cannot copy from the video, and the text steps beneath it are where the address lives. So the video's job is to show which field it goes in, not to display each character.

Sound: Narration or Silence, Never Music

Narration comes from the headset, in a room with the door shut, with the microphone the same distance from your mouth for the whole take. Record ten seconds, listen back, and fix what you hear: a fan, a keyboard, a corridor, a hum from the monitor, a mouth too close so that every p pops. Then record the take speaking at the volume you would use to a colleague across a desk. Use the sentences from the script, one per action, with the beat of silence after each. The narration guidance itself, which words and in which tense, is in The Ninety-Second Video. This section is about the microphone.

Silence is acceptable when the video has captions. Some technicians dislike recording their own voice, some rooms are never quiet, and some tasks are so visual that a caption under each action does the whole job. A silent clip with captions reaches the reader with the sound off exactly as well as a narrated one, and it reaches the reader who cannot hear better. What is not acceptable is a clip that is silent and uncaptioned, because that is footage of a cursor moving about with no account of why. The caption and transcript side is in Accessibility: The Reader Who Cannot Watch.

Music is never acceptable. It adds nothing to an instruction. It is loud in an open-plan office, where most people will play the clip. It fights the narration and distracts from the captions. It dates the video the moment the tune falls out of fashion, which is sooner than the screen changes. It may not be licensed for the use. And it signals, to a reader who is stuck and in a hurry, that this is the kind of video with a logo at the front and a slow build. So they stop watching before the first action. A help video with a soundtrack is a help video that has forgotten who it is for.

Filming a Physical Thing With the Phone

A physical task, a cable, a lever, a button on a panel, is filmed with the phone's camera, and the technique is four habits. Hold the phone landscape, so the picture is the shape of the screen it will be watched on. Prop it rather than hold it, against a stack of books, a mug or a monitor base, because a held phone shakes and a propped one does not. Put the light behind the phone, not behind the object. A desk lamp pointed at the ceiling above the camera fills the shot evenly. A window behind the printer turns the printer into a silhouette. And wipe the lens, which has been in a pocket all day and is why phone pictures look foggy.

Frame the device and the hands, and nothing else. A plain surface under the object, no desk clutter at the edges, no name badges, no screens in the background with mail on them, no colleagues. Before recording, move the phone until the frame holds only what the reader needs to see. Zooming while recording produces a lurch and a loss of sharpness, and cropping afterwards is editing. If the detail is small, the lever under the lid, move the phone closer. Tap the screen on the lever so the camera focuses there and not on the lid.

For photographs, take one per position, as described in When a Picture Beats a Page of Steps, and take three of each to keep one. For a clip, keep it under fifteen seconds: a second of stillness, the hands do the thing slowly, a second of stillness, stop. The slowness matters more than on screen, because hands are faster than cursors and the reader needs to see which finger went where. If the clip is to be narrated, record the narration on the phone at the same time, with the room quiet, or add captions afterwards from the script. Do not film the phone's own screen with another phone unless there is truly no other way. A screen recording of the phone, which every phone can make, is sharper and smaller.

Where the File Lives: Beside the Article

The video and the photographs live beside the article in the knowledge base, attached to it or embedded in it. That way, finding the article is finding the media and the two are published, found and retired together. Not on a shared drive, where the folder is a secret known to the person who made it. Not in a chat channel, where it is three screens up by Friday and gone by the following month. Not in a personal folder, which leaves the organisation when the technician does. And not attached to an e-mail, which reached the people on that day's list and nobody who joins next quarter.

Where the knowledge base genuinely cannot hold media, the fallback is one shared folder, named for the knowledge base. Use one sub-folder per article carrying the article's exact title. Link to the clip from the article's text. The important property is that there is exactly one place, that it is named after the article, and that a stranger could find the clip from the article without asking anyone. Two places is no places, because nobody will check both when the screen changes. If you run QuerySolv, the article itself is either visible to agents only or to everyone. Anything kept beside it is reached through the article. So the question of who may see the clip is answered once, by the article, and not again for every file.

Keep the script sheet beside the article too, because it is the source. The raw recording is not worth keeping after the trimmed clip is published; it will never be re-edited, because the rule is to re-record instead. The sheet, by contrast, is what gets changed when the vendor moves a button, and the next clip, the next captions and the next text steps all come out of it. A folder containing a clip and no sheet is a clip that will be re-recorded from scratch, by someone who has to work out the steps again.

Naming the File

Name the file for the task, in the same words as the article's title, in lower case with hyphens, followed by a version number. For example: "connect-laptop-to-meeting-room-screen-v1", then v2 when it is re-recorded. The task words are so that a search in the folder, or in the knowledge base's attachment list, finds it from the same words the reader used. The version number is so that when a re-recording is made, the old and new clips cannot be confused. The article's link is updated to the new one deliberately rather than by overwriting a file that something else may still point at.

Use a version number, not a date. A date says when the clip was made, which nobody needs. A version says which clip the article currently points at, which everyone needs. It survives the question "is v3 the current one?" with a glance at the article. Photographs follow the same pattern with the step added: "label-printer-reload-step3-lever-v1". Everything about how versions are tracked, and when the number goes up, belongs to Keeping Media Current When Screens Change, which owns the register. Here the rule is only that the number is in the file name from the first version. The first version is the one nobody expects to replace.

Never name a file "final", "new", "latest" or "use this one". Every folder I have ever inherited has contained "final-v2-NEW" and a colleague who could not say which of the three was current. Naming is cheap at the moment of saving and impossible to fix six months later from memory. A clip with the task in its name is the only kind that gets found when the person who recorded it has moved on.

A Short War Story: The Production Budget at Northgate Retail

At Northgate Retail, the desk lead, Callum, won a budget after a presentation on "professional training content". It covered a camera on a stand, two lights, a desk microphone, an editing package and one day a week for a technician to learn it. Four months later the desk had produced three videos, each with an animated title, a music bed and a logo at the end, averaging six minutes. None of them was about the till receipt printer, which was the thing the stores actually rang about. In the same four months, Jess, the manager at the Harbor Street store, filmed a forty-second clip on her phone of her own hands reseating the receipt roll. The phone was propped against the till. The clip had no sound. She sent the clip to the other store managers in a chat message. Within a week every store had it. Within a month the receipt-roll calls to the desk had gone from most days to most months. The desk found the clip only when a new manager asked where "the till video" was and nobody could find it in the chat history. Callum attached Jess's clip to the till article in the knowledge base, with six text steps under it, and returned the lights. The lesson, which he put in the budget report, was that the budget had bought everything except videos. The one video that worked had cost a mug to lean the phone on.

The Production Checklist

Run the checklist before, during and after every recording, screen or phone, until it is habit. Then keep running it, because habit is exactly what lets the notification slide in. It is one page and joke-free. The "after" section is where the private detail in the corner gets caught, and it is the section most often skipped by people who are pleased with their take.

PRODUCTION CHECKLIST — SCREEN OR PHONE, ONE PAGE
Task: _________________________________   Article: ______________________________
Script sheet in hand, read aloud once:  [ ]      Audience: [ ] everyone  [ ] technicians

BEFORE (screen)
  [ ] test account, same permissions as the reader
  [ ] every other window closed; one browser tab; bookmarks bar hidden
  [ ] do-not-disturb on; update prompts dismissed
  [ ] default theme; text zoom raised until slightly too large
  [ ] recorder set to one window or a drawn region, not the whole monitor
  [ ] click indicator small and plain; no trail, spotlight or zoom effects
  [ ] headset on; ten-second test recorded and listened back; room door shut
  [ ] screen in the start state from the script sheet

BEFORE (phone)
  [ ] landscape; propped, not held; lens wiped
  [ ] light behind the phone; nothing bright behind the object
  [ ] frame holds the device and the hands only; plain surface; no badges, screens or people
  [ ] focus tapped on the detail that matters; no zooming during the take

DURING
  [ ] move, pause, click, pause; straight lines; no circling
  [ ] one sentence per action, naming the control as the screen names it; or silence with captions
  [ ] long values pasted, with "from the article below" said aloud
  [ ] window never moved or resized
  [ ] any fumble: stop, reset to the start state, go again from the top
  [ ] no music, at any point, for any reason

AFTER
  [ ] head and tail trimmed; nothing else cut except the middle of a long wait
  [ ] watched once at phone width; text readable; cursor visible
  [ ] every frame checked for names, addresses, ticket numbers, hostnames, mail
  [ ] file named task-words-vN; photographs named task-stepN-position-vN
  [ ] stored beside the article; script sheet stored with it
  [ ] text steps pasted under the clip; captions or transcript attached
  [ ] media register updated with the article, the file, the version and the owner
Recorded by: ____________   Checked by: ____________   Date checked: ____________

Owen's seventy-second clip is still the one attached to the meeting-room article at Redbrook, now at v2 after the room's screen was replaced. It was re-recorded in half an hour from the same sheet. The camera, the lamp and the microphone were never bought, which Farah mentions at budget time every year, gently. The weekly ticket about the meeting room has become a monthly one, raised by visitors, who are sent the clip and do not ring again.

Frequently Asked Questions