The Progress Timeline: You're Beginning At the Wrong Part of the Story

It’s smart to obsess over onboarding. “How do we get users to that "aha moment?" “How do we reduce time-to-value?” “How do we make the first experience sticky?”

Make no mistake, these are critical questions. A poor onboarding is a great way to get a lot of new users to churn.

But it’s also not the beginning of their story with you. If you ignore everything that happened before the user showed up, and everything that happens after they take a chance on you, then you’ve never going to build a robust customer base.

If you're only designing for the moment right after people sign up, you’re leaving an awful lot up to chance. And the truth is, in that case, the odds are not in your favor.

There's a top-level timeline that maps how people actually move through hiring a solution to do a job.  It looks like this:

First Thought → Passive Looking → Active Looking → Deciding → First Use → Ongoing Use→ Desired Outcome → Continued Use

Every user who is destined to stick around travels this path. The question is whether you're present at each stage, providing the necessary tools for them to make progress.

Let's make this concrete

Say you're building a tool that helps teams write better product specs. The job is something like "get alignment on what we're building so we stop wasting cycles."

First Thought:  A product manager finishes a frustrating meeting. The team spent an hour arguing about scope because everyone had a different picture in their head. She thinks, "There has to be a better way to do this."

This is the trigger. This is the moment she feels frustration, or even pain at the current status quo. She's not looking for your product yet; in fact, she's not looking for any product. She's just annoyed.

Passive Looking: Over the next few days, she notices things. A tweet about "spec debt." A colleague mentions they started using templates. An article about how Stripe writes product specs. She's not searching. She's just aware that other solutions might exist.

Active Looking: The next bad meeting is the Last Straw. It pushes her over the edge. She googles "product spec tools" and "how to write better PRDs." She's hunting now. She reads a few blog posts, clicks some ads, signs up for a couple free trials.

Deciding: She's narrowed it to two or three options. Now she's comparing. Reading reviews. Watching demo videos. Trying to figure out if this is worth the effort, if her team will actually use it, if she'll look dumb for suggesting a new tool that nobody adopts.

This is where fear of change peaks. She's on the edge of commitment but hasn't tipped.

First Use: She picks one. Creates an account. Starts a spec. This is what most product teams focus on – the onboarding flow, the empty state, the first template.

Ongoing Use: If all goes well, she writes a few specs. Her team starts commenting. The tool becomes part of how they work. Habits form. Data accumulates. Switching costs grow.

Desired Outcome: Six months later, her team ships faster with less rework. The arguments about scope are mostly gone. She's made the progress she was after. Now she’s a loyal customer.

Here's the problem

Most products are fixated on that first use. And of course that needs to impress. But there’s so much more to it. No one is going to get to that first use if you don’t understand why they'd consider switching in the first place - and why they’d continue.

The Four Forces Model explains this: Two forces push people toward something new, two forces hold them back.

Push is the pain of the current situation—the frustration, the cost, the thing that's not working.

Pull is the attraction to a better future—the vision of the problem being solved.

Habit is the status quo bias—the accumulated investment in the current way, the muscle memory, the "I know where the buttons are."

Anxiety is the fear of change—what if the new thing is worse? What if I look dumb? What if it doesn't work?

People switch when Push + Pull > Habit + Anxiety. When they don't, they stay—no matter how good your product is.

Here's the thing: These forces operate differently at each stage of the timeline.

Push peaks early. That frustrating meeting—the First Thought—is when the pain is freshest. By the time someone's in Active Looking, the acute pain might have faded. They're problem-solving now, not suffering.

Pull builds through Passive and Active Looking. Each piece of content, each example of a better way, each glimpse of the future adds to the Pull. Pull needs to be vivid and specific.

Anxiety spikes at the moment of Deciding. This is the moment of maximum fear. What if I'm wrong? What if this doesn't work? What if I waste my team's time?

Habit is strongest before any looking starts—it's what keeps people from even having the First Thought. But it resurfaces during Deciding ("maybe I should just stick with what we have") and again in Ongoing Use if the new tool isn't stickier than the old way.

Each stage needs a different design. You can't use the same messaging for someone in Passive Looking (gently entering their awareness) as someone in Deciding (reducing anxiety and creating urgency).

The Switching Moment is a specific point on this timeline—the instant they commit to change.

It usually lives somewhere between Deciding and First Use. It's the click that says "I'm doing this." The moment Push + Pull finally exceeds Habit + Anxiety.

Everything before the Switching Moment is about building toward it. Everything after is about validating that they made the right choice.

If you don't know where your users' Switching Moment happens—what finally tips them—you're guessing at your entire growth strategy.

And the timeline doesn't end at Ongoing Use.

Desired Outcome - aka the Job they hired you for in the first place –  is a real moment of truth. The user hired your product to make progress. Did they make it?

That product manager didn't want to "use a spec tool." She wanted her team to stop wasting cycles on misalignment. The spec tool was a means to that end.

If you never confirm she got there—if you never surface the progress she's made and celebrate it —you're leaving value on the table. She might not even realize the tool worked. She might churn without understanding why things got better, because you never showed her.

Confirmation isn't just nice. It's how you turn users into advocates. It's how you expand usage. It's how you earn the right to charge more.

"Look how much faster your team shipped this quarter" is worth more than any feature announcement.

The audit is simple.

Ask yourself some basic questions.

• Where does the job first surface?
• What's the trigger?
• What's the context?
• What makes someone have the First Thought?

If you don't know, you can't create content that meets them there. You can't be present in Passive Looking. You're invisible until they're already searching.

• How do users find and evaluate you?
• What do they search for?
• What do they compare you against?
• What questions are they trying to answer during Deciding?

Without this knowledge, your marketing is a guess and your landing page is probably speaking to the wrong stage.

• What finally nudges them to give you a try?
• A piece of social proof? A gut feeling? A deadline?

You can't engineer a switching moment if you don’t know when and why it would happen. You can't reduce the Anxiety or amplify the Push at the right moment.

• What's the first value delivered? Not the first feature used—the first value. The first moment they feel like this was worth it.

If you don't know, your new users sure won’t.

• What makes them stay?
• What deepens stickiness over time?
• What accumulates?
• What would they lose if they left?

If you can't answer this, you're relying on inertia instead of building real switching costs.

• How do you confirm the outcome?
• Do users know they've made progress?
• Do you show them?

If you don’t celebrate their wins, you're hoping they figure it out on their own. Most won't.

The progress timeline is a reminder that users exist before they find you and after they've signed up.

So design for the whole story, not just a chapter.