Isaac Donnelson
Founder of Krest. Building onboarding that gets every user to the moment that makes them stay.
Writing
When to ask onboarding questions
Ask onboarding questions when the answer changes the next control in the sequence. Day one is for the fork that picks invite, map, or ship. It is not a survey dump. If the answer only fills a profile, park it until after they stay, or until a later path needs a new fork. Timing is the decision. Field lists live on a different page.
Read more → HonestyWhy one-size onboarding fails
One-size onboarding fails because a single product tour, checklist, and email written for an average persona cannot be the first hour for two people who need different first work. Finishing that script is a false win. The fail is the published sequence, not the people who skip it. An enterprise lead from a competitor and a manager of a team of 10 can share the stay and still refuse the same first control.
Read more → ActivationHow to use empty states in onboarding
You use empty states in onboarding by treating the blank screen as the next control on the path to aha, not as a dead end. Name the first object this segment must create, put that create action on the empty canvas, and point a short product tour or checklist box at it. An empty project, board, or list is the room where first work starts. A polite "nothing here yet" with no button is a skip they earned.
Read more → PersonalizationHow to segment users for onboarding
You segment users for onboarding by naming two audiences that cannot share a first hour, mapping form answers into those audiences, then publishing a different product tour and checklist to each. A segment is a path you run, not a persona slide. Start with an enterprise lead from a competitor and a manager of a team of 10. Add a third audience only when you have a third hour.
Read more → ActivationWhen should a product tour wait?
A product tour should wait until the next control is on the page and the form answers that choose that control already exist. Fire it on empty settings and you taught them to skip. Fire it before they told you the job and you shipped one script to two first hours. Wait for the room and the answers. Then point at the one control that unlocks the next win.
Read more → HonestyWhy onboarding tooltips fail
Onboarding tooltips fail when they cover every control instead of pointing at the next work on a product tour or checklist, not because the widget is weak. One tooltip is a guidance step when it points at the control that produces the named aha. A tooltip on every button is help chrome, not onboarding. The fail is coverage. Keep the one pointer. Delete the forest.
Read more → HonestyHow to review an AI onboarding draft
You review an AI onboarding draft by opening it as two segments, signing the named aha, and keeping dual-save off new users until a person publishes. Read the product tour, checklist, and email as one path. Reject a step that could have been written for any product. AI drafts. You ship. The review is the publish gate, not a courtesy pass.
Read more → PersonalizationWhat is a SaaS welcome screen?
A SaaS welcome screen is the first in-app form after signup that picks the product tour, checklist, and email for this person, not a brand splash. A logo, a slogan, and a Continue button do not choose a path. Role, goal, size, and prior tool do. If every new user lands on the same first hour after they click through, you shipped a greeting, not a welcome screen.
Read more → ActivationWhat is in-app guidance?
In-app guidance is a product tour stop, checklist box, or tooltip that points at the next control on the way to a named aha, not a library of overlays. One step earns a place when it unlocks first work this segment can finish. A drawer of help chrome that covers every button is not guidance. It is a museum. Measure the stay, not whether they opened the overlay.
Read more → HonestyWhy new users skip onboarding lessons
New users skip onboarding lessons because they signed up to reach a named aha, not to sit through a curriculum of your chrome. A product tour or checklist written as a lesson asks them to learn the product before they do the first work that makes them stay. The skip is the correct response. Teach after the stay exists. Do not open with a class.
Read more → HonestyHow to replace hardcoded onboarding
You replace hardcoded onboarding by moving the first-hour product tour, checklist, and email out of the app bundle into an editor a human still publishes. Engineering keeps the session. Product owns the sequence. Dual-save keeps the draft off new users until someone ships. A rewrite that still ships one script to every signup only moved the same tour into a prettier file.
Read more → PersonalizationWhy personalize user onboarding?
You personalize user onboarding because one product tour, checklist, and email cannot be two first hours. An enterprise lead from a competitor and a manager of a team of 10 can share the stay and still need different first work. A first name in a tooltip is not the reason. The reason is matching: the next step has to change when the person changes, or they skip.
Read more → ActivationWhat user onboarding metrics should you track?
Track three user onboarding metrics: whether a named segment reached the named aha, how long that took from signup, and which product tour or checklist step they dropped. Tour completion, checklist completion, and email open rate stay as diagnostics on those steps. They do not replace the stay. If you only measure finished chrome, you optimize the tour while the aha never happens.
Read more → PersonalizationHow to personalize onboarding by role
You personalize onboarding by role by asking role on the form, then running a different product tour, checklist, and email for each role that cannot share a first hour. Role is a fork. A job title you store and ignore is a survey. An enterprise lead from a competitor and a manager of a team of 10 can share an aha and still need two sequences.
Read more → HonestyHow to write onboarding copy first
You write onboarding copy first by naming the aha in one sentence, then writing the product tour, checklist, and email as lines that only exist to produce that sentence. Open the builder after those lines exist. A tour written before the sentence is chrome looking for a job. The copy is the path. The widgets are how it shows up.
Read more → ActivationHow to onboard users with email
You onboard users with email by sending the same next step the in-app product tour and checklist already named, using the form answers that chose that path. Email is the surface they return to, not a second onboarding program. If the inbox asks for a different action than the tour, you split the first hour. Write one next step. Put it in both places.
Read more → PersonalizationWhat is contextual onboarding?
Contextual onboarding is a product tour, checklist, and email that change because of product state and form answers, not a tooltip on every click. Product state is the screen they are on and the objects already true in the session. Form answers are who they already told you they are. A hotspot that fires on every control is help chrome. If the next step does not change when the screen or the answers change, the onboarding is not contextual.
Read more → ActivationHow to reduce time to value?
You reduce time to value by cutting every onboarding step that does not produce the named aha, not by speeding up a longer product tour. Name the stay moment. Keep the fewest form fields, checklist boxes, and tour stops that walk that segment there. Delete the rest. Compressing chrome leaves the same empty product, just sooner.
Read more → ActivationWhat is in-app onboarding?
In-app onboarding is the product tour, checklist, and tooltip that run inside the product as steps on one sequence to a named aha. It is not a second program from the welcome email. If the in-app path and the email disagree on the next step, you have two onboarding programs. Users skip both.
Read more → HonestyHow to build user onboarding without developers?
You build user onboarding without developers by composing a sequence in a no-code editor, then publishing it yourself. A snippet in the product is a one-time install. After that, a PM ships a checklist and a product tour without a ticket. No-code is the surface. A human still owns live. AI drafts. You ship.
Read more → HonestyWhat is no-code user onboarding?
No-code user onboarding is an editor that lets a product team compose a product tour, checklist, and email without waiting on an engineering ticket. The builder is the surface. The product is still a sequence a human publishes. A no-code tool that ships live paths without review is not no-code honesty. It is unsupervised onboarding with a friendlier canvas.
Read more → ActivationWhat is product-led onboarding?
Product-led onboarding is a sequence per segment built from product context, not a single happy path shown to every signup. You name the aha in one sentence, qualify once, and compose the shortest first hour for an enterprise lead from a competitor or a manager of a team of 10. A one-size tour is product-led marketing language. It is not product-led onboarding.
Read more → PersonalizationWhat is user segmentation?
A user-onboarding segment is a named audience you can operate: who they are plus what they already told the form. It is not a persona slide. It is not a filter on every trait. The product tour, checklist, and email for that audience change because those answers sit on a real group, not because you labeled a spreadsheet. If you cannot name the audience in a standup, you do not have a segment.
Read more → HonestyHow to automate user onboarding
You automate user onboarding by letting AI draft the sequence from product context and form answers, then dual-save so a human still publishes. Models fill structured steps: form, checklist, tour, email. Publish, policy, and taste stay human. Unsupervised live paths ship noise with your logo. The locked rule is AI drafts. You ship.
Read more → ActivationWhat is an onboarding checklist?
An onboarding checklist is one step on the path from signup to the moment a user stays. It lists the next finishable wins for a named segment. It is not the product. It is not a tour of every control. It is not a completion score. If every box can be checked and leaving still feels cheap, the checklist was inventory, not onboarding.
Read more → PersonalizationWhat is personalized onboarding?
Personalized onboarding is a user onboarding path that runs a different product tour, checklist, and email because of product context and form answers. It is not a first name in a tooltip. It is not one static tour shown to every segment. If the next step stays the same when the answers change, the onboarding is not personalized. It is a greeting.
Read more → ActivationWhat is time to value?
User onboarding time to value is the elapsed time from signup to the named aha, the first experience that makes a user stay. It is not the time to finish a product tour, a checklist, or a welcome sequence. If you measure tour completion instead of the moment, you optimize chrome while the stay never happens.
Read more → PersonalizationWhat is product context in onboarding?
User onboarding uses product context when the path cites what you sell, learned from the product itself, not a first name in a tooltip. Form answers say who they are. Product context says which features, USPs, and aha the sequence is allowed to cite. Together they compose a path that could only exist for that pairing. If the copy could sit in any tool in your category, you do not have product context. You have a greeting.
Read more → ActivationWhat is SaaS user onboarding?
SaaS user onboarding is a product decision plus a path, not a welcome modal. You name the first win a new software user must reach, then compose the shortest sequence that gets each segment there. A splash, a chrome tour, and a generic drip are setup. They are not SaaS onboarding. If leaving still feels cheap after they finished the modal, you shipped a greeting, not the first hour of the product.
Read more → PersonalizationWhat should a qualification form ask?
A user onboarding survey should ask only what changes the first path. Role, goal, company size, and what they used before are enough to pick a sequence. Everything else is a survey they skip. A qualification form is a fork, not a clipboard. If an answer cannot change a step, it does not belong on day one.
Read more → ActivationWhat is user onboarding?
User onboarding is the path from signup to the first experience that makes a person stay. It is not a product tour, and it is not a welcome email. It is a named aha, a way to know who they are, and a short sequence that gets that segment there on purpose. If they can finish the chrome and still leave cheaply, you shipped a walkthrough, not onboarding.
Read more → HonestyShould AI run user onboarding unsupervised?
AI should draft user onboarding, not run it unsupervised. Models are good at turning your product, ICPs, and a user's answers into a structured sequence. They are bad at owning publish, policy, and taste. Dual-save keeps draft and live apart so nothing reaches a new user until you say so.
Read more → ActivationWhat is an aha moment in SaaS?
An aha moment is the first experience that makes a user stay. It is not a tooltip and it is not a completed product tour. It is a product decision you name in one sentence before you compose any onboarding path. If you cannot say the moment, every checklist and email is decoration around a hole.
Read more → ActivationWhy users skip product tours
Users skip a product tour when the steps ignore role, goal, and why they came. A static tour is one script shown to every new user in the same order. Coverage of controls is the usual success metric, not the moment they stay. The matching failure is the point. The walkthrough was written for a persona who is not in the session.
Read more →