Podcasts about Gartner

On this episode of Christopher Lochhead: Follow Your Different, we talk about how the consulting and research industry is facing a reckoning. Gartner, once a $42 billion empire built on telling companies which technologies to buy, has shed more than $30 billion in market value. Trading around $155 per share after peaking at $551 in November 2020, Gartner represents something far bigger than one company’s misfortune. It is a warning signal to every knowledge worker and consulting firm that the traditional model of acquiring and reselling existing knowledge is being quietly dismantled by artificial intelligence. The Pirate Street Journal recently broke down this shift through a category design lens, and the conclusions are both uncomfortable and urgent for anyone whose career is built around advice, analysis, or strategic guidance. You're listening to Christopher Lochhead: Follow Your Different. We are the real dialogue podcast for people with a different mind. So get your mind in a different place, and hey ho, let's go.   When AI Gives Away What Consultants Used to Sell For decades, consulting firms like Gartner monetized a simple formula: gather knowledge, package it into reports and subscriptions, and charge companies handsomely for access. A $100,000 research subscription felt justified when getting that knowledge required significant time and access. That equation has fundamentally changed. The moment a business leader can ask an AI which CRM platform or security stack to buy and receive a well-reasoned, sourced answer in seconds for free, the traditional research subscription starts looking like a fax machine. As strategy thinker Roger Martin has noted, true strategy represents only about 3% of what large consulting firms actually produce. The remaining 97% is largely benchmarking, gap analysis, and best practices work, exactly the kind of structured, retrospective analysis that AI now handles effortlessly.   The Only Consulting Work AI Cannot Replace What separates truly valuable strategic advice from commoditized knowledge is judgment. Courage. Wisdom. The ability to make a call when the spreadsheet offers no clear answer and the outcome remains genuinely uncertain. These are the qualities that have always driven the most important strategic wins, and they are precisely what AI cannot replicate or monetize anytime soon. Consider how often the best strategic decisions required someone to say “I believe this is the right direction” without proof. Timing a market entry too early, betting on a consumer behavior before it becomes mainstream, or designing an entirely new category rather than competing within an existing one all demand human conviction. The consultants who have consistently done this well rarely stay in advisory roles for long. They move into the arena, become entrepreneurs, or deploy their own capital because genuine foresight commands far greater economics than a consulting retainer.   What This Means for Knowledge Workers and the Consulting Profession Gartner’s market cap decline is not simply a story about one company failing to adapt. It is a broader signal to every knowledge worker that the value of their value has shifted. Technology does not take jobs outright. It relocates where value gets created. The professionals who repackage existing knowledge are seeing that value erode fast. The professionals who can create genuinely new knowledge, new frameworks, new categories, new experiences, are seeing their value rise. This distinction matters enormously for how consultants should think about their own positioning. Firms that continue to offer benchmarking, retrospective market summaries, and structured best practices comparisons are directly competing with AI at a game AI will eventually win. The consultants who build practices around future-oriented, judgment-heavy, courageous strategic work are the ones whose services will remain irreplaceable, and whose market caps, whether literal or metaphorical, will reflect a world that still believes in their future. To hear more from the Pirate Street Journal, download and listen to this episode. You can also read more Pirate Street Journal entries in the Category Pirates newsletter.   We hope you enjoyed this episode of Christopher Lochhead: Follow Your Different™! Christopher loves hearing from his listeners. Feel free to email him, connect on Facebook, X (formerly Twitter), LinkedIn, and subscribe on Apple Podcast / Spotify!  

Dr. John Gartner returns to The Daily Beast Podcast to mark Donald Trump's 80th birthday with a deeply provocative conversation about aging, cognitive decline, power, and the presidency. Speaking with Joanna Coles, Gartner argues that the public is witnessing something far more serious than normal aging, laying out his assessment of Trump's behavior, speech patterns, late-night social media activity, health concerns, and decision-making as global crises escalate. The discussion explores dementia, malignant narcissism, stress, sleep deprivation, executive power, and why millions of Americans remain drawn to Trump despite mounting concerns from critics. From White House medical visits and cognitive testing to the psychology of leadership and the dangers of unchecked authority, this is an intense and unsettling examination of one of the most consequential figures in modern politics. Visit https://ffrf.us/BEAST or text "BEAST" to 511511 to join or learn more. #ad If you're ever injured in an accident, you can check out Morgan & Morgan. You can start your claim in just a click without having to leave your couch: https://ForThePeople.com/DAILYBEAST #ad Learn more about your ad choices. Visit podcastchoices.com/adchoices

Every organization relies on secure digital connections across suppliers, partners, and platforms. Yet many of the technologies that protect those connections were built for a world before quantum computing.  While practical quantum capabilities may still seem years away, the risks associated with them are already prompting concern, particularly as encrypted data collected today could potentially be decrypted in the future. For supply chain leaders, that creates a unique challenge: preparing for a technological shift that is still emerging while protecting information that remains valuable far into the future. In this episode of Supply Chain Now, hosts Scott W. Luton and Karin Bursa sit down with Akhilesh Agarwal, President of P2P Solutions and Technology at apexanalytix, and William McNeill, Vice President of Market Intelligence, for a conversation on what the quantum era could mean for supply chains. Together, they unpack the growing conversation around quantum computing, the implications of "harvest now, decrypt later" strategies, and why supply chain ecosystems may be particularly vulnerable due to the vast amounts of supplier, financial, and contractual data that move across them every day. As digital transformation continues to accelerate, they discuss why understanding emerging risks today may be just as important as preparing for the opportunities quantum technologies could unlock tomorrow. Jump into the conversation: (00:00) Intro (00:42) Quantum risks supply chain leaders must know (02:13) Meet apexanalytix quantum risk experts (03:35) Space exploration lessons for innovation (07:03) Apexanalytix protects supplier data at scale (10:16) Why they wrote The Quantum Paradox (10:46) Harvest now decrypt later threat (15:46) Where to start with quantum readiness (21:38) Four major supply chain impacts (24:39) Supplier risk extends beyond tier one (26:27) Why supplier collaboration matters (27:42) Building a three-to-five-year quantum plan (33:20) Audit technology stack and supplier data (48:47) White paper resources and next steps (51:37) Gartner recognition and key takeaway (54:48) Act now on quantum readiness   Additional Links & Resources: Connect with Akhilesh Agarwal: https://www.linkedin.com/in/akhilesh78/ Connect with William McNeill: https://www.linkedin.com/in/wimcneill/ Learn more about apexanalytix: https://www.apexanalytix.com/ Learn more about Qbiton: https://www.qbiton.com/ Learn more about our hosts: https://supplychainnow.com/about Learn more about Supply Chain Now: https://supplychainnow.com Watch and listen to more Supply Chain Now episodes here: https://supplychainnow.com/program/supply-chain-now Subscribe to Supply Chain Now on your favorite platform: https://supplychainnow.com/join Work with us! Download Supply Chain Now's NEW Media Kit: https://supplychainnow.com/media-kit/ WEBINAR- Amazon Supply Chain 101: Enabling efficiency and growth for businesses everywhere–and everywhere they sell: https://bit.ly/49r8N7D WEBINAR- The Expanding Role of Supply Chain Optimization Teams in Driving Business Impact: https://bit.ly/3PHRAAf WEBINAR- AI that moves at velocity: Cut through latency with agentic workflows: https://bit.ly/4x4626t This episode was hosted by Scott Luton and produced by Trisha Cordes, Joshua Miranda, and Amanda Luton. For additional information, please visit our dedicated show page at: https://supplychainnow.com/leader-briefing-quantum-risk-to-practical-action-1596 The content in this episode, including all audio, videos, visuals, and graphics, is the property of Supply Chain Now and is protected by copyright law. Unauthorized use, reproduction, distribution, modification, or re-uploading of this content in any form is strictly prohibited without explicit written permission from Supply Chain Now.For licensing inquiries or permissions, please contact us at production@supplychainnow.com© 2026 Supply Chain Now. All rights reserved. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Agentic AI has taken off in software engineering, but most CIOs still cannot make agents work in everyday knowledge work in the enterprise. Aaron Levie, co-founder and CEO of Box, explains why that gap exists and what enterprises must change to close it. Drawing on what Box sees across its enterprise customer base, including 68% of the Fortune 500, Levie covers data access, verification, budgets, architecture, and the new roles required to realize real value from enterprise AI agents.======This episode is brought to you by Gartner IT Symposium/Xpo™. Ready to scale agentic AI from pilot to production? Join top CIOs and IT executives at Gartner IT Symposium/Xpo, taking place this October 19th through the 22nd in Orlando, Florida. Over 300 Gartner analyst-led sessions will cover top priorities shaping IT—from AI value, governance, and cybersecurity to cost optimization, IT operating models, and beyond. Get practical, actionable insights—and connect with peers tackling the same challenges you are.Secure your spot today at gartner.com/us/symposium.======YOU'LL DISCOVER✅ Why agentic coding raced ahead while knowledge work agents lag, across three properties: text based work, verifiability, and data access✅ The "AI psychosis" pattern Levie says makes CEOs overestimate agents, and why distance from the last mile of work distorts executive judgment✅ Why you should retry a failed AI project roughly every six months as frontier models keep improving✅ The forward-deployed engineer role, internal and external, and why it becomes essential to enterprise AI adoption✅ Why your IT and data architecture, not the model you pick, often determines what you actually get from agents✅ The end of venture-subsidized tokens, and why the line of business, not just IT, now has to own the AI budget✅ Why Levie says you should not vibe-code core systems of record like ERP or CRM, and where agent value actually accrues✅ Value maxing versus token maxing: how to judge AI ROI and avoid a surprise overnight token bill⏱️ TIMESTAMPS0:00 The promise of agentic coding5:11 Why knowledge work resists agents8:52 The AI psychosis trap for CEOs14:57 Be ambitious, then retry in six months17:25 The rise of the forward-deployed engineer21:09 Frontier models need your data architecture27:14 The end of subsidized tokens31:18 How knowledge workers should prepare36:37 Where software value shifts39:03 Reimagining workflows around abundance43:03 Value maxing versus token maxing49:46 Advice for CIOs

Every organization is told they need context for AI to work. Almost none of them know where to start. The answer has been sitting in their metadata all along — but most CDOs haven't connected those dots yet.

The Anthropic IPO is officially in motion. IPO season is back, and companies like Anthropic and SpaceX are leading the race to go public. Anthropic just filed confidentially with the SEC at nearly a trillion dollar valuation, and Claude has been dominating the AI conversation all year. Almost at the same time, two of their biggest customers, Microsoft and Uber, are quietly pulling back on how much they're actually spending on AI. That tension is what this episode is all about.Here's what we're sippin on:What an SEC filing actually means, and why the timing of Anthropic's IPO matters more than the numberWhy Microsoft and Uber are cutting AI spend even though the tools are workingWhat the Gartner forecast on AI budgets tells us about where this whole thing is headed, and what it means for anyone investing in AI right nowIf you've been watching the AI market and wondering what any of this means for you on the ground, this one is for you.A SpaceX deep dive is coming soon, so stay subscribed for that one.Thank you for listening, and as always... enjoy your first sip!Click here to watch the full episode on YouTubeWhat did you think about this episode?--------------------------------JOIN THE NEWSLETTER: Stay sharp on business, career, and life. First Sip Weekly delivers honest lessons, tips, and real conversations from the show to your inbox every week. https://firstsipweekly.beehiiv.com/CONNECT WITH DEKIMBE: YouTubeInstagram  Facebook LinkedInFOLLOW THE PODCAST:InstagramApple PodcastsSpotifyFor podcast sponsorship & advertising opportunities please contact: firstsippod@gmail.com

AI is delivering pockets of productivity, but far less business value than expected. In this episode of Gartner ThinkCast, Distinguished VP Analyst Fran Karamouzis explores why so much AI ROI remains stuck inside organizations, never reaching the bottom line. While many leaders expect gains in individual productivity to translate directly into financial outcomes, legacy processes, siloed structures and outdated operating models often prevent that value from scaling. In a preview of a recent standout webinar, you'll hear what it really takes to unlock measurable impact — from rethinking how work flows across teams, to redesigning end‑to‑end processes, and leading the organizational change required to make AI stick.   You'll learn: Why productivity gains alone don't guarantee financial returns Where AI value gets trapped inside workflows and operating models How to redesign work around end‑to‑end outcomes, not individual tasks What it takes to lead organizational change and consistently convert AI into ROI   Dig deeper: Register to watch the full "Value is Trapped" webinar Learn how to prove quantifiable value from AI See why Gartner is the world authority on AI  

