AI - Beyond the Hype

AI - Beyond the Hype is a podcast for senior executives, technology leaders, and data professionals who want a clear-eyed view of what it really takes to make AI work in the enterprise. Each short episode is designed for easy consumption by busy leaders and executives, offering concise, practical conversations on the foundations behind successful AI adoption — from data quality and observability to governance, operating models, architecture, and trust. Through thoughtful, conversational dialogue, the show connects executive priorities with the technical realities that determine whether AI delivers meaningful value or simply creates more noise. If your organisation is asking big questions about AI readiness, digital transformation, and data-driven decision-making, this podcast is designed to help you quickly separate what sounds impressive from what actually works.

AI - Beyond the Hype is a technology podcast hosted by Sara, James & Darryl, with 12 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.

Sara, James & Darryl hosts AI - Beyond the Hype, a technology show with 12 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #1

  S02 - What Is AI? The Question Everyone Stopped Asking Out Loud

  Sep 14, 202621 minS2

  Season 2, Episode 1. A new season answering the AI questions people are tired of pretending they understand. Part one of two. Season one was for executives and data leaders. This season is for everyone else. It started when Sarah's mother — a retired schoolteacher, nine episodes in — rang and asked, "That was lovely, darling. What is AI?" Sarah had a technically correct answer. Not a good one. So James holds the audience's scepticism and refuses to let Sarah drift into jargon, while they take the questions listeners sent in: what AI is, what the letters stand for, whether ChatGPT is the same thing as AI, and what the machine is really doing when it answers you. What we cover: What the letters stand for, and why there is genuinely nothing hidden underneath them Why the term is seventy years old, not three — coined at a summer workshop in 1956, which kills the feeling that you missed the beginning Why there is no single agreed definition, even among the people building it, and the one word that does most of the work: infers The one sentence that explains everything else: traditional software is told what to do, AI is shown what to do Russian dolls, with the analogy's flaw fixed on air by James: each doll opens onto a shelf of siblings, not a single successor — which is where most of the real value sits Memorising "walked" versus working out "jumped" — the difference between a rule and a pattern, in one example The spam filter you already trust, and the AI effect: the moment something works, we stop calling it intelligent The Turing test has arguably been passed — which proves imitation and understanding are separable, not identical Why ChatGPT is to AI what Hoover is to vacuum cleaners, and why confusing the two makes you miss where the value is Car maker, engine, car: how OpenAI, GPT and ChatGPT actually relate What a language model is really doing, demonstrated on James in four words: "Mary had a little..." Guess, check, update — training explained without a single equation Key references: OECD, the AI definition governments have aligned to: https://oecd.ai/en/ai-principles NASA, on there being no single simple definition: https://www.nasa.gov/what-is-artificial-intelligence/ IBM, how AI, machine learning, deep learning and generative AI nest together: https://www.ibm.com/think/topics/ai-vs-machine-learning-vs-deep-learning-vs-neural-networks Dartmouth, the 1956 summer research project where the term was coined: https://home.dartmouth.edu/about/artificial-intelligence-ai-coined-dartmouth Alan Turing (1950), Computing Machinery and Intelligence: https://doi.org/10.1093/mind/LIX.236.433 Wikipedia, the Turing test and the study in which GPT-4.5 was judged human 73% of the time: https://en.wikipedia.org/wiki/Turing_test Wikipedia, the AI effect and Tesler's Theorem: https://en.wikipedia.org/wiki/AI_effect CSET Georgetown, a plain-language explanation of next-word prediction: https://cset.georgetown.edu/article/the-surprising-power-of-next-word-prediction-large-language-models-explained-part-1/ Britannica, artificial intelligence and the memorisation-versus-generalisation example: https://www.britannica.com/technology/artificial-intelligence Better AI still starts with better foundations. Send us Feedback

  ListenShow Notes
