First Major Win State: Onboarding’s Key Metric

I spent the last decade watching good products with smart teams fail for the same reason: they were optimizing for the wrong moment. The signup. The tutorial completion. The profile fill. None of it mattered, because the user never reached the moment that actually decides retention.

Most teams measure onboarding success by asking: Did users sign up? Did they upload a photo? Did they watch the tutorial? Those are the wrong questions. And the reason is this: None of those moments matter if users never experience the magic.

The moment that matters — the one that changes everything — is what I call the First Major Win State. Most product teams know it by its older name: the aha moment. It’s the second your user says “Wow, this product is awesome.” Not the moment they create an account. Not the moment they fill out their profile. The moment they actually experience the payoff.

And here’s the uncomfortable truth I’ve seen again and again: many products burn through motivation before that payoff ever arrives. By the time the user reaches the good part, their energy is already gone.

Author Credibility: Yu-kai Chou

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003 — years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and Google Scholar — with 3,700+ more academic publications. Explore his books here.

TEDxLausanne · Gamification to Improve Our World17 min

What Actually Counts as a Win State?

Let me be specific because vagueness here kills products.

On Pandora, the First Major Win State isn’t hearing your first song. It’s hearing 3–5 songs you love — including ones you never knew existed. That’s the moment you say “Okay, this algorithm actually understands me.” Before that point, you’re still testing. You’re uncertain.

Pandora got there first. Spotify Discover Weekly proves the principle still wins more than a decade later — the win state isn’t the song play, it’s the third unfamiliar song that lands. Same Core Drive 7 (Curiosity) into Core Drive 2 (Accomplishment), different generation of the product.

With Octalysis Prime, the First Major Win State isn’t signing up. It’s not entering your birth year. It’s building your companion through an interactive drag-and-drop quiz, then watching it come alive with sparkle animations and personalized responses. That’s the moment you feel connected to the product.

What does NOT count as a win state?

• Creating an account
• Uploading a profile photo
• Watching an intro video
• Setting preferences
• Completing a tutorial

These are all costs. Friction points. Toll booths between the user and the actual payoff. We call them “progress indicators” because we’re trying to make ourselves feel better about the user’s experience, but the user is asking a simpler question: “When do I get to see what this thing can do?”

The Motivation Energy Economy

Here’s the mental model I use: Every user arrives with a finite amount of motivation energy. Think of it like a battery meter. Every click drains it. Every loading screen drains it. Every form field drains it.

Each interaction has a cost:

• Creating an account: Medium cost
• Tutorial video: High cost
• Navigating to external website: high cost
• Each loading screen: Medium cost per screen
• Celebration/emotional moment: Negative cost — it adds energy back

Most onboarding flows drain all the energy before delivering a reward. You’re asking for the account, the profile, the preferences, maybe a tutorial — all before the user has seen anything remarkable.

But here’s where it gets interesting: a well-timed emotional reward actually refills the battery.

This isn’t fluff. It is functional design. When Octalysis Prime shows a user their companion with a personalized animation, that moment of delight adds energy back to the system. Now they’re willing to scroll a little further, click a little more — because they’ve seen proof the product works.

The goal is to reach your First Major Win State before the motivation meter hits zero. Every second counts.

One quick frame before the principles. The six rules below map onto the Octalysis Framework’s 8 Core Drives — the human motivations that decide whether a user leans in or leans out. When I say a principle is about Core Drive 7 (Curiosity) or Core Drive 4 (Ownership), I’m pointing at the underlying motivational lever — the principle is the rule, the Core Drive is why the rule works.

Principle 1: Remove All Friction Before the First Major Win State

This is non-negotiable. I audited Octalysis Prime and recommended removing all external links from the onboarding flow. Other websites, “help” buttons, login redirects — anything that takes users out of the experience.

In that Octalysis Prime audit, removing the external links and the “Need a Hint” button produced a measured 20% improvement in onboarding conversion — and the users who would have clicked “Need a Hint” turned out to be the least engaged people on the island over the long run. The pattern is what matters: when you stop asking users to leave the experience, more of them reach the payoff. Core Drive 7 (Curiosity) only stays alive while the curiosity object is one click away.