In this week's Omni Talk Retail Fast Five, sponsored by the A&M Consumer and Retail Group, Mirakl, Ocampo Capital, Quorso, and Veloq, Chris Walton and special guest Chap Achen, Senior Director, Analyst for Digital Commerce and Supply Chain at Gartner, discussed: • Walmart partnering with Subway to deliver made-to-order restaurant meals alongside groceries and household essentials through its Express Delivery service, and why Chris sees it as another example of Walmart executing a cohesive long-term growth strategy built around convenience, loyalty, and retail media expansion: https://www.wsj.com/business/retail/now-you-can-get-a-subway-sandwich-with-your-walmart-delivery-5a003b24 • Amazon expanding Fresh Same-Day Delivery in London, allowing customers to add groceries to the same basket as millions of other products, and whether this signals the future of grocery retail as Amazon continues playing the long game in global commerce: https://www.aboutamazon.com/news/retail/amazon-grocery-same-day-delivery-uk • New York passing legislation aimed at limiting so-called surveillance pricing, and whether regulating AI-driven personalized pricing strikes the right balance between consumer protection and innovation: https://chainstoreage.com/news-briefs/2026-06-05?article=new-york-legislators-pass-bill-curb-personalized-pricing • Amazon rolling out new AI-powered visual search capabilities, including real-time image generation, curated style collages, and visual suggestions, and whether these tools could strengthen Amazon's position as the product search super app: https://chainstoreage.com/news-briefs/2026-06-03?article=amazon-expands-visual-search-capabilities-shopping-app • A startup called The Mall launching an invite-only shopping app designed to aggregate products from more than 10,000 brands into one personalized feed, and whether it represents the future of discovery or another well-intentioned idea destined to be overtaken by larger platforms: https://techcrunch.com/2026/06/01/a-new-app-the-mall-is-building-a-universal-feed-for-online-shopping/?utm_source=Sailthru&utm_medium=email&utm_campaign=Issue:%202026-06-04%20Retail%20Dive:%20Tech%20%5Bissue:85662%5D&utm_term=Retail%20Dive:%20Tech And Duvo CEO Tomáš Čupr also stopped by for 5 Insightful Minutes to discuss why retailers need to stop waiting for perfect data, focus on solving their messiest problems first, and rethink how they approach AI implementation across their organizations. There's all that, plus Barcelona architecture, Vienna bucket lists, Vikings quarterback predictions, European retail favorites, Fashionology Summit takeaways, and why Gen Z may be more comfortable shopping through image-first and intent-driven experiences than retailers realize. P.S. Be sure to check out all our other podcasts from the past week here, too: https://omnitalk.blog/category/podcast/ P.P.S. Also be sure to check out our podcast rankings on Feedspot: https://podcasts.feedspot.com/retail_podcasts/ Music by hooksounds.com

Join Mark Westlake, Founder and CEO of GearBrain, for an essential look at the architecture of our connected future. With over 25 years of digital media and product strategy leadership at foundational platforms like AutoTrader.com and About.com, Mark has built a career helping people navigate complex digital shifts. Today, as the creator of GearBrain's patented IoT Compatibility Find Engine, he is tackling the industry's ultimate bottleneck: fragmentation. In this episode, we move past the era of isolated smart gadgets controlled by disjointed phone apps to explore the rise of GearBrain Assistant—and how autonomous AI agents are quietly turning fragmented smart homes into fully unified, contextual environments.

Welcome to this week's episode of the PEBCAK Podcast!  We've got four amazing stories this week so sit back, relax, and keep being awesome!  Be sure to stick around for our Dad Joke of the Week. (DJOW) Follow us on Instagram @pebcakpodcast   Please share this podcast with someone you know!  It helps us grow the podcast and we really appreciate it!   Simple 6 signup link https://simple6.co/r/CFUR98   Meta's AI support bot was weaponized to hijack Instagram accounts, including the Obama White House page, by tricking it into adding attacker-controlled emails during password resets. https://x.com/zachxbt/status/2061251183675949365?s=46 https://www.bleepingcomputer.com/news/security/instagram-users-locked-out-after-meta-ai-abused-to-steal-accounts/ https://krebsonsecurity.com/2026/06/hackers-used-metas-ai-support-bot-to-seize-instagram-accounts/ Meta's AI customer support bot was socially engineered into resetting account passwords for targets, exposing the new attack surface that AI-powered support creates — and enabling hijacks that MFA would have blocked.   A Google security engineer was arrested and charged with insider trading after using confidential "Year in Search" data to pocket $1.2M on the prediction market Polymarket. https://www.bleepingcomputer.com/news/security/us-charges-google-security-engineer-with-polymarket-insider-trading/ Operating under the alias "AlphaRaccoon," Michele Spagnuolo went 22-for-23 on Google search trend bets using nonpublic internal data — marking the second high-profile Polymarket insider trading arrest this year, following a Special Forces soldier who bet on the Maduro raid he was part of.   New data shows 55% of companies regret their AI-driven layoffs, with half already quietly reversing them — the so-called "Layoff Boomerang." https://medium.com/@curiouser.ai/the-great-ai-layoff-boomerang-68e38c88fa7d Forrester, Gartner, and PwC data confirm the "replace humans with AI" thesis is failing: companies that cut aggressively are scrambling to rehire at higher cost, while firms that augmented their workers are seeing 3x revenue growth per employee.   Google's Verily is seeking EPA approval to release up to 64 million Wolbachia-infected male mosquitoes in Florida and California to crash disease-carrying mosquito populations. https://x.com/bulltheoryio/status/2060810332831129782?s=46 https://www.usatoday.com/story/graphics/2026/06/04/google-mosquito-release-florida-california/90384899007/ The Debug Project's sterile male mosquitoes mate with wild females but produce no viable eggs — a technique that's already shown 80–90% suppression of Aedes aegypti in prior trials and has the internet predictably losing its mind.   Dad Joke of the Week (DJOW)   Find the hosts on LinkedIn: Chris - https://www.linkedin.com/in/chlouie/ Glenn - https://www.linkedin.com/in/glennmedina/ Raja - https://www.linkedin.com/in/rajazkhalid/

Neste episódio do Vamos de Vendas, Gustavo Pagotto recebe Nathalia Koga, fundadora da PartnerPro, para uma conversa sobre como profissionalizar a gestão de parcerias, estruturar canais de vendas e transformar ecossistemas em uma fonte previsível de receita.Ao longo do episódio, Nathalia explica por que a maioria das empresas falha ao criar programas de parceiros: falta dedicação, processos claros, tecnologia adequada e uma estratégia consistente de engajamento. Ela mostra como a venda indireta deixou de ser uma alternativa improvisada para se tornar uma das principais alavancas de crescimento em mercados com CAC elevado e pressão por eficiência comercial.A conversa também aborda o papel do gestor de parcerias, as diferenças entre CRM e PRM, os erros mais comuns na estruturação de canais e o passo a passo para criar um programa de parceiros escalável. Nathalia compartilha ainda métricas essenciais para acompanhar a saúde do ecossistema, além de tendências envolvendo automação, inteligência artificial e gestão baseada em dados.

Le retour d’expérience client a toujours existé dans la communication B2B. Mais il est resté systématiquement sous-exploité, faute d’un cadre et d’un dispositif adaptés pour le valoriser et le rendre vraiment exploitable. C’est précisément le constat qu’Éric Mattern a fait au terme de vingt-cinq ans de terrain dans la tech et la data. Sa réponse est une plateforme dédiée, Show Me The Rex, lancée officiellement fin mars 2026, dont l’ambition est de faire du REX un actif stratégique à part entière pour les acteurs de la tech, de la data et de l’intelligence artificielle. Voici donc le compte-rendu de mon entretien avec Éric Mattern, fondateur de Show Me The Rex (transparence : nous sommes partenaires de Show Me The Rex). Le retour d’expérience client (REX) est un outil stratégique en B2B Les décideurs sont tous à la recherche de retours d’expérience client nous explique Éric Mattern Avant même d’aborder la méthode, les données du marché confirment l’enjeu du retour d’expérience client en B2B. Dans un parcours d’achat B2B profondément digitalisé, la preuve concrète est devenue en effet le premier filtre des décideurs. Ce que les chiffres disent du retour d’expérience client (REX) Les chiffres ci-dessus traduisent une réalité que tout professionnel du B2B comprend de manière intuitve. Au moment où un décideur arrive en contact avec un commercial, il a déjà effectué l’essentiel de son évaluation. Ce qui a orienté son choix, ce sont les preuves qu’il a trouvées par ses recherches. Le REX (retour d’expérience client) est précisément l’un de ces leviers de conviction. Image réalisée avec Gelmini. Sources : Forrester Pulse Study, 2023, Gartner, B2B Buying Journey, 2024 et Content Marketing Institute, 2024. Retour d’expérience client : du terrain à la plateforme D’où vient ta conviction que le retour d’expérience mérite une plateforme entière ? J’ai travaillé pendant vingt-cinq ans sur tous les canaux de visibilité et de go-to-market dans les secteurs technologiques. Et j’ai constaté qu’un levier fort restait systématiquement sous-exploité : le REX. Ces retours d’expérience client ont toujours existé, mais ils n’ont jamais disposé du cadre ni du dispositif qui leur auraient permis d’être vraiment valorisés et exploitables. Or c’est précisément ce qu’attend le marché. Les décideurs veulent identifier des solutions, comprendre des méthodologies, appréhender des démarches concrètes. Le REX rassemble tout cela. En quoi le REX se distingue-t-il du livre blanc classique ? Le livre blanc apporte généralement une vision macro, dépersonnalisée et très orientée marketing. Le REX donne la parole aux praticiens : ceux qui ont mis en place des solutions, éprouvé des méthodologies et résolu des contraintes budgétaires ou politiques internes que les études ne racontent jamais. Les études se concentrent souvent sur les échecs en chiffres. Le REX montre comment une équipe a su contourner une difficulté, gérer un risque et résoudre sa problématique. C’est là que réside toute sa valeur. Le décideur B2B du 21e siècle, surtout en MarTech et en SalesTech, est littéralement noyé de messages et d’informations produits. Mais ce qu’il recherche sont des éléments tangibles. Et qui plus est, pas trop habillés afin qu’ils restent crédibles et percutants – image réalisée avec Midjourney. Les producteurs et les lecteurs de REX À qui s’adressent ces retours d’expérience, côté lecteur ? À tous les porteurs de projet dans une organisation. On pense évidemment aux équipes techniques et aux DSI, mais aussi aux directeurs de l’innovation et de la transformation. Ceux-ci ont besoin de se projeter et d’identifier des partenaires capables d’accompagner leur évolution. Toutes les directions métier sont concernées : finance, marketing, supply chain, RH. On peut même imaginer des investisseurs qui regardent un acteur à travers ses réalisations concrètes pour évaluer sa capacité réelle à aller sur le marché. Et côté producteur, qui sont vos clients principaux ? Sur le secteur tech, data et IA, on trouve aussi bien des éditeurs que des intégrateurs et des sociétés de conseil. Les ESN et intégrateurs sont naturellement très légitimes pour produire des REX. Ils sont au coeur de la mise en oeuvre et de la conduite du changement. Mais les éditeurs ont eux aussi un intérêt fort à valoriser les bénéfices concrets apportés par leurs solutions. C’est un potentiel important que nous accompagnons. La taille de l’entreprise a-t-elle une incidence sur les besoins ? Tous les acteurs y trouvent un intérêt, mais pour des raisons différentes. Les grands groupes ont souvent un problème de partage interne. Ils accumulent des REX sans disposer d’un cadre pour les référencer et les diffuser entre services et départements, avant même de les exposer à leurs futurs clients. Pour les acteurs plus petits, c’est avant tout un enjeu de visibilité et de crédibilité. Le REX démontre leur capacité à résoudre de vraies problématiques marché. Faire un choix de logiciel est rarement anodin, surtout en ces temps de sovereignty washing. Le décideur avisé se tournera donc vers ses pairs pour faciliter son choix. C’est à cela que sert un retour d’expérience client. Image réalisée avec Midjourney. Les bénéfices mesurables du Retour d’expérience client (REX) Peut-on espérer des bénéfices quantifiables, en termes de génération de leads par exemple ? Oui, clairement. Le marché attend des REX. Il est désormais impossible d’organiser un événement, une conférence ou un webinaire sans inviter un client qui vient témoigner de son projet : c’est ce qui attire les clients potentiels. Dans un contexte où l’IA évolue à un rythme soutenu, les décideurs ont besoin de se raccrocher à du concret. Ce concret accélère la transformation d’un prospect en client, parce qu’il lui apporte des garanties tangibles sur la mise en oeuvre et les bénéfices. C’est un vrai levier de visibilité et de conversion pour tout acteur de la tech, de la data et de l’IA. Et pour l’entreprise utilisatrice qui témoigne, quel est l’intérêt ? Les motivations sont multiples. Il y a d’abord une dimension personnelle. Celui qui vient témoigner renforce son positionnement d’expert, en interne comme en externe. Il y a aussi un enjeu d’image de marque et d’innovation. Montrer qu’une organisation se transforme, c’est attirer les talents. Quand une grande entreprise met en avant ses projets de transformation data ou IA, elle envoie un signal fort à des profils qui cherchent des environnements stimulants. La recette d’un bon REX Quels sont les ingrédients indispensables d’un REX réussi ? Il en faut trois. D’abord, un contexte bien décrit et incarné : la problématique métier du client doit être suffisamment précise pour que le lecteur s’y reconnaisse immédiatement. Ensuite, un fil narratif clair, qui parte du problème business jusqu’au résultat mesuré, en passant par le choix de la solution et toutes les étapes de mise en oeuvre. Enfin, des preuves tangibles : indicateurs, données sur les délais, taux d’adoption, gains qualitatifs. Et tout cela partagé par le client lui-même pour que la valeur soit authentique. Disposez-vous d’un modèle structuré pour produire ces REX ? Oui, la plateforme Show Me The Rex propose un template qui structure l’ensemble. On démarre toujours par les enjeux, la problématique et le contexte initial, Puis on aborde le choix de la solution et la démarche projet, Avant de conclure sur les gains obtenus. On inclut aussi systématiquement les bonnes pratiques et les points de vigilance. Un REX doit apporter de la valeur ajoutée réelle, et un projet n’est jamais sans embûches Les erreurs à éviter dans la création d’un Retour d’expérience client Quelles sont les erreurs les plus fréquentes dans la production d’un REX ? La première, c’est de transformer le REX en brochure commerciale : tout lisser, éliminer les tensions, les contraintes, les arbitrages. Un REX trop parfait n’est pas crédible. La deuxième erreur, c’est de verser dans le trop technique ou le trop produit, en listant des fonctionnalités plutôt qu’en racontant la démarche projet. Le troisième écueil, c’est l’anonymisation excessive. Si le client final est trop peu présent dans le témoignage, le REX perd l’essentiel de son intérêt. Il faut embarquer le client, pas le dissimuler. Par où commencer quand on n’a jamais fait de REX ? Je suis directeur marketing dans une entreprise tech. Par où commencer concrètement ? Je vous conseillerais de commencer par cartographier vos cinq à dix plus beaux projets clients récents, en identifiant pour chacun un angle business clair. Sur cette sélection, repérez un ou deux ambassadeurs prêts à témoigner et construisez avec eux un premier format simple : interview écrite, courte vidéo ou webinaire. Ensuite, impliquez très tôt les équipes commerciales, parce que le REX doit leur servir directement dans leur démarche et pour leurs rendez-vous. Une fois ces premières étapes franchies, industrialisez progressivement la démarche en vous appuyant sur un template structuré, comme celui que nous proposons sur Show Me The Rex. Le REX, un atout compétitif durable Éric Mattern a trouvé un angle simple et puissant : là où tout le monde produisait du contenu générique, il a misé sur la preuve concrète. Show Me The Rex arrive au bon moment, dans un marché saturé de promesses et avide de preuves concrètes. Pour les acteurs de la tech et de la data, la capacité à produire et diffuser des retours d’expérience solides est en train de devenir un facteur de différenciation à part entière. Les décideurs qui s’informent en autonomie, les comités d’achat qui comparent en ligne avant tout contact commercial, les talents qui choisissent leur employeur sur la foi de projets concrets… Tous cherchent la même chose. Une preuve que ça marche, racontée par ceux qui l’ont vécu. La plateforme est accessible sur showmetherex.com. À propos d’Éric Mattern Éric Mattern est entrepreneur dans l’univers de la tech et du digital B2B depuis plus de vingt-cinq ans. Après un parcours dans les fonctions commerciales et marketing au sein de plusieurs acteurs de la tech et de la data, il fonde Show Me The Rex, une plateforme dédiée à la production, la structuration et la diffusion de retours d’expérience sur les projets tech, data et IA. À propos de Show Me The Rex Show Me The Rex est une plateforme B2B dédiée à la valorisation des retours d’expérience dans les domaines de la tech, de la data et de l’intelligence artificielle. Elle s’adresse aussi bien aux producteurs de REX (éditeurs, intégrateurs, sociétés de conseil) qu’aux décideurs et porteurs de projet à la recherche de cas concrets pour guider leurs choix. The post Retour d’expérience client (REX) : un outil stratégique appeared first on Marketing and Innovation.

