The most useful product meeting might be a customer conversation.
Before adding a feature, understand the need behind the request.
Socheat Leang · Co-founder, MEKA Asia
Sample draft — this article is a template awaiting personal examples and editorial review.
Listen for the underlying problem
A feature request is a starting point. Ask what someone is trying to do, what gets in the way, and how they handle the problem today.
Close the learning loop
Group what you hear, look for patterns, and test a small response. Explain what changed and invite the customer to tell you whether it helped.
Make this yours: add an example from your experience, the decision you made, and what you learned.
Have a perspective to share or an idea to explore?
Let’s talk ↗