What Curiosity Looks Like in a First Session, and Why Most Products Design Past It

Most products treat the first session as a funnel. Get the user oriented, push them through onboarding, and move them toward the action that registers as a conversion. The logic makes sense on paper, and it completely misreads what a person is actually experiencing when they open something new for the first time.

There is a window, somewhere in those first few minutes, where a user is neither committed nor gone. They are genuinely curious. They are exploring the edges of a new thing, deciding whether it feels worth their attention. That state is fragile, and it is specific. Curiosity asks to be met with just enough to keep the thread alive, and most products respond by either overwhelming people with information or rushing them toward a goal they have not yet decided they want.

Designing for curiosity in a first session means understanding it as a psychological state with its own needs, its own triggers, and its own way of collapsing when handled clumsily. It is not a personality type or a demographic. It is something that happens inside a person for a short period of time, and the product either works with it or works against it.

The first session is a fragile window of curiosity, and most products design straight past it.

The products that understand this tend to feel different from the first moment. They do not feel like they are in a hurry. They feel like they have thought about who is on the other end of the screen.

The Feel Factor Arc and Where Curiosity Sits

At WAA, we think about the emotional journey through a product using what we call the Feel Factor Arc. It maps the emotional states a user moves through from the moment they decide to try something, all the way through to loyalty or abandonment. Curiosity sits near the beginning of that arc, and it is one of the most under-designed states in most products.

Before curiosity, there is usually anticipation, the feeling a person carries into a product based on what they have seen or heard about it. After curiosity, there is either orientation anxiety if things do not become clear fast enough, or a sense of reward when the product delivers something that feels worth the effort. Curiosity is the bridge between those two states, and it needs careful handling.

What curiosity needs is partial revelation. Not full disclosure, and not a closed door. It needs the sense that there is more to find, that the product has depth worth exploring, and that the next step will be rewarding rather than exhausting. That is a subtle design brief, and it is easy to get wrong in either direction.

Products that dump everything in a first session kill curiosity by removing the sense of discovery. Products that tell users almost nothing kill it by making the effort of exploration feel pointless. The productive space sits between those two failure modes, and finding it requires understanding what the user is actually feeling when they arrive.

Why Efficiency Is the Wrong Goal in a First Session

Efficiency is the dominant design value in most digital products, and in many contexts it is exactly right. A returning user who knows what they want and just needs to do the task should face no unnecessary friction. But a first session is not that context, and treating it as one creates a product that feels cold to the people it most needs to warm up.

When someone opens a product for the first time, they are simultaneously assessing its quality, trying to understand what it does, working out what will be asked of them, and figuring out roughly how long any of this will take. Those assessments happen on both conscious and subconscious levels at the same time. An efficient funnel does not give any of that space to breathe. It just pushes.

The user who feels pushed in a first session is not experiencing efficiency. They are experiencing a product that does not seem interested in them. That feeling is hard to recover from, and it tends to show up in the data as early drop-off that teams misread as a UX flow problem when really it is an emotional design problem.

Curiosity is slower than efficiency. It involves a little wandering, a little testing of edges, a moment of pleasant surprise when something behaves in an interesting way. Designing for it means accepting that the first session is not a conversion moment. It is a relationship moment, and relationships take a beat longer than funnels.

What Curiosity Actually Looks Like as a Design State

Curiosity as a psychological state has a few consistent signatures. People in it move slightly more slowly than they would in a task-focused state. They pause at things that catch their eye. They make small exploratory taps or clicks that are not strictly necessary. They are looking for feedback, checking whether the product responds to them in interesting ways. They are, in short, sniffing around.

A person in a genuine curiosity state is giving the product a kind of provisional trust. They have not decided to commit, but they have decided to look. The worst thing a product can do in that moment is demand something back before it has offered anything of value. Forcing registration, requiring permissions, or launching an aggressive onboarding checklist all carry the same subtext, which is that the product needs something from the user before the user has established that the product is worth anything to them.

Curiosity gives a product provisional trust, and most onboarding flows spend it immediately.

What sustains a curiosity state is reward at low cost. A small animation that responds to a tap. A piece of content that is more interesting than expected. A navigation pattern that reveals something useful without requiring the user to dig for it. These are the micro-moments that tell a curious person they are in the right place and that more discovery will pay off.

Map your first session against a simple question: at which points does the product offer something to the user before asking for something back? If the ratio is reversed early on, curiosity is being spent rather than fed.

The design challenge is building that reward in without making the product feel like it is performing for the user. Curiosity is undermined by obviousness. If a user can see that the product is trying hard to delight them, the spell breaks. The best curious-state design feels effortless from the user's side, even when it has been thought about very carefully.

