So your product just shipped a new feature, and now your walkthroughs are out of date—again. If you’re using Arcade, updating those guides shouldn’t eat your entire afternoon, but let’s be honest: the “it’s easy!” marketing doesn’t always match real life. This guide is for anyone who needs to keep product tours current without losing their mind (or blowing up the rest of their roadmap).
Let’s get your walkthroughs fixed up fast, with as little busywork as possible. Here’s what works, what’s a waste of time, and how to avoid common headaches.
1. Figure Out What Actually Changed
Before you even log in to Arcade, know what you’re dealing with. Not every feature release breaks your walkthroughs. Sometimes the change is minor enough that your existing tours still make sense.
Checklist: - Did the UI layout change? (New buttons, moved menus, updated colors, etc.) - Did the workflow change? (Steps added, removed, or reordered?) - Are there new “must-see” features worth highlighting? - Any terminology changes in the interface or onboarding?
Pro tip:
Don’t assume every walkthrough needs an update. If you’re only adding a tiny feature tucked away in settings, most users won’t notice if your main tour skips it for a few days.
2. Audit Your Existing Walkthroughs
Now, in Arcade, check which walkthroughs are affected. If you have a bunch, don’t panic.
- List all public or embedded walkthroughs: These are the ones customers see.
- Prioritize: Update the highest-traffic or most critical ones first. Internal enablement tours can usually wait.
- Check analytics: If Arcade’s analytics show a walkthrough isn’t getting much use, it’s probably not urgent.
What not to do:
Don’t waste time updating old drafts or internal demos unless you need them. Stick to what’s live and customer-facing.
3. Prep Your New Feature
You’ll need a stable, accessible build with the new feature. Don’t try to record a walkthrough if your staging environment’s half-broken.
- Use a reliable environment: Production is best—unless the feature’s not live yet.
- Get test data ready: Set up accounts or data so the walkthrough looks real. Nothing kills credibility like empty states or placeholder text.
- Close distractions: Hide browser tabs, notifications, and anything else that’ll make your walkthrough look messy.
Pro tip:
If you’re demoing user-specific features (e.g., admin-only options), make sure you’re logged in as the right role.
4. Open Your Walkthrough in Arcade’s Editor
Arcade lets you update specific steps instead of starting over. Here’s how to do it without breaking what already works:
- Navigate to your walkthrough: In Arcade, open the tour you want to update.
- Use “Replace Step” or “Insert Step”: If just one screen changes, swap out that step. If a new feature adds a step, insert it where it fits.
- Edit text and callouts: Update captions, arrows, and highlights so they match the new UI and don’t point to the wrong place.
- Trim dead steps: Delete anything obsolete—old buttons, retired features, etc.
What works:
Arcade’s “replace step” is genuinely useful for small changes. You don’t need to redo everything.
What to ignore:
Don’t bother with fancy transitions or effects unless they actually help users. Focus on clarity.
5. Redo Screenshots or Recordings (When Necessary)
If the feature changes big chunks of the UI, you’ll need fresh captures.
- Re-record only what’s changed: No need to redo the whole walkthrough unless the flow is unrecognizable.
- Keep file sizes reasonable: Too many high-res captures slow things down for users and can cause loading issues.
- Check for branding: If you’ve updated logos or colors, make sure the walkthrough matches. Inconsistencies look sloppy.
Honest take:
Arcade’s recording tools are solid, but sometimes the browser extension glitches. If you’re having trouble, try restarting your browser or switching to a different one. Don’t bang your head against it for an hour.
6. Preview and Test
Before you hit publish, double-check everything.
- Run through the walkthrough as a new user: Make sure instructions make sense and match the current UI.
- Check for typos or outdated references: “Click the blue button” isn’t helpful if the button’s now green.
- Test embedded versions: If your Arcade is embedded in your app or help docs, preview it there too. Sometimes layouts break in unexpected ways.
What to ignore:
Don’t stress about perfect polish at this stage. Just make sure nothing’s obviously broken.
7. Publish and Replace Embeds
Once you’re happy, publish the updated walkthrough.
- Update embed codes if needed: Most Arcade updates are live, but if you created a new walkthrough, swap out old embed codes in your docs, website, or help center.
- Announce the update: Slack your team, ping support, or drop a note in release notes so everyone knows the walkthrough’s current.
Pro tip:
Keep a simple changelog—just a bullet list in a doc—so you can track what walkthroughs were updated, when, and why. It helps next time something changes.
8. Set a Reminder to Review Again
Product keeps moving. Set a reminder—monthly or after every big release—to quickly audit walkthroughs. It’s way easier to fix small things regularly than to let walkthroughs rot for months.
What works:
A simple recurring calendar event works just as well as any fancy content management workflow. Don’t overthink it.
Real Talk: What to Skip
You’ll see a lot of advice about making every walkthrough “delightful” and “immersive.” That’s fine if you have unlimited time. In reality:
- Don’t re-record just because a font changed.
- Don’t obsess over minor UI tweaks nobody cares about.
- Don’t try to highlight every single new feature. Focus on what users actually need to know.
- Don’t panic if it’s not pixel-perfect. Most users just want to solve their problem and move on.
Summary: Keep It Simple, Iterate Often
Updating product walkthroughs in Arcade doesn’t have to be a nightmare. Know what changed, fix only what matters, and ignore the rest. The key is to update often, in small batches—you’ll save yourself a lot of pain. Don’t chase perfection, just keep things useful and up to date. If you’re not sure whether something needs updating, it probably doesn’t.
Now go ship your walkthrough updates and get back to building cool stuff.