We scan new podcasts and send you the top 5 insights daily.
Stakeholders must first interact with an AI agent about their feature ideas. The agent asks clarifying questions to assess impact and alignment. If the idea is weak, the agent politely rejects it, protecting PMs from distractions and poorly framed requests.
To manage the constant stream of requests from the business, set up a formal triage function. This gatekeeper forces requesters to articulate the problem and desired outcome before work is considered, enabling more intelligent conversations about trade-offs and team capacity.
Integrate AI agents directly into core workflows like Slack and institutionalize them as the "first line of response." By tagging the agent on every new bug, crash, or request, it provides an initial analysis or pull request that humans can then review, edit, or build upon.
Create distinct AI agents representing key executives (e.g., CEO, CMO, CSO). By posing strategic questions to each, you can simulate how different departments might react, identify potential misalignments in priorities, and refine proposals before presenting them to real stakeholders.
Embed your team's design principles into your development environment so an AI agent can perform automated critiques. This provides an objective first-pass analysis of new designs, ensuring they align with core values before involving the wider team.
PMs can use AI agents connected to their codebase to explore technical feasibility and iterate on ideas. This serves as a 'digital tech lead,' saving immense time for senior engineers who were previously burdened with speculative 'how hard would it be?' questions from product managers.
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.
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.
Most PMs work on existing products, not new ones. Use a specialized LLM skill, like 'Vet a Feature,' to rigorously analyze new feature ideas against anti-patterns and opportunity costs before committing development resources, ensuring you work on the highest-impact items.
Leverage AI to gain external perspectives without meetings. Prompt it to act as a specific persona—like a skeptical CEO, an enthusiastic user, or a New York Times reviewer—to critique your work. This reveals blind spots and strengthens your idea before sharing it.
When users request a specific feature, like an API, don't take it at face value. Ask 'why' to uncover the underlying job-to-be-done. The user's goal might be a centralized view of comments, which can be solved with a dedicated feed—a much simpler solution than building a full API.