A team starts its strategy with a market map. Competitor A has this feature. Competitor B charges less. Competitor C serves the enterprise. So the team sharpens the feature set, polishes the story, and makes the comparison look favorable.
Meanwhile, the team keeps losing to the trusty spreadsheet its customers have used for the last five years. What would moving their work actually cost them? Which familiar habits would they lose? What would make switching to a new solution feel safer than staying? That choice gets made long before anyone reads the comparison.
The decision to change comes before the product comparison
Comparison work helps once someone has decided to buy. It does almost nothing for the harder decision that comes first: whether changing is worth the disruption. Products don’t compete just because they share a category label. They compete because they get hired for the same job.
The real competitor is usually a shared spreadsheet everyone complains about, a weekly meeting nobody likes, an assistant who knows the workaround, a patchwork of tools, a process held together by memory, or the decision to tolerate the chaos and do nothing. It’s inefficient, but it’s known. People understand its failure modes. They know where to look when it breaks. They’ve built habits around it.
A new product doesn’t enter a blank space. It asks people to abandon what they’re already doing today—even if it’s suboptimal.
Pain doesn’t automatically create movement
Teams often assume obvious pain creates demand. It doesn’t. People can live with astonishing amounts of friction when the alternative feels risky.
Every adoption decision involves a tug of war. On one side, there’s frustration with the current way and the pull of something better. On the other, there’s the comfort of familiar habits and the anxiety that switching might not be worth it—or might make things worse. People switch when the frustration and the pull outweigh the habit and the anxiety. They stay when they don’t. Those are the four forces: Push, Pull, Habit, and Anxiety.
Most product messaging invests everything in Pull: faster, smarter, simpler, powered by AI. Meanwhile, people’s habits and anxieties make it harder for them to switch, and the messaging never answers them. Who migrates the data? Will the result be reliable? Will the team look foolish if the change fails? Why people stay when the pain is obvious takes these questions one at a time.
Fill-in table
Four forces
Answer these before you plan a feature or write the message; the answers show whether you need more Pull or less Habit and Anxiety.
| Force | Direction | Questions to ask yourself |
|---|---|---|
| Push | Away from the status quo | What frustration with the current way makes people consider leaving? |
| Pull | Toward a brighter future | What brighter future can they picture? |
| Habit | Keeps people in the status quo | What do people already know how to do, and who do they do it with? |
| Anxiety | Keeps people in the status quo | What perceived pain of adopting something new makes the switch feel risky? |
A product can be better on every feature dimension and still lose to the spreadsheet a team already relies on if the experience of switching feels riskier than the pain of staying.
The workflow people tolerate holds value you have to keep
Sometimes the status quo is doing nothing at all. Doing nothing is the most underestimated competitor because the status quo is tolerable and switching feels harder than suffering. If it keeps winning because the job isn’t intense enough, that’s not a competitive problem. It’s a market selection problem.
Don’t define the status quo as “they use another product.” A normal workday reveals the tools, handoffs, and workarounds people depend on. A realistic day of use makes those details concrete.
The details expose what the replacement must preserve as well as what it should improve. A shared tracking spreadsheet may be ugly, but it’s transparent. A manual process may be slow, but everyone knows who owns it. A meeting may waste time, but it gives leaders confidence that nothing slipped through.
Example
A project tracker nobody wants to give up
For many teams, the real alternative to a project management tool is a spreadsheet called “Project Tracker” that someone built two years ago and everyone maintains because it’s good enough. For others, it’s a fifteen-minute weekly standup where everyone says what they’re working on, what’s stuck, and what they need.
- Push: Project Tracker’s weakness is reliability at scale: version chaos, manual updates, no true source of truth, fragile ownership. In the standup, problems surface too late.
- Pull: one place to see what’s happening, what’s stuck, and who owns what, so nothing slips and nobody gets surprised in front of leadership.
- Habit: Project Tracker is flexible, universally understood, and fast to modify. Everyone already knows how it works.
- Anxiety: Not known yet: What makes switching away from Project Tracker or the standup feel risky?
- Value to preserve: Project Tracker does exactly what the local team needs without asking anyone to change their world. The standup creates accountability without requiring anyone to learn a tool.
Fill-in table
Map the workflow people actually tolerate
Map the steps people rely on, then name what each step still provides—such as visibility in a shared spreadsheet or accountability in a meeting.
| What to ask | What the current step still provides |
|---|---|
| What happens first, and which tools are open? | What familiar starting point does this give people? |
| Where does someone copy information by hand? | What control or visibility does the manual step preserve? |
| Who gets asked for help? | What knowledge or reassurance does that person provide? |
| What gets checked twice? | What risk are those repeated checks meant to prevent? |
| Which failure is normal enough that nobody logs it? | What lets the team keep working despite it? |
| What part is annoying but socially safe? | Does it provide control, familiarity, visibility, or political safety? |
| What happens if they do nothing at all? | What effort, risk, or decision does doing nothing spare them? |
Replace the visible task while ignoring what people rely on, and the new product creates fresh anxiety.
The switch needs as much design as the destination
A better future needs a believable bridge.
Start with a narrow trigger moment where the current way becomes newly unacceptable, such as when version chaos makes the team’s shared tracker unreliable or a standup surfaces problems too late. Offer a first step that’s easy to evaluate and easy to reverse. Preserve familiar objects and language long enough for recognition to form. Let people compare before and after. Make the cost of trying smaller than the cost of staying.
The first experience shouldn’t ask users to believe the whole roadmap. It should prove one meaningful improvement while keeping their escape route visible. Before the first successful job, value is a promise. After it, the user has a memory of the product helping.
That’s why “book a demo” is often too large a first ask. The user hasn’t decided to change yet. Give them a calculator, a diagnostic, a realistic prototype, a small imported sample, or one finished result. The first yes should be small and reversible.
A practical status-quo audit
If you can describe your feature set more clearly than the behavior you’re replacing, you’re not ready to compete. The market isn’t waiting for a better product comparison. It’s waiting for a reason to leave the devil it knows.
Before deciding what to build or say:
0 of 6 done
