There's a certain type of person who first encounters Excel and, instead of running in terror, leans in and grins. Rob Collie has spent his career-from the Excel team at Microsoft to helping birth Power BI to now running P3 Adaptive—building things for exactly those people. He calls them "Crafters," and his new book, Fair Game: Customizing AI to Your Business Is Easier Than You Think, makes the case that this same crowd (hi, it's us) is uniquely positioned to do something genuinely remarkable with AI. Not because we're developers, not because we've cracked some secret, but because we've always lived on the boundary between the business and the tech-and that's precisely where the real AI work happens. The conversation covers the two "voids" crafters need to jump to go from chatting with Claude to actually building useful custom solutions, why the off-the-shelf AI tools are mostly useless for business purposes (and what to do about it), the faucets-first philosophy for semantic models, and why the developer isn't dead-just moving to the suburbs. Also: Tim built a quiz about his marriage and let his adult children take it. That happened.

This episode is brought to you, in part, by our sponsors, Stape and Prism from Ask-Y.

For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

If you've ever poured months into building a semantic layer only to watch it become shelfware the moment the business pivoted, Jacob Matson has some thoughts. And a metaphor. Your data is a jungle—and a semantic layer is a highway. Great if you need to get somewhere fast and reliably (monthly active users: highway, please). But the interesting business questions? The slicing, the dicing, the nuanced dimensions that actually differentiate your company from its competitors? There's no highway for that. There never will be. Jacob, a developer advocate at MotherDuck with deep roots in accounting and ERP systems, joined Michael, Moe, and Julie to talk through what comes after the semantic layer—or at least alongside it. The conversation covered why the most important parts of any business are precisely the parts that resist being modeled in someone else's framework, why AI is actually pretty good at writing SQL but not so great at remembering what it figured out yesterday, and whether the real job to be done here is less about modeling and more about search. Oh, and the uncomfortable truth that at episode 300, we still don't have a great answer for metric drift. But we've got some really good questions.

This episode is brought to you, in part, by our sponsors, Stape and Prism from Ask-Y.

For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

There are roughly a thousand ways to roll out a new analytics platform, a BI tool migration, or an AI initiative to your organization. Most of them involve a town hall, an email with a link to some training materials, and the quiet hope that everyone figures it out. Most of them also don't really work. On this episode, Yehonatan Schwarzmer joined Michael, Val, and Tim to bring some long-overdue organizational change management thinking into the analytics conversation. Yehonatan has the unusual combination of real-world experience in both change management consulting and data leadership, which makes him exactly the right person to explain why the technical rollout is the easy part. The harder part is understanding that when someone says "this tool doesn't have what I need," they might really be saying "I was the hero in the old system and I don't know who I'll be in the new one." The Kübler-Ross grief model shows up. Psychological safety shows up (reluctantly). And Val's question about who analysts should recruit to help them manage change at scale almost gets answered.

This episode is brought to you, in part, by our sponsors, Stape and Prism from Ask-Y.

For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.