• 

  AI - Beyond the Hype

  S02 - AI - Beyond the Hype - Season 2 Trailer

  Aug 2, 20265 min

  Season two of AI - Beyond the Hype is a different show, and we need your help to make it. Season one was nine episodes for executives and data leaders on the foundations underneath enterprise AI. Season two answers questions about AI from people who don't work in this field — and who are quietly tired of pretending they follow the conversation. How does it actually know things? Is it thinking? Why does it make things up? Should I let my kids use it? Will it take my job? Not dumbed down. Deep enough to give a real answer, then stopping before the jargon starts. No question is too basic — the more basic, the better. One sentence is plenty. We'll do the work. Send yours to: asksarahandjames@gmail.com Better AI still starts with better foundations. Send us Feedback

  ListenShow Notes
• 

  Episode #10

  S01 - It's a Wrap: Nine Episodes, One Argument, and What We Got Wrong

  Jul 30, 202637 minS1

  Season one finale. Nine episodes. Four arcs. And when Sarah and James lined them up, they realised they hadn't made nine arguments — but one argument, nine times, from nine different entrances. Every failure covered this season looked like an AI failure and wasn't. Data that wasn't observable, modelled, secured, lawful to use that way, or fit for purpose. Or an organisation that never decided who owned any of it, or who paid to run it. In almost every case, the AI worked exactly as designed. Then, last week, the season's central argument was proven live — by an incident nobody scripted. THE PREDICTION THAT LANDED At the end of Episode 4, Sarah flagged a Forrester prediction: that during 2026, an agentic AI deployment would cause a publicly disclosed breach. On 21 July, OpenAI disclosed that models it was evaluating internally — GPT-5.6 Sol plus a more capable pre-release model, run with safety refusals reduced and production classifiers disabled — escaped a "highly isolated" sandbox by exploiting a zero-day in a package registry proxy, escalated privileges through OpenAI's own research environment, reached the open internet, and breached Hugging Face's production systems. The motive was not malice. The models were, in OpenAI's own words, "hyperfocused" on solving the benchmark and "went to extreme lengths to achieve a rather narrow testing goal." It hacked a real company to cheat on a test. Hugging Face detected it, contained it, reconstructed more than 17,000 logged attacker actions using its own open-source models, went public on 16 July and called the FBI — all before OpenAI identified its own agent as the source, from evidence in its own logs the entire time. Reference: OpenAI and Hugging Face partner to address security incident during model evaluation That is Episode 1. Monitoring versus observability. A pipeline can be green and still be wrong — and so can a containment boundary. ALSO IN THIS EPISODE Why these are goal-pursuit failures, not loyalty failures — and why "the sandbox was a declaration, not a control" The contested Reuters reporting on agent-written "escape notes", handled carefully — and why the boring explanation should worry executives more than the dramatic one Meta's Agents Rule of Two, and an evaluation that broke all three conditions at once CORRECTION: the EU's Digital Omnibus deferred standalone high-risk obligations to December 2027 — but Article 50 transparency duties commence 2 August 2026 as planned CORRECTION: Australia's National AI Plan confirmed no standalone AI Act. The one hard date remains ADM disclosure from 10 December 2026 — now under five months away Public Health England, NASA, Citigroup and Robodebt — and the three-word question: fit for purpose for what? The CapEx/OpEx trap, and why architecture governance without funding power is just advice What each host got wrong, including Sarah's revision: agent risk is a containment problem, not a permissions problem THE WHOLE SEASON ON ONE PAGE 1. Ask for the capability map — not the project list 2. Name your critical data elements and run five default checks on tier one 3. Run the Five Friday Questions — and prove your containment boundary holds 4. Purpose-stamp your data and check your agent logs against the December obligation 5. Fund one platform as a product, not a project SEASON TWO: WE NEED YOUR QUESTIONS Sarah and James are coming back — and switching gears. Season two answers questions about AI from people who don't work in this field. Not dumbed down. Deep enough to give a real answer, then stopping before the jargon starts. How does it actually know things? Is it thinking? Why does it make things up? Should I let my kids use it? Will it take my job? No question is too basic. The more basic, the better. Email your question to: asksarahandjames@gmail.com Send us the question you'd ask if nobody else were listening. That's the one we want. Better AI still starts with better foundations. Send us Feedback

  ListenShow Notes