Rabbi Nachman on wealth with Rabbi Baruch Gartner.

AI is pushing the services industry into a new kind of competitive divide. In this episode of Gartner ThinkCast, Gartner experts Craig Lowery and Scott Frederick explore the growing split in AI services — where platform-driven, AI-enabled providers are accelerating ahead, and digital-only models are struggling to keep up. From autonomous agents and intelligent service delivery platforms to the rise of "phygital" experiences, they unpack how AI is moving beyond apps into real-world environments — and what that means for competition, growth and strategy.   You'll learn: Why the AI services market is splitting and who's winning How AI agents and platforms enable "growth without growth" Why hyperscalers threaten digital-only service strategies Where "phygital" experiences create new competitive advantage   Dig deeper: Download the Top 3 Priorities for Tech Services Leaders Learn more about Gartner for Tech Services Practice Leaders See why Gartner is the world authority on AI

As the Fifa World Cup looms, we're joined by experts in sponshorship and talent partnership - Gartner's Nicole Greene and Outreach's Joe Hockley, respectively - to map the upcoming 'most commercial World Cup ever'. As creators' stars continue to rise and budget scrutiny reaches sponsorships, what makes the big-ticket activations still worth it? Hosted on Acast. See acast.com/privacy for more information.

Supply chain is evolving rapidly and AI is changing how decisions are made. In this episode of Supply Chain Now, Scott Luton, Karin Bursa, and Jake Barr talk with Mike Griswold, Vice President Analyst at Gartner, about the key insights from the Gartner Supply Chain Symposium. They explore how supply chain leaders can leverage AI to improve operational efficiency, redesign workflows, and enhance decision-making to remain competitive in the coming years. They discuss the importance of cross-functional initiatives, storytelling for CSCOs, and understanding where technology fits as an enabler rather than the solution. The episode breaks down strategies for shifting supply chain operations toward autonomy, including optimizing decision velocity, redesigning critical workflows, and applying AI thoughtfully to reduce manual handoffs and eliminate inefficiencies. Listeners gain insight into how to balance growth, cost, risk, and talent, and why CSCOs need to communicate their strategic value effectively within the C-suite. The conversation also highlights real-world examples of organizations leveraging technology to enable their workforce, not replace it, and emphasizes the potential of agentic AI in planning and disruption management. Together, the panel explores why focusing on decision stacks and workflow design is critical for AI readiness, how to prioritize high-impact areas for operational improvements, and why relying solely on technology without a defined problem can lead to missed opportunities. They provide guidance for supply chain professionals on preparing for the future of planning, autonomous operations, and AI-enabled decision-making, illustrating the massive potential for efficiency gains and strategic advantage over the next several years.   Jump into the conversation: (00:00) Intro (04:07) AI adoption challenges and budget concerns (06:41) Avoiding siloed implementation of AI (08:56) CSCO influence and strategic storytelling (10:24) Autonomy as the new operating model (15:45) Technology as an enabler, not a driver (20:00) Decision stacks and workflow redesign (27:42) Planning summit highlights and upcoming events (34:28) Agentic AI market potential by 2030   Additional Links & Resources: Connect with Mike Griswold: https://www.linkedin.com/in/mike-griswold-6a68922/ Connect with Karin Bursa: https://www.linkedin.com/in/karinbursa/ Connect with Jake Barr: https://www.linkedin.com/in/jake-barr-3883501/ Learn more about Gartner: https://www.gartner.com/en Learn more about our hosts: https://supplychainnow.com/about Learn more about Supply Chain Now: https://supplychainnow.com Watch and listen to more Supply Chain Now episodes here: https://supplychainnow.com/program/supply-chain-now Subscribe to Supply Chain Now on your favorite platform: https://supplychainnow.com/join Work with us! Download Supply Chain Now's NEW Media Kit: https://supplychainnow.com/media-kit/ WEBINAR- From AI Pilots to Performance: How Supply Chain Leaders Are Scaling Agentic AI: https://bit.ly/49hCqIq WEBINAR- Amazon Supply Chain 101: Enabling efficiency and growth for businesses everywhere–and everywhere they sell: https://bit.ly/49r8N7D WEBINAR- The Expanding Role of Supply Chain Optimization Teams in Driving Business Impact: https://bit.ly/3PHRAAf WEBINAR- AI that moves at velocity: Cut through latency with agentic workflows: https://bit.ly/4x4626t Subscribe to our Newsletter, With That Said: https://www.linkedin.com/newsletters/with-that-said-6966779254495723520/ This episode was hosted by Scott Luton and produced by Trisha Cordes, Joshua Miranda, and Amanda Luton. For additional information, please visit our dedicated show page at:  https://supplychainnow.com/key-takeaways-gartner-supply-chain-symposium-2026-1591 The content in this episode, including all audio, videos, visuals, and graphics, is the property of Supply Chain Now and is protected by copyright law. Unauthorized use, reproduction, distribution, modification, or re-uploading of this content in any form is strictly prohibited without explicit written permission from Supply Chain Now.For licensing inquiries or permissions, please contact us at production@supplychainnow.com© 2026 Supply Chain Now. All rights reserved. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Episode Overview Michael Levitt sits down with executive advisor Chris March to discuss one of the most common yet underaddressed challenges facing founder-led businesses: the founder themselves becoming the primary obstacle to growth. Chris works with organizations generating between $5 million and $20 million in revenue, helping founders identify structural dysfunction, reclaim their time, and build organizations that can operate independently. Key Topics Covered Founder Gravity Chris introduces the concept of "founder gravity," the organizational pull that keeps all decisions, approvals, and responsibilities flowing back to the founder regardless of company size. He explains that structural problems cannot be coached away, and that solving them requires an intentional redesign of how the organization is built. The Delegation Trap A critical distinction emerges between transferring tasks and transferring decision-making authority. Many founders delegate responsibilities without ever relinquishing the sign-off, which trains their teams to wait for approval rather than exercise independent judgment. True delegation requires trusting people with the authority to make decisions, not just the work itself. AI as an Accelerant, Not a Silver Bullet Both Michael and Chris address the widespread rush to adopt AI without first establishing the operational fundamentals it requires. Without documented SOPs and clearly defined workflows, AI cannot fill the gaps. Chris references a Gartner projection that up to 40 to 90 percent of AI projects may be canceled by 2027 due to this misalignment, noting that organizations are often simply accelerating broken systems rather than fixing them. The Business Continuity Test Chris offers a practical diagnostic: if a founder cannot step away from the business for two to three weeks without it breaking down, they do not have a business. They have an expensive job. He uses this exercise with clients as a structural audit to identify exactly where the organization is fragile. Time as a Strategic Asset Chris closes with his single most impactful recommendation: audit how you spend your time. Founders who operate with unstructured, reactive calendars are commonly leaking 10 to 20 hours per week. Time is the one asset that cannot be recovered, and managing it with intention is foundational to everything else. Actionable Takeaways Conduct an honest organizational design review to determine whether your structure still fits the size of your business. Distinguish between delegating tasks and delegating decision-making authority, and make the latter a priority. Document your SOPs and institutional knowledge before introducing any AI or automation tools. Schedule a planned absence and observe what breaks. Use the results as a structural roadmap. Audit your calendar. Reactive scheduling is one of the most common and costly forms of operational drag. About Chris March Chris March is an executive advisor specializing in founder-led organizations. He helps business owners scale past the point where they themselves are the constraint, focusing on organizational structure, operational design, and leadership development. LinkedIn: Active 2 to 3 times per week with insights on founder leadership and organizational dynamics Website: chrismarchadvisory.com LinkedIn:  https://www.linkedin.com/in/christopherrmarch/ Connect with Michael Levitt Website: breakfastleadership.com "If you can't step away from your business for two to three weeks, you don't have a business. You have a very expensive job." -- Chris March

Join Angel Horvat, Founder and CEO of AI Readi, for a candid evaluation of why the corporate rush into generative AI is grinding to an unexpected halt. Despite massive infrastructure investments, the enterprise journey is hitting a hard wall: while 88% of organizations have initiated AI pilots, a staggering 94% remain permanently trapped in pilot purgatory. Drawing on his years leading AI and data strategy at Nike (EMEA) and Gartner, Angel reveals that these failures are almost never a failure of the tech—they are structural failures of the organization itself. In this episode, we discover how to bridge the gap between initial demo and scaled business value.

Live from the Gartner supply chain conference, host Ulf Venne speaks with two guests in separate segments. David Shillingford shares what stands out this year versus last: a shift from broad AI talk to the “so what” and “how,” focusing on autonomy, the autonomous ecosystem, and the need for pristine data; he also discusses physical automation driven by regionalization, reshoring, and workforce challenges, and argues supply chain is firmly a board-level issue amid geopolitics and extreme weather. Austin Myers of Certifical explains how manual, document-heavy vendor onboarding and insurance compliance create inefficiencies and risk, and describes Certifical's real-time verification and monitoring of insurance data to automate compliance year-round; he notes issues like fake documents and emphasizes consolidation to a single source of truth, system understanding, and learning how to improve “tomorrow” beyond AI hype. 00:00 Podcast Intro and Sponsor 00:35 Live at Gartner Orlando 01:17 AI to Autonomy Trends 02:35 Automation and Physical Supply Chain 03:49 Keeping Supply Chain Board Relevant 06:11 Personal Future Theme AI Adjacencies 07:35 Gartner Tips and Networking 08:42 Meet Austin from Certificial 09:22 Why Supply Chain and Manual Docs 10:57 What Cert Official Does 12:02 Fake COIs and Risk Control 14:29 First Gartner Takeaways and AI Hype 16:07 Consolidation and Clean Slate Systems 17:49 Final Takeaways and Sign Off

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

