Evolving Markets and User Expectations

Your product is not judged against your competitors. It is judged against whatever the person used ten minutes before they opened it, which is usually not in your category at all.

That is why "we are better than the other tools in our space" stops being a defence. The baseline moves because of products you have never heard of, in markets you do not sell into, and it moves whether or not anyone in your industry notices.

Quick Summary (Key Takeaways)

• Expectations transfer across categories. A logistics dispatcher who banks on a phone expects your dispatch screen to behave like the bank did.
• The baseline moves without an announcement. Nobody tells you the standard changed; you find out through support tickets and churn.
• Speed of understanding beats speed of loading. Users forgive a slow page and abandon a confusing one.
• Most "market shifts" are fads. A shift changes what users expect by default; a fad changes what they will tolerate once.
• Support tickets are the earliest signal you own. Cheaper than research and available today.
• Audit quarterly, not annually. A year is long enough for a baseline to move past you twice.

Where Expectations Actually Come From

Not from your market. From four places, in rough order of influence.

• The consumer products everyone uses daily. Messaging, banking, maps, streaming. These set the floor for what "working normally" means, and they are updated constantly by teams larger than yours.
• The last tool the user was forced to learn. If their previous system was worse, you get credit you did not earn. If it was better, you inherit a complaint on day one.
• Their own phone. Enterprise buyers stopped accepting that work software is allowed to be worse than personal software somewhere around the mid-2010s, and the tolerance has kept falling.
• Whatever their peers are showing off. In B2B this travels through conference demos and group chats faster than through any analyst report.

None of these are visible in a competitor analysis, which is why competitor analysis keeps missing the thing that hurt you.

Four Shifts That Reset the Baseline

These are not predictions. They are changes that have already landed, and products that have not absorbed them now read as dated.

1. An Answer Is Expected Where a Search Box Used To Be

People have been retrained to ask a question and receive an answer, not a list of results to work through. A product that responds to a query with twelve rows and a filter panel now feels like an older generation of software, even when the rows are correct.

This does not mean bolting a chat box onto everything. It means the interface should carry more of the interpretation, and the user should carry less.

2. Setup Is Something You Do Later, Not First

The expectation that a product is useful before it is configured came from consumer software and has fully crossed into work tools. Long onboarding wizards read as a signal that the product will be hard forever.

Products that survive this show value on a partial account, with sample data, and ask for the rest when the user has a reason to give it.

3. Operations Moved to the Phone

Not the whole product, but the part somebody needs while standing up: approve, check status, reassign, respond. Categories that assumed a desk are being judged by whether the urgent five percent works on a phone in a warehouse or a car park.

4. Pricing Is Expected To Be Visible

Buyers now treat a hidden price as information about the seller rather than a normal step in a sales process. Some enterprise categories still get away with "contact us", and the number that do is falling every year.

How To Tell a Shift From a Fad

Chasing fads costs more than missing them. Three tests separate the two.

• Did it change the default, or add an option? A shift becomes what people expect without asking. A fad is something a subset asks for loudly.
• Did it cross a category boundary? Things that spread from consumer to work software, or from one industry to another, are usually structural. Things that stay in one vertical are usually fashion.
• Does it survive a recession? Fads are funded by good years. If the behaviour persisted through a downturn, it is a shift.

What To Do About It

Four practices, in increasing order of cost.

• Read your support tickets as market research. Every "why can't I just" is a user importing an expectation from somewhere else. That is a free, continuous signal about where the baseline moved, and almost nobody mines it.
• Watch adjacent categories, not competitors. Once a quarter, look at what the best product your users touch daily is doing. That is the standard you are being held to.
• Measure time to first value, not feature count. How long from arriving to the product having done something useful once. It is the number that expectations bite hardest.
• Run a quarterly expectation audit. An hour with the core flow, someone who has not seen it in a month, and one question: which step would feel dated to someone who used a good consumer app this morning.

What It Costs To Ignore

The damage does not arrive as a dramatic loss. It arrives as drift: activation slipping a point a quarter, sales calls needing one more demo, a rising share of churn that exits saying nothing was wrong exactly.

That last one is the tell. Users rarely say "your product feels five years old". They say it was fine, they just moved on. By the time it shows up in a number large enough to argue about in a board meeting, the fix is a redesign rather than an adjustment.

Frequently Asked Questions

How often do user expectations actually change?

Continuously and unevenly. The floor for basic interaction moves every year or two; the expectations attached to a specific workflow can sit still for a decade and then move all at once when a large product changes how it does that one thing.

Should we copy what the market leader does?

Copy the behaviour, not the interface. The leader's layout is tuned to their scale and their users. What transfers is the expectation their product created, not the way they satisfied it.

How do we know a change is worth making?

Tie it to one number before you build: activation, time to first value, tickets of a particular kind. If nobody can name the number the change should move, it is a preference argument wearing a strategy hat.

Is this a design problem or a product problem?

Both, and it fails when they are treated separately. The expectation shows up in the interface, but satisfying it usually means changing what the product does first, then how it looks.

Where should a small team start?

Support tickets this week, time to first value this month, one adjacent product a quarter. That is most of the value for almost none of the budget.

Conclusion: Watch the Products Your Users Actually Use

Your competitors are the wrong reference. The right one is whatever your users open on their phone at breakfast, because that is what set the standard they will hold you to at nine.

Watch that, read your tickets, and measure how fast a new person gets something out of your product. Three habits, no budget, and they catch most of what would otherwise arrive as a redesign in two years.

If the drift has already happened and the product feels dated, a UX audit is the cheapest way to find out how far. If you would rather compare who could do it, we keep an honest list of UX design agencies.