AI Lead | Embedding AI into enterprise software and internal workflows | Production AI with results
I have spent twenty-five years inside one company watching technology change in cycles — from desktop to client-server, to fully web-based, and now to AI-native. What that teaches you, mostly, is humility. Every wave looked transformational. Most were. But the ones that delivered lasting value were rarely the ones that arrived loudest. They were the ones that earned their place inside systems that already worked. This shapes how I think about AI today. Not as a replacement for what works, but as a layer that earns its place inside systems that already serve real customers. I lead AI company-wide adoption across products, operations and teams. My approach favors production over pilots, integrating over rebuilding from scratch, and delivery speed over endless planning cycles. Twenty-five years in, I still find this work interesting — and that surprises me as much as anyone.
Markdown supported · ⌘↵ to post
OneLifeVibe
The three-duties test is the sharpest part of this piece: switch-off authority, budget accountability, and answering for mistakes are usually held by three different people, which is exactly why the owner column stays blank. The ten-minute test turns that into something a team can run without a governance project — three questions, three names, and the split is visible. The switch-it-off-for-a-week check is a blunt but honest way to find out who actually relies on a tool.