The latest Gartner Market Guide for Telecom Expense Management Services makes clear that TEM is no longer just about invoice processing, inventory and dispute management, or wireless optimization. The category is expanding into broader technology expense management, cloud, SaaS, UCaaS, IoT, utilities, and even emerging areas like AI license sprawl and API consumption.  Tony Mangino is joined by Theresa Knutson, head of the TC2 IT Cost Management Practice, to review the key updates compared to 2024's Gartner Market Guide and to provide additional market input and insights based on TC2's work with its clients on  competitive RFPs, TEM implementations and TEM health check reviews. 

Welcome to SIT Podcast. Just a few hours ago, the eyes of the global tech world turned to the Taipei Music Center, where NVIDIA CEO Jensen Huang delivered a GTC Taipei keynote that sent a jolt through the industry. As we speak, the doors of Computex 2026 have yet to officially open — but NVIDIA has already seized the moment, declaring the arrival of a "new era of PC."In this episode, we take a close look at three defining trends:1. NVIDIA moves into laptop silicon. After more than a decade away, NVIDIA returns to the consumer CPU arena with the N1 and N1X chips. According to supply-chain reports, the high-performance N1X is said to feature a 20-core Arm CPU and Blackwell-architecture graphics, with performance reportedly compared to the desktop-class RTX 5070. More significantly, this could mean the CUDA ecosystem running natively on a Windows-on-Arm laptop for the first time.2. Taiwan — the center of global AI. In his keynote, Huang revealed that NVIDIA's annual spending in Taiwan has grown to roughly $100 billion. The company is also planning an overseas headquarters called "Constellation," reportedly slated to open around 2030 and house some 4,000 employees. From TSMC's manufacturing to Foxconn's assembly, Taiwan has become the heart of what Huang envisions as the AI factory producing computational tokens.3. The rivals respond, and an industry test. Faced with NVIDIA's momentum, Intel has rolled out its Arc G3 chips built for handheld gaming devices, while Qualcomm defends its ground with a $300 entry-level Windows laptop platform. With DRAM and SSD costs climbing, Gartner projects PC prices will rise a notable 17% in 2026 — a real test of what every maker can deliver.歡迎來到 SIT Podcast。就在幾個小時前，全球科技界的目光都聚焦在台北流行音樂中心，NVIDIA 執行長黃仁勳發表了震撼產業的 GTC Taipei 主題演講。此時此刻，Computex 2026 的展覽大門尚未正式開啟，但 NVIDIA 已經先聲奪人，宣告了「PC 新紀元」的到來。在本集節目中，我們將深入解析三大關鍵趨勢：NVIDIA 跨足筆電矽晶片： NVIDIA 睽違十年重回消費型 CPU 戰場，推出 N1 與 N1X 晶片。根據供應鏈報告，高性能的 N1X 據傳搭載 20 核 Arm CPU 與 Blackwell 架構繪圖核心，其性能甚至被拿來與桌機等級的 RTX 5070 相比。更重要的是，這可能代表 CUDA 生態系將首度原生運行於 Windows-on-Arm 筆電。台灣——全球 AI 的中心： 黃仁勳在演講中透露，NVIDIA 每年在台灣的支出已增長至約 1,000 億美元。此外，NVIDIA 正計畫興建名為「Constellation」（星座）的海外總部，預計 2030 年啟用，將容納約 4,000 名員工。從台積電的製造到 Foxconn 的組裝，台灣已成為黃仁勳眼中生產「計算代幣」的 AI 工廠核心。競爭對手的回擊與產業逆風： 面對 NVIDIA 的強勢，Intel 隨即推出專為掌上型遊戲機設計的 Arc G3 晶片，Qualcomm 則以 300 美元的低價 Windows 筆電平台防守市場。然而，在 DRAM 與 SSD 成本飆升的壓力下，Gartner 預測 2026 年 PC 價格將大幅上漲 17%，這對所有廠商來說都是嚴峻的考驗。

Neste episódio do Vamos de Vendas, Gustavo Pagotto recebe Douglas Gomes, Diretor de Estratégia e Governança na Bem Mais Benefícios, e aborda como governança comercial, tecnologia e estratégia podem impulsionar crescimento saudável em operações complexas de vendas B2B.Ao longo do episódio, Douglas explica por que governança não significa burocracia, mas, sim, criar limites claros para crescer com sustentabilidade, previsibilidade e eficiência. Ele mostra como políticas comerciais, CRM e inteligência artificial ajudam a evitar “vendas com rastro de destruição” e fortalecem a capacidade da empresa de escalar sem comprometer a entrega ao cliente.A conversa também explora os desafios de vendas complexas envolvendo sindicatos, benefícios corporativos e múltiplos stakeholders. Douglas compartilha aprendizados sobre negociação, relacionamento institucional, confiança, treinamento comercial e o papel da tecnologia na construção de operações mais inteligentes e orientadas por dados.

Tu credibilidad bien trabajada antes de la reunión te hace llegar con la venta medio decidida. Aquí tienes el plan de 90 días. Apúntate a la newsletter semanal aquí → https://eticacomercial.com/newsletter — y recibe la auditoría de credibilidad del vendedor. La venta ya no se decide cuando te sientas con tu cliente. Se decide antes: él te busca, se forma una opinión de ti y llega a la reunión a confirmarla. No es un detalle menor cuando el 94% de los grupos de compra se ordenan por preferencias y el 80% acaba comprando a su favorito inicial. La buena noticia es que esa parte la controlas. En este episodio te doy un plan de 90 días, en tres fases, para construir tu credibilidad antes de entrar por la puerta. Lo que vas a aprender: — Por qué la decisión de tu cliente se cocina antes de la reunión, no durante. — Las tres fases del plan: diagnóstico, pruebas, y método y medición. — Mes 1: cómo buscarte como te busca tu cliente — Mes 2: cómo convertir a tus últimos 10 clientes en casos de éxito y quedarte con tres sólidos como mínimo. — Mes 3: qué medir para saber si tu tasa de cierre ha mejorado de verdad. — El dato de Gartner que explica por qué en 2030 el vendedor humano pesa más, no menos. Por la newsletter te llega la auditoría de credibilidad del vendedor para empezar tú mismo por la fase de diagnóstico. Apúntate aquí → https://eticacomercial.com/newsletter

The structural shift highlighted in this episode is a move from simple AI enablement to a managed service model centered on agent governance, enforcement, and workflow automation within IT environments. The episode identifies unmanaged AI agents as a source of escalating risk, citing vendors like Scalepad shifting from remote monitoring to SaaS and AI usage discovery, and referencing research and audits from SNCC and Verizon that identify tangible security flaws and unapproved AI activity within organizations. Managed service providers are increasingly positioned as the operational layer that defines and enforces governance over automation systems, rather than simply deploying AI tools. The primary evidence for this shift is found in audit findings and market reports. SNCC's audit of 4,000 AI agent skills showed over a third had at least one security flaw, while Verizon's data cited by The Register noted a fourfold increase in employees using unauthorized generative AI, with 28% of data loss prevention violations involving code or proprietary data submitted to AI platforms. Gartner, as reported by The Register, predicts 40% of organizations will demote or remove AI agents due to failed governance efforts—attributing the problem to all-or-nothing approaches that lead to operational and compliance failures. Secondary developments reinforce the move toward operationalized governance. Scalepad and Watchguard are bringing AI and SaaS governance capabilities to the MSP channel, with product releases focused on real-time discovery, policy enforcement, and automation control. Incidents like Anthropic's leak of its full source code for Claude Code, exposing permission and sandboxing details, illustrate how transparency in AI agent operations can also create attack vectors—emphasizing the need for robust operational controls and ongoing auditability. The market is shifting to sell "coherence"—packaging identity, permissions, and workflow automation—rather than just technological capability. Operationally, the consequences for MSPs include increased responsibility for defining and enforcing permission boundaries, approval rules, and evidence collection. Failure to address agent governance will expose providers to operational ambiguity, unpriced liability, and recurring support burdens. The guidance is to move beyond AI enablement projects and toward agent operation retainers that include clear workflows, permission maps, execution logs, and contractual clarity on responsibility and incident management. MSPs that cannot prove and control agent behavior risk inheriting the complexity and fallout from system failures or misuse. 00:00 Shadow AI Surge  05:01 Context Is Infrastructure 07:46 Agent Control Plane 11:16 Why Do We Care?  Supported by:  JumpCloud TimeZest 

Shoot us a Text.Episode #1357: Honda rides hybrid momentum toward bigger market share, Ford gets an AI-fueled stock boost from repurposed EV batteries, and Target bets family-friendly upgrades will drive customer loyalty.Show Notes with links:Honda says it's aiming for more than 9% U.S. market share in 2026 and thinks 10% is within reach as hybrids continue to surge. With gas prices climbing and EV demand cooling, the company says its flexible production strategy is helping it stay ahead.Honda finished last year with 8.7% U.S. market share, hit 10% in April of this year and still expects to grow sales 4% this year to around 1.5 million vehicles.Hybrids made up nearly a third of Honda brand sales in Q1, and the company is ramping up production and marketing around Civic, Accord, CR-V, and Prelude hybrids.Despite tariff uncertainty, Honda says its North American manufacturing footprint protects it from major disruption with nearly 99% of vehicles built in-region.Honda says hybrids are now the sweet spot, expecting them to land in the “mid-to-low 30 percent range” of total sales this year as gas prices push more buyers away from pure ICE models.Ford stock is suddenly surging, not because of trucks, but because Wall Street is betting on Ford becoming an AI-era energy player. The company's new Ford Energy division plans to repurpose EV batteries into massive storage systems for data centers and utilities.Ford stock jumped 28% in two weeks after launching Ford Energy with a $2 billion investment aimed at powering AI data centers and utilities.The business will repurpose excess EV battery capacity into stationary storage systems, putting Ford into competition with Tesla and LG Energy Solutions.Investors are especially bullish on Ford's partnership with Chinese battery giant CATL, with one analyst valuing the new energy arm at up to $10 billion.Ford says it plans to deploy at least 20 gigawatt hours of battery storage annually, including a major supply agreement with energy company EDF starting in 2028.BNP Paribas analyst James Picariello summed up the shift saying: “It's hard to find another comparison on the OEM side of things with the exception of Tesla.”Target is betting that winning over busy families doesn't require flashy AI, it just requires cleaner bathrooms, smarter shopping carts, and fewer parenting headaches. The retailer says those small upgrades could create much bigger long-term customer loyalty.Target is investing $1 billion into customer experience upgrades, including 130+ store remodels focused on family-friendly improvements.New shopping carts feature larger cupholders, deeper child seats, and flat storage surfaces designed to make shopping easier for parents.The retailer says modernized bathrooms are a surprisingly important loyalty driver because “busy families” are now Target's core growth audience.Executives admitted Target lost focus in recent years and are now doubling down on creating “the most delightful experience in retail” for younger families.Gartner analyst Halle Stern said the smaller upgrades matter more than flashy tech: “The minor changes are making this huge difference.”Join Paul J Daly and Kyle Mountsier every morning for the Automotive State of the Union podcast  as they connect the dots across car dealerships, retail trends, emerging tech like AI, and cultural shifts—bringing clarity, speed, and people-first insight to automotive leaders navigating a rapidly changing industry.Get the Daily Push Back email at https://www.asotu.com/JOIN the conversation on LinkedIn at: https://www.linkedin.com/company/asotu/

Most organizations default to replicating data: copying it from source systems into warehouses and lakes so their tools can reach it. Anu Jain, founder and CEO of Nexus One, thinks that's the wrong answer. Malcolm isn't so sure and that's where it gets interesting.

Kaylin Lohmaster, Director Analyst in Gartner's HR practice, said in a statement with the release of the study's results, "AI is ultimately going to reverse the course and result in more jobs gained than those lost by twenty twenty-eight." This does depend, however, on the need for organizations to rethink how employees gain expertise and grow within the organization, or companies will find themselves without ready talent for the jobs AI will help to create in the future. As companies continue to harness the capabilities of AI in the workplace, it will become increasingly important for HR leaders to take a more skill-centric approach. Hosted by Simplecast, an AdsWizz company. See https://pcm.adswizz.com for information about our collection and use of personal data for advertising.

