Push: The Force That Makes People Finally Stop Tolerating the Status Quo

Most teams can tell you why their product is better than the competition. But they’re often less sure about precisely why someone would stop using their current inferior solution and switch.

That reason is Push. Push is what happens when value stops being theoretical and the pain of the current way starts feeling unacceptable. Not "annoying." Not "a little inefficient." Unacceptable.

That moment is where the adoption journey begins.

What Push really is

In the JTBD lens, Push is one of four forces that determine whether someone switches products. Push and Pull drive people toward change. Habit and Anxiety hold them back. Push is the pain of the current situation.

It can be functional and practical:

• "This takes me five hours a week."
• "We're losing money because we miss things."
• "Our handoffs are broken."

But the functional pain is usually not the thing that creates movement. Push becomes more powerful when the functional pain turns into an emotional tax:

• "I feel behind all the time."
• "I'm embarrassed when this breaks in front of other people."
• "I don't trust myself to catch mistakes anymore."

Push isn't "what's wrong with the tool." Push is what the current way is doing to the person using it.

Zendesk's early growth is a good example. In the late 2000s, customer support teams were running on shared inboxes, spreadsheets, or enterprise help desk software that cost six figures and took months to implement. The functional problem was obvious — tickets got lost, nothing was tracked, customers waited too long. But the emotional problem was worse: support managers couldn't tell if their team was drowning or coasting. They'd get blindsided in meetings by complaints they'd never seen. The push wasn't "we need a ticketing system." It was "I can't keep finding out about problems from my boss."

Push isn't constant. It spikes.

If you want to understand push, don't ask a potential user, "Do you like your current solution?" People can dislike something for years and never change it.

Push shows up in spikes. Moments where the status quo stops being tolerable. The day-to-day annoyance doesn't create switching. Moments of desperation and pain do.

Shopify's co-founder Tobias Lütke built the platform because he tried to set up an online snowboard shop in 2004 and the available e-commerce tools were either terrible or wildly expensive. He didn't wake up wanting to build a platform company. He hit a desperation spike: the existing options couldn't do the thing he needed to do, right now, for the business he was trying to run. The push was immediate and personal.

That's the pattern. People tolerate a surprising amount of friction as long as it stays below a threshold. Meaningful Push happens when something forces it above.

The Push Curve: how pain accumulates

Push is rarely one big event out of nowhere. It's usually a slow accumulation of frustrations that build into a sharp moment of pain.

1. Normalization

At first, the pain feels temporary.

"It's fine. We're moving fast." "It's just a messy quarter." "We'll clean it up later."

This is where people build workarounds. And workarounds are a warning sign — they're proof the job matters enough to suffer for.

Think about how many teams used spreadsheets for CRM before adopting Salesforce or HubSpot. They knew the spreadsheet wasn't a real CRM. But it was there, it was free, and everyone understood it. So they added columns. They color-coded stages. They built formulas that only one person understood. The pain was real, but it felt manageable, right up until it wasn't.

2. Taxation

Then the workaround becomes the work.

You're not just doing the job anymore. You're doing the job plus the overhead of managing the system that's supposed to help you do the job. The functional cost grows — more time, more steps, more coordination, more rework. And the emotional cost grows with it — more dread, more cognitive load, more background anxiety.

With the spreadsheet CRM, this looks like a sales manager spending Friday afternoons reconciling deal stages across three tabs, then building a pipeline report by hand because the spreadsheet can't generate one. The tool is still "working." It's also eating hours that should be spent selling.

3. The last straw

Then something happens that makes the pain undeniable.

A miss. A public embarrassment. A major customer escalation. A deadline that exposes the cracks.

This is the moment push stops being "I should fix this" and becomes "I need this to change." If you're selling into teams, this is often the moment the problem becomes social too. It's no longer private frustration. Other people can see it.

Basecamp, the project management tool from 37signals, built its early marketing around this exact moment. Their landing pages didn't list features first. They described the feeling: projects running on email chains, things falling through cracks, nobody knowing what's current. They named the last straw before the user had to.

