Roland Butcher grew up in St. Philip, a rural parish on the eastern edge of Barbados. When he came on my podcast, Corey-osity Unleashed, he described Barbados as a small island "of once 166 square miles." Then he said something I keep coming back to.
"I think Barbados per capita has produced more world-class cricketers than anywhere else on the world."
Think about the scale. A plantation parish, twelve kilometers from the capital. And the ambition of the kid growing up there? Not to play for the parish. Not to play for the island. Roland told me he had two ambitions as a boy. One was to be a pilot. The other was to be an international cricketer.
He made it. In 1980 he became the first Black cricketer to play for England.
A kid on a small island measured himself against the whole world. Most software teams I work with measure themselves against the company across the road.

Your rival isn't the one your customer is thinking about
Ask a product team who they compete with and you'll get a list. Three or four companies in the same sector, same price band, same region. Someone keeps a spreadsheet. Every quarter the team checks the spreadsheet and feels fine, because the rival's checkout is slower than yours.
Your customer has never seen the spreadsheet.
Your customer opened a banking app this morning, ordered lunch in three taps, and watched a parcel move across a map in real time. Then they opened your app. They don't compare you to your rival. They compare you to the best thing they touched today.
Baiju Shah, then chief strategy officer at Accenture Interactive and co-lead of the design firm Fjord, gave this a name: Liquid Expectations. Writing in Adweek in 2017, he put it plainly: "Exceptional customer experiences raise the bar every day, and we know the consumer makes little distinction between sectors."
Little distinction between sectors. Your insurance portal is competing with a food delivery app. Your internal HR tool is competing with whatever your staff use on their phones at the weekend. Nobody told them they're in different leagues, and they wouldn't care if you did.
The numbers say experience is the product now
Salesforce surveyed over 13,000 consumers and nearly 4,000 business buyers across 29 countries for the fifth edition of its State of the Connected Customer report. 88% of customers said the experience a company provides is as important as its products or services. Salesforce called it the highest figure it had ever recorded. The same report found 71% of consumers had switched brands at least once in the previous year.
Read those two numbers together. People care about the experience as much as the thing you sell, and they'll leave without much fuss.
Now look at speed, the bluntest measure of experience there is. In 2018 Google published new industry benchmarks for mobile page speed. Its research found 53% of mobile site visits leave a page taking longer than three seconds to load. A neural network trained on bounce and conversion data found the probability of a visitor bouncing rises 123% as load time goes from one second to ten.
Your rival's slow page doesn't give you permission to have a slow page. Someone you never put on the spreadsheet set your customer's patience.
I'm not sure about this part: the Google figures date from 2017 and 2018 and come from Google's own analysis with SOASTA. I couldn't find a newer public study with the same method, so treat the exact percentages as a snapshot, not a law.

Engineering teams benchmark locally too
This isn't only a product problem. Look at how engineering teams judge themselves.
"Our deploys take two hours, but the last place I worked took a day." "Our incident response is fine, we're faster than the team on the third floor." "Our onboarding takes six weeks, which is normal round here."
Normal round here. Three of the most dangerous words in a planning meeting.
Every one of those comparisons uses a local yardstick. The previous job. The team down the corridor. The other firm in the same business park. Meanwhile, somewhere in the world, a team half your size ships to production twenty times a day, onboards a new engineer in a week, and publishes how they do it for free.
The same goes for the tools you build for your own staff. Your engineers use the best developer tools in the world on their side projects at the weekend. On Monday they log into your internal deploy dashboard, wait forty seconds for it to load, and click through four screens to restart a service. They notice. They don't compare your dashboard to the one at their last job. They compare it to the tools they chose for themselves, and they draw conclusions about how much the company values their time.
Your internal users have liquid expectations too. They aren't allowed to switch brands. Some of them switch employers instead.
I've sat in plenty of rooms where a team defended a slow process because it beat the local average. Nobody in the room had looked further than the local average. Comfort feels like competence when your reference point is small.
How to stretch your team's frame of reference
You don't need a travel budget to fix this. You need to change what your team compares itself against.
Rewrite the competitor list
Take your competitor spreadsheet and add a second column. Call it "who sets our customer's expectations." Put the best apps and services your customers use in there, whatever sector they sit in. Review the new column every quarter, not the first one.
Use your own product like a stranger
Pick a task your customers do every day. Time it on a cheap phone over a weak connection. Then do the same task in the best app you know. Put both timings on a slide. Nothing changes a roadmap conversation faster than a stopwatch.
Benchmark against published practice, not neighbors
Plenty of excellent engineering organizations write openly about their deploy pipelines, incident reviews and onboarding. Assign one engineer a month to read one of those write-ups and present what your team would steal. The goal isn't to copy. The goal is to see where the bar sits outside your building.
Hire and listen to people from elsewhere
The engineer who joined from a different industry, a different country or a different size of company carries a different yardstick. Ask them, early and often, what looks odd to them. In month six they'll have adjusted to your normal and the question will stop working.

Look past the building across the road
Roland didn't know anywhere else when he was a boy in St. Philip. He told me his ambition was to play for the West Indies, because the West Indies was all he knew. And still the target in his head was international. The island was small. The yardstick wasn't.
Your team has the opposite problem. You have access to more of the world than any generation of engineers before you, and you still compare yourselves to the people next door.
Roland's book, Breaking Barriers, tells the rest of his story. If you want to hear him tell it, find him at rolandbutcher.co.uk.
So here's my question for your next team meeting. Who sets your customer's expectations? If the answer is a company in your own sector, look again.