AI initiatives often require significant learning and iteration, which can derail a roadmap. To combat this, PMs should dedicate a fixed percentage of development bandwidth (e.g., 5-10%) specifically for iteration on high-priority AI projects. This creates a structured buffer for discovery without compromising the entire plan.
Related Insights
Contrary to the impulse to automate busywork, leaders should focus their initial AI efforts on their most critical strategic challenges. Parkinson's Law dictates that low-value tasks will always expand to fill available time. Go straight to the highest-leverage applications to see immediate, significant results.
Mandating AI usage can backfire by creating a threat. A better approach is to create "safe spaces" for exploration. Atlassian runs "AI builders weeks," blocking off synchronous time for cross-functional teams to tinker together. The celebrated outcome is learning, not a finished product, which removes pressure and encourages genuine experimentation.
For leaders overwhelmed by AI, a practical first step is to apply a lean startup methodology. Mobilize a bright, cross-functional team, encourage rapid, messy iteration without fear, and systematically document failures to enhance what works. This approach prioritizes learning and adaptability over a perfect initial plan.
Unlike traditional software development, AI-native founders avoid long-term, deterministic roadmaps. They recognize that AI capabilities change so rapidly that the most effective strategy is to maximize what's possible *now* with fast iteration cycles, rather than planning for a speculative future.
In ROI-focused cultures like financial services, protect innovation by dedicating a formal budget (e.g., 20% of team bandwidth) to experiments. These initiatives are explicitly exempt from the rigorous ROI calculations applied to the rest of the roadmap, which fosters necessary risk-taking.
The rapid pace of AI makes traditional, static marketing playbooks obsolete. Leaders should instead foster a culture of agile testing and iteration. This requires shifting budget from a 70-20-10 model (core-emerging-experimental) to something like 60-20-20 to fund a higher velocity of experimentation.
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.
In the fast-moving AI sector, quarterly planning is obsolete. Leaders should adopt a weekly reassessment cadence and define "boundaries for experimentation" rather than rigid goals. This fosters unexpected discoveries that are essential for staying ahead of competitors who can leapfrog you in weeks.
In a rapidly evolving field like AI, long-term planning is futile as "what you knew three months ago isn't true right now." Maintain agility by focusing on short-term, customer-driven milestones and avoid roadmaps that extend beyond a single quarter.
When pursuing a long-term strategic solution, dedicate product management time to high-level discovery and partner alignment first. This doesn't consume engineering resources, allowing the dev team to remain focused on mitigating the immediate, more visceral aspects of the problem.
