Maybe LabsMaybe Labs
← All posts
Guide·2 min read

Knowledge Base Videos: Add Demonstrations Without Hiding the Answer

Maybe LabsBy the Maybe Labs team

Knowledge base videos demonstrate a task inside a support article. They work best as a companion to a searchable written answer, not as a barrier someone must watch through to find one setting. The page should explain the task, the prerequisites, and the result even when playback is unavailable.

Decide whether a video adds information

A changing sequence, a difficult interaction, or a visual comparison may benefit from a demonstration. A single menu location may need only a screenshot and a sentence. Choose video when it reduces the user’s interpretation work, not because every article should contain media.

Consider the cost of keeping it current. A frequently changing interface may require a narrowly framed clip rather than a long tour. The smaller demonstration can be replaced without redoing unrelated instructions.

Structure the support page around the answer

Page elementPurposeCommon failure
Task summaryConfirm that the user found the right answerA promotional introduction delays the solution
PrerequisitesExplain access and starting conditionsMissing permissions look like user error
Written stepsMake the procedure searchable and scannableThe only instructions are inside the video
DemonstrationClarify sequence or visual behaviorA long overview replaces the specific task
Verification and exceptionsHelp the user confirm success or recoverThe clip ends before showing the result

A fictional permissions article

Suppose customers ask how to share a report with a colleague. The article should explain the available access choices and any role requirements in text. The video can show the control, the selection, and the recipient’s resulting access in a safe demo environment.

The most useful moment may be the verification step. Showing only the sender clicking “Share” leaves the user uncertain about whether the permission took effect. Demonstrate the result without exposing private account information.

Make updates traceable

Record the interface version, asset source, content owner, and trigger for review. A trigger might be a permission-model change or a renamed control rather than a calendar date alone. Connect the article to the relevant product area so release owners can find it when behavior changes.

If the video becomes inaccurate, remove or replace it while keeping the useful written answer available. A stale video can undermine an otherwise current article because viewers may trust the moving demonstration over the text.

Give readers playback choices

Use clear controls and avoid unexpected sound. Supply corrected captions and a descriptive transcript where needed. Place the alternative near the video so users do not have to search elsewhere for equivalent information.

W3C’s transcript guidance distinguishes a basic audio transcript from one that also describes important visuals. For a UI procedure, the latter may be more useful because control changes and resulting states often carry essential meaning.

Measure resolution, not just plays

A play can mean the user needed help, not that the help worked. Look at task success, relevant feedback, repeat support contacts, and whether the article answers the stated question. Interpret those signals with the product context attached.

Ask support agents what they still need to explain after sending the article. Their answer can reveal the missing step more clearly than a generic satisfaction score.

Use the tutorial-video guide to produce the demonstration and the video content audit to maintain the library. For a help center, the best media makes the answer easier to use and easier to keep accurate.

Make your next launch in motion

Bring a brief, brand assets, and product captures. Review the story, visuals, and exported video before publishing. Request free private-beta access.

Get early access →

Keep reading