"Is your AI guessing?" It’s a question that keeps many technology leaders up at night, and for Chris Palmer, CITO of Libro Credit Union, the answer depends entirely on your data. With industry reports suggesting that 95% of AI pilots fail to deliver ROI, Libro is taking a different path—one that prioritizes augmentation over automation and data preparation over marketing hype. From using AI to fight "the evil side" of fraud to reimagining digital banking as a conversation, explore how Libro is building a foundation of governance and quality data to ensure their AI journey delivers real value for members and staff alike.

In an industry obsessed with speed, UNI Financial is doing something radical: they are slowing down. CIO Tyson Johnson has watched other institutions rush headlong into AI deployments, only to stumble. Instead of chasing immediate productivity gains, Johnson is leading UNI Financial through the unglamorous but essential work of "level-setting"—building a common language around AI, strengthening data foundations, and establishing robust governance frameworks. Discover why the path to sustainable AI success starts with a breath, a pause, and a commitment to getting the fundamentals right before leaping into the journey.

AI shouldn’t automate away our humanity; it should free us to be more human. In this installment of the 2Oaks CIO Spotlight Series, Barry Hensch, CTO of General Bank of Canada, explains why the bank’s AI strategy isn't about reducing headcount—it's about removing "drudgery." From auto credit adjudication to a revolutionary 128-language chatbot for collections, discover how one of Canada’s most efficient banks is leveraging AI to move faster than the "Big Six" while keeping human judgment and empathy at the center of the customer experience.

For decades, banks bought software because building it was too risky. AI has flipped that script. We explore the new 'Development Economics' where building custom solutions is now faster, cheaper, and smarter than buying off-the-shelf.

Is your team just finding bugs, or preventing them? We explain why 'QA' and 'QC' are not the same thing, and how distinguishing between Prevention (QA) and Detection (QC) can save your project from costly rework.