On this episode of The Voice of Retail, host Michael LeBlanc welcomes Jackie Swanson, Managing Partner at Gartner Consulting, for a wide-ranging and highly practical conversation about artificial intelligence, agentic commerce, and the rapidly changing future of retail. Swanson brings Gartner's global perspective to one of the most urgent strategic issues facing retailers today: how AI is fundamentally reshaping customer discovery, commerce channels, operating models, and competitive advantage. Drawing on Gartner's extensive AI research and consulting work with retailers and consumer brands in Canada and around the world, she explains why generative AI represents a structural shift unlike previous technology waves such as cloud computing or mobile commerce. At the centre of the discussion is the rise of “agentic commerce” — a world where AI agents like ChatGPT, Claude, and future large language model interfaces increasingly sit between retailers and consumers. Instead of browsing websites or apps, customers are beginning to shop conversationally through AI interfaces that recommend, filter, compare, and eventually complete purchases on their behalf. Swanson explains why this represents an entirely new commerce channel and why retailers must rethink their strategies before they lose control of customer discovery and loyalty. Michael and Jackie explore the major implications for SEO, branding, merchandising, customer relationships, and organizational design as AI-driven commerce accelerates. Swanson introduces the emerging concept of “AEO” — AI Engine Optimization — and discusses how retailers must rethink product data, customer signals, and digital infrastructure to ensure their brands surface inside AI-driven shopping experiences. The conversation also tackles one of the industry's biggest strategic questions: who inside a retail organization should own AI? Swanson argues that an AI strategy cannot be confined solely to IT or digital teams. Instead, it must become a CEO-level, cross-functional transformation involving merchandising, marketing, loyalty, operations, and technology leadership. Swanson outlines three critical priorities retailers must address over the next 12 to 18 months: establishing strong AI governance and ethical frameworks, cleaning and restructuring enterprise data for AI readiness, and creating clear organizational ownership for AI strategy and execution. The episode closes with a fascinating discussion about which retail categories may benefit most from AI-driven commerce, why smaller challenger brands could gain unexpected advantages, and why retailers that adopt a “wait and see” approach risk falling dangerously behind. Michael LeBlanc is the president and founder of M.E. LeBlanc & Company Inc, a senior retail advisor, keynote speaker and now, media entrepreneur. He has been on the front lines of retail industry change for his entire career. Michael has delivered keynotes, hosted fire-side discussions and participated worldwide in thought leadership panels. He brings 25+ years of brand/retail/marketing & eCommerce leadership experience with Levi's, Black & Decker, Hudson's Bay, CanWest Media, Pandora Jewellery, The Shopping Channel and Retail Council of Canada to his advisory, speaking and media practice.Michael produces and hosts a network of leading retail trade podcasts, including the award-winning No.1 independent retail industry podcast in America, Remarkable Retail with his partner, Dallas-based best-selling author Steve Dennis; Canada's top retail industry podcast The Voice of Retail and Canada's top food industry and one of the top Canadian-produced management independent podcasts in the country, The Food Professor with Dr. Sylvain Charlebois from Dalhousie University in Halifax.Rethink Retail has recognized Michael as one of the top global retail experts for the fifth year in a row, the National Retail Federation has designated Michael as on their Top Retail Voices for 2025 and 2026. Thinkers 360 has named him on of the Top 50 global thought leaders in retail. If you are a BBQ fan, you can tune into Michael's cooking show, Last Request BBQ, on YouTube, Instagram, X and yes, TikTok.Michael is available for keynote presentations helping retailers, brands and retail industry insiders explaining the current state and future of the retail industry in North America and around the world.

Schneider Electric, a global energy technology leader, will showcase the latest advancements in its AI-Ready solutions portfolio, designed to support next-generation AI factories and large-scale digital infrastructure, during Datacloud Global Congress 2026. As governments and businesses globally continue to accelerate investments in artificial intelligence (AI) to drive economic growth, AI infrastructure is becoming one of the defining industrial challenges of the decade. According to Morgan Stanley Research, nearly $3 trillion of AI-related infrastructure investment is expected to flow through the global economy by 2028, while Gartner forecasts worldwide AI spending will exceed $2.5 trillion in 2026 alone. Central to the AI revolution are data centers, which are transforming into the AI factories of the future. As AI workloads become more compute-intensive, operators are facing unprecedented demands around power availability, rack density, cooling and infrastructure resiliency. Throughout Datacloud Global Congress, which takes place from the 1st to the 4th June 2026, Schneider Electric will demonstrate how organizations can deploy AI-ready infrastructure responsibly through next-generation power architectures, liquid cooling technologies, intelligent software, and digital services. Keeping pace in the race for AI On 2nd June at 10.30am, Frédéric Godemel, EVP, Energy Management Business at Schneider Electric, will join executives from Oracle, DATA4, QTS Data Centers and CBRE for the Keynote Panel, entitled 'How is the Data Center Ecosystem Keeping up with AI Demand', to discuss why neocloud's have become the next disrupter in the market, how their deployments differ from hyperscale and enterprise requirements, and how Europe can keep pace in the race for AI. Additionally, on the 2nd June at 12pm, Schneider Electric will host a panel discussion exploring how operators can de-risk their energy investments via innovative project structures, stronger utility collaboration, and greater engagement with local governments. Thierry Chamayou, Vice President of Cloud and Service Providers in EMEA at Schneider Electric, will join industry experts from GreenScale, Trench Group, Kao Data, JSM Group and Solar Turbines to discuss the strategies needed to support responsible AI infrastructure growth. "AI is fundamentally reshaping the future of digital infrastructure, creating new demands around power, cooling and resiliency, at unprecedented scale," said Marc Garner, Global President, Cloud and Service Provider Segment, Schneider Electric. "At Datacloud Global Congress, we will demonstrate how collaboration across the ecosystem is enabling the next generation of AI factories and helping organizations build scalable, resilient and sustainable infrastructure, built for the AI era." Design, build, simulate and operate On the 1st June at 12pm, Sébastien Cruz-Mermy, VP Datacenter Innovation at Schneider Electric, will lead a technical innovation session focused on the future of AI factories and the infrastructure strategies required to support them. During the session, Sébastien will explore how ultra-high-density rack design, next-generation DC power delivery architectures and resilient cooling strategies are becoming critical to enabling the future of AI infrastructure at scale. The session comes as Schneider Electric continues to expand its AI infrastructure ecosystem. Later, Schneider Electric and NVIDIA will also co-host an exclusive invitation-only executive briefing, bringing together senior leaders and industry experts to discuss the evolving landscape of AI-driven infrastructure and explore NVIDIA's 5?Layer Cake framework, including the DSX Blueprint, supported by Digital Twins, that bridge the gap between design, deployment, and operations. Designed as a high-level executive networking experience, the event will feature strategic discussions focused on how advanced technologies are reshaping data centers and accelerating innovation at...

Agentic AI is likely the most hyped technology in enterprise IT, but its long-term potential is still just as real. In this episode of Gartner ThinkCast, Distinguished VP Analyst Rajesh Kandaswamy breaks down the 2026 Hype Cycle for Agentic AI — what it is, why it matters, and how leaders can separate real opportunity from market noise. From rising investment interest to the challenges of governance, integration and scale, this conversation unpacks where organizations are today — and what comes next.   You'll learn: What Gartner Hype Cycles reveal and how to use them effectively Why agentic AI is at peak hype, but still early in adoption The real barriers to success: governance, guardrails and clean data How to identify high-value use cases and avoid "agent washing"   Dig deeper: Download the full Hype Cycle for Agentic AI See why Gartner is the world authority on AI Try out AskGartner for more AI-powered insights  

Join co-hosts Peter Argondizzo and Patrick Daley as they break down a recent Gartner study and what it means for the translation industry. The study found that 80% of large companies cut jobs for AI, yet those cuts did not improve financial returns. Peter and Patrick connect the Gartner findings to real risks for language service providers, including the brand damage that comes from replacing skilled linguists with AI, the questions buyers should ask their providers about AI use, and the difference between using AI to grow the business and using AI to reduce headcount.

In this special episode of The Daily Beast Podcast, Joanna Coles speaks with Dr. John Gartner and Dr. Bruce Davidson about the alarming signs they believe point to Donald Trump's physical and cognitive decline, from garbled speeches and late-night posting frenzies to what Davidson argues are visible symptoms of a past stroke. The two doctors break down Trump's increasingly erratic public behavior, explosive decision-making, obsession with personal glorification, and troubling verbal confabulations, while warning about the risks of unchecked power in the hands of a president they believe is rapidly deteriorating. Drawing on decades of medical experience and years of closely tracking Trump's behavior, Gartner and Davidson deliver a chilling analysis of the man currently commanding America's military and political future. Sign up for your one-dollar-per-month trial today at https://shopify.com/dailybeast #ad Learn more about your ad choices. Visit podcastchoices.com/adchoices

Sean Barnes opens this episode from Nashville, having just stepped off the stage after delivering a personal branding keynote to a room of cybersecurity executives. He reflects on how unlikely this version of his life would have sounded five years ago, when he was still the extreme introvert who couldn't imagine traveling the country to speak in front of hundreds of people. In this conversation, he walks through the actual journey from quiet executive to in demand speaker, including where most people start, where most people quit, and what separates the executives who eventually own a stage from the ones who never get past their first panel. He shares the 75/25 framework he uses with anyone he coaches on keynotes, why social proof matters more than people realize, and gets honest about the emotional moments that hit him mid talk when he remembers how far he's come.   Key Moments 00:00:01 — Setting the scene in Nashville after a cybersecurity keynote, and the realization that sparked the episode 00:00:32 — The five years ago version of Sean who would have laughed at the idea of giving keynotes 00:01:23 — Why he started on panels at Gartner and Cyber Risk before ever giving a keynote 00:02:09 — The first move anyone should make: tell event organizers you want to speak 00:02:57 — What pre call prep with moderators actually looks like 00:03:16 — Where most people quit, and why one panel isn't enough 00:04:03 — Social proof, pictures from stage, and how that gets you access to bigger stages 00:04:48 — The mistake people make when they finally get offered a keynote 00:05:31 — The 75 to 80 percent core story plus 20 to 25 percent audience nuance framework 00:06:24 — What it actually feels like to be the only person on stage 00:07:10 — Reading the room: who's leaning in, who's on their phone 00:07:36 — The emotional moments mid talk when the journey hits him 00:08:03 — Marathon not sprint, plus the coaching question 00:08:27 — Why he does this in the first place   Key Takeaways Start on panels, not keynotes. The moderator carries most of the pressure, the audience splits its attention across multiple people, and your reps cost a lot less than they would solo on a stage. Sean did this for years before ever giving a keynote, and it's the lowest stakes way to find out if speaking is something you actually want to keep doing. One panel isn't enough. Reps are the whole game. The biggest reason people never become speakers isn't that they bombed their first panel. It's that they did one, walked off, and never asked for the second. The executives who keep going are the ones who get better, build social proof through pictures and posts, and end up with people coming to them. Your story is 75 to 80 percent of every talk you give. The other 20 to 25 percent is audience. When event organizers ask what you want to talk about, the worst answer is "whatever you want." Have a core narrative you can repeat across every stage and then tweak the remaining slice to land with the room in front of you. HR executives need a different flavor than technology executives, but the spine of the story stays the same.   Podcast Show Notes – Episode 283 | 05.26.2026 Episode Title: How Do You Start Speaking on Stage When You're an Introvert? Sean Barnes Breaks Down the Process     Host: Sean Barnes Website: https://www.wolfexecutives.com   https://www.seanbarnes.com   LinkedIn: https://www.linkedin.com/in/seanbarnes/ https://www.linkedin.com/company/wolfexecutives https://www.linkedin.com/company/thewayofthewolf/ LinkedIn Newsletter: https://www.linkedin.com/newsletters/7284600567593684993/   Twitter: https://x.com/seanbarnes https://x.com/wolfexecutives   Instagram: https://www.instagram.com/the_seanbarnes https://www.instagram.com/wolfexecutives   TikTok: https://www.tiktok.com/@the_seanbarnes   Facebook: https://www.facebook.com/theseanbarnes

