Honestly, it's too early to claim anyone has the perfect recipe for navigating the AI journey. But we can already identify failure modes that cause real problems. Avoiding those is half the battle.
The first is focusing too much on technology and losing sight of business and customer requirements. Many institutions are jumping on the bandwagon thinking "we have to do something with AI" without first identifying actual problems worth solving. They end up building solutions that seem cool or are engineering-driven based on what's possible with their data, rather than what's actually valuable. That's a trap.
The opposite failure mode is equally damaging: waiting for perfect conditions. Massive “AI ready” infrastructure projects become redundant before they're finished in a space moving this fast.
A smarter approach is partnering with companies where AI is a core business. For financial institutions, AI is a technology to leverage, not their core competency. Building everything from scratch is often a waste of resources. Instead of waiting for perfect conditions, focus on high-value use cases. Build solutions, iterate, get quick wins. Once something works, extend it, scale it, add use cases. Having a vision is good, but the iterative approach generates learnings and maintains momentum – rather than sinking money into projects that go nowhere.
A mindset shift is required: People are accustomed to deterministic software where you get the same output every time. AI is probabilistic. Evaluating AI solutions with the same lens and processes used for traditional software is a failure mode.
Finally, you need the data to be there. AI tools get better with better context. Context engineering is a real differentiator, and that requires a solid data foundation. Without it, even the most capable models underperform.