Help Video

Origin & evolution

Screencast tutorials🧑‍🏫TutorialCustomer EducationA step-by-step tutorialView reference → are nearly as old as consumer software, but they became a standard support channel once screen-recording tools and cheap video hosting made them quick to produce. The case for video rests on a simple observation👁️ObservationUser ResearchA specific behaviour or statement observedView reference →: some tasks☑️TaskProduct SpecificationA unit of work within a story or epicView reference → are easier to watch than to read, because seeing the cursor move through a real interface removes the ambiguity that prose leaves behind.

The cost structure🧮Cost StructureBusiness ModelA cost category or structureView reference → cuts the other way. A written article can be edited in a minute when a button moves; a video has to be re-recorded, re-narrated, and re-uploaded. That maintenance burden is why mature help centres pair the two, using video for the show-don't-tell moments and written articles for anything that changes often or needs🫀NeedUserA user need, pain, desire, or constraintView reference → to be searched, skimmed, and translated. The discipline is matching the medium to how volatile and how scannable the content is.

How it works in practice

A team finds that 40 percent of new users abandon setup at the integration step. A written guide already exists, but the drop-off persists. They record a 90-second help video walking through the exact screens, and embed it on the setup page and in the onboarding email. Completion at that step climbs from 60 to 82 percent over the next month. Then the integration UI is redesigned, the video silently goes out of date, and support tickets🆘Support TicketCustomer SuccessCustomer support request or issueView reference → referencing "the video doesn't match my screen" appear within a fortnight. The win was real; so was the maintenance bill that came due.

Help video vs. its neighbours

• Tutorial is a structured, often multi-step learning path🥾Learning PathCustomer EducationA structured learning pathView reference → that can be text, video, or interactive. A help video is one short clip, typically scoped to a single task rather than a curriculum.
• Walkthrough🚶WalkthroughCustomer EducationA guided product walkthroughView reference → runs inside the product, guiding a user through the live interface with tooltips and prompts. A help video sits outside the product as passive media the user watches, then returns to the app to imitate.
• Knowledge base article📓Knowledge Base ArticleContent & KnowledgeA knowledge base articleView reference → is the written, searchable counterpart. It is cheaper to keep current and easier to index; the video earns its place only where demonstration genuinely beats text.

In the graph

In the Unified Product Graph, a help video sits in the education region with three connections: an education_program🏫Education ProgramCustomer EducationA customer education programView reference → presents it (education_program_demonstrates_via_help_videoEducation Programdemonstrates viaHelp Videohierarchy), it documents a specific screen🖥️ScreenExperience DesignA distinct screen or view in the productView reference → (help_video_documents_screenHelp VideodocumentsScreencross-domain), and a marketplace_listing🛒Marketplace ListingPartners & EcosystemA marketplace listingView reference → can reference it (marketplace_listing_references_help_videoMarketplace ListingreferencesHelp Videocross-domain). The edge to a screen is the one that earns its keep: because the video is linked to the exact interface it captured, a change to that screen flags every video that documented it, turning the staleness problem from a surprise in the support queue into a tracked dependency⛓️DependencyTeam & OrganisationA cross-team or system dependencyView reference →.