Your Onboarding Reveals Whether the Job Is Real

There are two kinds of onboarding.

One is a hallway with doors. The user shows up already wanting something. They already feel the job. They already have the pressure. They just need you to point to the right door and get out of the way.

The other is a timeshare presentation. The user shows up curious, uncommitted, and only vaguely bothered by the problem. So onboarding has to do the heavy lifting: explain the category, persuade them the job matters, reassure them this isn't a waste of time, and gently drag them toward a moment that might create belief.

Look at what your onboarding actually spends its time doing. If it's mostly helping users reach an outcome, you have a hallway. If it's mostly explaining why the outcome matters, you have a timeshare. And if your onboarding reads like a timeshare presentation, the fix probably isn't another tooltip.

It's job intensity.

Because time-to-first-value isn't just a UX metric. It's a job intensity signal. It tells you whether users arrived with pull already present — or whether your product has to manufacture pull from scratch.

The Job Intensity Signal You Need To Read

People love to say "we have a conversion problem" and then spend six months rebuilding onboarding. Sometimes onboarding really is broken — confusing, slow, or risky. Fixing that is real work.

But there's another scenario that looks identical in the metrics and feels identical in the meetings: your onboarding is doing too much explaining because your users aren't arriving with a job that feels urgent enough.

When the job is intense, onboarding is a bridge — a short path between the user's existing motivation and the product's outcome. When the job is weak, onboarding becomes a persuasion engine.

This is what makes onboarding a diagnostic. When the job is intense, users arrive already leaning forward. They don't want a tour. They don't want a manifesto about your mission. They want to get to the outcome that's been nagging them all day.

In that world, onboarding has one job: connect intention to outcome quickly, safely, and without making the user do extra thinking.

What Hallway Onboarding Looks Like: Expensify

Expensify — the expense management app founded in 2009 by David Barrett — serves a job that spikes to maximum intensity at a specific, recurring moment: you just got back from a business trip and you have a pile of receipts that need to become an expense report before the deadline.

That moment has real pressure. The receipts are crumpled in your bag. The finance team is waiting. The reimbursement won't happen until the report is submitted. Nobody wants to do this. Everyone needs to do it.

The onboarding is the outcome. Open the app, tap the camera icon, take a photo of a receipt. SmartScan extracts the merchant, date, amount, and currency. The expense is created, categorized, and added to a report. The user's first meaningful unit of progress — one receipt processed — happens in under thirty seconds.

No tour. No feature walkthrough. No "here's what Expensify can do for you." The user arrived with the job already burning. The product met them at that moment and delivered relief before the motivation could fade.

That's hallway onboarding. The user doesn't need to be convinced the job matters. They need the door to be opened.

What Timeshare Onboarding Looks Like

Now flip it. If users aren't arriving under pressure, they show up in a completely different posture. "I heard about this." "I'm browsing." "This might be useful."

Those aren't bad users. They're just not at the switching threshold. So onboarding starts trying to do something it was never designed to do: create urgency.

That's where you get the classic symptoms. Long "here's why we exist" intros. Feature marketing inside the product. Excessive examples meant to inspire. Over-explaining the category. "Education" that's really persuasion.

You can almost hear the anxiety in the design: please don't leave before you understand why this matters.

If you're in this situation, you can tighten onboarding until it squeaks and still not get the conversion you want. The underlying force balance hasn't changed. The user isn't failing to understand your product. The user is correctly deciding the job isn't intense enough to justify the time, effort, risk, or habit change required to commit.

The Litmus Test

There's a clean way to read your own onboarding as a job intensity diagnostic: Does your onboarding spend more time telling users why the product is valuable — or helping them experience that value?

If it's mostly explanation, you're not designing a path to first value. You're designing a narrative to cover the lack of pull.

One caveat: some categories genuinely require education. If you're introducing a new mental model, or your product is a platform with multiple jobs, some orientation is necessary.

But necessary education behaves differently than persuasion. Necessary education says "here's the one thing you need to know to succeed" and "here's the safe next step." Persuasion says "let us tell you why you should care" and "here are twelve use cases you didn't ask for."

One builds confidence. The other tries to build desire. Only one reliably produces repeat hiring.

What Your Onboarding Is Really Measuring

If the job is intense, users will forgive ugly. They'll push through friction. They'll tolerate imperfections. They'll do setup work. They'll come back. If the job is low intensity, they won't.

Low-intensity jobs require a product that feels effortless and instant, because the user's willingness to invest is near zero. High-intensity jobs give you more room — but only if you protect trust and don't create new anxiety along the way.

This is why onboarding is such a reliable job intensity diagnostic. It reveals whether users are arriving with motivation already in motion, or whether you're trying to ignite motivation in a cold room.

What to Do If Your Onboarding Is a Timeshare Presentation

You can absolutely improve onboarding flows. You should. Bad onboarding can bury real pull. But if you're doing all that and the product still feels like it needs to argue for its own existence, stop polishing the argument and go find the force.

Find the segment where the status quo is no longer tolerable. Find the moment where the user is already in motion — the Expensify moment, where receipts are piling up and the deadline is real. Find the version of the job where failure has consequences.

Then build onboarding that meets that person at that moment and gets them to relief fast.

The only onboarding that consistently converts is onboarding that rides an existing pull. You can't lecture someone into urgency. You can only meet someone who already has it.