Validate a new idea by having ~30 customer conversations—enough to see a pattern, but not too many to be impractical. However, to truly understand the core of your PMF, you need the real-world feedback that only comes from the process of selling to your first 100 customers.

Don't just collect feedback from all users equally. Identify and listen closely to the few "visionary users" who intuitively grasp what's next. Their detailed feedback can serve as a powerful validation and even a blueprint for your long-term product strategy.

A CEO's main function isn't constant ideation but relentless information consumption to build deep context and intuition. This groundwork enables them to make the one to three truly pivotal decisions each year that shape the company's future, while also creating an environment where the team's best ideas can emerge.

Effective, fast research isn't about skipping steps but about rightsizing the effort. Instead of defaulting to a previous method like "10 interviews," teams should determine the minimum insight needed to mitigate the specific risk at hand, using that to define the research scope and approach.

Before an innovation workshop, focus interviews on employees and customers who interact with the product daily, not just executives. Their ground-level insights are essential for defining the strategic 'white spaces' that will guide the workshop and ensure it addresses real problems.

Spreading strategy sessions over weeks often isolates decision-making to the founder and loses momentum. Compressing the process into a single, focused day with the entire team creates a powerful shared experience. This intensity fosters a common language and immediate alignment that a drawn-out process cannot replicate.

Instead of broad surveys, interview 10-12 satisfied customers who signed up in the last few months. Their fresh memory of the problem and evaluation phases provides the most accurate insights into why people truly buy your product, allowing you to find patterns and replicate success.

Instead of arguing for more time, product leaders should get stakeholder buy-in on a standardized decision-making process. The depth and rigor of each step can then be adjusted based on available time, from a two-day workshop to an eight-month study, without skipping agreed-upon stages.

The story of interviewing 600 developers to find one CTO highlights a key lesson: high-volume interviewing isn't just about finding one person. It's about developing pattern recognition. By speaking with dozens of candidates for a single role, you rapidly tune your ability to distinguish between mediocre and exceptional talent.