
This distills frameworks from 94 product leaders into practical guidance for building AI products. Use it when you're deciding where AI fits in your product, evaluating build versus buy, or planning your roadmap. It pushes you to start with user problems instead of capabilities, design for model failures, and build feedback loops that improve over time. The concrete frameworks help with the messy middle decisions like defining human-AI boundaries and accounting for non-determinism. Especially useful if you're past the "should we use AI" question and into the harder "how do we actually ship this" territory.
$ npx -y skills add refoundai/lenny-skills --skill ai-product-strategy --agent claude-codeInstalls into .claude/skills of the current project.
Prioritize high-impact workflows and navigate non-deterministic development to build defensible AI products.
Help the user with ai product strategy using insights from 26 guests and posts across Lenny's Podcast and Newsletter.
Alex Komoroske: "LLMs allow writing shitty software to be significantly cheaper, not necessarily good software, but good enough in certain contexts. And also it means that there's certain software now that isn't plain old computing that can be run cheaply. It's relatively expensive marginal cost."
Design product experiences that assume AI is non-deterministic and imperfect rather than trying to force 100% accuracy into your UI.
Asha Sharma: "Because these models are so effective at this point, you want to start to tune them to certain types of outcomes. All of a sudden, these are these living organisms that just get better with the more interactions that happen. I think this is the new IP of every single company products that think and live and learn."
Measure success by the team's metabolism in ingesting data and improving learning loops rather than static feature releases.
Logan Kilpatrick: "We're not going to launch some of these varied verticalized products. We're not going to launch an AI sales agent. That's just not what we're building towards. And companies who are and have some domain specific knowledge and they're really excited about that problem space, they can go into that and leverage our models and end up continuing to be on the cutting edge without having to do all that R&D effort themselves."
Avoid competing with foundational models by targeting specific industry niches where domain expertise provides a structural advantage.
Noah Weiss: "I think in the AI space, we're trying to hear from customers, what do you wish Slack could do if it had these new superpowers? Let's incubate a couple teams or prototype, give them space to run and pilot and then get something to launch that's amazing. Blows people away. That's the formula that we've seen."
Avoid generic AI features by identifying specific customer needs and giving dedicated teams space to prototype them independently.
Sherwin Wu V2: "The field and the models themselves are just changing so, so quickly. They tend to disrupt themselves. The models will eat your scaffolding for breakfast."
Design for the capabilities expected in 12 to 18 months to avoid building custom scaffolding that will eventually be absorbed natively by the models.
Aishwarya Naresh Reganti + Kiriti Badam: "You need to be deliberately starting in places where there is minimal impact and more human control so that you have a good grip of what are the current capabilities and what can I do with them and then slowly lean into the more agency and lesser control."
Safely deploy agentic systems by starting with human-in-the-loop suggestions before scaling to full autonomous interactions.
See references/artifacts.md for the full list with details.
For all 45 sourced insights from 26 guests, see references/guest-insights.md
Sponsors