Your Real Competitors Aren't Who You Think They Are

Asana's biggest competitor isn't Monday.com. It isn't Jira. It isn't ClickUp. It isn't even  whatever just launched on Product Hunt with a slick landing page and an AI angle.

Asana's biggest competitor — for a huge portion of the people who might hire it — is a Google Sheet called "Project Tracker" that someone on the team built two years ago and everyone maintains because it's good enough.

For another portion, it's the Monday morning standup meeting. Not a product. A ritual. Fifteen minutes where everyone says what they're working on, what's stuck, and what they need. It's inefficient. It doesn't scale. It has no dashboard. But it produces alignment, and alignment is what the job actually requires.

For another portion, it's a Slack channel. #team-updates. Pinned messages for priorities. Threads for decisions. It's chaotic and unsearchable and nothing is a source of truth — but the team is already there, so the coordination happens where the people already are.

None of these show up on a feature comparison grid. None of them have pricing pages. None of them would surface in a competitive analysis that starts with "who else is in our category?"

And all of them are potential reasons people might not switch to Asana. Or switch and go back to their old solution.

If you want to understand your competitive landscape, you have to stop asking "who else is in our category?" and start asking "what else gets hired for this job?"

Feature Grids Miss the Point

Feature comparison grids assume that products compete because they look similar. You line up competitors across the top, list capabilities down the side, and color-code until the answer feels obvious.

The conclusion is always some version of: "We're behind on X. We need parity on Y. They have Z, so we should build Z."

That's building a roadmap based on someone else's product decisions — without knowing whether any of those features are the reason people hire them.

Products don't compete just because they share a category label. They compete because they get hired for the same job.A project management tool competes with the spreadsheet, the standup meeting, the Slack channel, the team lead who routes everything manually, and the decision to tolerate the chaos and do nothing. Those alternatives have two advantages: they're already embedded in habits, and everyone already knows how they work.

If your competitive analysis doesn't include them, you'll keep misreading why people don't switch, why they churn, and why "objectively better" isn't winning.

The Job Defines the Competitive Set

The first move is to define the job in specific enough terms that the real competitive set becomes visible.

"Manage projects" is a category description. It produces a competitive set of other project management tools. That's not wrong — it's just incomplete. And the incomplete part is where you're actually losing.

"When our work is scattered across conversations and docs, I need one place to see what's happening, what's stuck, and who owns what — so nothing slips and I don't get surprised in front of leadership."

Now the competitive set changes. Because anything that helps someone achieve that outcome — see what's happening, know what's stuck, avoid being surprised — is a competitor. Whether it's a product, a meeting, a spreadsheet, or a person.

And each of those competitors serves the job with a different tradeoff profile:

The spreadsheet is flexible, universally understood, and fast to modify. Its weakness is reliability at scale — version chaos, manual updates, no true source of truth, and fragile ownership. But it does exactly what the local team needs without asking anyone to change their world.

The Slack channel is where people already are. It supports fast coordination. Its weakness is memory — decisions get buried, context evaporates, and "what's the current state?" becomes a scavenger hunt. But the switching cost is zero because the team is already there.

The standup meeting forces alignment through ritual. Its weakness is latency — problems surface too late, and progress depends on the meeting continuing forever. But it creates accountability without requiring anyone to learn a tool.

Doing nothing is the most underestimated competitor because the status quo is tolerable and switching feels harder than suffering. If the job isn't intense enough, or if the product increases anxiety, people won't switch even when you're objectively better.

Each of these tells you something a feature grid never could: what tradeoff the user is currently accepting, and what you'd have to offer to make them stop accepting it.

Your Real Competition

When you see the competitive set through the job lens, the basis of competition shifts from features to something more fundamental: what's keeping the user from switching?

Every adoption decision involves a tug of war. On one side, there's frustration with the current solution 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. A user switches when the frustration and the pull outweigh the habit and the anxiety. They stay when they don't.

Your real competition isn't another product's feature list. It's whatever combination of habit, comfort, and anxiety is keeping the current alternative — spreadsheet, meeting, Slack channel, doing nothing — hired for the job.

If the spreadsheet keeps winning because it's immediate and flexible, your product needs a path to a real win in minutes — not after a week of setup and configuration. The spreadsheet's advantage is zero switching cost.

You have to make your switching cost low enough to overcome that, while delivering something the spreadsheet can't: reliability, shared visibility, and confidence that nothing is falling through the cracks.

If Slack keeps winning because the team is already there, you won't beat it by adding chat. You beat it by making coordination possible while also making state durable so the team gets the fast back-and-forth they want without losing decisions to the scroll.

If the meeting keeps winning because it creates accountability, you beat it by making accountability visible continuously so the meeting becomes unnecessary, not "more efficient."

If doing nothing keeps winning because the job isn't intense enough, that's not a competitive problem. That's a market selection problem. The job might not be desperate enough to sustain a product.

The competitive advantage isn't more features. It's understanding why the incumbent keeps getting re-hired — and building an experience that makes switching worth it despite those reasons.

The Hidden Battle: Progress vs. Switching Cost

Every alternative the user currently hires has two values: the progress it provides and the switching cost it avoids.

Incumbents — especially informal ones like spreadsheets, meetings, and Slack channels — are rarely beloved. They're familiar. They're controllable. They're understood. They feel safe.

When you analyze competitors through the job lens, you're analyzing two battles at once: can you outperform them on progress, and can you outperform them on perceived risk and switching cost?

If you only analyze progress, you'll keep saying "we're better" while users keep saying "I'm not ready." The force balance has to tip. Frustration with the old way and the pull of the new way have to outweigh the comfort of familiar habits and the anxiety about switching.

This is where the JTBDUX lens changes competitive analysis from a product comparison into a design problem. The question isn't just "is our product better?" It's "does our experience make the switch feel safe enough that the progress advantage actually matters?"

Does the onboarding reduce the anxiety of abandoning the familiar system? Does the first-use experience deliver a win before the motivation fades and the spreadsheet pulls them back? Does the product speak the language of the job — not the language of the category?

A product can be better on every feature dimension and still lose to a spreadsheet if the experience of switching feels riskier than the pain of staying.

How This Changes Your Strategy

When you map your competitive landscape by job instead of by category, the strategic moves become clearer.

You stop chasing feature parity with category competitors, because feature parity with Monday.com doesn't help you if the user's real alternative is a Google Sheet. You start designing experiences that address the specific tradeoff the user is currently accepting with their current hire.

You stop positioning against other products and start positioning against the status quo, because for most potential users, the status quo isn't a competing product. It's the cobbled-together system they've already built, and the switching cost of leaving it is emotional and organizational, not financial.

You stop asking "what features do they have that we don't?" and start asking "why does the user keep re-hiring this alternative, and what would our experience need to feel like to change that decision?"

That's competitive analysis that actually changes what you build, because it shows you what the experience needs to do to win the hiring decision against the alternatives that are actually in the running.