제로투원 단계에서 프로덕트 디스커버리에서 무엇이 중요한가? 요새 가장 좋은 인사이트 주고 있는 Ravi의 글 요약입니다 1. Learn from other domains At Tripadviso

제로투원 단계에서 프로덕트 디스커버리에서 무엇이 중요한가? 요새 가장 좋은 인사이트 주고 있는 Ravi의 글 요약입니다 1. Learn from other domains At Tripadvisor, we started a new team to focus on the product's search & discovery experience. We knew that people often struggled to find the right restaurants, attractions, and accommodations—both before and during their trip. We looked at other travel companies for inspiration, but couldn't find an experience that put enough emphasis on discovery. Established players were optimized for the conversion-driven search for bookable hotels. Instead, we found inspiration in other domains: Spotify, Etsy, and Amazon all excel at solving for search & discovery when the user isn't sure what they are looking for. 다른 domain에서 우리가 참고할 부분을 찾는 능력. 전 이 능력이 generalist의 가장 큰 역량중 하나라고 봅니다.(적당히 다 잘 하는게 아니라요.) 관련해서는 책 읽어보시면 좋음 ㅎㅎ 2. Speed is more about latency than velocity The problem is that velocity comes with a cost. The faster a car is going, the slower it turns. The same is true for teams & companies. In the early days of product discovery, the most important metric to optimize is time from hypothesis to insight. Surprisingly, the primary advantage of these no-code tools hasn't been saving time (i.e., increasing velocity). For example, a good designer can build a page just as fast in CSS as in Webflow. Instead, the advantage has been flexibility and agility. Our small team can make and deploy constant changes to decrease the latency between idea and impact. no code 툴 찾는 능력, 활용하는 능력도 필수 4. A conversation is worth a 1,000 data points The best product teams I've worked with triangulate their insights—using both quantitative data and qualitative research to make product decisions. This is even more critical during zero-to-one product discovery. Of course, there isn't a lot of data to begin with. That's one problem. But, that can lead to another problem. The process of getting more data can be counter-productive—both because growing prematurely can accelerate momentum in the wrong direction and because data is often misleading at this point. Frequent conversations with early users is the antidote. Each conversation will add deeply to the team's understanding. We don't have a lot of process yet, but we've built a habit around a lightweight feedback process—every time a customer provides feedback, we put quick notes into Notion and discuss a couple of takeaways. 초기 프러덕트에서 숫자에 매몰되지 말고 정성 분석을 하고, 초기 사용자와 가깝게 지내는 것 다시한번 강조! 5. Fall in love with the problem, not the solution. Innovators need to strike a tricky balance. On one hand, they need to craft a convincing & inspiring story about their best working hypothesis. On the other hand, they need to be skeptical of that story—constantly open to new and disorienting feedback. 왜 문제 중심으로 사고하는게 중요한가? 하나의 가설에 매몰되지 않고, 다른 방향에 오픈되어 있기 위함이라는 포인트!