Product leaders must personally engage with AI development. Direct experience reveals unique, non-human failure modes. Unlike a human developer who learns from mistakes, an AI can cheerfully and repeatedly make the same error—a critical insight for managing AI projects and team workflow.
When deploying AI tools, especially in sales, users exhibit no patience for mistakes. While a human making an error receives coaching and a second chance, an AI's single failure can cause users to abandon the tool permanently due to a complete loss of trust.
Using AI to code doesn't mean sacrificing craftsmanship. It shifts the craftsman's role from writing every line to being a director with a strong vision. The key is measuring the AI's output against that vision and ensuring each piece fits the larger puzzle correctly, not just functionally.
Product managers should leverage AI to get 80% of the way on tasks like competitive analysis, but must apply their own intellect for the final 20%. Fully abdicating responsibility to AI can lead to factual errors and hallucinations that, if used to build a product, result in costly rework and strategic missteps.
Effective enterprise AI deployment involves running human and AI workflows in parallel. When the AI fails, it generates a data point for fine-tuning. When the human fails, it becomes a training moment for the employee. This "tandem system" creates a continuous feedback loop for both the model and the workforce.
Instead of waiting for AI models to be perfect, design your application from the start to allow for human correction. This pragmatic approach acknowledges AI's inherent uncertainty and allows you to deliver value sooner by leveraging human oversight to handle edge cases.
AI is not a 'set and forget' solution. An agent's effectiveness directly correlates with the amount of time humans invest in training, iteration, and providing fresh context. Performance will ebb and flow with human oversight, with the best results coming from consistent, hands-on management.
Simply instructing engineers to "build AI" is ineffective. Leaders must develop hands-on proficiency with no-code tools to understand AI's capabilities and limitations. This direct experience provides the necessary context to guide technical teams, make bolder decisions, and avoid being misled.
Vercel designer Pranati Perry advises viewing AI models as interns. This mindset shifts the focus from blindly accepting output to actively guiding the AI and reviewing its work. This collaborative approach helps designers build deeper technical understanding rather than just shipping code they don't comprehend.
AI's occasional errors ('hallucinations') should be understood as a characteristic of a new, creative type of computer, not a simple flaw. Users must work with it as they would a talented but fallible human: leveraging its creativity while tolerating its occasional incorrectness and using its capacity for self-critique.
Pega's CTO warns leaders not to confuse managing AI with managing people. AI is software that is configured, coded, and tested. People require inspiration, development, and leadership. Treating AI like a human team member is a fundamental error that leads to poor management of both technology and people.