I’ve been reflecting on the cacophony of feedback that surrounds both my roles as an IVF specialist and an angel investor. This isn’t a complaint; rather, it’s an acknowledgment of the complex tapestry that feedback weaves into the fabric of our professional lives. Last week, a founder I backed in a promising edtech startup came to me, overwhelmed by conflicting customer feedback. One school wanted more interactive features, while another preferred a minimalist approach. Similarly, in my clinic, a couple debated whether more information about IVF would ease their anxiety or just add to their stress. The truth is, whether in medicine or business, feedback is rarely a straightforward guide. It’s a puzzle, and fitting its pieces together requires an understanding of not just what is said, but why it’s said.
Feedback, by its nature, is subjective. In my experience, the key lies in discerning the underlying needs and the context behind each piece of feedback. For instance, when a patient says they need more information, do they really need more, or do they need reassurance and clarity on what they already have? Similarly, when a customer requests a new feature, is it a genuine need, or is it a reaction to a temporary inconvenience? These are not mere rhetorical questions but reflections of genuine challenges we face daily.
In the startup world, the allure of feedback is its promise of direction. But as I often remind the founders I mentor, feedback is not a democratic process. Popularity doesn’t equate to priority. One of the most profound lessons I’ve learned from my medical practice is the importance of understanding core needs. In IVF, the core need is clear: help couples have a baby. Everything else, from the ambiance of the clinic to the nuances of patient communication, serves that singular goal. The same principle applies to startups. Identify the core task your product or service is meant to accomplish, and let that guide your response to feedback.
Take, for example, a platform like Asha’s. Her customers report multiple issues—employees dislike re-entering data, owners rarely check a separate screen, and a distributor wants integration with existing systems. Each piece of feedback highlights a different perspective and need, but not all can or should be addressed immediately. Prioritizing changes requires a careful consideration of the impact on the core task, the frequency within the segment, the strength of evidence supporting the feedback, and the cost of implementation.
In my clinic, I’ve seen how addressing the core need can sometimes mean saying no to well-intentioned suggestions. A patient once suggested a series of wellness seminars, which, while beneficial, would have diverted resources from our primary goal of successful IVF treatments. Similarly, Asha might need to explain to her distributor that while integration is valuable, it doesn’t align with her current priorities.
This doesn’t mean ignoring feedback that highlights serious issues. In both startups and medical practice, any failure in accuracy or trust is a red flag that demands immediate attention, regardless of how many customers it affects. The stakes are high in both fields, and sometimes, even a single voice can uncover a systemic issue that needs fixing.
I’ve also learned the value of keeping a decision history. In a world where team members change and projects evolve, having a record of what users reported, what was changed, the outcomes, and lingering uncertainties is invaluable. This history prevents the reintroduction of ideas that were previously dismissed, simply because they are presented with a new enthusiasm.
There is an art to saying no. In the course of building a product or a medical practice, not every request can be accommodated. The key is to communicate this refusal with respect and clarity, explaining why a particular request falls outside the current scope or priorities. Listening to customers or patients does not mean turning your service into an incompatible blend of suggestions. It means understanding their needs and aligning them with your capabilities and goals.
In conclusion, navigating feedback is akin to balancing on a tightrope. It’s a process of refinement, of distilling what truly matters from a sea of opinions. Whether it’s in helping a couple achieve their dream of parenthood or guiding a startup to success, the challenge remains the same: to listen, to discern, and to act with conviction. As I’ve learned through my journey across these fields, it’s not about the volume of feedback you receive, but the clarity with which you interpret and act upon it.
Part of the Building Frugal Startups: Lessons from the Trenches series — read the full guide.