The Myth of the Single "Aha Moment"

There's no single "aha moment" when users lack the foundational understanding to appreciate your product. Instead, we need to orchestrate a sequence of smaller realizations that build on each other.

Welcome Eric, Clair, Pedro, Ty, David, Amy, Brandon, Sheila, Jon and the 48 others who subscribed this week! Connect with me on LinkedIn if you haven’t already!

---

Products in mature categories can activate new customers in minutes because they’re dealing with educated buyers. For a company like Dropbox, everybody understands file storage. Upload a doc, create a password, done.

Webflow couldn’t do that because nobody had experience using a visual designer.

Users signed up, opened the editor, and fumbled through layout properties and the CSS box model. They didn’t have the context or experience to value the possibilities.

That’s a defining challenge of emerging categories: Our prospects are encountering an entirely new way of addressing a problem, and that requires a learning curve before value can be recognized.

Melissa Tan, Webflow’s head of growth, came from Dropbox where growth engineering was programmatic. She shared that activation at Webflow happened over several sessions with lots of learning along the way. The standard onboarding playbooks and optimization tactics didn’t work.

I experience this at Recurrent every day. None of us grew up with an electric car. For a first-time EV owner, our product solves problems they don’t know they have yet. People need to understand some pretty intimidating basics on battery health and degradation before they can appreciate the value of the data at their fingertips.

The task for us is to fully appreciate how and when comprehension happens for our customers. Here’s a playbook that I derived from Webflow (and Notion and Clay) that your team can steal.

The Aha Sequence Playbook

Most growth playbooks assume your prospects already understand the problem you solve. Essentially, the conceptual groundwork is in place for them thanks to competitors and lots of prior experience.

In less developed categories, that groundwork doesn’t exist. The prospect has to understand the problem and solution before they can value what you offer.

1. Map the Comprehension Gap

People exploring Webflow for the first time needed to understand the design model, layout properties, and visual development principles before the product could deliver on its promise. It sounds like a product problem, but it’s really a comprehension problem.

The team ran two-week user diary studies — screen recordings with play-by-play narration — because traditional analytics couldn’t capture where onboarding broke down.

They discovered that new users consistently got stuck just before critical breakthrough moments. It wasn’t because the onboarding flow was bad or the product was buggy, but because the concepts were totally new.

Prospects didn’t understand enough to know how to find value.

Test it: Make a list of the concepts your customer needs to grasp before your product clicks for them. For Webflow, it was the CSS box model. For Recurrent, it’s battery degradation basics.

• Where are your customers supposed to learn those concepts?

• Do they need them before, during or after onboarding?

That’s your comprehension gap.

Lesson: Prospects without the experience or context needed to appreciate what you’re offering is more of a comprehension barrier than a conversion barrier.

Common misstep: Don’t treat confusion like a UX problem. Cleaner design and crisper calls-to-action won’t necessarily fix it.

2. Sequence the Moments

There’s no single “aha moment” when users lack the foundational understanding to appreciate your product. Instead, we need to orchestrate a sequence of smaller realizations that build on each other.

Webflow’s onboarding checklist has 6-10 items, each designed to deliver a different moment of understanding. They explain the purpose of each one before diving in to set the expectation that this is more of a learning journey than a product tour.

The sequences are also tailored to the path. Users starting with a blank site get a different sequence than users starting from a template.

• Blank-site users need a preview of what’s possible before they care about building it.

• Template users can see what’s possible so they need to experience the ease of modifying it.

Whether you have a product or service business, it’s different from the standard playbook of “get people to the core action ASAP.” Rushing to the destination is counterproductive when comprehension is the bottleneck. We have to sequence the learning that makes the outcome meaningful.

Notion faced a version of this with the blank canvas problem. A new user opening an empty workspace doesn’t know what’s possible, let alone what to build. “What will you use Notion for?” became the first step so the product could pre-load workspaces with relevant templates. This shows people what’s possible before asking them to create it themselves.

Test it: Sequence the essential concepts from Step 1 into the (ideal) order of operations: Which understanding enables the next? That’s the sequence taking shape.

Lesson: Each small realization should guide customers to the next one. Even if customer activation takes weeks, we can deliver bite-sized understanding in a series of moments.

Common misstep: It’s rare that one-size-fits-all. Different customers arrive with different levels of comprehension so it’s best if we can meet them where they are.

3. Clear the Path

Customer patience is often correlated with understanding. In other words, is the destination worth reaching?

• I’ll spend 90 minutes setting up a new TV, including painfully logging into each of the apps with the tiny remote.

• An AI app with bold promises on efficiency gets 90 seconds before I cancel the account.

Webflow’s diary studies uncovered what the head of growth described as “death by a thousand paper cuts.” These were small friction points that individually seemed minor but collectively drove users to quit before comprehension could take hold.

For example, users consistently got stuck on the layout feature because it required understanding a specific model. The team formalized a Webflow University and built onboarding offramps to get people the context they needed to be successful.

Test it: Think about the last 5 customers who didn’t make it.

• Where did they get stuck?

• Was it because the concepts were confusing or the experiences were confusing?

Those are different problems.

Lesson: Comprehension problems need education, whereas friction problems are often in need of simplification.

Common misstep: It’s easy to see customer education as a support function that should be automated as much as possible. Imagine it as a strategic asset rather than a CS cost.

4. Bridge the Sessions

Education takes time. Since time and customer adoption are enemies, that means builders in emerging categories need to be very intentional.

Webflow uses a variety of tactics to signal progress and possibility.

• Tutorials explain their purpose before diving in.

• Users check off milestones as they build.

• Estimated completion times set expectations.

Clay confronted this by forcing early customers into a public Slack channel. Users who might have quietly abandoned the product instead saw peers working through the same learning curve. The shared channel shortened learning curves while providing proof that the journey was worth finishing.

As we covered in Clay’s ecosystem playbook, that Slack channel evolved from a support hub into the peer community that became Clay’s powerful growth engine.

Clay also flipped sales demos into live onboarding calls. Instead of pitching the product, they had prospects share their screen then walked them through solving their own real problem inside Clay. The customer left with an actual, valuable outcome. That’s a session bridge to bring them back.

Notion pre-loaded workspaces with templates based on user goals that gave people something to return to immediately. That gap between “I can see it” and “I can make it” was a reason to come back.

Test it: Walk through your customer’s first week from their perspective. After their first real interaction, whether that’s a product session, a sales call or a demo, what specific reason do they have to come back tomorrow?

Lesson: Patience isn’t finite. It’s a resource you can replenish.

Common misstep: There’s a tendency to fill the gap between sessions as a marketing problem with generic drip campaigns. The best bridges aren’t reminders, they foster reasons to continue by:

• Connecting to something the customer already learned

• Previewing the next realization they’re close to reaching

Building Your Sequence Playbook

Our customers likely don’t have the context they need to fully appreciate what we’re offering them. We can’t fall into the trap of viewing it as a product flaw to fix, a marketing message to push or a growth lever to dial.

• “How do we get prospects to activate faster?” ❌

• “How do we guide prospects through understanding why this matters?” ✅

Webflow’s product takes weeks to learn. That complexity could/should have stunted their growth. Instead, they built a $4 billion company by treating education as the product experience.

Your users are out there. They just don’t understand why to appreciate you yet.