The Customer Is Already Talking. Are You Listening?

You get a message from a customer. A complaint, maybe. Or a weird request. You read it, think "noted," and move on.

That moment — that small, forgettable moment — is where most businesses quietly lose.

Not because the complaint was fatal. Because the signal inside it was real, and nobody did anything with it.

Sam Walton used to walk his own store floors. Not to look busy. To listen. He'd talk to customers directly, write notes on yellow legal pads, and bring what he heard straight back to his team. The guy running one of the most successful retail operations in history thought listening to customers was still the job.

"There is only one boss. The customer. And he can fire everybody in the company from the chairman on down, simply by spending his money somewhere else."

— Sam Walton

That line isn't a motivational poster. It's a description of how money actually moves.

The Gap Most Builders Ignore

Founders are usually good at building. They're fast, they're creative, and they have opinions about what the product should do. That's exactly what makes this hard — your own conviction can drown out the customer's voice without you noticing.

So the feedback sits in a support thread. The churn goes unexplained. The feature nobody uses stays on the roadmap.

And you keep building based on what you think people want, instead of what they're already telling you they need.

The cost is quiet. You don't feel it until suddenly growth stalls or a competitor shows up doing the thing your customers kept asking for.

What This Looks Like in Practice

Walton's move wasn't complicated. He just got close. He removed the layers between himself and the person spending money.

That's the thing to try this week. Pick five customers — recent ones, not the biggest ones, just real ones — and read every word they've sent you. Support tickets, reviews, replies, whatever. Don't analyze it yet. Just read it the way Walton walked the floor: curious, not defensive.

You'll find at least one thing that surprises you. Probably something small. A word they keep using, a job they're trying to do that you didn't design for, a frustration they mentioned once and then stopped mentioning.

That's the signal.

In Signals, this is exactly the kind of thing worth dropping into your weekly reflection — not a big insight, just a honest answer to "what did I actually hear this week that I didn't want to hear?"

The answers to your hardest business problems are usually already in your inbox. Someone wrote them down for you. They just need you to actually read them.