Your onboarding is your product.

Nobody ever fell in love on a second date that almost didn't happen.

First dates are brutal, efficient sorting machines. Research on speed dating shows that people form a judgement within the first four minutes. Not an impression. A judgement. The rest of the evening is mostly spent confirming what they already decided while the appetisers were arriving.

And here's the part that matters for anyone building a product: the people who fail on first dates almost always fail for the same reason. They spend the whole time talking about themselves.

Their job. Their hobbies. Their impressive marathon time. Their opinions on craft beer. They treat the date like a presentation. Forty-five minutes of "let me tell you about me" and then genuine surprise when there's no second date.

But your product's onboarding does the same thing. And it's just as unattractive.

Most onboarding flows are designed as introductions. "Welcome to our product. Here's what we do. Here's how it works. Here's a tour of the features. Here's a tooltip pointing at a button you'll never click. Now please fill out this form so we can personalise your experience, which really means so we can segment you for marketing emails."

I've sat in rooms where teams spent weeks designing these flows. Beautiful illustrations. Smooth animations. A friendly mascot who waves at you. Genuinely impressive craft, all in service of answering a question the user never asked.

But the user didn't open your product wondering "what does this do?" They opened it wondering "does this understand my problem?"

That's a fundamentally different question. But the gap between those two questions is where most products quietly die. Not with a dramatic failure. Not with a crash or an error message. With a shrug. A closed tab. A user who signed up, looked around for ninety seconds, felt nothing, and left.

I wrote recently about the shift from MVP to MVE, from minimum viable product to minimum viable experience. This is where that shift lives or dies. Not in your feature set. Not in your roadmap. In the first ninety seconds after someone gives you a chance.

At a SaaS company I worked with a few years ago, we had what the team proudly called a "comprehensive onboarding experience." Four screens of setup. A welcome video. A guided tour that walked you through every major feature before you could touch anything. The team had spent an entire quarter building it.

Our completion rate on the onboarding flow was 73%. The team celebrated.

But here's what they didn't celebrate: of the users who completed the full onboarding, fewer than 30% came back the next day. They'd sat through the entire presentation, nodded politely, and never returned.

We'd built the equivalent of a first date where one person delivers a TED talk about themselves for twenty minutes and then says, "So, should we do this again?" The other person smiles, says "definitely," and then blocks your number in the car park.

The onboarding wasn't broken. It was thorough. It was polished. It was entirely about us.

The turnaround, when it came, was almost embarrassingly simple.

A junior designer on the team, someone who'd been at the company for maybe four months, asked a question in a review meeting that nobody had thought to ask: "What if the first thing the user sees is their own data instead of our features?"

That's it. That was the whole insight.

Instead of opening with a tour, we opened with an import. Instead of showing users what the product could do, we showed them what the product could do with their stuff. The first screen after signup became a single prompt: bring in your existing work. No tour. No tooltips. No mascot.

The user's first experience went from "let us tell you about ourselves" to "we already know why you're here."

Retention after day one nearly doubled. Not because we'd added a feature. Because we'd subtracted everything between the user and the moment they felt the product understood their problem.

The best first dates are the ones where someone asks you a genuinely good question in the first two minutes. Not because asking questions is a technique. Because it signals something rare and specific: this person is paying attention to me, not performing for me.

I've spent twenty years designing products across startups and enterprises, and in almost every case, the pattern is the same. The teams that obsess over their onboarding as a feature tour are solving for comprehensiveness. The teams that obsess over the first moment of recognition are solving for retention.

Comprehensiveness feels responsible. It feels like good product management. You're being thorough. You're educating the user. You're reducing support tickets.

But thoroughness is not the same as care. Showing someone every room in the house is not the same as making them feel welcome at the door.

The metric that actually predicts whether someone stays is not "did they complete the onboarding?" It's something much simpler and much harder to measure: did they feel, within ninety seconds, that this product was built for someone like them?

I've started calling this the recognition moment. The point where a user stops evaluating and starts using. Where the internal question shifts from "what is this?" to "oh, this is for me." Everything before that moment is friction. Everything after it is momentum.

Most products never reach it. But not because they're bad products. Because they buried the recognition moment under a welcome video and a four-step setup wizard.

The teams getting this right are not building better onboarding. They're eliminating the distance between signup and recognition. They're asking: what's the fastest path to showing this user that we understand why they're here? And then they're cutting everything that sits between the user and that moment.

Sometimes that means showing real data on the first screen instead of sample data. Sometimes it means asking one smart question instead of ten. Sometimes it means doing less on purpose so the user can feel more on arrival.

It's the same instinct that makes a great first date great. Not the performance. Not the rehearsed stories. The moment where someone makes you feel like they actually showed up to meet you, not just to be seen.

Your onboarding is not an introduction to your product.

It's your product's first answer to the only question that matters: do you understand why I'm here?