top of page

Stop Building Products for Your Customers

Writer: Paul Johns
Paul Johns
Sep 18
5 min read

I’ve spent a lot of my career around companies that would describe themselves as customer-centric. And, to be fair, most of them genuinely are. They care about their customers. They invest enormous amounts of time trying to understand them. We create advisory boards, run research, conduct interviews, measure satisfaction, map journeys and sit through hours of conversations about customer needs.

But I’ve increasingly found myself questioning something about the way we do all of this.

We spend an extraordinary amount of time listening to customers, and then we go away and build things without them.

There is something slightly strange about that when you think about it. We ask people what they need, take that information back inside the organization, interpret it through the lenses of product, marketing, technology, finance and commercial priorities, and then months later return with something and proudly say: we built this for you.

And sometimes we absolutely get it right.

But sometimes we build something that answers the question we thought the customer was asking rather than the problem they were actually trying to solve.

I’ve seen this many times over the years. A customer describes a frustration. They explain how they work, where something slows them down, where information disappears between systems or where they have created some slightly ridiculous workaround that everybody has simply learned to live with. We take that information away and translate it into requirements, features and roadmaps. By the time it eventually comes back to the customer, something has been lost in translation.

The feature works. The technology works. The launch goes well.

That, to me, is where the interesting conversation begins.

Because I think we need to move beyond the idea of simply building products for customers and become much more comfortable building products with them.

This isn’t about turning customers into product managers or allowing every individual request to dictate a roadmap. In fact, I think that would be equally dangerous. Customers don’t necessarily know what the answer should be, and nor should we expect them to. But they understand the problem in a way that we often can’t because they are living inside it.

There is a huge difference between asking somebody what they want and watching how they actually work.

Where do they leave your platform? What do they download? What do they put into Excel? What do they email to somebody else? What information are they combining manually? What have they stopped complaining about because the workaround has simply become part of their working day?

I find those questions fascinating because that is often where the real product opportunity is hiding.

The irony is that we have never had more data about our customers, and yet sometimes I wonder whether we have become slightly more distant from them. We can measure almost everything. We know what people clicked, how long they stayed, what they opened, what they downloaded and where they dropped out. We can create incredibly sophisticated pictures of customer behavior without ever actually sitting beside somebody and asking: what are you trying to do?

And perhaps more importantly: why are you having to do it this way?

There was a time when building in isolation made more sense. Product cycles were longer. Technology moved more slowly. Vendors often had access to information and expertise customers simply didn’t possess. You could spend a year building something, unveil it and reasonably expect the market to wait.

That world has gone.

Customers are experimenting themselves now. They are using AI, combining tools, creating workflows and finding answers before many organizations have finished writing the business case. The distance between somebody recognizing a problem and expecting an answer has collapsed.

Which means our relationship with customers has to evolve as well.

I think the first evolution is from listening to participating.

Bring customers closer. Show them things before they are perfect. Let them see the thinking. Put prototypes in front of them. Let them challenge assumptions. Allow somebody to tell you that the feature everybody internally loves isn’t actually particularly useful.

That can be uncomfortable. I’ve been in enough rooms to know how difficult it is when a team has spent months creating something and a customer punctures the excitement with one very simple question.

“But why would I use this?”

It can feel brutal.

But I would rather hear that question three weeks into development than eighteen months later when we’ve built the thing, launched the campaign, trained the sales team and discovered that nobody particularly wants it.

There is something else that happens when customers participate, though, and I think this is perhaps even more important.

They begin to care about the outcome.

There is a subtle psychological difference between being shown something and being part of creating it. When somebody has contributed an idea, challenged an assumption, tested an early version or watched something improve because of their feedback, there is a little bit of them in the finished product.

It isn’t simply something you’ve sold them anymore. It’s something they helped shape.

And that creates a form of connection that no customer marketing campaign can manufacture afterwards.

But participation isn’t the destination either.

Because if we work closely enough with customers, if we understand their world deeply enough and if we stay close enough to the problems they are trying to solve, something much more interesting starts to happen.

We begin to anticipate. And for me, that is the real opportunity.

The best customer relationship isn’t one where I repeatedly ask you what you want me to build next. It’s one where I understand your business, your pressures and your ambitions well enough that occasionally I can see the problem coming before you’ve even articulated it.

It means understanding not simply what customers are asking for today, but what is changing around them. Regulation. Technology. Economics. Competition. Expectations. The way their own customers are behaving. The decisions they are going to have to make six months from now that they perhaps haven’t even started thinking about yet.

And suddenly product development becomes something much bigger than a roadmap.

It becomes a continuous conversation between what customers are experiencing today and what we believe they are going to experience tomorrow.

That is the progression I keep coming back to.

We listen long enough that we begin to participate. We participate deeply enough that we begin to understand. And eventually, if we really understand, we begin to anticipate.

That, to me, is what customer-centricity should actually mean.

Not another survey. Not another advisory board where we present forty slides and leave ten minutes for questions. Not another journey map pinned to a wall somewhere.

It means collapsing the distance between the people building the product and the people living with the problem.

Because customers don’t always know what product they need. But they almost always know where it hurts and our job is to stay close enough to understand why.

So maybe we should stop asking ourselves what we are going to build for our customers and start asking a much more interesting question. What could we build together?

Originally published by Paul Johns on LinkedIn.

Comments


bottom of page