Fit Decay: When the Job Stays the Same But the Context Shifts

You can have real product-market fit and still lose it.

Not because you shipped a worse product. Not because the team got lazy. Not because a competitor out-innovated you.

You can lose fit because the world around the Job changed. The Job stayed the same. The context didn't. And the context is where products live.

Most definitions of PMF assume the market holds still long enough for fit to be a destination. Build the thing. People want it. They pull it out of you. Retention climbs. You made it.

But markets aren't snapshots. They're ecosystems. Tools get adopted. Workflows get rewired. Teams reorganize. AI shows up and resets what "good" feels like. Competitors teach customers to expect faster, easier, safer, more automatic.

Your product can stay exactly the same while the environment makes it feel slightly less obvious. Slightly less necessary. When fit decays, it doesn't usually look like a mass exodus. It looks like this: people still like the product. They still say nice things about it. They just stop reaching for it first.

It becomes "where we store things," not "where we do things." It becomes "the system of record," not "the system of work." It becomes "we should keep using it," not "I can't imagine doing this without it."

Retention metrics won't scream right away. They'll whisper. And they’ll be late. Because the real change happened earlier.

What Happened to Dropbox

In 2007, Drew Houston forgot his USB drive on a bus from Boston to New York and spent the entire ride unable to work on the files he needed. He built Dropbox to solve a job that millions of people felt acutely: access my files from anywhere, on any device, without emailing them to myself.

By 2011, Dropbox had 50 million users. By 2012, 100 million. The product had genuine fit because the job was real and the alternatives were terrible. USB drives, email attachments, clunky FTP servers. Dropbox was the first product that made file syncing feel invisible.

Then the context shifted.

In 2011, Apple launched iCloud. In 2012, Google launched Google Drive — free, bundled with Gmail and Google Docs, automatically integrated into the workflow millions of people were already living in. Microsoft followed with deeper OneDrive integration into Office 365.

Dropbox didn't get worse. The job didn't go away. But the forces that had produced fit changed underneath it.

The push that had driven people to Dropbox — the pain of not having files accessible — got solved by default. If you used Google Docs, your files were already in the cloud. If you used an iPhone, your photos were already syncing. The specific frustration that made people seek out Dropbox was dissolving, not because Dropbox fixed it, but because the ecosystem absorbed it.

The pull weakened too. Dropbox's promise — your files, everywhere — had been the future in 2008. By 2015, it was table stakes. Competitors didn't need to match Dropbox's polish. They just needed to be bundled with something the user was already paying for.

The habit force shifted against Dropbox in the most dangerous way: people didn't switch away deliberately. They just started doing the job somewhere else without noticing. Collaboration moved into Google Docs. File sharing moved into Slack. Photo backup moved into iCloud. The job fragmented across tools that handled it as a side effect of their primary function.

Houston described it bluntly: "They just totally nuked our business model."

By 2024, Google Drive held roughly 48% of the cloud storage market. Dropbox held about 21%. The job "access my files from anywhere" was as real as ever. Dropbox was no longer the obvious hire for it.

Fit Decay Is a Forces Problem

Every product's fit rests on a force balance. Push plus pull has to exceed habit plus anxiety. When that equation holds, the product feels default. When it shifts, the product starts feeling optional.

Fit decay happens when context moves one or more forces without the product doing anything wrong.

Push decays when the original pain stops being acute because the world solved it around you. A new internal process. A new integration. A bundled feature in a tool people already use. When push decays, customers aren't desperate anymore. They're merely interested.

Pull decays when expectations rise. Competitors train the market that something should now happen instantly, or automatically, or for free. The bar moves. What used to feel like magic now feels like "why is this still manual?" Your pull can shrink without you shipping a single regression.

Habit shifts when a new tool becomes the place where work starts because muscle memory moved. The default changed, and yours stopped being it.

Anxiety rises when stakes increase. The tool a team adopted casually two years ago now feels like a political decision because leadership is paying attention, or compliance requirements changed, or the company grew past the stage where "we just use whatever" is acceptable.

Any one of these can erode fit. When multiple forces shift at once — which is what happened to Dropbox — the decay can be swift even when the product is still good.

Retention Metrics Are a Bad Early Warning System

By the time churn rises, the switching decision was already made internally. The user had been running an evaluation for months. The earlier signal is behavioral and contextual.

Are you still where the workflow starts? Are you still where decisions land? Are you still the shortest path from "we need to do this" to "it's done"?

If the answer is slowly becoming no, fit is decaying. Even if usage hasn't collapsed. Even if NPS is fine. Even if customers keep renewing because it's easier than ripping you out.

That last one is the most dangerous signal to misread. Renewal without enthusiasm isn't fit. It's the habit force doing your retention work. And habit is a loan, not equity. The moment someone makes migration feel safe, the loan must be paid.

How to Monitor Context Drift

If fit decay is forces shifting, the fix isn't "ship more features." It's "notice which force moved, and why."

Watch for new defaults. What tool started the workflow this year that didn't start it last year? Where do people naturally begin their day? That's habit forming in real time, and if it's forming somewhere else, your gravity is weakening.

Watch for new stakes. What used to be a team-level choice that's now an org-level decision? What used to be casual that now requires approval? That's anxiety rising, and it makes your product harder to defend even when the user likes it.

Watch for new expectations. What feels like table stakes now that didn't a year ago? What did competitors normalize? That's pull getting squeezed because the standard moved.

Watch for disappearing pain. What frustration did customers rant about that they now shrug at? That's push fading. And if push fades, you're in the most dangerous position of all: customers who aren't suffering, just subscribing.

Don't wait for a churn spike to run this check. Run it anytime the environment changes: new category entrant, new platform shift, new buyer persona, new AI capabilities, new economic pressure. Those are context shocks. And context shocks are where fit decay starts.

The job might stay the same for years. The context won't.

The teams that keep fit aren't the ones who find a perfect roadmap. They're the ones who stay honest about the ecosystem. Who keep asking not "what feature are we missing?" but "which force moved, and what moved it?"