According to research by Gartner, 84% of business leaders report their company's identity must significantly change to achieve strategic objectives. But how do you know when the time is right? And more importantly, how do you ensure that change goes smoothly? Riley Rogers: Welcome to the Win/Win Podcast. I’m your host, Riley Rogers. Join us as we dive into changing trends in the workplace and how to navigate them successfully. According to research by Gartner, 84% of business leaders report their company's identity must significantly change to achieve strategic objectives. But how do you know when the time is right? And more than that, how do you ensure that the change goes smoothly? Here to discuss this topic is Shelly Luciano, Vice President of Strategy at Leah. Thank you so much for joining us today, Shelly. I’d love if you could just kick us off by telling us a little bit about yourself, your background, and your role. Shelly Luciano: I’m Shelly Luciano. I’m Brazilian. I studied industrial engineering in Brazil and France. I started my career working in infrastructure and R&D, so that experience gave me a strong foundation in execution early on. Back in 2014, I moved to the UK to pursue my MBA at London Business School. I used business school to transition from a technical background into strategy on a global scale. After my MBA, I spent three and a half years in strategy consulting. That work helped me learn how companies compete in larger markets. What I realized is that although strategy consulting is intellectually fascinating, I was being more and more drawn to the business. So I transitioned into tech about five years ago. I joined what was then ContractPodAI, which is now Leah. Today, I’m Vice President of Strategy and Operations. My team focuses on aligning strategic priorities, supporting cross-functional execution, and ensuring our go-to-market approach reflects both where the company's headed and what our customers need. One of the most valuable parts of my role is staying close to our customer base. These conversations give me and the company a lot of valuable insight into how the market is evolving and how organizations are actually adopting AI. I then bring these insights back into the organization, back into Leah, to inform product direction, enable our customer success team, and ensure that our strategy remains grounded in real market needs. Ultimately, my role sits at the intersection of strategy, go-to-market execution, and customer insight. RR: I think you have a fascinating role, to be quite frank, and also a really wonderful story. To go from “I'm trained as an engineer,” to “now I've got my MBA, I'm in consulting, and today I work in tech and have for the last five years,” that's really an incredible journey that I imagine must have given you a real wealth of experience that serves you very well at Leah. SL: It’s funny because if you asked me when I graduated in Brazil what I'd be doing now, I wouldn't have guessed. The world has changed so much. My world has changed so much. So I feel very lucky and blessed to do the job that I do. I really like it. My company's fascinating. My role is fascinating. My company gives me room to change as long as I'm adding value and my team is adding value. So I'm really happy. RR: Yeah, and that's certainly evidenced by the fact that you spent five years in one tech company when the average tenure is just over two, so something really must be going right. I'd love to dig a little bit deeper into this exciting, challenging, and evolving role that's been keeping you at Leah for the last few years. You're there to keep an eye on what's happening in the market so your reps can tell a story and your engineering teams can build a product that the market both wants to hear and to see. More than that, you're also there to break down silos and operationalize your strategy so it really shows up in everyday workflows. In this work, what kind of things tend to crop up—challenges or obstacles that make it difficult to build the connections that bridge that gap between strategy and execution? SL: For me, there are two major challenges I see in equipping internal teams to drive growth. First, strategy and execution often evolve at different speeds. A leadership team can align relatively quickly on a strategic direction, but translating that direction into how hundreds or thousands of people operate day to day can take much longer. For me, strategy only really lands when it keeps showing up in customer conversations. What you portray needs to align with what your client base and the market are seeing. If the people talking to customers every day don't understand the problems that your company is solving and why, then your strategy hasn't really landed. It's just a deck. It's lovely to build these ideas, but you've got to be able to execute on them. As companies scale, the complexity increases much faster than people expect. You have more industries, more personas, a larger product portfolio, and if you don't have the right systems and alignment, that complexity can create a lot of confusion internally. And if your team is internally confused, then everyone else is too. RR: So your job is to keep an incredibly close pulse on the market and on technology as they both evolve. And it's a little bit of an endless task because the market will always shift and technology will always evolve. So you've got to be right there with it as the voice of reason for the organization, telling everyone, “Okay, here's what's happening, and here's how we're going to move with it.” As someone who, by job description, is very comfortable with change and evolution, can you share with us how you're thinking about how Leah, as an AI-first company, is keeping pace through major technology shifts, and then how other organizations should think about translating these shifts into their own organizational and operational processes? SL: Leah has been an AI-first company for years, way before LLMs. What changed with LLMs is the speed and scope at which we can execute our strategy much faster. We've been using machine learning in our platform for a long time, so the foundation was already there. We already had a really strong team. What LLMs did was introduce a step change, and our founder, Sarvarth, is a visionary. He saw straight away how that was going to change the game. All these changes in the past few years did not change our direction, but for the client base, what they can really see is that LLMs have expanded the use cases that we can deliver. And I think that's what matters to customers—how can we solve more of their problems? With Leah, we've moved from traditional automation into what we describe as an agentic operating system. That means our AI is not just supporting workflows. We can do much more than that. We can now reason across data, understand context, and orchestrate actions. That is so exciting, as you can imagine, for someone who works in strategy because it feels limitless. Going beyond static workflows, you now have systems that can adapt dynamically to the problems that we're solving. And that's where the speed and pace of innovation really comes in. Once you move into an agentic model, you're no longer limited to predefined use cases. You can continuously expand how AI is applied across not only our internal organization but also our client base. From a strategy and operations perspective, the challenge is not adopting the technology, because we've been able to do it and we continue to do it. The challenge is how do we operationalize it? Strategists love frameworks, so if I had to group it, I'd say there are three ways I think about this. The first part is strategic focus. The risk with AI, within all this opportunity, is diffusion. So we need to be deliberate about which use cases we prioritize. We need to define where we can deliver the most value, because being AI-first doesn't mean doing everything. It means scaling the right use cases. The second part is how do we translate that into go-to-market execution? As I mentioned before, strategy only really lands when your customers can speak about you. Organizations need to understand how to position AI. We need to be able to explain it clearly so we can apply it across different industries and contexts. That's where systems like Highspot can really help us translate this within our organization and externally. The third thing is continuous customer feedback loops, because customer proximity is the most valuable strategic signal we can have. To be a strategist in tech, your goal is not to define a static AI strategy. You're always on a feedback loop, and you need to be agile. The tools and teams that support you need to be comfortable with always learning and always putting our best foot forward. RR: So as you alluded to, you and the team actually recently went through a rebrand. From ContractPodAI, you became Leah, named after the organization's flagship AI offering. I'd be curious to hear how, with these challenges to strategy-aligned execution in mind, you and the team made sure that everyone was telling the same story and supporting the same strategy, even as the brand message and narrative shifted so drastically. SL: Leah was already a product of ours that had taken a bigger and bigger piece of our client base. So moving from ContractPodAI, which was very contract-focused, into Leah made sense because the Leah product had become a much bigger part of who we were and our identity. When we came into becoming the Leah brand, we were ready in many ways. You're never fully ready for a full rebrand. There's still a lot of work. But we had the tools and processes in place to help us in that transition. In 2021, we had just raised $150 million from SoftBank's Vision Fund. At that point, I knew we were going to grow exponentially, so I wanted to manage as many growing pains as possible. At that stage, we were evolving from having a relatively general pitch to a much more sophisticated message tailored by industry and persona, and our platform was expanding even back then. I realized that we needed a way to ensure that our entire organization stayed aligned on how we communicate value because, as companies scale, complexity increases. More products, more industries, more ways customers can use your platform. So when trying to solve that problem, that's when we looked into Highspot. We wanted Highspot to help us ensure the entire organization could work from the same narrative. Highspot is now used across our sales teams, SDR teams, CX teams, and actually it has expanded because once people hear about it, they want to know what the go-to-market teams are presenting. I'm really glad we implemented Highspot four or five years ago now because since then the customers that we serve have grown and the breadth of our platform has grown. Putting things in place before you come to that stage is actually really important. RR: Can you walk through where Highspot fit into the picture and how you and the team used it to trickle down that message so, to your earlier point, strategic vision didn't get lost in that wonderful game of telephone between C-suite strategy and individual contributor execution? SL: When I came in, we had a general pitch on how we went to market. One of the reasons I was hired is because I came in to do an industry strategy, and there was a lot of research involved—both internally, looking at how we were using the tool for certain industries, and externally, looking at market potential and product fit for each industry. Based on that, I prioritized a few industries to start developing content and enablement around. That's when I looked into Highspot because we had a SharePoint at the time, and it was already not fully updated. People pasted things on top of it or saved materials to their computers and never checked the right version again. I came to Highspot with a very clear use case. There were other features and capabilities that we wanted, but the core problem I wanted to solve was creating one single source of truth. It seems like a SharePoint should do that just fine, but it didn't because we needed something that would help us as we continued scaling product growth, use case growth, and overall organizational growth. It was going to become really hard to enable everyone and make sure people accessed the information they needed at the right time. That's what we got Highspot for, and that's what we continue using it for. RR: So once you defined the strategy of the rebrand, where did you see friction between what you were telling reps—“Here's our new message, here's our new strategy”—and what they were actually saying and doing in the field? Where was there misalignment, and how did you and the team tackle that? SL: Once the strategy and story are defined, the real challenge is behavioral change at scale. Organizations tend to align on a narrative relatively quickly at a conceptual level. But alignment alone is not the end goal. Execution is. Execution, particularly in customer conversations, can take time. The friction I've observed is not usually resistance. It's normally a knowledge gap or a confidence gap. Sometimes you have the knowledge, but you're not confident in that knowledge. As your platform evolves and you're no longer selling a single product for a very defined use case, you're helping customers on a journey. You need to understand a variety of challenges across different workflows, industries, and personas. In that environment, the challenge is not whether teams understand the narrative. The bigger challenge is whether they can apply it dynamically in real conversations. What we consistently see is that reps are comfortable with the core story, but uncertainty appears around the edges. When a customer asks something slightly outside the standard pitch or challenges how the solution applies to their specific context, that's where execution can break down. For reps to feel confident using the right language and positioning the platform correctly, they need to understand things at a deeper level. With all the advancement in AI, we can develop things so quickly, but that also creates challenges because emerging technologies move incredibly fast. There's something new every week. If your software can deliver so much, there are a lot of questions reps need to feel prepared for, and we need to give the organization the ability to operate with clarity and confidence in this complex environment. Highspot has helped us do part of that, particularly in making sure teams understand how we're positioning ourselves, but there's also a lot of technical enablement and training that we need to make sure they complete. Teams have to prepare for conversations in many different contexts, and that fundamentally changes how an organization executes. You can't just memorize anymore. You need to understand. Ultimately, scaling a company is not about having the best strategy on paper. It's about ensuring that all of your employees can bring that strategy to life and communicate it with passion. RR: Yeah. I love the way you landed that because you're 100% right that to a certain extent it can be a knowledge gap, and another layer can be that confidence gap. But then that third and final layer is the context gap. Can reps embody the strategist? Can they embody the strategy? Reps want to do well. It benefits them and it benefits you. So when things are going awry, it's not intentional. It's hard to get up to speed and start delivering in the field, especially when things are changing so rapidly. If you can slowly bridge all those gaps, your strategy starts to encompass the whole company. And again, it's such a cool role that you have, getting to bring that to life and then watch it trickle out into every customer conversation your teams are having. You mentioned 2021 and implementing Highspot, and it's been five years since then. In that time, what key results have you seen? Any wins that you're especially proud of, whether early on or today during this rebrand phase? SL: Highspot is now widely used across the organization. We have the sales team, SDR team, CX team, and leadership all using it. Initially, we bought licenses only for the sales team, and since then we've more than doubled, if not tripled, our licenses because people continue asking for access. I think that's one of the biggest indicators of value. What I continue to see, and why I continue investing in the platform, is consistency. You want to be consistently delivering and positioning yourself in the market. As our product offering expanded and we began serving multiple industries and personas across different regions, it became critical that teams could access the most relevant materials quickly. Highspot ensures that everyone across the organization is working from the same narrative and delivering a consistent experience to customers and prospective customers. That alignment becomes very important as the organization scales. One of the most impressive things after the rebrand was that from the very next day, everything had changed. Everything in Highspot was Leah. I knew the marketing team had been working incredibly hard, but from day one everything was available to us. That's what tools are for. When you buy a tool, you want to make sure it makes you look good. RR: I can imagine that's a monumental task—to take every single piece of collateral, every single deck you've ever built, and overnight update it so every rep has all the content, messaging, and everything they need to hit the ground running on day one of the rebrand, day one of Leah. To the point of bringing strategy to life, you really did it. Very early on, you said you're never ready for a rebrand. And yes, it's certainly a huge task, but it does seem like you've come through it successfully. That takes me to the last question I had for you, which is: for other leaders navigating a rebrand or shifting message while trying to position themselves in a constantly changing market, what advice would you share? SL: One of the most important lessons for me is that rebrands are not simply marketing exercises. They're full organizational transformations. The success of a rebrand depends on whether the entire organization is bought in and understands the narrative, and whether they feel confident communicating what you're doing to customers. Like I said before, the success of the rebrand is really only clear when you see that it has landed with your customer base. Another key element is staying very close to your customers during the process. Understand how they're going to perceive this, and once you've launched it, pay attention to their initial reactions so you can address anything quickly. That's your most valuable insight because customers really know how you're positioning yourself in the market and what you can actually deliver. You want to make sure what you've changed feels true to who you are. Luckily, with Leah, customers responded positively to the rebrand. They felt the narrative resonated. When your organization combines strong strategic direction with customer insight, you're much more likely to build a story that's authentic and compelling. That's what you want with your brand. It needs to make sense. People need to know it wasn't just done to look good. It needs to resonate with the company and what you're offering. RR: Yeah. You absolutely need to prove that this is something worthwhile and valuable to your customer base, and that it tells the story and provides the value they're looking for. Otherwise, to your point, it winds up feeling like a vanity exercise because someone didn't like the colors or didn't feel the name was quite right. It needs to be strategic and feel strategic. Shelly, thank you so much for joining us today. It has been an absolute pleasure talking with you and learning more about the work that you're doing at Leah. To our audience, thank you so much for listening to this episode of the Win/Win Podcast. Be sure to tune in next time for more insight on how you can maximize go-to-market success with Highspot.