Push is positive (even when it sounds like a complaint)

When someone tells you what's broken, they're not being negative. They're revealing the job they care about enough to fight for.

A user who shrugs is hard to help. A user who is angry is often close to switching. Anger means they're invested.

Slack's origin is a version of this. Stewart Butterfield's team was building a game called Glitch, and the internal communication tool they'd hacked together for development kept getting more attention than the game itself. The team's complaints about email and IRC were evidence of a job that mattered enough to build around. The frustration pointed directly at the opportunity.

You can't build adoption on apathy. You build it on the moment someone says "this isn't good enough anymore" — and means it.

Push has a rival: status quo bias

If push is so powerful, why do people stay stuck so long?

Because habit isn't just habit. It's status quo bias.

People disproportionately stick with what they already have because they know where the buttons are, they've built workflows around the limitations, they've invested time and training and muscle memory, and switching feels like risk — even when staying is clearly costly.

This is why so many companies stayed on Microsoft Excel for tasks that Excel was never designed for — project management, CRM, inventory tracking, budgeting with twenty stakeholders. Excel is the universal default. It's on every computer. Everyone knows the basics. Switching to a purpose-built tool means learning something new, migrating data, convincing your team, and accepting a period where you're slower before you're faster. For most people, the pain of the current way has to get very loud before that trade-off feels worth it.

This is why push has to climb high before anyone moves. It's not enough for your product to be better. The current way has to start feeling worse.

The Push mistake to avoid

A lot of teams either avoid push or overdo it.

When they avoid it, they lead with aspirational futures. "Work smarter." "Be more productive." "Streamline your workflow." It sounds nice. It doesn't match the user's lived experience. If the user is in a push moment, aspirational language can feel tone-deaf. They don't want a glow-up. They want relief.

When they overdo it, they turn push into fear-mongering. "You're wasting time." "Your data is at risk." "You're leaving money on the table." Push isn't a scare tactic. It's recognition.

The best push messaging doesn't exaggerate. It makes someone feel seen. Compare these two lines:

"Stay organized."

vs.

"Stop losing track of decisions because they're scattered across Slack threads, docs, and meetings."

One sounds like marketing. The other sounds like a real Tuesday.

How to actually use push in product and messaging

Push tells you what someone can't tolerate anymore. That has direct implications for how you build and how you talk about what you've built.

Design for the moment they show up. People often arrive during a spike. They're stressed, they're rushed, they need proof fast. This is not the time to make them explore. Your product has to answer one question immediately: "Can you make this pain stop?" That's why clarity beats cleverness at the top of the funnel, and why fast first value matters more than feature tours. Typeform understood this. When someone searches for "survey tool," they don't want a product philosophy. They want to build a form in the next ten minutes.

Name the pain precisely. Generic pain is ignorable. Specific pain lands. Dropbox didn't say "manage files better." It described the exact moment: you emailed yourself a file because you forgot your USB drive. Mailchimp didn't say "email marketing made easy." It showed a small business owner that they could send a professional-looking newsletter without hiring a designer. The more precisely you can describe the moment your user is in, the faster they recognize themselves.

Let push guide prioritization. Push tells you where users feel the biggest cost. If ten people are using a workaround, that's a signal. If ten people are complaining about the same failure point, that's a signal. Push points to the bottleneck in the job.

But don't treat push as the whole story. Push gets someone to look. It doesn't get them to commit. Push is the shove out of the status quo. They still need pull — a believable better way — plus reduced anxiety and habit barriers before they'll actually switch. But push is where the energy comes from. Without it, the rest of the equation stalls.

If you're trying to understand Push for your product, ask this: "What finally made you start looking for something else?"

Not "what do you want in a product." Not "what features do you need."

But: "What happened that made the current way feel unacceptable?"

That answer is your push. And it's the closest thing you'll get to the truth about why someone might switch.