The successful approach to AI isn't applying the technology broadly and searching for value. Instead, leaders must first define a specific business outcome, such as improving pipeline conversion. From there, they can work backward to identify and procure the exact data needed to enable AI to solve that targeted problem.

The impulse to "add AI" is common, but workshops exploring it must first ask "where do we have good, clean data?". Without a solid data foundation, AI ideation is futile. The first innovation step might be improving data collection, not implementing machine learning.

The impulse to make all historical data "AI-ready" is a trap that can take years and millions of dollars for little immediate return. A more effective approach is to identify key strategic business goals, determine the specific data needed, and focus data preparation efforts there to achieve faster impact and quick wins.

Data is only truly "AI-ready" when it is not just technically accurate but also compliant with business context hidden in unstructured documents like policies. This involves vectorizing business logic and verifying it against facts in data warehouses.

AI's effectiveness is entirely dependent on the quality and structure of the data it's trained on. The crucial first step toward leveraging AI for operational leverage is establishing a comprehensive data architecture. Without a data-first approach, any AI implementation will be superficial.

Contrary to the belief that AI requires perfect, clean data, the biggest opportunity lies in building technology that can find signals in messy, diverse data sets across different modalities and organisms. The tech should solve the data problem, not wait for it to be solved.

Many leaders mistakenly halt AI adoption while waiting for perfect data governance. This is a strategic error. Organizations should immediately identify and implement the hundreds of high-value generative AI use cases that require no access to proprietary data, creating immediate wins while larger data initiatives continue.

IT departments often halt AI initiatives by citing data readiness and security concerns. However, many valuable early use cases (e.g., in marketing) don't require access to proprietary data. Companies should pursue these in parallel while addressing larger data infrastructure issues.

Revenue leaders are pressured to show AI ROI, but focusing on the shiniest new AI tool is a mistake. Real gains come from addressing foundational issues like internal data silos and poor data quality before deploying AI, as the technology is only as good as the data it's fed.