This episode features Mark Diodati, Managing Vice President for Identity and Access Management at Gartner.Mark has spent two decades shaping how the industry thinks about authentication, privileged access, and cloud identity, working with renowned companies like Ping Identity, CA, RSA, and now, Gartner. Today, he leads Gartner's global IAM for Leaders analyst team and sets its research agenda across the full identity stack.In this episode, Mark explains how Gartner's research model works and what his team is prioritizing across identity verification, authorization, ITDR, and decentralized identity. He also breaks down what AI means for identity right now and why securing AI agents is harder than most teams realize.This episode is a deep dive into where identity is heading from someone whose job is to listen to everyone.Guest Bio Mark Diodati is the Managing Vice President for Identity & Access Management at Gartner.Mark is a longtime identity pioneer who helped shape the way the industry thinks about authentication, privileged access management, and cloud identity. He leads a large team of analysts, sets the global IAM research agenda, and rigorously reviews every document to keep the bar high. Before that, he guided Gartner's IAM research for technical professionals, chaired major industry conferences like Catalyst Europe and the Cloud Identity Summit, and drove triple-digit growth in attendance and sponsorships. Earlier in his career, he held key leadership roles at CA, RSA, and Ping Identity, influencing product strategy and partnerships that many identity practitioners rely on today.Guest Quote " One thing we're critically aware of at Gartner is that nobody knows everything. It's impossible.”Time stamps (02:11) Meet Mark Diodati: Identity Analyst and IAM Research Leader (06:00) Inside Gartner: Research, Conferences, and Consulting (09:18) Hiring and Training the Gartner Analyst (15:26) How the Inquiry Process Works (24:07) Gartner Research Products for Identity Professionals (28:02) IAM Research Priorities Right Now (32:31) AI and Identity: Opportunity and Risk (39:35) A Musical Moment with Mark (44:26) Conclusion and Final ThoughtsSponsor The HIP Podcast is brought to you by Semperis, the leader in identity-driven cyber resilience for the hybrid enterprise. Trusted by the world's leading businesses, Semperis protects critical Active Directory and Entra ID environments from cyberattacks, ensuring rapid recovery and business continuity when every second counts. Visit semperis.com to learn more.LinksConnect with Mark on LinkedInConnect with Sean on LinkedInDon't miss future episodesLearn more about Semperis

Guest post by Sapthagiri Chapalapalli, Head of TCS Europe The European Environment European organisations have a unique opportunity to lead with trusted infrastructure, rigorous compliance, and innovation that advances both growth and societal goals. The European Union is seen as a regulatory superpower globally, often setting the standards which the world then adopts. In technology, traditionally Europe sets the bar high on risk, safety, rights and antitrust, but there is recognition that there is tension between this approach, versus the more innovation-friendly and hands-off attitude in the US. Organisations are caught in the middle, needing to be compliant, to work globally, and ultimately ensure their entire digital ecosystem is serving their needs with minimal friction. Maintaining a competitive environment for growth is a constant tightrope to walk. Right now, the game-changing nature of AI, a fluctuating global legislative environment, and concern over geopolitical risks, data dependencies, and concerns over supply chain vulnerabilities are driving European organisations to reevaluate their technology stacks as a business priority. A sovereign cloud approach is a strong route to advancing business goals while maintaining compliance and being in control of your data. The sovereign cloud objective Sovereign cloud is a strong option for European organisations because, by placing the concept of sovereignty at the core of transformation, they integrate data protection and compliance mechanisms from the start to create a framework within which they can competitively innovate, while exercising ultimate control over their data in a protected environment. At its core, sovereign cloud is a purpose-built cloud computing environment that specifically meets certain protection, security or legal requirements, granting organisations more comprehensive control over their digital assets. Data stays within defined borders or jurisdictions, even when the organisation is working with a global cloud provider, while remaining scalable to the needs of the business. Sovereign cloud provides strategic autonomy, including protecting intellectual property and personal data to maintain business continuity in the face of geopolitical or supply chain shocks, while preserving speed, elasticity, and interoperability. And sovereign cloud infrastructure as a service (IaaS) is gaining popularity; spending in this area is forecast to total $80 billion (€68 billion) in 2026, a 35.6% increase from 2025, according to Gartner. As a technology service provider, we're seeing clients coming TCS with four needs in particular. 1. To reduce exposure to extraterritorial laws. With most mid and large-scale enterprises today storing data in off-premise in the cloud, organisations are often relying on international data centres. And as non-EU laws like the US Cloud Act and China's Cybersecurity Law become more numerous and powerful, organisations are increasingly looking to keep all of their data in a single controlled sovereign environment. 2. To adhere to strict EU data residency and processing requirements, and react to increasing pressure from regulations like GDPR, DORA, and other sector-specific policy. Organisations want a simple solution to stay compliant. 3. To manage data and supply chain risks in a tricky geopolitical environment by their data. This often means keeping data closer to home in Europe, but not always. 4. To competing on a global scale with new technologies like AI. Organisations want to control and protect the data environment for their AI solutions. Consequently, sovereign clouds are increasingly seen as critical for sovereign AI solutions. Achieving cohesive design and prioritising a 'Minimum Viable Enterprise' approach When talking with clients, we see sovereign cloud often described as a destination. In practice, it is a set of deliberate design choices working flawlessly in concert with the objective of ensuring meaningful and unambigu...

AI already knows your buyer better than most sales reps do. The question is — what are you going to do about it?In this episode, John is joined by Scott Gillum, author of The Hidden Buyer Journey, to unpack seven years of research on how buyers actually make decisions — and why our sales and marketing tools are barely scratching the surface of what's possible. From personality profiling and corporate culture mapping to the death of the sales stage, this conversation goes deep on what it really takes to sell in a world where the buyer is more informed, more protected, and more machine-assisted than ever before.If you're serious about staying relevant as a sales professional in an AI-first world, this one's a must-listen.Want to make sure you're equipped before the market moves on without you? Visit www.jbarrows.com and learn how you can Make It Happen.What You'll LearnWhy corporate culture predicts deal velocity better than any sales methodologyHow to use personality profiling tools to adapt your style to any buyerWhy 85% of the people who actually influence your deals aren't in your CRMThe one thing AI still can't replicate — and why it's your biggest competitive advantageWhy Return on Effort (ROE) is replacing ROI as the real measure of AI in salesScott Gillum is the Founder and CEO of Carbon Design. Prior to founding Carbon Design, he was the President of the Washington, DC office for gyro (a Dentsu agency), the world's largest B2B agency.His career follows the pipeline. Starting at the bottom closing deals as a sales rep. Then as a management consultant after graduate school, helping clients build and capture demand for sales and marketing channels. Advertising broadened his knowledge and experience in building brands and creating awareness.Along the way, he's been the head of marketing for an Inc. 500 company, and an interim CMO for a Fortune 500 company. Today, Scott helps clients improve the effectiveness of their marketing efforts up and down the funnel. From transitioning to digital to finding new ways to communicate, connect, and motivate audiences.Scott's a member of the Gartner for Marketing Leaders Council and he writes a regular column for MediaPost on business marketing. He's articles have appeared in leading publications such as Forbes, Fortune, Adage, the Huffington Post and he has contributed to various books on marketing. Additionally, his work on sales and marketing integration was made into a Harvard Business School Case Study and is taught at leading business schools across the nation.Website: https://carbondesign.com/scott-gillum/LinkedIn: https://www.linkedin.com/in/scottgillum/John Barrows is a sales trainer, speaker, and founder of JB Sales with over 25 years of experience in the industry. He has made hundreds of cold calls a week, led startups to acquisition, and trained high-performing teams at companies like Salesforce, LinkedIn, Amazon, and Okta. Through JB Sales, John focuses on practical sales execution—helping reps fill pipeline, close deals, and build trust with buyers in today's AI-driven sales environment.Connect with John Barrows:LinkedIn: https://www.linkedin.com/in/johnbarrows/ Instagram: https://www.instagram.com/johnmbarrows/TikTok: https://www.tiktok.com/@johnmbarrowsCheck out John's Membership: https://go.jbarrows.com/Join John's Newsletter: https://www.jbarrows.com/newsletter

Neste episódio do Vamos de Vendas, Gustavo Pagotto recebe Pedro Rodrigues, CRO da Alice, para uma conversa sobre saúde, tecnologia e os bastidores da construção de uma das healthtechs mais inovadoras do Brasil.A conversa passa pelos desafios de vender em um setor altamente regulado, a complexidade do canal de corretores e a importância de encontrar o product-market fit antes de escalar vendas.Pedro também compartilha os erros e aprendizados na definição de ICP, e como dados, CRM e pós-venda se tornaram peças-chave para retenção e crescimento sustentável. Além disso, o papo explora o impacto da inteligência artificial na saúde e como o comportamento do consumidor está mudando rapidamente.

Would you like access to our advanced agency training for FREE? https://www.agencymastery360.com/training Are you still showing up for every function in your business after years because stepping back feels like abandoning what you built? Do you publish content consistently but wonder why it is not moving the needle? Today's featured guest owns a social media agency and built her client roster by getting on stage before she was comfortable doing so. She wrote a book that got her on the stages she wanted, and carved out a niche so specific that it made content marketers uncomfortable. In this conversation, she'll talk about how she landed enterprise clients with zero churn over nine years, what it actually takes to find a real differentiator, and much more. Brooke Sellas is the CEO and founder of B Squared Media, a Michigan-based agency offering social media management, paid media management, and social media customer care. Her social care practice works exclusively with enterprise brands at $5 billion and above in annual revenue, including long-term clients she originally closed nine years ago with zero churn since. She is the author of Conversations That Connect, a book built around the idea that social is a conversation channel, not a content channel. Brooke speaks at major marketing conferences, including Social Media Marketing World and now teaches AI at the University of California. In this episode, we'll discuss: Why your differentiator must be an outcome Being stuck in the Founder Evolution Framework Why hesitation regarding AI will kill your agency Sponsors and Resources This episode is brought to you by Wix Studio: If you're leveling up your team and your client experience, your site builder should keep up too. That's why successful agencies use Wix Studio — built to adapt the way your agency does: AI-powered site mapping, responsive design, flexible workflows, and scalable CMS tools so you spend less on plugins and more on growth. Ready to design faster and smarter? Go to wix.com/studio to get started. How She Built a Client List Enterprise Brands Still Have Not Left Brooke's first two major clients came from a speaking appearance she almost did not take. She hated being on stage but agreed anyway. She closed Brother International and Miele from that first talk, and immediately made speaking her primary lead generation strategy. Nine years later, those clients are still with the agency. That zero churn across the social care practice is the result of a positioning decision made early: social is a revenue channel, not a content channel, and every client relationship is built around proving that. Getting on bigger stages required a longer game. Brooke spent years speaking for free, asked her network exactly how they were getting booked, and eventually took advice to write a book. The book cost around $25,000 to produce and self-publish. It opened stages that had been closed before. Social Media Marketing World followed because the book got in front of the right people and gave the organizer enough confidence to put her on stage. The ROI was not immediate. It compounded across years of bookings, consulting fees, and speaking revenue that now functions as a separate income stream while still generating agency leads. Your Differentiator Has to Be an Outcome, Not a Vibe Brooke is direct about what does not work as positioning. Saying your agency is a people-first agency, that you care more, that you have great culture: none of it separates you in a room where everyone is saying exactly the same thing. She spent years telling content marketers they were wrong, walking into rooms full of people who measured social by follower counts and publishing frequency, and saying the right metric is revenue from social. That took a stance. It made some people uncomfortable, and that discomfort was the signal she was in the right territory. The lesson she draws from her own experience is not that you need to be contrarian for its own sake. It is that your differentiator has to connect directly to a business outcome your client already cares about. Her agency's tagline is Conversation Not Campaign. That is a positioning claim with a revenue argument underneath it. If you cannot articulate what outcome your positioning produces for the client, you do not have a differentiator yet. You have a personality. Where She Is in the Founder Evolution Framework and What It Costs Her Fourteen years into building B Squared, Brooke is somewhere between Architect and CEO and honest about what that means in practice. She still runs most things. She knows it is holding back growth. She also knows that the identity piece is real: when you have built something for over a decade and your name is synonymous with what the agency delivers, stepping out of that role is not just a structural decision. It requires a different relationship with your own sense of contribution. What she articulates clearly is the tension every founder at this stage knows. She does not want to be the bottleneck anymore. She also has not yet handed the systems over to someone who can own them at the level she would. The move at this stage is not to wait until someone earns total trust before stepping back. It is to build the systems, put the right person in charge of them, and let the fender benders happen so the team develops the capability to solve problems without routing everything through the founder. The alternative is staying indispensable in a way that caps everything the agency could become. Stop Hesitating and Treat AI with Curiosity Brooke runs social media and paid media services. She is clear-eyed about what AI is doing to both: content that used to take weeks to produce is now a matter of seconds, and ad copy that required real craft is being generated faster and often better than agency teams can match manually. That is the honest read. The response she chose is not to protect what exists but to figure out where AI creates opportunity she was not positioned to capture before. The Gartner stat she cites is worth repeating: people who use AI to help them sell, sell 3.7 times more than those who do not. Brooke is a speaker, a consultant, and a sales-driven founder. That number is an opening, not a threat. The agencies that are struggling right now are the ones that treated the last two years as a window to observe and decide. The window is closing. Curiosity and willingness to play with new tools before mastery arrives is not optional. It is the trait that has always separated the founders who build something lasting from the ones who stay comfortable until the market moves without them. Do You Want to Transform Your Agency from a Liability to an Asset? Looking to dig deeper into your agency's potential? Check out our Agency Blueprint. Designed for agency owners like you, our Agency Blueprint helps you uncover growth opportunities, tackle obstacles, and craft a customized blueprint for your agency's success.

