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.
Related Insights
To prepare for a future of human-AI collaboration, technology adoption is not enough. Leaders must actively build AI fluency within their teams by personally engaging with the tools. This hands-on approach models curiosity and confidence, creating a culture where it's safe to experiment, learn, and even fail with new technology.
Vercel's Pranati Perry argues that even with no-code AI tools, having some coding knowledge is a superpower. It provides the vocabulary to guide the LLM, give constructive criticism during debugging, and avoid building on a 'house of cards,' leading to better, more stable results.
AI is a 'hands-on revolution,' not a technological shift like the cloud that can be delegated to an IT department. To lead effectively, executives (including non-technical ones) must personally use AI tools. This direct experience is essential for understanding AI's potential and guiding teams through transformation.
For product managers not yet working on AI, the best way to gain experience is to build simple AI tools for personal use cases, like a parenting advisor or a board game timer. Using no-code prototyping tools, they can learn the entire development lifecycle—from ideation to prompting and user feedback—without needing an official AI project at work.
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.
The primary focus for leaders should be fostering a culture of safe, ethical, and collaborative AI use. This involves mandatory training and creating shared learning spaces, like Slack channels for prompt sharing, rather than just focusing on tool procurement.
Organizations fail when they push teams directly into using AI for business outcomes ("architect mode"). Instead, they must first provide dedicated time and resources for unstructured play ("sandbox mode"). This experimentation phase is essential for building the skills and comfort needed to apply AI effectively to strategic goals.
Non-technical founders using AI tools must unlearn traditional project planning. The key is rapid iteration: building a first version you know you will discard. This mindset leverages the AI's speed, making it emotionally easier to pivot and refine ideas without the sunk cost fallacy of wasting developer time.
When an engineering team is hesitant about a new feature due to unfamiliarity (e.g., mobile development), a product leader can use AI tools to build a functional prototype. This proves feasibility and shifts the conversation from a deadlock to a collaborative discussion about productionizing the code.
GSB professors warn that professionals who merely use AI as a black box—passing queries and returning outputs—risk minimizing their own role. To remain valuable, leaders must understand the underlying models and assumptions to properly evaluate AI-generated solutions and maintain control of the decision-making process.
