Key takeaways
- First value is a route — not a slideshow before the route exists.
- Empty states teach when there is nothing to click yet. Write them like product copy, not placeholders.
- A tour is a patch. Fix the path, then measure activation on the action that matters.
Day-one users clicked through eleven coach marks and still could not send the first invoice.
The tour was polished. The empty dashboard was not. Tooltips pointed at buttons that stayed disabled because setup was incomplete — but the tour never said that. Activation flatlined. Support tickets asked the same question the slideshow skipped.
SaaS onboarding best practices are not "add a product tour." They are a first-value map, empty states that teach, and progressive disclosure that respects memory. If the tour is the only place the product explains itself, the product is not ready.
Draw the first-value map before you animate anything
Name the first value moment — the earliest action that makes someone say "this was worth it."
Examples:
- Send one invoice paid
- Publish one page live
- Invite one teammate who accepts
- Run one report with real data
Work backward in five steps maximum:
1. Land signed in 2. Minimum setup that unlocks the action — not all setup 3. The action itself 4. Confirmation they can trust 5. Obvious next step — not a menu of twelve
What to do after you launch is the go-to-market mirror: the promise on the site must match the first hour inside the product. SaaS is not dead argued the offer still has to be a tool someone finishes. Onboarding is where that promise survives or breaks.
Run the progressive disclosure test after the map
Use this once the map exists — notes series, after setup.
1. Skip test. Can a motivated user reach first value without the tour? If no, fix the UI — do not lengthen the slideshow. 2. Empty test. Open every screen with zero data. Does each empty state name the one action that fills it? 3. Return test. Come back seven days later without notes. Can you resume without replaying tips? 4. Measure test. Log completion of the first-value action — not tour completion. Tours lie; activation does not.
Fail the skip test and you do not have onboarding. You have a video manual blocking the product.
Empty states are the real onboarding
An empty state is a screen with no rows yet — projects, clients, campaigns, files. Most products waste it with "No data" and a grey icon.
Write empty states like product copy:
- Headline: the job this area will do when filled
- One action: verb that matches the first-value map
- Proof or sample: optional template, import, or demo row — labeled honestly
- Help link: short doc, not a generic knowledge base dump
Replace lorem with structured placeholders only when the layout needs shape — and label them as samples. Confusing sample data with production is how users delete the wrong row on day two.
Checklist templates beat blank screens: import a CSV, duplicate a starter project, connect one integration — each path should be one obvious control with helper copy that names the time cost honestly.
Tours are patches — use them sparingly
A coach-mark tour helps when:
- You shipped a redesign and need a one-time orientation
- A single new feature changes an existing muscle-memory path
- Legal requires a consent step before work begins
A tour fails when:
- It replaces missing labels
- It runs on every login
- It blocks the UI until dismissed
- It celebrates completion while the account is still empty
If you must ship a tour, tie it to one release, keep it under five steps, and never block the primary action behind "Next."
Marketing sites sometimes ship a tour on a logged-in app by mistake — copying a SaaS pattern without a first-value map. If your product is mostly read-only until someone fills a form, the empty form is the onboarding surface. Fix the form labels and defaults before you animate arrows.
Measure activation, not applause
Dashboards that track tour completion reward the wrong behavior. Track:
- Time to first value action
- Drop-off on the setup step that unlocks it
- Support tags that mention "getting started"
- Week-one retention correlated with first value — not with tour finish
- Cohort charts split by whether users imported data or skipped setup
Instrument those events before you debate animation. App development can wire the logging; web design can make the empty states readable. Neither fixes a map nobody wrote.
Instrument a setup completion funnel separately from login: account created, profile filled, first object created, first share or send. The step with the cliff is where copy and empty states need work — not another coach mark.
Nielsen Norman Group's onboarding research consistently shows that users skip guided tours when they can — and resent them when they cannot. Design for skip-first behavior.
What you can wire in-house — and when to hire the path
You can write the first-value map, rewrite empty states, and kill tours that fail the skip test. You can measure one activation event and stop optimizing slideshows.
What stays unfinished is the product path itself: setup flows that unblock the action, UI that labels itself, and an app prototype or full website where marketing and product tell the same story. That is cross-functional build work — not another tooltip layer.
CLICK.BLUE has shipped product and marketing surfaces since 2014 — more than fifty businesses, more than a hundred websites. If day one still needs a tour to explain the dashboard, get started with the map and the empty states first.
