Understanding your ideal customers and their problems

If Henry Ford had asked people what they wanted, they'd have said faster horses. It's the most quoted line in product management for a reason — customers are so focussed on the solution they know that they can't envisage another approach.

When partners and customers define their needs as feature requests, they're giving you horses. Your job is to understand why they want to travel faster, where they're trying to get to, and what's slowing them down. That understanding opens up solution spaces that no feature request ever will.

In many product companies — especially those that work through partners or channel relationships — the default state is partner-led development. Partners explain their needs via solutions. Custom development is everywhere. The planning horizon is 30 to 45 days, and the decision of what to build next comes down to who's shouting loudest.

In this world, you never truly understand the problems until it's too late — until you've built something that doesn't quite fit, and the partner is already frustrated.

The fix isn't to stop listening to partners. It's to own the vision and change what you're listening for.

When you establish a clear product vision and publish it — share it with partners, document the journey, set out where you're going — something remarkable happens. Partners stop trying to fill the void with their own expectations. They stop perceiving your product team as a blocker and start seeing them as a strategic partner.

The majority will climb aboard. Those who don't were probably never aligned with your direction anyway. Publishing a roadmap, even a broadly thematic one, signals confidence and invites collaboration instead of demands.

Understanding your ideal customers means deeply understanding their business — their goals, their growth plans, their opportunities, and their constraints. It means looking for the overlaps between what they need and where your product is heading, and being honest when the overlap isn't there.

It means avoiding distractions: every piece of work must have clear value and impact.

The practical shift is simple but hard — instead of asking partners "what features do you need?", you ask "tell us about your business." That one question transforms the entire conversation from solution definitions to problem discovery.

Not every customer is the right customer. Your ideal customer profile (ICP) should describe the characteristics of customers who get the most value from your product and deliver the most value to your business.

That might be defined by scale (companies above a certain transaction volume), by sophistication (businesses that will become power users), by growth trajectory (companies whose needs will expand alongside your platform), or by alignment (businesses whose goals overlap with your product direction). When you know your ICP, you can qualify opportunities before they consume development resources, and you can ensure that new customer acquisition doesn't dilute the engagement of your existing base.

When you own the vision, understand the problems, and attract the right customers, the effects compound. Your WAU/MAU ratio holds steady because you're not bringing in wrong-fit customers. Your north star metric climbs because you're building features that address real needs.

Your partners become advocates because they feel heard and see progress. Your engineering team builds with purpose because every feature connects to a clear problem.

And your product stops being a collection of disconnected features and starts becoming a cohesive platform that customers can't imagine working without.