# Update help videos after a product change Source: https://www.ngram.com/docs/update-help-videos-after-ui-changes Published: 2026-11-03T00:00:00Z Updated: 2026-11-03T00:00:00Z Audit help center videos after a product update. Prioritize instructions that now lead to the wrong action, choose the smallest accurate revision and test the original embed. Edit and export Find the videos that send customers to the wrong place and check the corrected cut. [Open ngram](https://www.ngram.com/app) [All docs](https://www.ngram.com/docs) ## Read before this Read these direct prerequisites in order. Each guide lists any earlier context it assumes. 1. [1 Revise a generated video Give useful feedback with examples, chat, frame targeting, and direct editing.](https://www.ngram.com/docs/revising-a-video) ## When to use this guide Use this if you maintain a Help Center and a release moved a control shown in several videos. Suppose invoices moved from Settings to Account. Some videos send customers to the wrong menu, while others only show an old icon. Gather the affected article URLs, the existing videos and access to the current billing view. ## Step 1. Find the articles that send viewers to the old screen Read the written article alongside the video. A correct narration can sit beside an obsolete screenshot, or a current picture can sit beside instructions that name the old menu. Mark the time and the exact sentence that require attention. A billing menu moved from Settings to Account. A tutorial that merely mentions billing in its introduction may still work. A video whose opening instruction says “Choose Billing under Settings” now sends a customer to the wrong place. A third tutorial shows an old icon but the same visible label and destination. Those three videos deserve different priority even though all three appeared in the same keyword search. Start with a task inventory rather than a list of filenames. For each article, record the viewer's starting role, first click, changed label, time of the affected scene and destination. Attempt the task from the published help page using a clean account. Mark whether a viewer is blocked, sent on a detour or merely seeing an older visual. Update the blocked instructions first. ## Step 2. Rank each mismatch by what it prevents Update first when the old video directs the customer to a control that no longer exists, selects the wrong option or shows an obsolete result. Update next when the task still works but a changed label makes the action hard to locate. If the product changed a color and the action remains obvious, the video may still be accurate. A designer sees an old icon and wants the entire tutorial rerecorded. Support sees customers completing the task and would leave it alone. Test the actual path with someone unfamiliar with the interface. If the distinct old icon sends the viewer to the wrong control, change the affected scene. If the label and route still work, track the visual refresh for the next substantive edit. A product owner may call a changed permission “just copy.” Try the lesson using the audience's role. A missing permission can make the first step impossible and warrants higher priority than an old visual detail. Put the prerequisite before playback and update the recorded path if the audience changed. ## Step 3. Capture the route that works in the current product For the highest-priority lesson, capture the new navigation and the screen that proves the action succeeded. Reuse the accurate remainder if the transition makes sense. If the new role or workflow changes the audience entirely, create a separate lesson or revise the article's prerequisites. A cosmetic patch cannot fix instructions written for a different user. When the billing menu really has moved, give ngram Studio the updated article and the billing URL. Ask it to show the route from the dashboard to the invoice. Use [Browser Handoff](https://www.ngram.com/docs/browser-handoff) to sign in to a demo account if asked. Compare the first click and the final invoice screen with the revised article before replacing the clip. For the invoice example, start at the dashboard and record the current route through Account. Stop on the invoice list. Compare those two screens with the written article before you replace the older billing clip. ## Step 4. Choose which viewers should receive the updated cut For a shared feature rollout, a replacement in the existing hosted upload is useful when everyone should see the revised procedure. For two product editions that require different directions, keep separate videos and identify which audience each serves. Otherwise, updating one embed could silently give the wrong instructions to a customer still on the earlier path. Use the [help center video workflow](https://www.ngram.com/use-cases/help-center-video) to keep the tutorial tied to its source article. Use [the revision guide](https://www.ngram.com/docs/revising-a-video) when the original editable project can supply a corrected scene. ## Step 5. Test the revised clip where customers watch it Open every affected article, play from just before the changed step and check the onscreen action against the written instruction. Check copied files separately: a file uploaded directly into another platform has a different source from the hosted embed. Review chapter timestamps if the new cut changes the timing. Finally, test links into the middle of a recording. A correction at the front of the video can move the relevant chapter while leaving every button visually correct. Fix the incoming article link or timestamp as well as the cut. Refresh the same help article and play through the changed step after switching the video version. Check the text, screenshots, chapter timestamps and any links into the middle of the recording. A new video beside a paragraph that still sends people to Settings leaves the article internally inconsistent. ## Step 6. Record the result for the next release Record the article URL, video identity, checked time and result for the next release. The [sharing and publishing guide](https://www.ngram.com/docs/sharing-and-publishing) helps distinguish the watch link, embed and downloaded file when tracing a stale copy. Save one line in the maintenance record: article URL, task, verified new instruction, version, owner and date. The next UI change can begin from that inventory instead of hunting through every project with a similar title. Ask support whether tickets still mention the old label. That real-world wording can reveal another article or downloaded copy the initial search missed. ## References and next steps - [Revise a video](https://www.ngram.com/docs/revising-a-video) — change the scene that failed your review. - [Sharing and publishing](https://www.ngram.com/docs/sharing-and-publishing) — choose how viewers will receive the finished video. - [Help Center videos](https://www.ngram.com/use-cases/help-center-video) — plan a lesson to sit beside a written support article. ## Continue in ngram Open the workspace and put this guide into practice with your own project. [Open ngram](https://www.ngram.com/app)