A few weeks ago, I was getting my daughter a bank card and her first question was whether I would get her one that was as pretty as mine.

I remember finding that interesting. I don’t think I had ever looked at my bank card and considered whether it was pretty. Functional, yes. Does it work when I tap it? Can I use it online? Does it decline at an inconvenient moment and force me to start mentally calculating whether I have somehow spent all my money? These are the things I tend to ask of a bank card. But she cared about how hers looked.

And why shouldn’t she? We personalise almost everything else. Our phones, watch faces, laptop covers, even the backgrounds on apps we use every day. A bank card is something you carry around and use regularly. There is no reason its design shouldn’t matter too.

It got me thinking about how products sometimes become more than the original job they were designed to do. A bank card exists to give you access to your money, but how it looks can still be part of the experience. The fact that she thought it was pretty wasn’t frivolous. It was one of the reasons she liked it.

Then, a little while later, I noticed she had gone back to her old card. It turns out the new one has several restrictions. She can’t add it to her digital wallet, and she doesn’t like the idea of carrying a physical card around all the time (pretty or otherwise) . Eventually, that became inconvenient enough that she reverted to the old one.

So I asked her, “So what does that tell you about pretty products that are not functional?”

I left it there as food for thought for her, but I kept thinking about it myself.

The obvious lesson is that a product has to work. You can make something beautiful, personalise it, package it brilliantly and create all sorts of reasons for people to want it, but if it doesn’t do what they need it to do, they will stop using it. But there was something else about her behaviour that I found more interesting.

She hadn’t complained about the card. There was no strongly worded email. No customer survey explaining that the product wasn’t meeting her needs. No call to customer service. She actually admitted that she still likes the pretty card. She just finds it too restrictive, so she stopped using it.

And I wonder how much customer feedback looks exactly like that.

We tend to think of feedback as something customers give us deliberately. They answer a survey, leave a review, call to complain or speak to a salesperson. They tell us what they like, what they don’t like and what they wish we would change. But customers are also telling us things all the time without saying a word.

They choose one product and then barely use it. They use a feature differently from how we intended. They create their own workaround for a process we think works perfectly well. They keep calling about something we believe we have already solved. They buy once and don’t come back. They stay with us but quietly move part of their business somewhere else.

Or they go back to the old card.

The interesting thing is that these behaviours can be easy to misread. If lots of people choose a new product, we celebrate the uptake, and rightly so. Something made them choose it. But what happens afterwards tells us something else. Do they keep using it? Which parts do they use? Where do they find another way around? At what point does something we considered a small inconvenience become important enough for them to change their behaviour?

It has also made me think differently about complaints. We often treat fewer complaints as a sign that things are going well. Sometimes they are. But a customer who isn’t complaining isn’t necessarily a happy customer. Sometimes they have simply found another solution or moved their business elsewhere. Or every time they try to raise a complaint, they enter an endless loop with a chatbot and end up regretting the time they wasted more than the original issue.

That is a much quieter form of feedback, and possibly a more dangerous one, because nobody has opened a ticket for us to resolve. Nothing has turned red on a dashboard. There is no angry email demanding attention. From inside the business, everything can look fine while the customer is slowly changing what they do.

The reverse is interesting too. Customers sometimes complain loudly about things and continue using the product anyway. There are things we say annoy us but apparently not enough to change our behaviour. There are features we insist are important and then rarely use. There are things we say we would happily pay for until somebody actually asks us to pay for them.

None of this means we should stop asking customers what they think. What people tell us matters. Their reasons matter. Context matters. Behaviour on its own can be misinterpreted too. But listening to customers is bigger than asking them questions. It is also paying attention to what happens after the conversation.

And I don’t think this only applies to paying customers. We have internal customers too. The people who use the processes, systems, reports and tools we build are constantly giving us the same kind of feedback. We train them, launch the new thing and explain how much better it is supposed to make their lives. Sometimes they tell us when it doesn’t work. But sometimes they don’t. They build a spreadsheet, add three manual steps nobody designed, keep the old tracker somewhere “just in case,” find the one person who knows how to get around the system, or quietly stop using the thing we spent six months building.

From one perspective, we can call that resistance to change, and sometimes it is. People resist perfectly good changes too. But sometimes the workaround itself is feedback. The old spreadsheet sitting stubbornly on someone’s laptop may be telling us something our adoption dashboard isn’t.

I find that particularly interesting because organisations put a lot of effort into designing how work should happen. We map the process, build the tool, define the standard and measure adoption. All of that matters. But there is also something to learn from the distance between the process we designed and the behaviour that emerges around it. If people repeatedly find another way to get something done, I want to understand why.

Maybe they haven’t understood the new process. Maybe we haven’t made the change well enough. Maybe the old habit is simply hard to break. But maybe they have found a gap that wasn’t obvious to the people who designed it. You don’t know which one it is until you get curious about the behaviour rather than simply trying to eliminate it.

I think the same curiosity is useful with external customers. What are they doing with the product once it is actually in their hands? Not only whether they bought it, whether they said they liked it or whether they gave us a good score, but how it fits into the reality of their lives. Where do they adapt it? Where do they abandon it? Where do they quietly choose something else?

My daughter still liked the pretty card. That part of the feedback hadn’t changed. She just didn’t use it. And if I were looking only at what she said she liked, I would have missed half the story. Because sometimes the clearest feedback isn’t what the customer tells you. It’s what they do next.


Leave a Reply

Your email address will not be published. Required fields are marked *