Early-stage ideas are easily killed by practical objections. To prevent this, implement a rule where feedback must begin with "Yes, and...". This forces critics to be additive and constructive, building upon the initial concept rather than immediately shutting it down. It creates space for a bold idea to develop before facing harsh reality checks.
Related Insights
The goal of early validation is not to confirm your genius, but to risk being proven wrong before committing resources. Negative feedback is a valuable outcome that prevents building the wrong product. It often reveals that the real opportunity is "a degree to the left" of the original idea.
Leaders can reduce team anxiety and prevent misinterpretation by explicitly categorizing input. 'Do' is a direct order (used rarely), 'Try' is an experiment, and 'Consider' is a low-stakes suggestion (used 80-85% of the time). This ensures a leader's random thoughts aren't treated as gospel.
Instead of defaulting to skepticism and looking for reasons why something won't work, the most productive starting point is to imagine how big and impactful a new idea could become. After exploring the optimistic case, you can then systematically address and mitigate the risks.
Don't pitch big ideas by going straight to the CEO for a mandate; this alienates the teams who must execute. Instead, introduce ideas casually to find a small group of collaborative "yes, and" thinkers. Build momentum with this core coalition before presenting the developed concept more broadly.
To prevent a culture of complaining, Coinbase requires employees to document issues using a "Problem, Proposed Solution" framework. This forces individuals to move beyond simple criticism and contribute constructively, ensuring that dissent is paired with a thoughtful potential solution.
When a senior stakeholder proposes a potentially disruptive idea, direct resistance ('pushing') is counterproductive and strengthens their resolve. Instead, 'pull' them into a collaborative exploration. Acknowledge the idea, discuss the underlying problem it solves, and then gently steer the conversation back to how it aligns with the agreed-upon North Star, defusing tension.
To encourage participation from everyone, leaders should focus on the 'why' behind an idea (intention) and ask curious questions rather than judging the final output. This levels the playing field by rewarding effort and thoughtfulness over innate talent, making it safe for people to share imperfect ideas.
When giving feedback, structure it in three parts. "What" is the specific observation. "So what" explains its impact on you or the situation. "Now what" provides a clear, forward-looking suggestion for change. This framework ensures feedback is understood and actionable.
To truly validate their idea, Moonshot AI's founders deliberately sought negative feedback. This approach of "trying to get the no's" ensures honest market signals, helping them avoid the trap of false positive validation from contacts who are just being polite.
To get candid early-stage feedback, founder Janice Omadeke disarmed potential advisors by explicitly asking them to tell her if her "baby is ugly" and why. This framing signaled a thick skin and a genuine desire for constructive criticism, leading to more valuable insights instead of polite encouragement.