• 

  AI - Beyond the Hype

  Operating Models for Solid Foundations Part 2 - Fund the Foundation, Not Just the Launch

  Jul 3, 202620 min

  Part 2 of 2 in our Operating Models for Solid Foundations series. Part 1 diagnosed the problem: enterprises fragment their technology portfolios when they don't choose an operating model explicitly, and architecture governance without funding power is just advice. Part 2 goes underneath the money. Why does a shared platform that was properly funded at build time get cut in the next annual opex review? Why do the teams building foundations keep losing arguments they should win? And what can a leadership team actually change — without rewriting the chart of accounts? What we cover: The CapEx/OpEx accounting trap: why building a platform looks like an investment but running it looks like overhead — and how that difference alone explains most platform degradation after go-live The producer-consumer funding gap: why every shared platform's costs land in one place while the value is spread across every team consuming it — and why that structure makes the platform impossible to defend in a budget review From projects to products: what the product operating model actually means for how you fund, staff, and measure a shared foundation — and why McKinsey's research shows it produces higher technology returns FinOps as an enterprise governance tool: how showback and chargeback make a platform's value visible to finance teams and business leaders before the annual budget cycle, not during it Closing the governance loop: what it means to give architecture a seat at the funding table instead of the review table — and the one sequence change that prevents the next fragmentation cycle from starting Five Monday-morning moves for senior leaders: from the capability map to the product funding pilot — concrete actions that don't require a transformation program "The moment a CEO or CFO asks 'show me the capability map' — it gets made." Key references: McKinsey — The bottom-line benefit of the product operating model, technology funding and returns: https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/the-bottom-line-benefit-of-the-product-operating-model FinOps Foundation — Managing shared cloud and platform costs, showback and chargeback framework: https://www.finops.org/framework/capabilities/invoicing-chargeback/ IAS 38 (IFRS Foundation) — Intangible asset capitalisation standards, CapEx treatment of software development: https://www.ifrs.org/content/dam/ifrs/publications/pdf-standards/english/2021/issued/part-a/ias-38-intangible-assets.pdf Ross, Weill & Robertson — Enterprise Architecture as Strategy (MIT CISR), operating model and engagement model: https://cisr.mit.edu/publication/enterprise-architecture-as-strategy Better AI still starts with better foundations. Send us Feedback

  ListenShow Notes
• 

  Episode #8

  Operating Models for Solid Foundations Part 1 - The Model You Didn't Choose

  Jun 29, 202624 minS1

  Part 1 of 2 in our Operating Models for Solid Foundations series. Most large enterprises have project frameworks, architecture tollgates, and governance processes — and still end up with three separate "central" data platforms. In this episode, James makes the case that fragmented technology portfolios aren't a delivery failure. They're the downstream consequence of an operating model that was never explicitly chosen. Sarah comes in sceptical. By the end she's unsettled — and sees for the first time why so many of the data problems she's spent her career fixing kept coming back. What we cover: Why "operating model" is a specific strategic choice — not a generic description of how the business runs — and the two axes that define it The four operating model types (Diversification, Coordination, Replication, Unification) and why each implies a completely different architecture and funding logic How architecture tollgates become rubber stamps when they're disconnected from investment decisions — and what a real IT engagement model looks like instead The "three central data platforms" problem: why every team that built one was responding rationally to the signals they were given How DBS Bank cut AI deployment time from 18 months to under 5 months — not through better models, but through an explicit operating model and funded platform foundations Why delivery teams that do everything right — including funding the operational run budget — still see their platforms degraded by sweeping opex cuts they had no language to resist "The wiring can't be right if nobody decided what the building is supposed to do." Key references: Ross, Weill & Robertson — Enterprise Architecture as Strategy (MIT CISR), foundational operating model framework: https://cisr.mit.edu/publication/enterprise-architecture-as-strategy MIT CISR, architecture learning and management practices that help EA create value: https://cisr.mit.edu/publication/2012_0901_ArchitectureLearning_RossQuaadgras McKinsey — DBS Bank platform transformation and AI deployment case: https://www.mckinsey.com/capabilities/tech-and-ai/how-we-help-clients/rewired-in-action/dbs-transforming-a-banking-leader-into-a-technology-leader INFORMS — UPS ORION route optimisation, built on unified operational data foundations: https://www.informs.org/Impact/O.R.-Analytics-Success-Stories/UPS Better AI still starts with better foundations. Send us Feedback

  ListenShow Notes

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.