SOFTWARE

After years of following @lennysan's wonderful takes on product, I finally had the opportunity to chat with him about AI products! piped.video/watch?v=qbvY0dQg… 1. Many AI product problems aren’t because of AI. It’s usually because of user experience, data quality, or organizational structure. A chatbot failed to get traction because their targeted users simply couldn’t type (because their hands were usually busy — taking care of kids or driving), so showing pre-populated questions and adding a voice option significantly improved traction. Another team told me their lead scoring model was broken. It turns out that it’s because the marketing team wasn’t asking the right questions to get data. The biggest product improvements still come from understanding your users, preparing your data, and investing in your team! 2. Senior engineers see the most productivity improvement with AI coding because they have more experience with writing design docs and API specs, which help them write better instructions. However, they’re also more resistant to using AI for coding. Senior folks are often more opinionated and get frustrated easily when AI doesn’t do what they want. 3. Many teams spend a lot of time debating which tool to use, which can be counter-productive. When teams ask me which of the 2 tools to use, I usually ask 2 questions: “How much performance improvement will the optional tool give over the less optimal one?” –> If the improvement is small, then spend less time debating. “How hard is it to change from one tool to another once you’ve adopted it?” –> If the tool is new and not yet battle tested, I’d think twice about adopting something that I can’t get out later. 4. Many people know that the most effective way to learn AI is to build with AI. Yet, people keep asking me: “But what should I build?” We seem to be having an “idea crisis”. We have all these wonderful tools to help us build things, and no idea what to build. An exercise I often recommend is to spend a week noticing what frustrates you in your daily work, then build small tools to solve those specific pain points.

→ View original post on X — @chipro, 2025-10-30 19:14 UTC