Being Loved Isn't the Same as Being Necessary

There's a version of product love that looks like job-market fit but isn't.

Users say they'd be disappointed without the product. They recommend it. They've built workflows around it. They'd notice if it disappeared. But if it did disappear — if you pulled it tomorrow — they'd adapt. They'd find a workaround. They'd go back to the old way and be basically fine within a week.

That's attachment. Attachment is about the product — users love the tool. But job-market fit isn't about loving the tool. It's about the job. A product has fit when it's the best hire for a job the user needs to make progress on, and when going back to the old way of doing that job now feels intolerably worse.

The difference between "I'd miss it" and "I can't go back" is the difference between a product that's liked and a product that's load-bearing for the job. And only the second one holds up when competition arrives, when budgets tighten, and when the next cohort has to be convinced from scratch.

What Google Reader Revealed About the Difference

On March 13, 2013, Google announced it was shutting down Google Reader, its RSS feed aggregator, launched in 2005, used by millions to curate and read content from across the web.

The reaction was immediate and intense. Over 46,000 people signed a petition within hours. Tech blogs ran eulogies. The outpouring of grief was real. Run any attachment survey the day before the announcement and the scores would have been enormous.

Then Google shut it down on July 1, 2013. And something instructive happened.

Some users moved to Feedly. Some moved to other RSS readers. But a large number — probably the majority — just stopped using RSS entirely. They'd already been getting their content from Twitter, Facebook, Reddit, and algorithmic feeds.

The job "stay current with content I care about" hadn't disappeared. It had been migrating to other hires for years. Google Reader users just hadn't noticed, because the product was familiar. The job was still getting done — just not by Reader anymore.

The attachment was real. The necessity wasn't. People missed Google Reader. Most of them didn't need it back — because the job had already found replacements.

A product can generate genuine emotional connection, real usage, real loyalty, and still not be the kind of hire that the user can't reverse. If they’ve found other solutions, or if the pain of going back is mild, the product is sitting on attachment that feels like fit but doesn't behave like it under pressure.

Why This Matters for PMF

Attachment and necessity produce identical metrics right up until they don't.

Both show strong retention, but attachment-driven retention is brittle. It holds as long as nothing disrupts the habit. A competitor with a lower switching cost, a price increase, a change in the user's context — any of these can break attachment-driven retention in ways that necessity-driven retention would absorb.

Both show high satisfaction scores, but satisfaction with an attached product is about comfort, while satisfaction with a necessary product is about outcomes. "I like using this" and "this is how I get the job done" sound similar in a survey. They behave completely differently when the user has to justify the cost, defend the choice to a manager, or decide whether to renew.

Both produce word-of-mouth, but the character of the recommendation is different. Attachment produces "you should check this out." Necessity produces "I don't know how I'd get this done without it." The first is a suggestion. The second is a referral. And referrals compound in ways suggestions don't.

The distinction matters most when you're trying to scale beyond your current users. Your existing base might be deeply attached. But the next cohort doesn't share that attachment. They're evaluating the product cold.

If the product's hold on current users is attachment rather than necessity, the next cohort will be harder to acquire and easier to lose, because they'll be measuring the product against the job, not against the comfort of familiarity.

The Question That Reveals Which One You Have

The standard PMF survey asks "how would you feel if you could no longer use this product?" That measures attachment and it's useful for that.

But there's a better question for measuring necessity: "If this product disappeared tomorrow, what would you do?"

Not "how would you feel?" — that produces emotions. "What would you do?" — that produces a plan. And the plan tells you everything.

If the answer is specific and painful — "I'd have to go back to reconciling everything in spreadsheets, which used to take me four hours every Monday" — the product is necessary. The job doesn't have a better hire. Going back means accepting a cost the user can name and doesn't want to pay.

If the answer is vague and manageable — "I'd figure something out, I guess I'd use [alternative] or just do it manually" — the product is attached but not necessary. The job has other hires available. The user would adapt. The loss is real but survivable.

If the answer includes "I'd been meaning to look at other options anyway" — the product isn't even attached anymore. It's coasting on inertia while the user is already shopping for the next hire.

The follow-up that sharpens this further: "What were you doing before you had this product, and would you go back to doing it that way?"

That question forces the user out of abstract appreciation and into the concrete reality of how the job was getting done. When they describe "before," you hear the forces: the frustration that pushed them to switch, the habits they had to break, the anxiety they overcame. When they answer "would you go back," you hear whether the product has become the irreplaceable hire for this job — or whether going back is a shrug away.

How to Apply This

Talk to three groups. Users who renewed or upgraded quickly. Users who tried the product and didn't adopt. Users who churned after initial engagement.

Ask each group: what were you doing before? What specifically made you try something new? And if this product disappeared, what would you do tomorrow morning?

Listen for the difference between loss and inconvenience.

If going back feels like pain — lost time, lost quality, lost confidence, visible regression in front of colleagues — the product is the best available hire for the job. That's fit that holds under pressure.

If going back feels like a hassle — annoying but manageable, a few extra steps, a minor downgrade — the product is attached but replaceable. The job has other hires. That's fit that holds until something disrupts the habit.

Users will often describe this as a rational calculation. It usually isn't. The real force underneath is emotional — fear, confidence, embarrassment, identity. "I'd be fine" sometimes means "I'd rather not think about how not-fine I'd actually be." You have to listen for the layer underneath the reasonable answer.

Google Reader's users would have given it extraordinary attachment scores the day before it shut down. And most of them were fine within a month because the job had already found other hires.

Keep measuring attachment. It matters. Just don't mistake it for the whole picture. The market doesn't sustain products people would miss for a little while. It sustains products that are the best hire for a job that will always need to get done.