The Crucial Yet Overlooked Part of the Adoption Timeline

Steve Jobs walked onto a stage in San Francisco in 2007 and announced that Apple was introducing three products: a widescreen iPod with touch controls, a revolutionary mobile phone, and a breakthrough internet device.

Then he revealed it was all one thing.

People watching that keynote didn't buy an iPhone that day. The device wasn't available yet. Many of them had phones they were perfectly happy with, contracts they were locked into, habits that worked well enough.

But a question had been asked that no one had imagined before: what if a phone could work like that?

Somewhere else that same year, a project manager watched a deadline collapse because critical files were scattered across email attachments, a shared drive, and someone's desktop. Nobody had shown her a better tool. Nobody had demonstrated anything. She just thought, for the first time: there has to be a better way to handle this.

Both of those are First Thoughts. And the First Thought is the most underestimated stage in the entire adoption timeline.

The first thought stage

In JTBD thinking, the journey from dissatisfaction to committed use exists across six stages: First Thought, Passive Looking, Active Looking, Deciding, First Use, and Continued Use.

The First Thought is the earliest of these — the moment when someone first becomes aware, however dimly, that their current situation might be improvable.

It is not a decision. It is not a search. It is not even a complaint. It is the small crack that appears between "this is fine" and "there might be something better."

That crack can open from the outside — someone shows you a possibility you hadn't considered. Or it can open from the inside — something in your own situation breaks badly enough that the question forms on its own.

Either way, nothing visibly changes when it happens. The person goes back to their existing tools, their existing habits, their existing way of working. They file the thought somewhere — barely consciously — and move on.

But the filing changes how they see things afterward. A person who has had a First Thought starts noticing relevant information they would have previously filtered out. A mention in a newsletter registers now where it wouldn't have before. A colleague using something different prompts a question instead of indifference.

Two paths to the same thought

First Thoughts don't arrive from nowhere. They're triggered. But the triggers come from two fundamentally different directions.

From the outside: someone encounters a possibility they hadn't known existed. The iPhone keynote was an engineered version of this — Jobs designed the presentation to create a felt contrast between what a phone could be and what phones currently were.

The more common version is more understated: a colleague mentions a tool, you see someone navigate a workflow faster than you could, you read something that sticks.

From the inside: something in the current situation fails in a way that makes the question unavoidable. Not a chronic annoyance — those get normalized. A specific moment where the gap between what happened and what should have happened becomes sharp enough to notice.

The team whose project fell apart because decisions were buried in email threads. The salesperson who lost a deal because the CRM didn't surface a follow-up. The designer who shipped the wrong version of a file because feedback was scattered across three platforms.

None of these people saw a better alternative that day. They just had the thought for the first time that one should exist.

The difference matters for product teams. External First Thoughts happen when your product (or your content, or your users) creates a visible contrast. Internal First Thoughts happen when the status quo produces a failure sharp enough to open the question — and your product may not be anywhere in the picture yet.

Drew Houston and the video that created seventy-five thousand first thoughts

In early 2008, Drew Houston, co-founder of what would become Dropbox, had a problem. The product was entering private beta, but only about 5,000 people had signed up for the waitlist.

Houston's solution was a short demo video. It showed file syncing across devices in real time — simple, clear, and loaded with Easter eggs aimed at the Digg and Reddit communities where he planned to post it. The video hit the front page of Digg with over 12,000 votes.

The waitlist jumped from 5,000 to 75,000 overnight.

None of those people had been actively searching for a file syncing solution. Most of them had been living with the problem — emailing files to themselves, carrying USB drives, accepting the friction — without having categorized it as a problem worth solving.

The video created a First Thought at scale: this exists, it works like this, and my current approach is worse than I'd realized. It was an external trigger — but it landed because so many people already had the internal conditions (the friction, the workarounds) that made the thought stick.

What Houston had built wasn't just a demo. He'd built a First Thought delivery mechanism.

When the First Thought and the Last Straw are the same

Sometimes the internal trigger is so sharp that the First Thought and the urgency to act arrive simultaneously.

A team loses a major client because a deliverable was late — and the reason it was late is traceable directly to a broken handoff in their project management tool. They hadn't been thinking about switching tools. They hadn't been passively absorbing information about alternatives.

But the failure is acute enough that the First Thought, the Last Straw, and Active Looking all compress into the same week.

This is the exception, not the norm. Most First Thoughts simmer for months before anything happens. But for products that serve high-stakes, failure-sensitive jobs — payroll systems, security tools, anything where a single failure has visible consequences — the compressed path is common enough to design for.

Why it's often invisible

The First Thought stage creates almost no measurable signal.

The person isn't searching. They're not in a marketing funnel. They haven't filled out a form, clicked an ad, or attended a webinar. They've had a thought and filed it away. From the outside, nothing has happened.

This is why most teams build their acquisition strategy entirely around Active Looking — the stage when someone is actively evaluating options. At that point, they're generating signals: search queries, review site visits, demo requests.

But by the time someone is in Active Looking, the First Thought happened weeks, months, or sometimes years earlier. The question "what made you start looking?" — which Moesta's interview methodology uses to trace the timeline backward — almost always reveals a First Thought that predates the visible behavior by a significant margin.

If your product wasn't present when the gap first opened, you're competing against a mental shortlist that was written before the search began.

Designing for a stage you can't see

The practical challenge is that First Thought is difficult to measure and nearly impossible to optimize with traditional acquisition metrics. What you can do is work backward from how First Thoughts actually form in your category.

For external triggers: the design of your product's visible outputs — the links it generates, the documents it creates, the invitations it sends — are First Thought delivery mechanisms. Every artifact your product produces that a non-user encounters is a potential trigger.

Calendly's spread worked this way: receiving a scheduling link showed you what frictionless looked like from the receiving end.

For internal triggers: content that names specific frustrations precisely reaches people at the moment the gap has just opened. Not "improve your workflow" but "stop losing track of decisions because they're scattered across four tools." The person whose project just fell apart for exactly that reason reads that sentence and thinks: these people understand my problem.

For demonstrations: the demo is not a late-stage conversion tool. It's an early-stage planting mechanism. Its job is to make a possibility feel real rather than to close a decision. Houston's video worked because it did all three — it showed a contrast, named a frustration, and made the possibility feel concrete.

For compressed paths: if your category is one where First Thoughts often arrive with urgency attached, being findable in the moment of crisis matters more than brand building. The team that just lost a client isn't browsing thought leadership. They're searching for a solution. Being the credible answer they find in that search is First Thought work too.

The First Thought is the beginning of everything that follows. Most teams show up several stages too late to shape it.