The Hospitality Booking App: A Tale of Two First Sessions

Think about two versions of a hospitality booking app, both with identical inventory and identical pricing. The first version opens to a search bar, a date picker, and a prompt to create an account. It is efficient. It is also immediately demanding, because before the user has had a chance to understand what kind of experience this product offers, it is asking them to narrow their search and commit their data.

The second version opens to a curated set of properties that tell a small story about the kind of travel the app caters to. There is a subtle scroll that reveals more. Tapping a property does not immediately launch a booking flow but instead shows the kind of visual and contextual detail that makes a place feel real. The account prompt comes later, after the user has spent three or four minutes inside the experience and has some sense of what they might be booking.

Both apps could convert, but the second builds a user who arrives at the booking step already emotionally invested in what they are about to do. That investment changes the character of the decision. The user is not completing a transaction, they are following through on something they have already started to want.

Consider delaying your primary call to action until a user has had at least one moment of genuine discovery. The commitment that follows an interesting experience is qualitatively different from a commitment made under early pressure.

The first version optimises for the action, while the second optimises for the state that makes the action feel natural. Over time, those two approaches produce very different retention and satisfaction numbers, even if early conversion looks similar.

Designing Triggers, Not Just Pathways

Most UX design focuses on pathways: the routes a user takes through a product to reach a goal. Pathways matter, but in a first session they are not the whole picture. What a curious user needs alongside clear pathways are triggers, small design moments that generate the feeling that there is something worth finding.

A trigger is not the same as a tooltip or a feature highlight. Those are information delivery mechanisms. A trigger is something that makes a person lean forward slightly. It could be an unexpected animation, a piece of copy that breaks the pattern of what they expected to read, a visual element that rewards a second look, or a transition between screens that feels more considered than they anticipated. Triggers work on an emotional level, and they work fast.

• An animation that responds to scroll speed rather than just scroll position
• Copy that acknowledges where the user is emotionally, not just what they are trying to do
• A visual reveal that gives slightly more information than the user expected at that point
• A micro-interaction that makes a routine action feel satisfying rather than neutral
• A sound or haptic cue that confirms an action in a way that feels considered

None of these are expensive to build. What they require is attention to the emotional register of the first session, and a willingness to spend some design effort on moments that do not show up on a conversion dashboard. The return on that investment is a user who finishes a first session with the sense that the product is genuinely good, which is a different and more durable thing than a user who has simply completed onboarding.

When reviewing first-session designs, ask which moments are designed to trigger an emotional response and which are purely functional. A good first session needs both, and in roughly equal measure.

When Curiosity Becomes the Conversion Strategy

There is a version of first-session design where curiosity is treated as the conversion strategy itself, rather than as a state to be managed on the way to conversion. This shift in framing changes quite a lot about what the product prioritises in those first few minutes.

If the goal of a first session is to make a user curious enough to return, the success metric is not whether they completed the onboarding flow. It is whether they left the session wanting more. That is a harder thing to measure, but it is closer to what actually predicts long-term retention than completion rates are. A user who completes onboarding without feeling any pull to come back has been processed, not engaged.

The emotional state a user is in when they leave a first session matters as much as what they did during it. A user who exits feeling mildly curious and pleasantly surprised is in a better position than one who exited having ticked all the boxes but feeling no particular way about the experience. Session length tells you how long they stayed, but not whether that time built something or simply consumed it.

Products that treat curiosity as the conversion strategy tend to design first sessions that feel generous. They offer something before they ask for anything. They reward exploration. They leave a small gap, something slightly unresolved, that makes coming back feel like a natural next step rather than a chore. That gap is not an accident. It is a deliberate design decision that takes real thought about the emotional arc of the session.

Conclusion

The first session is not a funnel. It is a feeling. And the feeling that most reliably leads to a second session, and a third, and eventually to something that looks like loyalty, is curiosity that was handled well. That means a product that offered something before it asked for something, that built in moments of small reward, and that trusted the user to find their own way into a relationship with the experience rather than pushing them along a predetermined path.

Most teams do not design this way because curiosity is harder to measure than task completion. But the things that are hardest to measure in early sessions are often the ones that most determine what happens in the sessions that follow. Drop-off rates, low return visits, and poor word of mouth are frequently downstream of a first session that processed people rather than interested them.

The design questions worth sitting with are straightforward even when the answers are not. Does the first session give before it takes? Does it have moments that generate a small emotional response, not just a completed step? Does it leave the user wanting to come back, or simply having arrived and departed?

Getting those answers right requires thinking about the emotional arc of a session with the same rigour that most teams apply to the functional flow. If you are working through that kind of design challenge, we think about it at WAA every day. Let's talk about your first session experience.

Frequently Asked Questions