Steps

Announce with a spotlight modal

Start with a centered modal announcing the new feature. Include a short headline, one sentence of value proposition, and a CTA to 'See how it works.' Use a visual (screenshot or icon) that previews the feature.

Navigate to the feature location

Highlight exactly where the new feature lives in your UI. If it is a new menu item, point to it. If it is an enhancement to an existing feature, show the exact button or section. Users should think 'Oh, that is where it is!'

Demonstrate the key benefit

Walk through ONE use case showing the feature in action. For example, 'Click here to enable auto-save. Now your work is saved every 30 seconds — no more lost changes.' Focus on the benefit, not the mechanics.

Variations

Subtle Hotspot Announcement

Instead of a modal, place a pulsing hotspot on the new feature. When users click it, show a 2-step tour explaining what is new. Less intrusive for minor updates.

Multi-Feature Release

For major releases with 3+ features, use a single announcement modal with a carousel of features, then trigger individual tours for each feature the user clicks on.

Implementation Guide

Time is critical for feature announcements. Build the tour before the feature ships so it goes live simultaneously. Target the tour to active users who have not yet used the new feature. Set frequency to 'once' — do not re-show to users who have dismissed it. For major features, combine the tour with an in-app banner and an email announcement. For minor improvements, the in-app tour alone is sufficient. Measure success by comparing feature adoption rates for announced features vs unannounced features. Well-announced features typically see 3x higher first-week adoption.

Frequently Asked Questions

Should I announce every feature update?

No. Reserve tours for features that materially impact the user experience. For bug fixes and minor tweaks, a changelog is sufficient. Over-announcing leads to announcement fatigue and users dismissing future tours.

When should the announcement tour trigger?

Trigger on the user's first session after the feature ships. Do not interrupt active workflows — wait for a natural break point like navigating to the dashboard or completing a task.

How do I handle users who skip the tour?

Add a persistent but subtle indicator (badge or dot) on the new feature so users can explore it later. Remove the indicator once they have used the feature at least once.

Ready to Build Better Product Tours?

Create interactive onboarding guides in minutes. No coding required.

Start Free Trial