The structural shift outlined in this episode is the rapid evolution of search and productivity interfaces from static query tools to agentic platforms capable of autonomous action, oversight, and automation. Companies such as Google are redesigning search at the interface level, integrating multimodal input and agentic workflows powered by AI models like Gemini 3.5 Flash. The dynamic is not competition at the model level, but rather a pivot toward which provider can offer policy enforcement, cost controls, compliance, and documented governance over increasingly complex agent-driven environments. The most consequential development is Google's redesign of its search box for the first time in 25 years, transitioning to an AI-powered, chatbot-style interaction that can process longer prompts, images, files, and monitor tasks directly within the browser. According to New York Times and Channel Life New Zealand, this change embeds AI agents as defaults in the workflow, underpinned by Google's commercial growth—ad clicks up by 6%, cost per click up 7%, with profits over $132 billion since 2022. The shift is visible in adoption data as well: ChannelDive reports Anthropic's Claude overtook OpenAI's GPT suite for business usage, while Gartner forecasts $2.59 trillion total AI spending in the year, but only $33 billion is model-specific. Supporting developments reinforce risk and operational complexity as AI transitions into core business processes. Channel-focused reports note that vendors are offering managed agent services, operational sandboxes, and white-label security operations to simplify agent deployment and lower entry barriers. OpenAI pitching “buy before you try” guarantees, and launches like Acronis Cyber Freight — promised as “predictable” and “protected by default” — reflect client demand for reliability over raw capability. Across these moves, partners and IT providers are being drawn into defining, monitoring, and governing the new automation layers, with increasing requirements for documentation, provenance, and workflow auditing. For MSPs and technology leaders, the operational implications are direct and substantive. The work now centers on defining governance frameworks—inventorying systems that can act autonomously, classifying authority and registration requirements, building audit trails, and delineating contractual boundaries for automation responsibility. Providers who approach this as standard support risk carrying unpriced operational and compliance burdens, especially in environments where unauthorized automations or unregistered connectors proliferate. The emergent requirement is to treat agent governance as a managed service, pricing it separately, and establishing clear evidence and escalation protocols to avoid absorbing blame and liability for automation-driven incidents. 00:00 Beyond Blue Links  04:30 Predictability Wins 06:39 Govern or Absorb 09:19 Why Do We Care?  Supported by:  Moovila ScalePad

Dr. John Gartner returns to The Daily Beast Podcast to deliver an urgent, chilling analysis of Donald Trump's rapidly deteriorating clinical condition as he approaches his 80th birthday. Moving far beyond typical signs of aging, Dr. Gartner details to Daily Beast executive editor Hugh Dougherty the alarming behavioral symptoms pointing toward frontotemporal dementia—including a complete loss of empathy, dangerous disinhibition, and increasingly disorganized thought processes. Dr. Gartner unpacks the psychology behind Trump's late-night postings, his shocking new delusions of grandeur, and a calculated effort to "groom" the American public for an unthinkable nuclear conflict. Learn more about your ad choices. Visit podcastchoices.com/adchoices

AI adoption is accelerating fast, but so is enterprise risk. In this episode of Gartner ThinkCast, Distinguished VP Analyst Paul Furtado explores the growing reality facing leaders: nearly every organization is investing in AI, yet most expect it to increase their risk profile. Drawing from real-world examples, Paul breaks down how AI can shift from a source of exposure to a powerful driver of resilience — reducing remediation time, improving threat detection, and strengthening fraud prevention.   You'll learn: The three priorities leaders must get right: security, governance and talent How to focus on AI use cases that actually reduce risk What separates successful AI adoption from high-speed failure Dig deeper: Learn more and download the 2026 Gartner CIO Report Attend a Gartner CIO Conference near you See why Gartner is the world authority on AI Try out AskGartner for more AI-powered insights

May 19, 2026: Everyone has an opinion about AI and jobs. Today we have actual data — three major studies published this week that, taken together, tell a story that's more nuanced, more surprising, and more actionable than anything you'll hear in the headlines. First: a Wall Street Journal report reveals that the companies going deepest on AI are actually increasing entry-level hiring — nearly three times more than are cutting — and why a 22-year-old with AI fluency may be the most valuable hire in the market right now. Then we get into why nearly half of Gen Z workers say AI is making them cognitively weaker, what London taxi drivers and GPS research tells us about what's actually happening to the human brain, and why the most dangerous AI user isn't the person who refuses to use it. And we close with Gartner's bombshell finding: 80% of companies cutting headcount for AI are seeing zero ROI — and by 2030, the ones that starved their talent pipeline this year will be paying a 15% premium just to catch up. Plus: why commencement speakers keep getting booed.

Gartner studied 350 executives at billion-dollar companies. Eighty percent had cut staff for AI. None of it correlated with higher returns. Goldman Sachs found the stock bounce is gone. Forrester predicted half of all AI-attributed layoffs would be reversed by 2027. The data is in, and it says the same thing from every angle: the cuts were theater. This episode breaks down who knew, who stayed quiet, and what the companies actually winning at AI did instead. Plus, what HR leaders, recruiters, and job seekers can do with the receipts now that they're public. Brought to you by my newsletters: The Recruiting Life - Clarity on what's happening now and next in the world of work. Career Intelligence Weekly - Tracking the invisible job market for smarter career decisions. Subscribe to both at https://newsletter.jimstroud.com Research related to this podcast is cited in the Sunday, May 17, 2026 issue of The Recruiting Life Newsletter. Learn more about your ad choices. Visit megaphone.fm/adchoices

Secure your spot for the MULTI-AGENT ORCHESTRATION AI COURSE: https://multiplai.ai/multi-agent-orchestration-course/What if the biggest tech layoffs in history aren't really about AI… but the AI wave that justifies them is just getting started?Tech giants are posting record revenues while cutting tens of thousands of jobs. CapEx is hitting historic highs. And behind closed doors, the courtroom drama between Elon Musk, Sam Altman, and Microsoft is revealing things that sound straight out of a Hollywood script.In this weekend news episode, Isar Meitis breaks down the most important AI stories of the week — from the dissonance between booming tech revenues and mass layoffs, to the explosive testimonies in the Musk vs. OpenAI trial, to the cybersecurity exploits that just broke Apple's most advanced hardware in 5 days.You'll get a clear-eyed look at what's actually driving the layoffs, who's winning the enterprise AI race, and why the next wave of disruption is closer than most leaders realize.If you want to understand where the AI economy is heading — and what it means for your business, your job, and your industry — this episode connects the dots in ways most headlines won't.In this session, you'll discover:Why tech companies are laying off thousands while breaking revenue recordsThe truth behind "AI-driven" layoffs (and what Gartner's new data reveals)How OpenAI, Anthropic, and Google are racing to dominate enterprise AI deploymentThe shocking revelations from the Musk vs. OpenAI trial — including hidden personal ties and alleged lies at the topHow AI just cracked Apple's most advanced security in only 5 daysMicrosoft's research showing AI agents corrupting documents on long tasksGoogle's new Gemini Intelligence layer for Android and Chrome — and what it means for the future of appsAnthropic's first major push into the small business marketHow AI-generated political content is reshaping elections (LA mayor race case study)Why xAI's Grok 9 and "Grok Build" could disrupt the Claude Code vs. Codex raceThe Figure AI robots that just sorted 28,000 packages in 24 hours with zero mistakesAbout Leveraging AIThe Ultimate AI Course for Business People: https://multiplai.ai/ai-course/YouTube Full Episodes: https://www.youtube.com/@Multiplai_AI/Connect with Isar Meitis: https://www.linkedin.com/in/isarmeitis/Join our Live Sessions, AI Hangouts and newsletter: https://services.multiplai.ai/eventsIf you've enjoyed or benefited from some of the insights of this episode, leave us a five-star review on your favorite podcast platform, and let us know what you learned, found helpful, or liked most about this show!About Leveraging AIThe Ultimate AI Course for Business People: https://multiplai.ai/ai-course/YouTube Full Episodes: https://www.youtube.com/@Multiplai_AI/Connect with Isar Meitis: https://www.linkedin.com/in/isarmeitis/ Join our Live Sessions, AI Hangouts and newsletter: https://services.multiplai.ai/eventsIf you've enjoyed or benefited from some of the insights of this episode, leave us a five-star review on your favorite podcast platform, and let us know what you learned, found helpful, or liked most about this show!

Agentic AI is already reshaping how work gets done, and the biggest risk for CIOs isn't failure, it's falling behind. In this episode of ThinkCast, Gartner VP Analyst Brandon Germer explains why scaling agentic AI can't be done in silos, and how CIOs must co-lead with other C-suite members to build the financial, operational, and governance foundations for enterprise-wide impact.   You'll learn: Why the biggest risk in agentic AI isn't failure — it's waiting too long to act What it takes to scale AI beyond isolated use cases into enterprise-wide systems How to align the CIO, CFO, COO and CHRO around shared outcomes Why the CIO's role is shifting from technology owner to orchestrator Dig deeper: Download our guide to realizing AI value Attend a Gartner CIO Conference near you See why Gartner is the world authority on AI Try out AskGartner for more AI-powered insights  

Bill Press interviews psychologist Dr. John Gartner about a new ABC/Washington Post poll finding 59% of Americans believe Donald Trump is mentally unfit for the presidency and a physicians' letter urging Trump's lawful removal due to an unsanctioned war and his sole authority over nuclear weapons. Gartner argues Trump is a “malignant narcissist” with worsening frontotemporal dementia, claiming his disinhibition, tangential speech, confabulation, language errors, and loss of social context are increasingly visible, citing clips about “SEA” vs “SEE,” a Sharpie story, and graphic remarks to schoolchildren. He links Trump's self-glorification (coins, passports, building names, images as Pope/Jesus, a triumphal arch) to delusions of grandeur and warns of escalating war and possible first-use nuclear action, doubting political checks like the 25th Amendment or Senate conviction. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Most companies think they have an AI strategy. New data from Gartner says they're wrong — and it's costing them. In today's episode, Jacob Morgan breaks down three stories that cut through the hype and tell the real story of where AI and business stand right now. May 12, 2026: First, a landmark Gartner study of 350 global executives reveals that 80% of companies that cut headcount in the name of AI are seeing little to no return — and the ones getting real results are doing the opposite of what most CEOs are doing. Second: a provocative new framework from Fortune identifies the five AI postures most organizations have already drifted into without realizing it — and explains why the most dangerous one is the one that feels the most comfortable. Third: CNBC reports on how AI is creating a new C-suite power struggle, with the Chief AI Officer emerging just as every other executive function is being told it's their moment to lead.  

Jeff and Jim welcome back Henrique Teixeira, SVP of Strategy at Saviynt, for his fourth appearance on the podcast. The episode opens with Jim's firsthand experience building an AI agent for a work project and discovering in real time how identity management challenges surface in the agentic era. After conference updates on EIC in Berlin and Identiverse in Las Vegas, Henrique unpacks the crowded terminology around AI agent governance, from Gartner's agent management platforms to UADP, the Unified Agentic Defense Platform. He proposes a three-pillar framework for managing AI and non-human identities: discovery, identity lifecycle and governance, and runtime access management, with guidance on where to start depending on whether your organization is greenfield or legacy-heavy. The conversation then examines how AI is reshaping the analyst business model, what makes information sources trustworthy, and how proprietary inquiry data forms the real competitive moat for firms like Gartner and Forrester. The episode closes with a wide-ranging discussion on AI's risk to shared cultural experiences, hyper-personalized entertainment, and the ethics of licensing your digital identity in the afterlife.Connect with Henrique: https://www.linkedin.com/in/bernardes/Connect with us on LinkedIn:Jim McDonald: https://www.linkedin.com/in/jimmcdonaldpmp/Jeff Steadman: https://www.linkedin.com/in/jeffsteadman/Visit the show on the web at http://idacpodcast.com00:00:00 Intro00:00:55 Jim's AI Agent Experiment and Identity Lessons00:06:04 Conference News: EIC and Identiverse00:07:22 Identity Beer Community Events00:08:40 Introducing Henrique Teixeira00:12:00 AI Control Plane: Competing Terminologies00:17:36 Three Pillars of AI Agent Identity Management00:18:46 Why Visibility Matters More for NHI00:20:00 Ownership, Accountability, and Humans at the Control Plane00:24:26 Industry Maturity and the Gaps That Remain00:25:41 Where to Start: Governance-First vs. Visibility-First00:29:52 AI's Impact on the Analyst Profession00:34:57 What Analyst Firms Have That AI Cannot Replace00:39:04 Trust, Boutique Analysts, and Repeatability00:44:34 Proprietary AI Chatbots and Gated Intelligence00:49:30 IP Rights and the Legal Gray Zone of AI Training00:52:14 AI and the Erosion of Shared Cultural Experience00:58:00 AI Music, Personalized Entertainment, and the Future of Art01:03:47 Digital Afterlife, Voice Clones, and AI Personas01:08:18 Wrap-Up and ClosingKeywords: IDAC, Identity at the Center, Jeff Steadman, Jim McDonald, Henrique Teixeira, Saviynt, AI identity control plane, non-human identities, NHI, agentic AI, AI agents, AI governance, identity lifecycle, access management, discovery, agent management platform, UADP, IAM, Gartner, analyst firms, AI and culture, digital identity, identity security, EIC, Identiverse, identity beer