We scan new podcasts and send you the top 5 insights daily.
Use a dedicated AI chat as a dynamic feature backlog. Continuously feed it new ideas and user feedback, prompting the AI to maintain a ranked table of features based on estimated build time and potential impact. This creates a low-friction system for choosing what to build next during focused work sprints.
When stuck on product direction, use a simple prompt like "add five new features." The AI acts as a creative partner, generating ideas you may not have considered. Even if most are discarded, this technique can spark inspiration and uncover valuable additions.
Instead of codebases becoming harder to manage over time, use an AI agent to create a "compounding engineering" system. Codify learnings from each feature build—successful plans, bug fixes, tests—back into the agent's prompts and tools, making future development faster and easier.
Don't ask an AI agent to build an entire product at once. Structure your plan as a series of features. For each step, have the AI build the feature, then immediately write a test for it. The AI should only proceed to the next feature once the current one passes its test.
As AI automates routine tasks, employees will gain free time. Instead of letting this turn into busywork, leaders should create an 'innovation sandbox'—a backlog of prioritized, strategic projects—that employees can immediately begin working on to drive growth.
Instead of a multi-week process involving PMs and engineers, a feature request in Slack can be assigned directly to an AI agent. The AI can understand the context from the thread, implement the change, and open a pull request, turning a simple request into a production feature with minimal human effort.
Instead of adopting AI as a simple tooling exercise, identify where decision-making is slow or fragmented. For instance, during planning, AI can synthesize inputs and draft reports. This elevates product teams from low-value "busy work" to high-value strategic debate and tradeoff analysis.
Instead of guessing where AI can help, use AI itself as a consultant. Detail your daily workflows, tasks, and existing tools in a prompt, and ask it to generate an "opportunity map." This meta-approach lets AI identify the highest-impact areas for its own implementation.
Instead of writing detailed specs, a developer can copy conversations or take screenshots from community platforms like Discord. This raw user feedback becomes the direct starting point for a conversation with an AI coding assistant, dramatically shortening the development cycle.
Instead of immediately building, engage AI in a Socratic dialogue. Set rules like "ask one question at a time" and "probe assumptions." This structured conversation clarifies the problem and user scenarios, essentially replacing initial team brainstorming sessions and creating a better final prompt for prototyping tools.
To handle feature requests from customers or your team without getting derailed, create a 'not right now' list. This validates the suggestion and shows leadership by prioritizing, but protects the team's focus on essential work, preserving morale and focus.