Scaling AI Enablement: How Odevo Upskilled Engineering

The conversation begins with an inside look at Odevo, a massive Swedish property technology company managing residential assets globally. Tomasz outlines the early days of their AI adoption, characterized by an internal AI team building bespoke document sorting tools and a secure internal GPT instance. However, a significant pivot occurs when casual Slack debates about engineering productivity evolve into a structured realization: the rules of software development are fundamentally changing, and unstructured experimentation is no longer sufficient.The Technical CoreThe heart of the episode explores the mechanics of the comprehensive AI training rollout at Odevo. Tomasz and Deejay dissect the deliberate choices made during the enablement program, such as rejecting compressed three-day bootcamps in favor of spaced, bi-weekly modules. This pacing allowed engineers to digest concepts and test them in real-world scenarios. The duo delves into the tangible outcomes of this structured approach, noting that pull request volume increased by up to ten times while merge times plummeted by fifty percent. Importantly, they discuss how AI adoption actually reinforced foundational engineering practices, making tedious tasks like unit testing and documentation effortless rather than burdensome. Tomasz emphasizes that the training was not just about syntax, but about establishing a baseline of good and bad practices for utilizing tools like Claude Code and GitHub Copilot.Philosophical and Human ImplicationsA fascinating shift in the narrative happens when the discussion moves beyond the engineering department. Tomasz highlights the democratization of software creation, detailing how financial managers, product owners, and HR professionals are leveraging platforms like Lovable to build functional applications. This introduces a new paradigm of ownership, encapsulated by the you build it, you own it philosophy. The duo explores the psychological impact of AI, noting a marked increase in developer boldness. Engineers are no longer paralyzed by the fear of starting; instead, they are proactively rewriting legacy applications and exploring new architectures because the barrier to entry has evaporated.Future OutlookLooking ahead, Tomasz advocates for a culture of enablement over restriction. He argues against heavy-handed governance and token rationing, comparing AI access to basic utilities like Microsoft Office. The focus remains on fostering curiosity, sharing wins and failures openly, and allowing teams to push the boundaries of what is possible as the industry accelerates toward an agentic future.Key Themes ExploredStructured Enablement Over Organic AdoptionRelying on developers to figure out AI tools independently leads to uneven adoption and amplified bad practices. A guided, paced training program establishes a baseline of quality and accelerates true organizational fluency.The Rise of the Bold DeveloperAI tools significantly lower the activation energy required to start complex tasks. This results in engineers taking more calculated risks, prototyping faster, and tackling legacy debt with renewed confidence.Democratization of Software CreationNo-code and agentic tools are turning product managers and operational staff into functional developers. This shift requires a new approach to governance, emphasizing personal ownership and collaborative refinement over traditional IT gatekeeping.Treating AI as a Fundamental UtilityRestricting token usage or imposing heavy red tape stifles innovation and limits ROI. Forward-thinking enterprises view access to frontier models as a basic operational necessity rather than a heavily audited expense.