Another example: I-Done-This is a daily tracker that asks users to log their accomplishments. During onboarding, they included a feature called “Need a Hint?” Seemed helpful, right? It showed example entries users could reference.

But here’s what happened: Users who clicked “Need a Hint?” — the ones actively trying to prepare themselves — were the least engaged. The diligent users were actually the ones most likely to drop off.

Why? Because they were studying instead of doing. They were delaying the actual value moment. The friction of preparation exhausted them before they reached the point of experiencing the payoff.

The solution: Delete the hints. Delete the tutorial. Delete anything that delays the moment they log their first accomplishment and see it appear in the system. That’s the win state. Get them there faster.

Principle 2: Collect Personal Info After the Win State

Beacons.ai is a link-in-bio platform. Most competitors ask you to sign up, fill out your profile, customize colors, and then you finally get a working link. The friction is immense.

Beacons.ai got smart. They let you claim your URL first. Instant, no friction. That’s Autonomy (Core Drive 4) delivered immediately. Then, after you have a working link you can share, they ask for more profile details.

Compare this to a cardinal sin I see frequently: A product promises one thing, then delivers something completely different. I audited a platform marketing “Get brand deals and sponsorships” during signup. Users were excited. They filled out everything. Then the actual win state was… a link-in-bio builder. The marketing promised sponsorships; the product delivered link management. It’s like someone trying to be your friend but keeps forgetting everything about you.

The pattern is clear: Signup forms are toll booths. Users will tolerate a toll booth, but only after they’ve seen the destination and decided it’s worth it. Collect names, emails, and preferences after the First Major Win State. Not before.

Principle 3: Match the Win State to What Users Actually Want

This seems obvious, but I’ve seen it violated constantly. The win state you design has to deliver on the promise that brought users in.

For Pandora: The promise is “find music you love.” The win state is hearing music you love. Not following friends, not creating playlists. Music.

For Octalysis Prime: The promise is building a personalized AI companion. The win state is seeing your companion come alive with personality. Not reading theory about the Octalysis Framework, not planning future interactions. The companion itself, right now.

I audited a wellness platform that promised transformation. During signup, they asked detailed health questions, personal goals, trauma history. Users filled it out expecting personalized guidance. The actual win state? A generic 5-step plan that could have been written for anyone.

The disconnect between promise and payoff is brutal. It feels like betrayal because it is betrayal — not intentional, but from the user’s perspective, you promised one thing and delivered another. They gave you their most personal information and got a template.

So before you design your First Major Win State, ask: What problem did users think they were solving when they signed up? That’s your target. Not what you want them to care about. What they actually care about.

Principle 4: Every Screen Needs a Desired Action

Google+ died for many reasons, but here’s one that haunts me: When you first opened Google+, you saw a wall of options. Circles, games, photos, communities, hangouts, settings. It was overwhelming.

The user’s brain did what brains do under overwhelm: Paralysis. And paralysis leads to “Maybe I should just check my email instead.”

I call this the Google+ Effect, and I see it in onboarding constantly. A dashboard with six tabs. A setup wizard with ten customization options. A hero screen with five “learn more” links.

Humans are decision-fatigued creatures. Every choice costs energy. If I can’t immediately see which action moves me forward, I’ll move backward and leave your product.

SuperBetter is a resilience platform. I audited their onboarding dashboard and found six different sections with no visual hierarchy. Which tab should I click? Which action matters? The design was saying “everything is important,” which is the same as saying “nothing is important.”

The fix is what I call Glowing Choice design — a single action with a pulsing, glowing visual indicator that says “click here,” with everything else fading to grey. Same idea as a Desert Oasis: when the desert is empty, the oasis is unmissable. When the screen has six equally-loud destinations, none of them are.

