The product tour is dead. Here's what replaced it.
Walk into any SaaS product built between 2014 and 2022 and you'll meet the same houseguest: a five-step tour that interrupts you the moment you sign in, pointing arrows at things you haven't asked about and didn't know you needed.
The tour exists because someone — usually someone senior — argued, correctly, that users don't know how to use the product. Then someone else — usually someone in design — built the obvious solution: show them. The tour is the fossil of an honest impulse.
It still doesn't work.
Why tours fail the people they're for
A new user has one job for the first 60 seconds: figure out whether the product does the thing they came to do. A tour answers a different question — "what does the product do in general?" — and answers it before the user has earned a reason to care.
So the tour gets dismissed. Sometimes it gets read, in which case it gets immediately forgotten, because forgetting is what brains do with information that arrived without context. By the time the user actually needs the tooltip-with-arrow that pointed at the export button, the tour is hours behind them.
Internal dashboards confirm this every time someone bothers to measure: tour completion rates above 30% are rare, and the correlation between completing the tour and activating is somewhere between weak and inverted. Users who complete the tour activate at similar rates to users who skip it — a strong signal that the tour is not the thing doing the work.
What replaced it
The replacement is so obvious it took ten years to ship: don't explain the product. Explain the next thing the user is about to do, in the moment they're about to do it.
A user hovers over the export button for the first time → a one-line tooltip says "exports as CSV; large reports run in the background." That's it. No tour. No arrow. No modal. Information arrives at the moment the user has a question, in a form small enough to consume in less time than re-reading the button.
This is contextual help, but the word "help" undersells it. It's not help. It's a property of the interface — the same way a button has a label, an interaction has a one-sentence explanation that appears only when needed and disappears the rest of the time.
The practical shift
If your team is sitting on a five-step tour today, the replacement is not a six-step tour. The replacement is:
- A list of the moments where users have been getting stuck. Build it from session recordings, support tickets, and a single Tuesday morning of watching new users use the product. Sort by frequency.
- A short prompt for each moment, written like a label, not like a coach. "Exports as CSV" beats "Click here to export your data!" by a wide margin. The first respects the user; the second performs.
- A trigger. When does this prompt fire? Not "on first login" — that's the tour. "On first hover," "on second visit to this page without taking the action," "after the user has looked at the empty state for more than 8 seconds." Triggers are the design.
- A retirement plan. Each prompt should disappear once the user has demonstrated they don't need it. A tooltip that fires on every hover after the first is an interruption, not a guide.
The teams that ship the best contextual help write the prompts the way good copy editors write captions: to the point, in the user's language, on the side of brevity. Not "Welcome to Reports! Here you can build, save, and share reports with your team." but "Reports save automatically." The first sentence is a tour. The second is a fact.
Why this is harder, not easier
Tours are easy to ship because they're a single artifact: one component, one schedule, one A/B test. Contextual prompts are harder because they're not a feature — they're a sustained editorial practice. Every product change adds a new "moment where users get stuck"; every shipped prompt has a half-life; every retired feature leaves an orphaned tooltip pointing at nothing.
The teams that do this well treat in-product copy the way good newsrooms treat headlines: as a job someone owns, every week, forever. The tour was easier because nobody had to own it past launch. That's also why it didn't work.