One thing I learned while building software...

ShahrozS · Jul 22, 2026

I used to ask businesses, "What features do you want?"

Most gave a long wishlist.

But when I asked them, "What's the most frustrating part of your workday?" the answers were completely different.

The real problems weren't missing features. They were repetitive manual tasks, scattered information, and constantly chasing updates.

Since then, I've spent more time understanding workflows than collecting feature requests.

Has anyone else experienced this with clients or their own products? Sometimes the problem people describe isn't the one they actually need solved.

Israeliod · Jul 23, 2026

I completely agree. I've found that clients often ask for features because they think that's the solution, when the real issue is usually an inefficient workflow or a repetitive process. Asking about their biggest day-to-day frustration tends to uncover much more valuable insights and often leads to simpler, more effective solutions.

medialounge · Jul 23, 2026

That's why it's better to sell first before building
That's helps you not to build according to wishes but the real thing

Vynith · Jul 23, 2026

Your service should solve a problem anyway otherwise you'll end up like the Segway guy.

ShahrozS · Jul 23, 2026

Israeliod said:
I completely agree. I've found that clients often ask for features because they think that's the solution, when the real issue is usually an inefficient workflow or a repetitive process. Asking about their biggest day-to-day frustration tends to uncover much more valuable insights and often leads to simpler, more effective solutions.

Exactly. I've noticed that once you understand the workflow behind the request, many feature requests become unnecessary. Solving the root cause usually creates a better experience than adding another button or setting. It's a good reminder that listening to the problem is often more valuable than listening to the proposed solution.

ShahrozS · Jul 23, 2026

medialounge said:
That's why it's better to sell first before building
That's helps you not to build according to wishes but the real thing

I agree. Selling early validates whether the problem is worth solving before investing months in development. The only thing I'd add is that those early conversations should be about understanding the problem, not just collecting feature requests. That's usually where the biggest insights come from.

One thing I learned while building software...

ShahrozS

Newbie

Israeliod

BANNED

medialounge

Elite Member

Vynith

Regular Member

ShahrozS

Newbie

ShahrozS

Newbie

Main Menu

Marketplace

Making Money

BlackHat World