The mechanism behind this is psychological, not visual. The moment the user thinks “What should I do now?” is the same moment the brain thinks “Maybe I should check my email.” Choice paralysis isn’t a UX flaw — it’s a Core Drive 3 (Empowerment of Creativity & Feedback) underflow. The user wants to apply judgment; the screen refuses to give them one judgment to apply.

On Pandora, the first screen is simple: Play music or create a station. That’s it. Two options, both clear. You don’t see the settings or the social features or the premium upsell. You see the core experience.

In I-Done-This, when you first log in, one button dominates: “Log your accomplishment.” Everything else is smaller, quieter, secondary. The desired action is unambiguous.

Principle 5: Every Win State Needs Emotional Reward

Here is where good onboarding separates from forgettable onboarding. The celebration is not decoration. It is function.

When SuperBetter users completed an activity, the system said “High five! Tracker complete.” Flat. Impersonal. No energy. Compare that to Octalysis Prime, where your companion responds with a unique animation, a personalized message based on your data, a reaction that makes you feel recognized.

I-Done-This showed users a plain text welcome message when they first logged accomplishments. No visual celebration. No sense of achievement. Just confirmation that your text was received. Compare that to a system that shows your logged accomplishment with a little animation, maybe a star appearing, something that makes the moment feel real.

Why this matters: celebration moments aren’t nice-to-have. They refill motivation energy. They’re proof that the system cares about your success, not just your data. They make the win state feel like a win instead of just a completion.

When you log your first accomplishment in a tracker like I-Done-This — or in Apple Journal today — you should feel a little spark of pride. When you see your Octalysis Prime companion come alive, you should feel a little flutter of connection. These aren’t nice moments — they’re converting moments. They’re what turns a user into a returning user.

Principle 6: Don’t Let Users Stumble Into Bad Experiences

This is the principle that catches teams off guard because it’s about what you prevent, not what you create.

SuperBetter has a feature called “Design your own adventure.” Seems empowering, right? Users can customize their own experience. But during onboarding, this option without guardrails leads users to create scenarios they’re not ready for, goals they can’t achieve, interfaces they can’t move through.

I-Done-This had “dead-end” screens, places where users would land and have no clear next action. They’d logged something, the system confirmed it, and then… nothing. No prompt. No “what now?” They’d stare at the screen and leave.

And then there’s the 504 error. I audited a product that crashed mid-onboarding for a small percentage of users. For those users, the onboarding experience ended with a server error. No Recovery-First flow. No “sorry, let’s try again, here’s where you were.” Just the error message and the user’s assumption that the product doesn’t work. Core Drive 8 (Loss & Avoidance) doesn’t activate cleanly here — it activates and contaminates the entire next session, because the user can’t separate “this product errored once” from “this product can be trusted with my data.”

The principle: Every path a user can take during onboarding should lead somewhere. Every action should have a clear next action. Every error should have a recovery path. Don’t force users to stumble into dead-ends or technical failures. Guide them through every moment until they reach the win state.

The Three Wireframe States Designers Forget

This is a mental model that changed how I approach onboarding. Most designers think about onboarding in one state: normal state. That’s the state with all the features, all the options, the fully-loaded interface.

But users don’t see the normal state when they first arrive. They see the zero state. This is what a brand-new user with no data sees. No achievements logged, no companion built, no playlists created. Just the empty canvas.

And then there’s the max state — what happens when everything is full, when a user has maxed out the system. Hundreds of accomplishments logged, dozens of playlists, every feature populated with data.

The problem: Most designers spend 80% of their time in normal state. The interface with “average” data. Moderate number of items. Balanced feature usage. Then they release the product, and the first 10,000 users see the zero state — which was never actually designed. Just built by accident.

In I-Done-This, the zero state could be devastating. An empty dashboard could feel like failure or emptiness instead of potential. Apple Journal solved the same problem in 2023 by populating the empty state with prompts (“What was the highlight of your day?”) — turning a void into an invitation. Same Core Drive 2 problem, fifteen years apart. The fix in both cases: acknowledge the zero state. Show what this space will become. Maybe a placeholder that says “Your first accomplishment will appear here.” Maybe a gentle animation inviting action.

