.png)
What Customers Say They Want Is Often Wrong
When you ask customers what they want from your website, they lie. Not intentionally. They just don't know.
A customer survey might say: "We want a modern, clean design with better features." What they actually need is faster checkout and clearer product information. They don't know to ask for those things.
This gap between stated preference and actual behaviour costs NZ businesses tens of thousands annually.
The Psychology Behind What Customers Actually Want
Customers don't want features. They want outcomes. They don't want a "new website design." They want more sales, fewer customer service issues, and less time managing operations.
When they say "modern design," they often mean "I don't want to look outdated compared to competitors." The actual need isn't modern. It's competitive.
When they say "more features," they often mean "I have a problem I can't solve with what I have." The actual need isn't features. It's a solution to that specific problem.
Most brands respond to the stated want, not the underlying need. That's why so many new websites disappoint. They deliver what was asked for, not what was needed.
The Behaviour vs. Stated Preference Problem
What Customers Say vs. What They Do
Survey says: "I want product recommendations based on my browsing history."
Actual behaviour: 60% of customers find personalization creepy. They want recommendations, but not ones that prove you're tracking them closely.
Survey says: "I want detailed product specifications."
Actual behaviour: 70% of customers read fewer than 50 words of product description. They scan. They want the key information in a sentence.
Survey says: "I want easy access to customer service."
Actual behaviour: 80% of customers never contact support. They want to solve problems themselves, fast.
Build what customers say they want and you'll miss what they actually need.
How to Find What Customers Actually Want
Watch What They Do, Not What They Say
Look at your analytics. Which pages get the most time? Which product pages have the lowest bounce rate? Which categories get browsed most?
That's where actual interest lives. Build more of that. Ignore what customers said they wanted.
A NZ e-commerce store launched after customer feedback asking for "more brand story content." Analytics showed 95% of visitors skipped the brand story and went straight to product pages. The story was beautiful. Nobody read it. Removing it improved conversion by 8%.
Listen to Support Conversations
What do customers ask support about most? That's your most critical user need.
If 40% of support questions are "Do you ship to Australia?", put that answer above the fold on the homepage. That's a real need. That's where friction lives.
If customers are asking "What's the return policy?" fifty times, put it in the main navigation, not buried on a policy page.
Run Small Behaviour Tests
Don't ask customers what they want. Show them options and track which they choose.
Test A: Product page with 200-word description
Test B: Product page with 50-word description plus specs table
Track conversion. One will win. That's the real preference. Not what they said. What they did.
The Mistakes Brands Make Acting on Wrong Assumptions
Overcomplicating Based on Feature Requests
A customer says: "I want to filter products by multiple attributes at once." That sounds reasonable. But analytics show filters have a 2% usage rate. Most customers use the search bar.
Building complex filters based on one customer's request wastes dev time and clutters the interface for 98% of customers who don't want it.
Adding Features Nobody Asked For But Customers Don't Want
You add live chat because it's trendy. Users ignore it. It slows page load. Conversion drops 3%.
You add "social proof" widgets showing customer purchases. Users find it intrusive. It adds friction. They leave.
You add product recommendations. Users feel tracked. They leave faster.
None of these were asked for. None of them improved outcomes. But they felt like the right thing to do based on industry trends.
Not Addressing the Real Bottleneck
Customer: "I need a better checkout experience."
You redesign the entire checkout flow.
Actually: customers are abandoning at the shipping cost screen. They see NZD 45 shipping and leave. The real fix: offer free shipping over $150. The checkout process was fine.
You solved the wrong problem because you acted on stated preference instead of analysing actual behaviour.
How to Know What Actually Matters
Rank your potential changes by:
Impact potential: How much revenue could this change create or save?
Evidence: Do you have data showing this is actually a problem?
Effort: How much work is this?
Pursue changes with high impact, strong evidence, and low effort first. Ignore changes with vague evidence, "nice to have" impact, and high effort.
If customers say they want it but you have no data showing it's a problem, it doesn't go in the queue.
For NZ businesses making strategic website changes, stop asking customers what they want. Instead, watch what they do. That's the truth. That's where revenue lives.
