Helping Users Reach Their Future

Every product begins with a vision of what could be.

Not a feature list. Not a benchmark. A future.

When someone adopts a new tool, they aren't just switching software. They’re switching selves. They’re leaving behind who they were ("the person who Googles everything") and becoming someone new ("the person who asks AI").

This is why most AI products fail. They obsess over the technology and ignore the psychology. They build incredible models but forget that humans don't adopt tools—humans adopt futures.

Product Narratives Are Personal Futures

Our capacity for narrative thinking is hardwired. We evolved to structure experiences as stories—with beginnings, middles, and ends—because it makes the world feel predictable and meaningful.

When you strip away the bells and whistles, every great narrative arc has three elements: where the hero starts, how they change, and where they end up. Luke Skywalker. Harry Potter. Your user.

A product narrative is a compressed hero's journey. It answers the question: "Who do I become on the other side?"

If your product can’t answer that question in a way the user can see themselves in, they won’t cross. They’ll stay on the familiar shore, even if it's painful, because at least they know who they are there.

A Bridge Measured in Moments

Think of adoption as a bridge.

On one side is the Old Way—the user's current status quo. It's imperfect, frustrating, maybe even broken. But it's familiar.

On the other side is the New Way—the future your product makes possible. It's better, but it's unknown.

The bridge is the narrative journey that carries the user from who they are to who they could become.

But not all bridges are built the same. The angle of the bridge—the Slope—depends on how radically you’re asking them to change their mental model.

The Three Slopes

• "I am you, but faster."*

On the Gentle Slope, the New Way is just an optimized version of the Old Way. The user isn't changing their identity; they’re getting a speed boost.

• The Mindset Shift: Minimal. Automating a manual task.
• The Trust Required: Low. A free trial with a quick payoff.

Real-World Example: Gmail Smart Compose.

You hit Tab, and the sentence finishes. You didn't become a different person. You just became a slightly faster version of yourself.

Slope 2: The Standard Slope

• "I am a better way to do this."*

Here, the user has to abandon a familiar (but clunky) process for something new. They know the old way is broken, but they need proof that the climb is worth it.

• The Mindset Shift: Moderate. Swapping out proven workflows.
• The Trust Required: Medium. Robust proof and deeper buy-in.

Real-World Example: Perplexity.

Perplexity asks you to stop Googling. That's a real behavioral change. They win by showing their work—citations, sources, reasoning—proving the new way is better than ten blue links.

Slope 3: The Steep Slope

• "I am a completely new way of existing."*

This is where you ask users to rethink entire skill sets. The New Way isn't just better; it's revolutionary. The user must take a leap of faith to believe your claims.

• The Mindset Shift: Dramatic. Rethinking how work gets done.
• The Trust Required: High. A leap of faith.

Real-World Example: Cursor.

Cursor doesn't just help you code faster. It asks you to become an "AI-augmented developer"—a fundamentally different professional identity. That's a steep climb. They win by starting small (autocomplete) and gradually revealing bigger possibilities (full-file refactors, codebase-wide changes).

Three Stages of Crossing

Regardless of slope, every user crosses in three stages:

1.  Rerouting (14 milliseconds to 14 seconds): The instant someone snaps out of their usual routine and notices there could be a better way. This is the "Wait, what?" moment.

2.  Embarking (14 minutes to 14 hours): Curiosity translates into tangible steps. The user is actively exploring, building confidence that "maybe this is worth changing."

3.  Arriving (up to 14 days): New behaviors become second nature. The old frustrations fade. The New Way becomes the new status quo.

Why the Slope Matters

Recognizing your slope prevents two fatal errors:

• Overbuilding for a Gentle Slope: If your product solves a simple problem (messy inbox), don't overwhelm users with revolutionary messaging. They don't want to become a new person; they want to save 10 seconds.
• Underbuilding for a Steep Slope: If your product demands a dramatic change (AI-assisted legal review), don't pretend it's a "magic button." Users need to see the small steps, the proof, and the vision of who they become on the other side.

Building a Bridge of Many Planks

A great bridge doesn't demand one giant leap. It breaks the journey into small, confidence-building steps.

Each step is a plank. Each plank is stable. Each step feels rewarding rather than risky.

• Minimize Risk: Show that each step is doable.
• Maximize Value: Offer glimpses of how life improves on the other side.
• Celebrate Progress: Remind them how far they've come.

Because regardless of how steep the climb, it's the promise of a better future—and the confidence to claim it—that ultimately propels everyone forward.

The question isn't "How smart is my AI?"

The question is: "Can my user see themselves on the other side?"