For Pandora, the zero state is critical. No history, no stations, no algorithm yet. But the first screen doesn’t show emptiness. It shows music. It shows the action. “Create a station from an artist” — and suddenly the zero state becomes a launching pad, not a void.

For Octalysis Prime, the zero state becomes the entire onboarding: Building your companion. The empty state IS the win state. You’re not looking at an empty screen. You’re actively creating.

If you only design for normal state and skip the zero state and max state, you’ve designed 33% of the user experience. That’s why onboarding often feels awkward and disconnected. It wasn’t designed. It was what fell out of the system.

The most ruthless test is what I call the Pioneer Fallback. In Octalysis Prime, the Facebook friend-finder pulls a list of friends who already use the product. But if the new user has zero friends on the platform, the screen doesn’t say “we couldn’t find anyone.” It flips: “Congratulations — you’re the first person in your friend community to join Octalysis Prime. That makes you an innovator, a pioneer.” The empty state becomes a Core Drive 5 (Social Relatedness) and Core Drive 7 (Curiosity) double-win. The same negative state that would have read as rejection now reads as status.

The rule generalizes: every state with no data should also be designed as a state with intention. Replace zero counts with desired actions — instead of “Challenges: 0,” show “Pick your first challenge →.” Zeros are not motivating. Actions are.

Putting It Into Practice

If you’re worried about the wrong users signing up, focus on pre-signup messaging and positioning. Then remove friction once they’re in. Don’t use the onboarding as a gatekeeper.

Pandora doesn’t require users to understand algorithms. They just need to understand “I like music.” Octalysis Prime doesn’t require understanding gamification theory. Users just need to understand “I’m building a companion.” Start there. Let complexity come later, after they’ve experienced the payoff.

In almost every case, faster is better. This tells you the win state is real, not an artifact of design.

But the first major win state — the one that decides if users return or abandon — is singular. Protect it. Defend it. Remove everything between your user and that moment.

FAQ

How do I identify my product’s First Major Win State?

Interview retained users and ask what exact moment made them think, “Okay, this is worth coming back to.” Their answers usually cluster around one experience. That cluster is the win state. Then measure how quickly new users reach it.

What if different user segments have different First Major Win States?

That is normal. One segment may value progress visibility, while another cares more about discovery or social connection. The job of onboarding is not to force everyone through one identical path. It is to route each segment to its first meaningful payoff as directly as possible.

How fast should users reach their First Major Win State?

There is no universal stopwatch, but the principle is simple: get users to a meaningful payoff as early as you realistically can. Consumer products usually need that win very quickly. More complex tools get a little more runway, but not much. If users are still doing setup while wondering why they signed up, you are already late.

Can a product have multiple First Major Win States?

You can have multiple meaningful moments across the lifecycle, but each user segment usually has one first payoff that really matters. That first win turns curiosity into commitment. The later wins deepen engagement.

What if our product requires significant setup before any value?

Then you need to create value inside the setup itself. Use sample data, partial progress, or a visible early reveal so the user feels momentum before the full configuration is complete.

Isn’t some friction necessary to filter out users who aren’t serious?

Usually that is a positioning problem, not an onboarding problem. Friction rarely filters only the wrong people. It mostly removes motivation before the right people see the value.

What if my First Major Win State requires the user to understand the product first?

Then simplify the first promise. Instead of teaching the whole system up front, give users a smaller win that demonstrates the value of the larger system. Education should support the payoff, not delay it.

How do I measure if I’ve achieved a good First Major Win State?

Track the time from signup to the first meaningful success, then map the drop-off points before that moment. If faster paths consistently produce stronger activation and retention, you are getting closer to the right win state.

Related Reading

• Onboarding Design: The First 5 Minutes That Matter
• The Desired Action Audit: Screen-by-Screen UX Mastery
• The Complexity Threshold: Can Your Users Handle It?
• Books by Yu-kai Chou

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?