Podcasts about Jira

"Rovo knows everything, works everywhere, and helps everyone". With these words uttered by Mike Cannon-Brookes during TEAM '25 Europe, he introduced the further capabilities of Atlassian's Agentic AI solution.Joining us to help elaborate on this new chapter is return guest Jensen Fleming, Principal Product Manager for AI/Rovo. Tune in to see and hear the major and minor announcements that came from Barcelona!Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!  / the-jira-life  Become a member on YouTube to get access to perks:   / @thejiralife  Hosts:Alex "Dr. Jira" Ortiz ⁠  / alexortiz89  ⁠⁠   / @apetechtechtutorials  ⁠ Rodney "The Jira Guy" Nissen / rgnissen  ⁠⁠https://thejiraguy.com⁠Sarah Wright/ satwright  ⁠     Producer: "King Bob" Robert Wen  / robert-wen-csm-spc6-a552051  Executive Producer: Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codes   / monstercat  Outro: Fractal - Atrium   / monstercatinstinct  

Karim Harbott: From Requirements Documents to Customer Obsession—Redefining the PO Role Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Strategic, Customer-Obsessed, and Vision-Driven   "The PO role in the team is strategic. These POs focus on the customer, outcomes, and strategy. They're customer-obsessed and focus on the purpose and the why of the product." - Karim Harbott   Karim believes the industry fundamentally misunderstands what a Product Owner should be. The great Product Owners he's seen are strategic thinkers who are obsessed with the customer. They don't just manage a backlog—they paint a vision for the product and help the entire team become customer-obsessed alongside them.  These POs focus relentlessly on outcomes rather than outputs, asking "why are we building this?" before diving into "what should we build?" They understand the purpose of the product and communicate it compellingly.  Karim references Amazon's "working backwards" approach, where Product Owners start with the customer experience they want to create and work backwards to figure out what needs to be built. Great POs also embrace the framework of Desirability (what customers want), Viability (what makes business sense), Feasibility (what's technically possible), and Usability (what's easy to use). While the PO owns desirability and viability, they collaborate closely with designers on usability and technical teams on feasibility.  This is critical: software is a team sport, and great POs recognize that multiple roles share responsibility for delivery. Like David Marquet teaches, they empower the team to own decisions rather than dictating every detail. The result? Teams that understand the "why" and can innovate toward it autonomously.   Self-reflection Question: Does your Product Owner paint a compelling vision that inspires the team, or do they primarily manage a list of tasks? The Bad Product Owner: The User Story Writer "The user story writer PO thinks it's their job to write full, long requirements documents, put it in JIRA, and assign it to the team. This is far away from what the PO role should be." - Karim Harbott   The anti-pattern Karim sees most often is the "User Story Writer" Product Owner. These POs believe their job is to write detailed requirements documents, load them into JIRA, and assign them to the team. It's essentially waterfall disguised as Agile—treating user stories like mini-specifications rather than conversation starters. This approach completely misses the collaborative nature of product development.  Instead of engaging the team in understanding customer needs and co-creating solutions, these POs hand down fully-formed requirements and expect the team to execute without question. The problem is that this removes the team's ownership and creativity. When POs act as the sole source of product knowledge, they become bottlenecks.  The team can't make smart tradeoffs or innovate because they don't understand the underlying customer problems or business context. Using the Desirability-Viability-Feasibility-Usability framework, bad POs try to own all four dimensions themselves instead of recognizing that designers, developers, and other roles bring essential perspectives. The result is disengaged teams, slow delivery, and products that miss the mark because they were built to specifications rather than shaped by collaborative discovery. Software is a team sport—but the User Story Writer PO forgets to put the team on the field.   Self-reflection Question: Is your Product Owner engaging the team in collaborative discovery, or just handing down requirements to be implemented?   [The Scrum Master Toolbox Podcast Recommends]

In this episode, Aydin chats with Allan Isfan, Senior Director of Global Video Platform at Warner Bros Discovery, about how AI is reshaping creativity, software development, and large-scale enterprise culture. Allan explains how he drives AI literacy for 1,500+ employees, the power of internal demos and sandboxes, and gives a hands-on walkthrough of generative video tools like Gemini V3, Flow, and Sora. He also dives into AI video analysis, the Wizard of Oz project at The Sphere, and the future of creative storytelling powered by AI.

If you're a leader in game dev who feels stuck, able to spot problems but struggling to make a real difference, there is a path forward that levels up your leadership and accelerates your team, game, and career. Sign up here to learn more: https://forms.gle/nqRTUvgFrtdYuCbr6 Are you inadvertently forcing your team to serve a tool, instead of letting your tools serve your team and game? In a recent conversation with Clinton Keith, Ben asked how Clint would help all of game development. Clint's response? "Delete Jira" - and Ben laughed to keep from crying. Jira is a powerful tool, but in the hands of uninformed game development leadership, it often becomes a weapon against the very teams it's meant to help. Ben, who has used Jira and other tools as a producer within large studios, dissects the common, catastrophic misuses of Jira. While you might be better off deleting the tool, the real work is about fixing the broken cultural and organizational patterns that turn a simple work management system into the "boss" of your game studio. Learn the four cascading failure patterns that are draining your team's effectiveness and how to correct them, making collaboration and player outcomes your true north. What You'll Learn In This Episode: Why senior leaders keep breaking Jira without realizing it How Jira causes centralization and decision bottlenecks What Jira DOESN'T tell you, and why that makes it dangerous How perverse incentives emerge from overreliance on Jira and other tools like it The reason you end up feeling like a slave to the tool How to avoid the traps Jira leads you into Connect with us:

 In this eye-opening episode of UC Today, host David Dungay is joined by Paul Magnaghi, Zoom's Head of AI and ISV Go-To-Market, to unpack the real meaning of agentic AI—and why it's more than just a buzzword. As AI continues to reshape how we work, Paul shares how Zoom is positioning itself at the center of this evolution, empowering companies of all sizes to move faster, work smarter, and innovate with confidence. If you're wondering how to actually use AI (not just talk about it), this is a must-watch.Agentic AI is no longer on the horizon—it's here. But what does it really mean for your organization?In this expert-led interview, Zoom's Paul Magnaghi demystifies agentic AI and reveals how it's helping teams orchestrate workflows, act autonomously, and drive measurable ROI across departments—from IT to marketing.Key Takeaways:Defining agentic AI: Why reasoning, memory, orchestration, and action are the core pillars that separate agents from automation.Who needs it? Spoiler: Every business—from scrappy startups to sprawling enterprises—can benefit from agent-driven productivity.Real-world use cases: Discover how Zoom AI Companion automates webinar asset creation and turns meeting notes into live tickets (think: Jira as a meeting attendee).AI readiness: Why clean data, strong security policies, and cross-platform interoperability are non-negotiables in successful deployments.Zoom isn't just building smarter meetings—it's turning conversations into outcomes. 

TRELLOWEEN RETURNS! Joining us for this holiday tradition is Brittany Joiner, Mike Day, and Rob Hean for spooky stories of haunted apps!Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!  / the-jira-life  Become a member on YouTube to get access to perks:https://www.youtube.com/@thejiralife/...Hosts:Alex "Dr. Jira" Ortiz  / alexortiz89  ⁠⁠   / @apetechtechtutorials  ⁠ Rodney "The Jira Guy" Nissen / rgnissen  ⁠⁠https://thejiraguy.com⁠ Sarah Wright / satwright  ⁠ Producer:"King Bob" Robert Wen   / robert-wen-csm-spc6-a552051  Executive Producer: Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codes   / monstercat  Outro: Fractal - Atrium   / monstercatinstinct  

Here's the big problem with journey maps...It's often like you've composed a masterpiece, but no one is there to actually play it.This is what I feel when I see a carefully crafted map (our version of "music on paper"), which ultimately fails to make an impact. Sure, we do the research, map the insights, and identify opportunities, but on Monday morning, everyone just goes back to their old routines, checking off to-do items in Jira, ClickUp, or Asana.The map becomes an impressive visual, but it's disconnected from the way work is done.This is the implementation gap, and it's where most journey management efforts fail.So in episode 7 of the Journey Management Playbook series, Tingting Lin and I address this exact problem head-on. This isn't a guide about what to map rather, it's about how to plug your insights into the operational reality of your organization.We're moving beyond the theory and into the practical, day-to-day workflow.I even share my own project management setup, share how things get done in my business and we discuss how to bridge the gap between my project list and the customer journey.In this episode, you'll hear:* Why creating a "parallel workflow" for journey management is a recipe for failure.* How to "plug into" your organization's existing ceremonies.* A practical way to reverse-engineer your team's current project backlog and to connect it back to the journey.* The right way to use prioritization matrixes to spark stakeholder conversations and grow alignment.So if you want to make your journeys the driving force behind your daily decisions, not just another document lost on a hard drive or fading away on the wall, make sure you don't miss this one.--- [1. LINKS ] ---Playbook Slides - https://go.servicedesignshow.com/-sofmSign up for TheyDo - https://go.servicedesignshow.com/scjwb --- [ 2. GUIDE ] ---00:00 Welcome to TheyDo EP 0702:00 Implementation gap03:00 Defining the Operational Workflow06:00 The Practical Challenge09:00 Connecting the Triple Diamond to the Music Metaphor12:45 Understanding the big picture15:30 Connecting the churn-reduction journey map 16:30 Journey Management to Project Management 19:30 Modeling initiatives in TheyDo to show a successful integration approach21:30 How to Model Initiatives in TheyDo for Journey Linkage24:00 Linking Initiatives to Opportunities/Journeys25:30 Scoring Initiatives by Impact and Effort28:00 Connecting Discovery (TheyDo) to Delivery (ClickUp/JIRA)30:15 Context in the Journey Tool 32:00 Bi-directional Synchronization34:00 How to set up the connectio35:45 Understanding the Organizational Workflow37:30 Handoffs between the Triple Diamond Workflow39:00 How to Implement the Workflow 41:00 The needed Cultural shift42:00 Impact driven language44:30 How to handle non-journey work47:00 The Workflow is not a Designer's Job Alone49:00 Recap: The 4 steps50:30 Journey of the Journey Manager54:30 Journey Framework for Strategic Alignment56:30 Ensuring Business Value 58:00 Scaling and Governance1:02:30 Coming Up Next --- [ 3. FIND THE SHOW ON ] --- Youtube ~ https://go.servicedesignshow.com/journey-management-playbook-07-youtubeSpotify ~ https://go.servicedesignshow.com/journey-management-playbook-07-spotifyApple ~ https://go.servicedesignshow.com/journey-management-playbook-07-appleSnipd ~ https://go.servicedesignshow.com/journey-management-playbook-07-snipd

LIVE FROM LONG BEACH! Join us live from the Atlassian Builders' Summit as we see how Atlassian community members and JirAmigos get together and exchange ideas on Atlassian administration, Forge development, and Agile ways of working. Hear from attendees such as Josh Golosinskiy of GRYD.IO on the experience and see what's happening in real time.Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!  / the-jira-life  Become a member on YouTube to get access to perks:https://www.youtube.com/@thejiralife/...Hosts:Alex "Dr. Jira" Ortiz   / alexortiz89  ⁠⁠   / @apetechtechtutorials  ⁠ Rodney "The Jira Guy" Nissen / rgnissen  ⁠⁠https://thejiraguy.com⁠ Sarah Wright  / satwright  ⁠ Producer:"King Bob" Robert Wen   / robert-wen-csm-spc6-a552051  Executive Producer: Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codes   / monstercat  Outro: Fractal - Atrium   / monstercatinstinct  

Es war mal wieder so weit, ein Ausfall in einem Rechenzentrum von Amazon (AWS) sorgte weltweit für Probleme: Das Jira-Ticket-System fiel aus, Fortnite und Epic Online Services gingen nicht, Roblox, Duolingo und noch einiges mehr, bis hin zu eher kuriosen Erscheinungen wie Smart Betten bzw. Matratzen, die sich nicht mehr steuern ließen und zum Beispiel bei aufrechter Rückenlehne verharrten oder mit dem Heizen nicht mehr aufhören wollten. Alles ist vernetzt und das ist nicht gut. Microsoft möchte den "KI"-Assistenten Copilot persönlicher machen: Mico ist ein kleiner Blob mit Mund und Augen und darf in die lange Reihe von unvergesslichen Microsoft-Assistenten wie Clippy bzw. Karl Klammer treten. Zurück zu Amazon: In den USA stattet der Mega-Konzern die Paketzusteller mit Smart Brillen aus, die u.a. bei der optimalen Route helfen sollen. Nebenbei auch ein großartiges Instrument, um noch mehr Daten zu sammeln und die Fahrer unter Kontrolle zu halten. Die Mixed-Reality-Brille Galaxy XR von Samsung ist jetzt in Südkorea für 1799 Dollar erhältlich. Einerseits viel Geld, andererseits klingt neben der Apple Vision Pro alles irgendwie günstiger. Eine Besonderheit ist die Kooperation von Samsung mit Google für die Plattform Android XR, dabei setzt Samsung auch auf die offene Schnittstelle OpenXR der Khronos Group. Hat also durchaus Potential. Zwar schon älter, aber dennoch einen Blick wert: Die Smartwatch Huawei D2 mit echter, also medizinisch verwertbarer Blutdruckmessung. Viel Spaß mit Folge 279! Sprecher:innen: Meep, Michael KisterAudioproduktion: Michael KisterVideoproduktion: Michael KisterTitelbild: MeepBildquellen: Samsung/Android XR/AlphabetAufnahmedatum: 24.10.2025 Besucht unsim Discord https://discord.gg/SneNarVCBMauf Bluesky https://bsky.app/profile/technikquatsch.deauf TikTok https://www.tiktok.com/@technikquatschauf Youtube https://www.youtube.com/@technikquatschauf Instagram https://www.instagram.com/technikquatschauf Twitch https://www.twitch.tv/technikquatsch RSS-Feed https://technikquatsch.de/feed/podcast/Spotify https://open.spotify.com/show/62ZVb7ZvmdtXqqNmnZLF5uApple Podcasts https://podcasts.apple.com/de/podcast/technikquatsch/id1510030975 00:00:00 Herzlich willkommen zu Technikquatsch Folge 279! Mo macht nochmal Pause; marokkanische Minze, Fencheltee und verschiedene Süßungsmittel. 00:07:44 Guter Service bei der Telekom, und beide vergessen, ihre Auto-Geschichten zu erzählen. 00:17:37 AWS-Ausfall legt halbes Internet lahm, u.a. Atlassian (Confluence, Jira), Amazon Prime, Roblox, Fortnite, Epic Online Service, Duolingo und Smart Betten.https://www.heise.de/news/Amazon-Web-Services-Globale-Stoerung-10778963.htmlhttps://www.dexerto.com/entertainment/aws-crash-causes-2000-smart-beds-to-overheat-and-get-stuck-upright-3272251/ 00:34:40 Clippys Enkel: Microsoft gibt Copilot mit Mico ein Gesicht; Gaming Copilot will auch Daten sammeln.https://www.computerbase.de/news/apps/copilot-fall-release-mico-tritt-in-die-fussstapfen-von-clippy.94778/https://www.theverge.com/news/804122/microsoft-copilot-real-talk-mode-group-chats-featureshttps://doublepulsar.com/microsoft-builds-on-recall-with-gaming-copilot-fails-basic-privacy-tests-52988576bcc8 00:43:34 Amazon stattet Fahrer des eigenen Lieferdienstes in den USA mit Smart Brillen aus.https://www.computerbase.de/news/wearables/smart-delivery-glasses-amazon-stattet-fahrer-mit-ar-brillen-aus.94784/ 00:50:24 Konkurrenz für Apple Vision Pro: Samsung Galaxy XR für 1800 Dollar in Südkorea erhältlich.https://www.computerbase.de/news/wearables/samsung-galaxy-xr-mixed-reality-headset-mit-android-xr-startet-fuer-1-799-usd.94745/ 01:13:36 Huawei Watch D2: Smartwatch mit medizinisch zertifizierter Blutdruckmessfunktion.https://www.computerbase.de/artikel/wearables/huawei-watch-d2-smartwatch-test.89431 01:27:33 Das Ende naht, aber bleibt uns bitte erhalten!

Time to go through some of the updates from the @atlassian ecosystem #NewJiraFeatures #RovoDev #ServiceCollectionhttps://www.ravisagar.in/videos/atlassian-updates-new-jira-features-rovo-dev-service-collection

TEAM '25 Europe is done (at least when we do this episode!) Join Sarah #IBelieveSarah Wright and producer "King Bob" as we look at the best of field reports from Rodney and Alex. View the reactions of the latest news from Atlassian. Get insights from Atlassians, partners, and customers. And ease the FOMO.Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!  / the-jira-life  Become a member on YouTube to get access to perks:   / @thejiralife  Hosts:Alex "Dr. Jira" OrtizRodney "The Jira Guy" NissenSarah Wright"King Bob" Robert WenLina Ortiz   / alexortiz89     / @apetechtechtutorials     / rgnissen  https://thejiraguy.com   / satwright   Producer:   / robert-wen-csm-spc6-a552051  Executive Producer: Music provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codes   / monstercat  Outro: Fractal - Atrium   / monstercatinstinct  

Order in the court! This week on The Jira Life, we're putting Jira on trial. The charge? Being a tool only for technical teams.In this special jury-style debate, we'll examine both sides of the case:

Mike Cannon-Brookes is the Co-Founder and Co-CEO of Atlassian, the $50BN software giant behind products like Jira, Confluence, and Trello. Since founding the company in 2002, he has scaled it to over 300,000 customers globally, generating more than $5BN in annual revenue. Atlassian now employs over 10,000 people across 13 countries and is one of the most successful bootstrapped-to-IPO stories in tech history. Mike is also a leading climate investor and co-owner of several major sports teams. AGENDA:  00:00 Why Unreasonable Men Win in Startups 07:22 How to Make Co-CEOs Work  13:22 Are We in an AI Bubble? Is Everything Overvalued? 26:46 The Future of Software Development: More or Less Devs 32:53 Do Margins Matter in a World of AI 34:02 The Future of Vibe Coding… 36:35 Does Defensibility Exist in a World of AI 42:09 Is Per Seat Pricing Dead in a World of AI 49:01 The Founder Journey and Leadership 54:28 Quick Fire Round: Parenting Advice, Relationship to Money  

Gemini en el trabajo: La nueva apuesta de Google para llevar la inteligencia artificial a cada escritorio  Por Félix Riaño @LocutorCo  Escuchar esta y otras historias del Flash Diario en Spotify.   Google lanza Gemini Enterprise, una plataforma que busca transformar la forma en que las empresas usan la inteligencia artificial. Con precios desde 21 dólares al mes, promete un asistente personalizado para cada trabajador y una respuesta directa frente a Microsoft, OpenAI y Amazon.  Google presentó Gemini Enterprise, su nueva plataforma de inteligencia artificial para empresas. La propuesta busca integrar todos los servicios de Google Cloud y Workspace en un solo punto de acceso: un chat empresarial donde cada persona puede crear y usar sus propios agentes de IA sin saber programar. La plataforma ya está activa en todos los países donde se venden los productos de Google Cloud y tiene clientes como Figma, Klarna, Macquarie Bank, Gordon Food Service, Virgin Voyages y Gap. Su precio empieza en 21 dólares por usuario para pequeñas empresas y 30 dólares en los planes corporativos.  Gemini Enterprise es el paso más ambicioso de Google en inteligencia artificial aplicada al trabajo. No se trata de un complemento para Workspace, sino de una plataforma completa dentro de Google Cloud. Desde un solo chat, cualquier persona puede conectarse con sus datos en Google Workspace, Microsoft 365, Salesforce o SAP, y activar agentes inteligentes que responden, analizan y ejecutan tareas reales.El concepto de “agente” es clave: son pequeñas inteligencias diseñadas para hacer cosas específicas. Por ejemplo, redactar correos, analizar ventas, escribir código o resumir reuniones. Todo se coordina desde un entorno seguro con control centralizado, llamado Governance Framework, donde los responsables de TI pueden auditar y monitorear el comportamiento de cada agente.Thomas Kurian, CEO de Google Cloud, definió la plataforma como “la nueva puerta de entrada a la inteligencia artificial en el trabajo”. Y lo cierto es que el lanzamiento marca un cambio profundo: Google pasa de ofrecer herramientas dispersas, como Gemini para Gmail o Docs, a ofrecer una arquitectura completa de inteligencia artificial para toda la organización.  Aquí es donde el panorama se vuelve interesante. La llegada de Gemini Enterprise no ocurre en el vacío, sino en medio de una batalla abierta entre los gigantes de la inteligencia artificial. Microsoft ya vende Copilot dentro de su suite 365. OpenAI tiene ChatGPT Enterprise, con más de cinco millones de usuarios empresariales. Y Amazon acaba de anunciar Quick Suite, su propio entorno de agentes.Cada una de estas plataformas busca convertirse en el “centro” del trabajo digital. Microsoft apuesta por su ecosistema cerrado, OpenAI por la potencia de su modelo, y Google por un enfoque abierto, conectado a más de 100 000 socios tecnológicos. El precio también forma parte de la estrategia: Gemini Enterprise cuesta 30 dólares mensuales por usuario, menos que el plan de Copilot, que ronda los 40 dólares.En este contexto, la competencia no es solo técnica: es por el control del flujo de trabajo. Si las empresas adoptan Gemini, sus datos y procesos quedarán dentro del ecosistema de Google Cloud, con integraciones directas en su infraestructura. Por eso, esta batalla por la IA en el trabajo no trata únicamente de quién tiene el modelo más avanzado, sino de quién logra convertirse en el lugar donde todo ocurre.  Para Google, el reto está en convertir ese enfoque abierto en una ventaja real. Ya tiene aliados importantes. Virgin Voyages usa Gemini Enterprise para crear más de 50 agentes internos, incluido uno llamado Email Ellie, que aumentó un 28 % las ventas en julio y redujo el tiempo de producción de campañas en un 40 %. Macquarie Bank en Australia también adoptó la plataforma: el 99 % de sus empleados ya completó la capacitación en IA usando la herramienta Google Skills, y ahora desarrollan agentes que analizan documentos y mejoran la atención al cliente.Otro caso destacado es Gordon Food Service, con más de 12 000 empleados integrando Gemini Enterprise y Workspace. Sus equipos de ventas, marketing y recursos humanos ya usan agentes para automatizar informes, estudiar tendencias de consumo y crear contenidos internos. En todos los casos, el objetivo es el mismo: liberar tiempo humano para tareas creativas y estratégicas.Estos ejemplos muestran el verdadero propósito del proyecto: democratizar el uso de agentes de inteligencia artificial sin depender de programadores. Google quiere que cada trabajador tenga su propio “asistente empresarial”, entrenado con los datos de su organización y listo para colaborar en cualquier flujo de trabajo.  El ecosistema de Gemini Enterprise incluye seis componentes:Los cerebros: los modelos Gemini más recientes, incluidos Gemini 2.5 Flash Image y Gemini 2.5 Pro.El taller: un entorno sin código llamado Workbench, donde se crean y coordinan agentes.La fuerza de tarea: una colección de agentes preinstalados para investigación, análisis de datos y programación.El contexto: conectores que enlazan la IA con herramientas empresariales como Jira, Teams, Box o Confluence.La gobernanza: un tablero de control con seguridad, permisos y auditorías.El ecosistema abierto: más de 100 000 socios que desarrollan y venden sus propios agentes compatibles.Además, Google lanzó el programa GEAR (Gemini Enterprise Agent Ready) para formar a un millón de desarrolladores y una nueva plataforma educativa llamada Google Skills, con tres mil cursos gratuitos sobre inteligencia artificial. En paralelo, grandes consultoras como Deloitte, PwC, Capgemini y Accenture ya integran Gemini Enterprise en sus servicios para clientes corporativos.La estrategia de Google busca combinar tecnología, formación y un mercado de agentes certificados. Cada empresa podrá comprar, vender o compartir agentes dentro del ecosistema, lo que abre paso a una nueva economía digital: la de los agentes de IA.  Google está apostando fuerte con Gemini Enterprise, una plataforma diseñada para que la inteligencia artificial deje de ser un lujo y se convierta en una herramienta de trabajo cotidiana. Su enfoque abierto, su integración con sistemas de otras marcas y sus programas de aprendizaje apuntan a un futuro donde cada trabajador podrá diseñar su propio agente inteligente.Si te interesa cómo la IA está cambiando el mundo del trabajo, te invito a escuchar más historias como esta y seguir Flash Diario en Spotify.  Google lanza Gemini Enterprise, su nueva IA para empresas, capaz de crear asistentes inteligentes que automatizan el trabajo en cualquier sector.  

What's stopping CX leaders from turning mountains of customer data into executive-ready stories that prompt real change? In this episode, we dig deep into one of the most urgent—and often overlooked—challenges for customer experience (CX) teams: crafting compelling, actionable narratives from all that customer insight. Data is everywhere, but too often the dots just don't get connected in a way that the C-suite cares about. The difference between a statistic and a strategic priority? It's all in the storytelling. In my conversation with Ania Rodriguez, CEO of JourneyTrack, we explore the tools, techniques, and mindsets you need to bridge that gap—and the game-changing role that AI-driven storytelling is playing right now in CX strategy. If you're a CX practitioner, product leader, or anyone tasked with influencing business outcomes through customer insight, you'll want to hear directly from Ania. Her twenty-five years in the field, expertise in journey mapping, and insider knowledge on harnessing technology for business storytelling makes this episode essential listening. Whether you're tired of your insights landing with a thud—or want to lead boardroom conversations that spark action—Ania's guidance is practical, forward-looking, and instantly applicable. Here are three questions Ania answers in this episode: Why do even seasoned leaders struggle to translate customer data into executive-friendly narratives? How does JourneyTrack's Storytelling AI automate the process of building empathy and urgency for C-suite presentations? What are the crucial integrations and data strategies for making journey management systems truly enterprise-ready—and how can you put them to work right away? Ready to supercharge your customer storytelling and move your executive team from data fatigue to decisive action? Listen now and subscribe so you never miss an episode: Apple Podcasts Spotify You'll also find us on all your favorite podcast platforms! Meet Ania Rodriguez Ania Rodriguez is the CEO and founder of JourneyTrack, a pioneering journey management platform designed for enterprise-scale CX storytelling. With more than 25 years of experience, Ania has led transformational customer experience initiatives for some of the world's most recognizable brands—including Google, where JourneyTrack first launched. She is also the founder and CEO of Key Lime Interactive, a renowned CX consultancy known for its expertise in journey mapping, research, and strategy. Ania's leadership style blends human-centered design with data-driven rigor, and she has a longstanding reputation for coaching executives and teams on turning insights into action. She was among the earliest to bring AI-powered capabilities—like Storytelling AI and Recommendation AI—to journey management, ensuring that organizations can not only aggregate data from diverse sources (like Jira, Qualtrics, Medallia, Snowflake, and more) but can also deliver that information as compelling, actionable presentations tailored to any audience. Connect with Ania Rodriguez on LinkedIn Show Notes & References “Using Storytelling Playbooks to Supercharge Journey Management” (White Paper):  https://bit.ly/47gE1xE JourneyTrack platform: https://journeytrack.io/ LinkedIn: Ania Rodriguez "Made to Stick" by Chip and Dan Heath (Velcro theory of memory): https://heathbrothers.com/books/made-to-stick/ Integration partners referenced: Jira, Qualtrics, Medallia, Snowflake, Adobe Analytics, Google Analytics Forrester on Journey Management (industry wave publication): https://www.forrester.com/ Thanks for tuning in—subscribe for more expert strategies, and let's make customer data tell the stories that drive business forward!

Tyler chats with Andrew Black, co-founder and CEO of Kovr.ai and former AWS Emerging Tech lead, about the unsexy work that makes mission software real: turning security and compliance into something fast, predictable, and built into the dev loop. Andrew explains how Kovr.ai reads system docs, maps to NIST 800-53, drafts control implementations, flags gaps, and recommends fixes, so engineers focus on high-judgment problems while AOs and risk owners get reliable packages that move.What's happening on the Second Front:The true Valley of Death, speed and scale in productionAI that automates SSPs, findings, and control mappingHow to make compliance native to CI and CD with JIRA, Jenkins, SIEMWhy fixed-price software and clear architecture matter for customersCulture over strategy, setting weekly “big rocks,” hiring for gritConnect with AndrewLinkedIn: Andrew BlackConnect with TylerLinkedIn: Tyler Sweatt

Barcelona, here we come! Come join us on The Jira Life as we get ready for Atlassian Team '25 Europe in Barcelona! This week's episode is all about the must-haves, travel tips, and insider insights to help you make the most of the conference.It's also a special one, this will be Alex's first time traveling internationally, and he needs Rodney's and YOUR tips to help him prepare.From planning your agenda and packing essentials, to navigating Barcelona and finding the best community meetups, we'll cover everything you need to feel prepared (and excited!) for Team '25. Don't miss it live this Thursday!Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://lnkd.in/g5834KixOr Follow us on LinkedIn!https://lnkd.in/epszdbRjBecome a member on YouTube to get access to perks:https://lnkd.in/gzDWDAzNHosts:- Alex "Dr. Jira" Ortiz https://lnkd.in/eP2TQHcE https://lnkd.in/ewxmQs2s- Rodney "The Jira Guy" Nissen https://lnkd.in/exhJAMVm https://thejiraguy.com- Sarah Wright https://lnkd.in/gTbfSBka Producer:- "King Bob" Robert Wen https://lnkd.in/g5eRKWWEExecutive Producer: - Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codeshttps://lnkd.in/eZp7w7ieOutro: Fractal - Atriumhttps://lnkd.in/eMpcN8rf

What happens when the entire software industry gets repriced on the cost basis of AI? When AI procurement agents are pitting your product against five competitors in real-time speed trials? And when every project management tool builds the exact same agent platform? Welcome to Unsolicited Feedback, where we dig into the messy realities of building in the age of AI. Brian Balfour (Founder and CEO of Reforge) and Aaron White (Founder of Appy.ai, Former CTO at Vendr) are in the thick of building AI tools and their companies for the AI era. In this episode, they pull back the curtain on a massive shift happening right now: The entire industry is scrambling to shift from "all you can eat subscription" pricing to credit-based models that few consumers understand and the secondary effects. Brian and Aaron also tackle the launch of Notion's Agent platform and how it feels like every project management tool from Jira to Glean to Notion to Monday has the exact same strategy.

Nesrine Changuel helped build Spotify, Google Chrome, and Google Meet. Her work has helped her discover the importance of emotional connection in building successful products. At Google, she served as a dedicated “delight PM,” a role specifically focused on making products more delightful. She recently published Product Delight, a book that provides a practical framework for creating products that serve both functional and emotional needs. Based in Paris, she now coaches founders and CPOs on implementing delight strategies in their organizations.What you'll learn:1. Why delight is a business strategy, not just “sprinkling confetti” on top of functionality2. How to identify emotional motivators that drive product retention3. The 50-40-10 rule for balancing delight in your roadmap4. The 4-step delight model5. The origin story of Spotify's Discover Weekly6. Why B2B products need delight just as much as B2C products7. How to get buy-in from skeptical leaders who think delight is a luxury—Brought to you by:DX—The developer intelligence platform designed by leading researchers: https://getdx.com/lennyJira Product Discovery—Confidence to build the right thing: https://atlassian.com/lennyLucidLink—Real-time cloud storage for teams: https://www.lucidlink.com/lenny—Transcript: https://www.lennysnewsletter.com/p/a-4-step-framework-for-building-delightful-products—My biggest takeaways (for paid newsletter subscribers): https://www.lennysnewsletter.com/i/174199489/my-biggest-takeaways-from-this-conversation—Where to find Nesrine Changuel:• LinkedIn: https://www.linkedin.com/in/nesrinechanguel/• Newsletter: https://nesrinechanguel.substack.com/• Website: https://nesrine-changuel.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Introduction to Nesrine and product delight(04:56) Why delight matters(09:17) What makes a feature “delightful”(12:29) The three pillars of delight(13:03) Pillar 1: Removing friction (Uber refund example)(15:07) Pillar 2: Anticipating needs (Revolut eSIM example)(17:21) Pillar 3: Exceeding expectations (Edge coupon example)(18:35) The “confetti effect” and when it actually works(22:02) B2B vs. B2C: Why all products need emotional connection(29:52) The Delight Model: A 4-step framework(30:57) Step 1: Identifying user motivators (functional and emotional)(33:55) Step 2: Converting motivators into product opportunities(34:46) Step 3: Identifying solutions with the delight grid(36:46) Step 4: Validating ideas with the delight checklist(40:22) The Delight Model summarized(42:18) The importance of familiarity (Spotify Discover Weekly story)(45:21) Real examples: Chrome's tab management solution(51:32) Google Meet's solution for “Zoom fatigue”(55:02) Getting buy-in from skeptical leaders(59:39) Prioritizing delight: The 50-40-10 rule(1:02:41) Creating a culture of delight in your organization(1:06:45) The habituation effect(1:08:15) When delight goes wrong: Apple reactions example(1:10:21) How delight motivates product teams(1:12:24) Lightning round and final thoughts—Referenced:• Spotify: https://open.spotify.com/• Linear: https://linear.app/• How Linear builds product: https://www.lennysnewsletter.com/p/how-linear-builds-product• Jira: https://www.atlassian.com/software/jira• Asana: https://asana.com/• Monday: https://monday.com/• The Product Delight Model: https://nesrinechanguel.substack.com/p/the-product-delight-model• Revolut: https://www.revolut.com/• How Revolut trains world-class product managers: The “local CEO” model, raw intellect over experience, and a cultural obsession with building wow products | Dmitry Zlokazov (Head of Product): https://www.lennysnewsletter.com/p/how-revolut-trains-world-class-product-managers• Microsoft Cashback: https://www.microsoft.com/en-us/edge/features/shopping-cashback• Superhuman's secret to success: Ignoring most customer feedback, manually onboarding every new user, obsessing over every detail, and positioning around a single attribute: speed | Rahul Vohra (CEO): https://www.lennysnewsletter.com/p/superhumans-secret-to-success-rahul-vohra• Brian Chesky's secret mentor who died 9 times, started the Burning Man board, and built the world's first midlife wisdom school | Chip Conley (founder of MEA): https://www.lennysnewsletter.com/p/chip-conley• Workday: https://www.workday.com/• SAP: https://www.sap.com/• ServiceNow: https://www.servicenow.com/• Salesforce: https://www.salesforce.com/• GitHub: https://github.com/• Atlassian: https://www.atlassian.com/• Snowflake: https://www.snowflake.com/• Data Superheroes: https://www.snowflake.com/en/data-superheroes/• Google Meet: https://meet.google.com/• Andy Nesling on LinkedIn: https://www.linkedin.com/in/andynesling/• Matic: https://maticrobots.com/• Diego Sanchez's (Senior Product Manager at Buffer) post on LinkedIn: https://www.linkedin.com/feed/update/urn:li:activity:7365014292091346945/• Miro: https://miro.com/• Arc browser: https://arc.net/• Competing with giants: An inside look at how The Browser Company builds product | Josh Miller (CEO): https://www.lennysnewsletter.com/p/competing-with-giants-an-inside-look• Migros Supermarket: https://www.migros.ch/• The rise of Cursor: The $300M ARR AI tool that engineers can't stop using | Michael Truell (co-founder and CEO): https://www.lennysnewsletter.com/p/the-rise-of-cursor-michael-truell• Building Lovable: $10M ARR in 60 days with 15 people | Anton Osika (CEO and co-founder): https://www.lennysnewsletter.com/p/building-lovable-anton-osika• Linear's secret to building beloved B2B products | Nan Yu (Head of Product): https://www.lennysnewsletter.com/p/linears-secret-to-building-beloved-b2b-products-nan-yu• Suno: https://suno.com• Snapchat: https://www.snapchat.com/• Use Reactions, Presenter Overlay, and other effects when videoconferencing on Mac: https://support.apple.com/en-us/105117• Dr. Lipp: https://drlipp.com/• How to be the best coach to product people | Petra Wille (Strong Product People): https://www.lennysnewsletter.com/p/how-to-be-the-best-coach-to-product• The Great American Baking Show: https://www.imdb.com/title/tt21822674/• Le Meilleur Pâtissier: https://en.wikipedia.org/wiki/Le_Meilleur_P%C3%A2tissier• The Upside on Amazon Prime: https://www.amazon.com/gp/video/detail/amzn1.dv.gti.3cb8500f-31af-9f4f-5dec-701e086d58e8• The Intouchables: https://www.imdb.com/title/tt1675434/• Yoyo stroller: https://www.stokke.com/USA/en-us/category/strollers/yoyo-strollers• UppaBaby strollers: https://uppababy.com/strollers/—Recommended books:• Product Delight: How to Make Your Product Stand Out with Emotional Connection: https://www.amazon.com/Product-Delight-Stand-Emotional-Connection-ebook/dp/B0FGZ93D9Y/• Factfulness: Ten Reasons We're Wrong About the World—and Why Things Are Better Than You Think: https://www.amazon.com/Factfulness-Reasons-World-Things-Better/dp/1250107814• STRONG Product Communities: The Essential Guide to Product Communities of Practice: https://www.amazon.com/STRONG-Product-Communities-Essential-Practice/dp/3982235189/r—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.Lenny may be an investor in the companies discussed. To hear more, visit www.lennysnewsletter.com

BONUS: Nesrine Changuel shares how to create product delight through emotional connection! In this BONUS episode we explore the book by Nesrine Changuel: 'Product Delight - How to make your product stand out with emotional connection.' In this conversation, we explore Nesrine's journey from research to product management, share lessons from her experiences at Google, Spotify, and Microsoft, and unpack the key strategies for building emotionally resonant products that connect with users beyond mere functionality. The Genesis of Product Delight "I quickly realized that there is something that is quite intense while building Skype... it's not just that communication tool, but it was iconic, with its blue, with ringtones, with emojis. So it was clear that it's not just for making calls, but also to make you feel connected, relaxed, and part of it." Nesrine's journey into product delight began during her transition from research to product management at Skype. Working on products at major companies like Skype, Spotify, and Google Meet, she discovered that successful products don't just function well—they create emotional connections. Her role as "Delight PM" at Google Meet during the pandemic crystallized her understanding that products must address both functional and emotional user needs to truly stand out in the market. Understanding Customer Delight in Practice "The delight is about creating two dimensions and combining these two dimensions altogether, it's about creating products that function well, but also that help with the emotional connection." Customer delight manifests when products exceed expectations and anticipate user needs. Nesrine explains that delight combines surprise and joy—creating positive surprises that go beyond basic functionality. She illustrates this with Microsoft Edge's coupon feature, which proactively suggests discounts during online shopping without users requesting it. This anticipation of needs creates memorable peak moments that strengthen emotional connections with products. Segmenting Users by Motivators "We can discover that users are using your product for different reasons. I mean, we tend to think that users are using the product for the same reason." Traditional user segmentation focuses on demographics (who users are) or behavior (what they do). Nesrine advocates for motivational segmentation—understanding why users engage with products. Using Spotify as an example, she demonstrates how users might seek music for specific songs, inspiration, nostalgia, or emotional regulation. This approach reveals both functional motivators (practical needs) and emotional motivators (feelings users want to experience), enabling teams to build features aligned with user desires rather than assumptions. In this segment, we refer to Spotify Wrapped.  The Distinction from Jobs To Be Done "There's no contrast. I mean to be honest, it's quite aligned, and I'm a big fan of the job to be done framework." While aligned with Clayton Christensen's Jobs To Be Done framework, Nesrine's approach extends beyond identifying triggers to practical implementation. She acknowledges that Jobs To Be Done provides the foundational theory, distinguishing between personal emotional motivators (how users want to feel) and social emotional motivators (how they want others to perceive them). However, many teams struggle to translate these insights into actual product features—a gap her Product Delight framework addresses through actionable methodologies. Navigating the Line Between Delight and Addiction "Building for delight is about creating products that are aligned with users' values. It's about aligning with what people really want themselves to feel. They want to feel themselves, to feel a better version of themselves." The critical distinction between delight and addiction lies in value alignment. Delightful products help users become better versions of themselves and align with their personal values. Nesrine contrasts this with addictive design that creates dependencies contrary to user wellbeing. Using Spotify Wrapped as an example, she explains how reflecting positive achievements (skills learned, personal growth) creates healthy engagement, while raw usage data (hours spent) might trigger negative self-reflection and potential addictive patterns. Getting Started with Product Delight "If you only focus on the functional motivators, you will create products that function, but they will not create that emotional connection. If you take into consideration the emotional motivators in addition to the functional motivators, you create perfect products that connect with users emotionally." Teams beginning their delight journey should start by identifying both functional and emotional user motivators through direct user conversations. The first step involves listing what users want to accomplish (functional) alongside how they want to feel (emotional). This dual understanding enables feature development that serves practical needs while creating positive emotional experiences, leading to products that users remember and recommend. Product Delight and Human-Centered Design "Making products feel as if it was done by a human being... how can you make your product feel as close as possible to a human version of the product." Nesrine positions product delight within the broader human-centered design movement, but focuses specifically on humanization at the product feature level rather than just visual design. She shares examples from Google Meet, where the team compared remote meetings to in-person experiences, and Dyson, which benchmarks vacuum cleaners against human cleaning services. This approach identifies missing human elements and guides feature development toward more natural, intuitive interactions. In this segment we refer to the books Emotional Design by Don Norman, and Design for Emotion by Aarron Walter..  AI's Role in Future Product Delight "AI is a tool, and as every tool we're using, it can be used in a good way, or could be used in a bad way. And it is extremely possible to use AI in a very good way to make your product feel more human and more empathetic and more emotionally engaging." AI presents opportunities to enhance emotional connections through empathetic interactions and personalized experiences. Nesrine cites ChatGPT's conversational style—including apologies and collaborative language—as creating companionship feelings during work. The key lies in using AI to identify and honor emotional motivators rather than exploit them, focusing on making users feel supported and understood rather than manipulated or dependent. Developer Experience as Product Delight "If the user of your products are human beings... whether business consumer engineers, they deserve their emotions to be honored, so I usually don't distinguish between B2B or B2C... I say like B2H, which is business to human." Developer experience exemplifies product delight in B2B contexts. Companies like GitHub have created metrics specifically measuring developer delight, recognizing that technical users also have emotional needs. Tools like Jira, Miro, and GitHub succeed by making users feel more competent and productive. Nesrine advocates for "B2H" (business to human) thinking, emphasizing that any product used by humans should consider emotional impact alongside functional requirements. About Nesrine Changuel Nesrine is a product coach, trainer, and author with experience at Google, Spotify, and Microsoft. Holding a PhD from Bell Labs and UCLA, she blends research and practice to guide teams in building emotionally resonant products. Based in Paris, she teaches and speaks globally on human-centered design. You can connect with Nesrine Changuel on LinkedIn.

This week on The Jira Life, the TJL crew visit Josh Costella, Phoenix ACE co-leader. We'll see what Josh is up to lately including sneak peeks at his admin keynote for the upcoming Atlassian Builders' Summit.Join us for a fun hour, filled with knowledge and hot takes!Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!https://www.linkedin.com/company/the-jira-life/Become a member on YouTube to get access to perks:https://www.youtube.com/@thejiralife/joinHosts:- Alex "Dr. Jira" Ortizhttps://www.linkedin.com/in/alexortiz89/https://www.youtube.com/@ApetechTechTutorials- Rodney "The Jira Guy" Nissenhttps://www.linkedin.com/in/rgnissen/https://thejiraguy.com- Sarah Wrighthttps://www.linkedin.com/in/satwright/Producer:- "King Bob" Robert Wenhttps://www.linkedin.com/in/robert-wen-csm-spc6-a552051/Executive Producer: - Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codeshttps://www.youtube.com/c/monstercatOutro: Fractal - Atriumhttps://www.youtube.com/c/monstercatinstinct

Think cloud security is boring? Think again. Daniel talks with Tom Orbach, Director of Growth Marketing at Wiz and creator of the Marketing Ideas newsletter. His mission? Make “boring” impossible to ignore. Tom reveals the three-step framework he's used to turn a quiet cybersecurity brand into a social-media magnet: Humor. Participation. Status. He drops real examples you can steal: a CISO Toy Store, a cybersecurity musical, even a meditation app for stressed-out security leaders. These stunts turned brand awareness into fuel for sales and made Wiz the name everyone in cloud security knows. Whether you market SaaS, finance, or any “too serious” industry, this conversation proves “boring” can be exciting if you know how to Market your brand. If you want your brand to get noticed, talked about, and remembered, this episode is for you.  Atlassian is made for teams. Organize, collaborate, and manage work with a suite of tools that include Jira, Confluence, Trello, and more. To learn about how Atlassian can change the game for your team, go to https://www.atlassian.com/ Follow Tom: LinkedIn: https://www.linkedin.com/in/tomorbach/ Follow Daniel: YouTube: https://www.youtube.com/@themarketingmillennials/featured Twitter: https://www.twitter.com/Dmurr68 LinkedIn: https://www.linkedin.com/in/daniel-murray-marketing Sign up for The Marketing Millennials newsletter: www.workweek.com/brand/the-marketing-millennials Daniel is a Workweek friend, working to produce amazing podcasts. To find out more, visit: www.workweek.com

Be prepared for all things Jira on this week's episode of The Jira Life! The TJL crew welcome Ravi Sagar, CEO of Sparxsys and the OG of Jira authorities, for an hour of his perspectives of the history of Atlassian and Jira, recent events, and what he sees for Jira in the future.Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life===================================== Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group! https://ace.atlassian.com/the-jira-life/ Or Follow us on LinkedIn! https://www.linkedin.com/company/the-jira-life/Become a member on YouTube to get access to perks: https://www.youtube.com/@thejiralife/joinHosts: - Alex "Dr. Jira" Ortiz https://www.linkedin.com/in/alexortiz89/ https://www.youtube.com/@ApetechTechTutorials- Rodney "The Jira Guy" Nissen https://www.linkedin.com/in/rgnissen/ https://thejiraguy.com- Sarah Wright https://www.linkedin.com/in/satwright/Producer: - "King Bob" Robert Wen https://www.linkedin.com/in/robert-wen-csm-spc6-a552051/ Executive Producer: - Lina Ortiz Music provided by Monstercat: ===================================== Intro: Nitro Fun - Cheat Codes https://www.youtube.com/c/monstercatOutro: Fractal - Atrium https://www.youtube.com/c/monstercatinstinct

Adam Torres had a talk with Jonathan Shroyer, CEO of Quimbi.ai, to unpack his new venture: “agentic AI” super agents that plug into a company's stack (game data, Jira, CRM, Reddit, etc.), pre-draft hyper-personalized replies, flag fraud, suggest incentives, and help agents architect player/customer outcomes. Jonathan shares early traction (founded in May, first customers live, 20+ in pipeline), the plug-and-play rollout, and why this will be table stakes in five years. Follow Adam on Instagram at https://www.instagram.com/askadamtorres/ for up to date information on book releases and tour schedule. Apply to be a guest on our podcast: https://missionmatters.lpages.co/podcastguest/ Visit our website: https://missionmatters.com/ More FREE content from Mission Matters here: https://linktr.ee/missionmattersmedia Learn more about your ad choices. Visit podcastchoices.com/adchoices

⁠Adam Torres⁠ had a talk with ⁠Jonathan Shroyer⁠, CEO of Quimbi.ai, to unpack his new venture: “agentic AI” super agents that plug into a company's stack (game data, Jira, CRM, Reddit, etc.), pre-draft hyper-personalized replies, flag fraud, suggest incentives, and help agents architect player/customer outcomes. Jonathan shares early traction (founded in May, first customers live, 20+ in pipeline), the plug-and-play rollout, and why this will be table stakes in five years. Follow Adam on Instagram at ⁠https://www.instagram.com/askadamtorres/⁠ for up to date information on book releases and tour schedule. Apply to be a guest on our podcast: ⁠https://missionmatters.lpages.co/podcastguest/⁠ Visit our website: ⁠https://missionmatters.com/⁠ More FREE content from Mission Matters here: ⁠https://linktr.ee/missionmattersmedia⁠ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Shawn Dsouza: From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Shawn faces the massive AI transformation currently reshaping the tech industry, acknowledging both its benefits and the fear it creates among professionals questioning their relevance. In his organization, he witnesses AI delivering wonders for some teams while others struggle and lose projects. Rather than viewing AI as an overwhelming wave, Shawn advocates for experimentation. He shares practical examples, like helping a Product Owner streamline story creation from Excel to JIRA using AI tools, and leveraging MIRO AI for team collaboration. His approach focuses on identifying friction points where AI experiments could add value while keeping conversations centered on possibilities rather than fears. Self-reflection Question: Instead of fearing technological changes like AI, how can you create small experiments to explore new possibilities and reduce friction in your current work processes? [The Scrum Master Toolbox Podcast Recommends]

OpenAI has launched a beta version of Developer Mode for ChatGPT, which allows developers to utilize full read and write support for model context protocol tools. This new feature promises to enhance automation capabilities, enabling developers to create connectors for various applications, such as updating JIRA tickets or triggering workflows in services like Zapier. However, the introduction of this feature raises significant security concerns, particularly regarding the potential for prompt injections and the risk of malicious users exploiting these capabilities to access sensitive information. As the industry rapidly adopts this model context protocol, the need for secure configurations becomes increasingly urgent to prevent data breaches.In addition to Developer Mode, OpenAI has released GPT-5 Codecs, a large-language model optimized for coding tasks. This new model has reportedly led to a tenfold increase in usage among developers within a month, largely due to its integration with GitHub for dynamic code reviews. The Codex model has been trained on real-world coding tasks, making it a powerful tool for software engineers. Developers are already recognizing its potential to identify complex bugs that other tools may miss, which could lead to higher quality code and faster delivery cycles.Microsoft is also making strides in the AI space by introducing free co-pilot chat features in its Office applications for all Microsoft 365 Business users. This update includes a co-pilot chat sidebar in key applications like Word, Excel, and Outlook, allowing users to draft documents and analyze spreadsheets without needing an additional co-pilot license. While the premium version offers enhanced capabilities, the free features change the baseline for AI accessibility, putting powerful tools in the hands of every employee and raising concerns about shadow IT.On the cybersecurity front, the U.S. government has redirected crucial funding originally allocated to combat threats from Huawei towards tax cuts for wealthy individuals and corporations. This shift has left national security at risk, as projects aimed at enhancing U.S. cybersecurity and infrastructure suffer from a lack of follow-through. Meanwhile, the Department of Defense is set to implement its Cybersecurity Maturity Model certification requirements, which will be mandatory for defense contractors. As scammers increasingly target small businesses with fake reviews, the need for effective cybersecurity measures and compliance becomes more pressing for service providers.Four things to know today 00:00 AI Becomes Default: OpenAI Expands Workflows, Microsoft Democratizes Copilot, and Licensing Chaos Grows07:19 Huawei Money Gone, CMMC Is Here, and Your Reviews Are Under Attack10:04 Devicie, Zensai, and Apple Redefine Value: Automation, Adoption, and Repair Access12:57 Twice the Reach, No More Cash: Broadband Program's Success Meets a Dead EndThis is the Business of Tech.     Supported by: https://scalepad.com/dave/Webinar:   https://bit.ly/msprmail  All our Sponsors: https://businessof.tech/sponsors/ Do you want the show on your podcast app or the written versions of the stories? Subscribe to the Business of Tech: https://www.businessof.tech/subscribe/Looking for a link from the stories? The entire script of the show, with links to articles, are posted in each story on https://www.businessof.tech/ Support the show on Patreon: https://patreon.com/mspradio/ Want to be a guest on Business of Tech: Daily 10-Minute IT Services Insights? Send Dave Sobel a message on PodMatch, here: https://www.podmatch.com/hostdetailpreview/businessoftech Want our stuff? Cool Merch? Wear “Why Do We Care?” - Visit https://mspradio.myspreadshop.com Follow us on:LinkedIn: https://www.linkedin.com/company/28908079/YouTube: https://youtube.com/mspradio/Facebook: https://www.facebook.com/mspradionews/Instagram: https://www.instagram.com/mspradio/TikTok: https://www.tiktok.com/@businessoftechBluesky: https://bsky.app/profile/businessof.tech Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Feeling like you're spinning your wheels despite being busier than ever? You're not alone. Most productivity advice treats you like a machine that needs optimization, but you're a person created for relationship.In this episode, Nick and Kim break down the four core productivity challenges keeping Christian leaders overwhelmed and unfulfilled:Time awareness gaps - not knowing where your hours actually goPrioritization traps - spending more time on urgent than important tasksSystem shortages - constantly reacting instead of being proactiveFocus fallacies - getting distracted from meaningful workDiscover the urgent vs. important matrix that will transform your decision-making and learn why productivity isn't optimization—it's stewardship of the gifts God has given you.Resources:Michael Hyatt Focus PlannerAsana, Jira, Pomodoro TimerBook a strategy call: relationalleadership.co/contactConnect: relationalleadership.co | @relationalleadershipHow you can support us:• Leave us a 5-star review on iTunes or Spotify• Share this episode with a friend• Send a question for a future Office Hours episodeYou can work with us at Relational Leadership.

When Holly Grey first examined Horizon3.ai, she saw more than a cybersecurity startup. She saw a technology that could change the way companies safeguard themselves. Traditional pen tests, she tells us, are human-driven, vary widely by auditor, and usually happen just once a year. Horizon3.ai, by contrast, “started out as a technology alternative to pen testing.” Its platform can be deployed “within minutes, not hours or weeks or months,” Grey tells us, and has already executed “over 100,000 pen tests.”The system identifies exposures, connects them to known threat actors, and—most critically—prioritizes which vulnerabilities to fix. It integrates directly with tools like Jira, creates tickets, and confirms results after remediation. “Even as a CFO, I want to know we're not exposed,” Grey explains. That value proposition has already attracted more than 4,000 customers, she tells us.Her decision to join Horizon3.ai was equally deliberate. Grey noticed two respected colleagues had recently come aboard, including the CRO. That relationship, she says, is vital: “I need to know that I can trust that CRO implicitly.” After doing her own diligence, Grey was convinced of the company's momentum: “It's hard to grow over 100% year over year, and do that multiple years, without having product market fit.”The timing was fortuitous. Just as the company raised $100 million in Series D funding, its VP of Finance resigned. Horizon3.ai was ready to appoint its first CFO. “Here I am,” Grey tells us, “and I could not be happier in terms of joining.”

In this episode of The Jira Life, we reflect on the end of an era as Atlassian officially announces the end-of-life timeline for Data Center. From the plan to gradually ramp down support over the next three years to detailed dates and what that means for admins, app partners, and enterprises — we're covering it all.Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn!https://www.linkedin.com/company/the-jira-life/Become a member on YouTube to get access to perks:https://www.youtube.com/@thejiralife/joinHosts:- Alex "Dr. Jira" Ortiz https://www.linkedin.com/in/alexortiz89/ https://www.youtube.com/@ApetechTechTutorials- Rodney "The Jira Guy" Nissen https://www.linkedin.com/in/rgnissen/ https://thejiraguy.com- Sarah Wright https://www.linkedin.com/in/satwright/ Producer:- "King Bob" Robert Wen https://www.linkedin.com/in/robert-wen-csm-spc6-a552051/Executive Producer: - Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codeshttps://www.youtube.com/c/monstercatOutro: Fractal - Atriumhttps://www.youtube.com/c/monstercatinstinct

Waggoota torban dabran keessatti xurree heddurraa himannaan ተረኞች, ባለጊዜ, የኦሮሙማ መንግሥት, Oromoon masaraa seenee jiraa fi ka jiru mootummaa Oromooti jadhamee ballinaan hoggu himamu dhagahaa hardha geenye.Bara 2025 "mootummaa harkaa qaban" yookaan "mootummaa harkaa qabna" jachuun qoma dhiibanii dubbachuun kan dandahamu yoo warra furtuu diinagdee biyyaa bifa hedduun of- harkaatti galfatan adda baasanii beekan callaa. Kanaaf futuwwan diinagdee biyyaa yaroo ammaan kanatti Oromo moo warra biraati of-harkaa qaba? Furtuu diinagde dursanii of-harkatti galfachuun hegereef bu'aa maalii qabaa? Warra madda jajjabaa diinagdee ammayyaarraa moggaafamaniiho akkamiin miidhuuf jiraata? Dhihaadhaa!

Adam Cohen grew up in Toronto, in North York. He showed early signs of entrepreneurship by putting his lemonade stand on a wagon, and taking it door to door - or hustling his friends to buy souvenirs on a school field trip. His Dad was in VC, and was a big influence on his life, pushing him to succeed. Outside of professional life, he is big into sports, specifically basketball. In the past, he loved playing fantasy sports, which also influence how he built his business ventures.Adam and his team went through several iterations of AI tooling - summarizing AI, integrating git and JIRA, etc. While they were doing this, they realized that the best way to make a difference, was to first focus on the data itself.This is the creation story of Weave.SponsorsPaddle.comSema SoftwarePropelAuthPostmanMeilisearchMailtrap.TECH Domains (https://get.tech/codestory)Linkshttps://workweave.dev/https://www.linkedin.com/in/adam-b-cohen/Support this podcast at — https://redcircle.com/code-story-insights-from-startup-tech-leaders/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

Making Invisible Work VisibleLately I noticed, sprint velocity looked fine and Jira showed progress. But none of the key tests, critical analysis and silent validations are tracked.After my observations I questioned: How much of our real work is visible?In Agile teams, productivity is often measured by delivered outputs: written code, released features, completed user stories, increasing metrics in dashboards, sprint completion rates, closed Jira tasks, the number of successful CI/CD runs, pull requests deployed to production, or customer-facing new functionalities.These are all important indicators. However, the behind-the-scenes efforts that make these visible outcomes possible are just as valuable.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

From Chaos to Clarity: How AI is Rewriting the Playbook for Product ManagersLessons from my conversation with ex-Google PM Assaf Reifer on building tools that tame the noise, sharpen priorities, and give PMs back their most valuable resource: focus.When I think back on my time at Google, one of the highlights was building and scaling teams with incredibly talented product managers. Some of those PMs went on to lead big initiatives across YouTube, Google Health, and other parts of the company. A few branched out and became founders.One of them is Assaf Reifer, a former PM on my team at YouTube in Zurich. We first met over breakfast through what I think was a LinkedIn networking experiment. He had been at Bain, was exploring his next move, and we happened to be hiring. The match worked out beautifully. He ended up becoming one of the top performers on the team and played a key role in building YouTube Analytics and the transition from the old Creator Studio into what creators now use daily.Recently, I had the chance to catch up with Assaf on my Fireside PM podcast. He's been experimenting with new projects, one of which could change how PMs everywhere manage the daily chaos of inputs, competing priorities, and distractions. What follows is a long, deep dive into our conversation, plus my take on what early-to-mid career PMs in Silicon Valley can learn from it.The Setup: Why Now Is a Historic Moment for BuildersAssaf started by reflecting on what it feels like to be a builder in 2025. He's been a software engineer, a consultant, and a PM. But he emphasized that the past two years feel different, historic even.I remarked:“In the last two years with advancements in AI, a lot of the knowledge necessary to build something end to end is really bridged by some of these technologies. It empowers people to realize ideas and experiments that previously required 10 people and millions of dollars.”Think about that for a second. Not long ago, building a SaaS product that could ingest Zoom transcripts, Slack threads, and Jira tickets, then triage them into a priority list for a PM would have required a team of engineers, designers, and product folks. Now a single founder can stitch that together with off-the-shelf AI models, APIs, and some creativity.For early-career PMs, the actionable insight is clear: don't wait for permission to build. Even if you're not an engineer, AI has lowered the barrier to entry so much that you can tinker, prototype, and validate ideas faster than ever. Open ChatGPT or Gemini, describe what you want to build, and let the system guide you through the concepts you don't understand.Assaf encourages this approach:“The best way to start is open ChatGPT or Gemini, tell it what you want to build, and ask it how. It will respond with 30 terms you don't understand, and you just go one by one. You ask it to explain each concept, and gradually you close the gap very quickly.”That's the 2025 version of “learning to code.” You don't need to become a full-stack engineer. But you do need to become fluent in exploring, iterating, and leveraging AI as a co-pilot.The Problem: PMs as Air Traffic ControllersAfter talking about the broader builder landscape, we turned to the problem space Assaf is attacking. We discussed product managers as “air traffic controllers,” juggling multiple channels of information, each with different levels of urgency.“Being a PM is all about prioritizing. You're interacting with sales, engineering, customers, peers, executives. You have OKRs on one hand, and then Jira tickets or a customer threatening to churn on the other. Until recently, the best PMs just kept it all in their heads or in spreadsheets.”Sound familiar? If you're a PM, you've probably woken up to a wall of Slack notifications, 10 unread emails from sales, and a Jira dashboard full of tickets. Then, by 10am, you're in a meeting where a senior leader asks, “What do you think about this issue that came up this morning?” And you're embarrassed because you didn't even know it existed.I've been there. And I bet you have too.The core challenge: noise vs. signal. PMs succeed not because they read every message but because they know which ones matter. That judgment call has historically been a mix of intuition, experience, and luck.The Solution: Issue Center (PM Studio?)Assaf's project, tentatively called “Issue Center,” is a SaaS tool that ingests all the inputs PMs already swim in: Slack, Jira, Zoom transcript, and applies AI-powered rules to surface the truly critical items.The workflow looks like this:* Integration: Connect the tool to your company's communication stack. (His design partner is running Microsoft 365/Teams, but it could work with Slack and Google too.)* Rule Setup: Create rules that define what matters to you. For example, “API degradation impacting users” is critical. Or “customer mentions a competitor as better” is high.* AI Assistance: The system uses AI to evaluate whether inputs match your rules. It flags the items, explains why, and links you back to the source.* Prioritized Dashboard: Instead of drowning in messages, you wake up to a curated list of critical, high, and medium issues to tackle first.Assaf demoed it live, showing how rules surfaced relevant Jira tickets, Slack threads, and transcripts. At one point, he laughed at his own naming convention:“Clearly I'm not a marketer. It's called Issue Center for now, but we can call it PM Studio if that makes it sound cooler.”I told him PM Studio had a nice ring to it.The important thing wasn't the branding, though—it was the shift from reactive scrambling to proactive clarity.Actionable Takeaway #1: Define Your Own Rules of SignalHere's where PMs can learn something even before using a tool like this. Ask yourself: What are the true signals in my work?* Is it when a customer threatens to leave?* When an API is degrading?* When an executive brings up a competitor?Whatever they are, write them down. These are your “rules.” Even if you don't have AI filtering your inputs yet, the discipline of defining rules forces you to separate noise from signal.Assaf admitted that rule-writing is an art:“The rule description is very important, because that's what the system uses to match. If it's too narrow, it won't pick up. If it's too broad, you'll get noise. That's why I want to make onboarding easier with quick-start templates for common rules.”This mirrors how you should think about your own prioritization framework. If you're too vague (“respond to all customer requests”), you'll drown. If you're too narrow (“only focus on API latency under 200ms”), you might miss the forest for the trees.The Bigger Picture: Managers of PMsAssaf also highlighted another layer of value, helping PM leads manage their teams.“If you're a PM lead and you have a team, you want visibility into what critical topics your PMs care about, what jeopardizes OKRs, and where they need support. This tool can give you that bird's-eye view.”This is huge. One of the hardest parts of managing PMs is knowing what's actually keeping them busy. Are they firefighting customer issues? Negotiating with engineering? Or chasing shiny objects?For managers, the actionable advice is: ask your PMs to share their “critical issue list” with you weekly. Even if you don't have Assaf's tool yet, that discipline will create alignment and uncover mis-prioritizations.The Privacy Angle: Building TrustWe also talked about the obvious concern: privacy. If your tool is reading Slack messages, Zoom calls, and Jira tickets, where does that data go?Assaf has thought about this deeply:“This is architected as a single-tenant SaaS. It's installed in your company's own cloud tenant. Nothing leaves the org. Even when we use AI, it runs through your enterprise API key, which isn't used for training.”For PMs evaluating AI tools, this is a reminder: always ask how data is handled. At many companies, legal and IT will shut down even the coolest tool if privacy isn't bulletproof. If you're the PM championing adoption, anticipate those concerns and come prepared with answers.Actionable Takeaway #2: Trust Is a FeatureIn 2025, building trust is not just about having the right feature set. It's about handling privacy, security, and reliability as first-class features.If you're building a product, or even advocating for one inside your company, bake trust into your pitch. Show that you've thought about data handling, failure modes, and user control.Beyond Explicit Rules: The Future of Inferred PrioritiesOne of the fun parts of our conversation was brainstorming future features. I suggested that beyond explicit rules, the system could infer priorities by watching behavior:* If you always jump into competitor-related Slack threads, the system could propose a rule.* If you consistently respond faster to certain stakeholders, it could bump their inputs up in priority.Assaf agreed this was interesting but also flagged the risks:“Whenever you do something that isn't explicitly set by the user and you get it wrong, you risk losing trust. You don't want noise creeping into the critical bucket.”That's a broader lesson for PMs: don't get seduced by complexity if it undermines trust. Sometimes a simple, transparent system is better than a magical one that feels unpredictable.The Side Project: An AI Teddy BearWe spent most of our time on PM Studio, but Assaf also showed me something else: a prototype for an AI-powered plush toy that serves as a conversational buddy for kids.The idea is part educational, part entertaining. Think Teddy Ruxpin meets ChatGPT, but with parental controls and guardrails.He tested it with his own kids, and at one point, a child said he wanted to “eat the squirrel” in a story. The system responded, “That's not a very nice thing. Let's try something kinder.”That made me laugh—and also highlighted the importance of building safe AI for children.As a parent myself, I told Assaf:“If this thing could help kids develop critical thinking and curiosity before they jump into ChatGPT, I'd pay money for it. We don't formally teach critical thinking to children, but a well-designed toy could do it through fun experiences.”While this project is still early, it connects to a broader theme: AI is reshaping not just how we work, but how we learn, parent, and play.Actionable Takeaway #3: Think About Second-Order EffectsFor PMs, the teddy bear might seem irrelevant. But the lesson is this: when you build with AI, think about the second-order effects.* How does this change how people learn, not just how they work?* How does it shape what they trust, not just what they use?* How does it influence long-term skills, not just short-term productivity?If you only optimize for immediate outcomes, you miss the deeper impact your product could have.Practical Advice for PMs in Silicon ValleyLet's bring this back to you, the early-to-mid career PM navigating the chaos of Silicon Valley. Here are five actionable insights from my conversation with Assaf:* Define Your Critical Rules. Don't wait for a tool. Write down the signals that truly matter in your role and use them to triage your own work.* Build Trust Through Clarity. Whether you're building products or pitching ideas internally, make privacy, reliability, and transparency part of your value prop.* Use AI as a Learning Co-Pilot. Open ChatGPT or Gemini and let it teach you the concepts behind the systems you want to build. Don't be afraid of looking dumb, ask it to explain everything.* Share Priorities with Your Manager. If you manage PMs, ask for their top three critical issues weekly. If you're managed, proactively share them. It will align expectations and reduce surprises.* Anticipate Second-Order Effects. Don't just think about what your product does today. Think about how it changes behavior, skills, and trust over time.Why This Matters: The Cambrian Explosion of BuildersWe closed our conversation reflecting on the bigger picture. I remarked:“You wonder if the next hundred billion dollars of market value will come not from 10 decacorns, but from a thousand smaller companies run by 5–10 people. That's good for customers. It's good for competition. And it's possible because of AI.”This is a turning point in product management. The PMs who thrive in the next decade will be those who can harness AI, not just as users, but as builders, integrators, and thinkers.Final ThoughtsCatching up with Assaf reminded me of why I love product management. At its best, it's about solving messy problems, shaping the future, and helping people focus on what matters most.As you navigate your own PM career, I encourage you to experiment with AI, define your rules of signal, and always keep trust at the core of what you build.And if you want more personalized support, I run a 1:1 executive, career, and product coaching practice at tomleungcoaching.com. If you want to try Assaf's Issue Center tool as a design partner, feel free to contact him or hit him up on X. OK. Enough pontificating. Let's get back to work. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit firesidepm.substack.com

In this episode of The Jira Life, we're joined by Chris Cooke to talk about CollabSoft Ventures and their role at TEAM '25 Europe.Chris shares how CollabSoft is investing directly into the Atlassian ecosystem, including initiatives that provide funding and support for small Marketplace vendors who want to grow, innovate, and scale their apps. As Chris put it, they're essentially “handing out free money to small vendors.”We'll dive into what this means for the community, how vendors can get involved, and why CollabSoft Ventures believes in building up the next generation of Atlassian Marketplace innovators.If you're an app builder, vendor, or partner curious about new opportunities, this is a conversation you won't want to miss.Thank you to Revyz for backing us up and making The Jira Life possible. https://www.revyz.io/The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn! / the-jira-life Become a member on YouTube to get access to perks:https://www.youtube.com/@thejiralife/...Hosts:Alex "Dr. Jira" Ortiz / alexortiz89 / @apetechtechtutorials Rodney "The Jira Guy" Nissen / rgnissen https://thejiraguy.comSarah Wright / satwright Producer:"King Bob" Robert Wen / robert-wen-csm-spc6-a552051 Executive Producer: Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codes / monstercat Outro: Fractal - Atrium / monstercatinstinct

This week on The Jira Life, we're excited to welcome Brittany Joiner and Rob Hean as they showcase their brand-new Udemy course: Project Management with Trello: A-Z Guide. Whether you're a beginner exploring Trello for the first time or a seasoned project manager looking to streamline workflows, this course is designed to take you from basics to advanced practices. Brittany and Rob will walk us through their favorite features, how Trello can be adapted to fit different project styles, and why Trello remains one of the most flexible, user-friendly tools for collaboration. We'll also dive into the behind-the-scenes process of creating the course, what learners can expect, and how this resource can help individuals and teams organize projects, boost productivity, and manage tasks with confidence. 

In this season of Building Better Developers with AI, hosts Rob Broadhead and Michael Meloche revisit a past topic: 'Transform Your Projects: The Ultimate Guide to Effective User Stories.' This episode offers a fresh perspective on how teams can achieve greater success by writing better user stories. The hosts initially tackled this subject in an earlier season, but they return to it because the challenge remains timeless: poorly written user stories continue to derail software projects. This time, they dive deeper into lessons learned, customer-centric approaches, and frameworks that make user stories truly work. Why Writing Better User Stories Still Matters Rob opens with a familiar frustration: sitting in sprint planning and realizing the user stories don't make sense. Vague requirements create confusion, rework, and wasted effort. A user story is not a specification—it's a promise for a conversation that builds shared understanding. By writing better user stories, teams maintain focus on outcomes, rather than implementation. They deliver features that users actually need, instead of technical solutions that fall short. The Philosophy of Writing Better User Stories User stories should always: Stay customer-centric by focusing on what the user wants, not the technical details. Break down work into small, manageable chunks that improve agility and estimation. Emphasize outcomes over implementation, avoiding the trap of data tables and CSS classes too early. Rob illustrates this with the ATM example: “As a customer, I want to withdraw cash so that I can access money in my account.” This keeps the story grounded in the user's experience. The Anatomy of Writing Better User Stories At the core of writing better user stories is a simple formula that makes requirements clear and human: As a [user role] I want [goal] So that [reason] This framework ensures that every story is tied directly to a user's perspective, their needs, and the value they'll receive. However, strong stories extend beyond this sentence structure. Rob and Michael highlight two key frameworks that add depth and clarity: The Three C's – Card, Conversation, and Confirmation, which explain how stories spark dialogue and define “done.” The INVEST Model – Independent, Negotiable, Valuable, Estimable, Small, and Testable- is a checklist that helps teams evaluate whether a story is ready to move forward. Finally, one important reminder: each story should only have one meaning. If a story can be interpreted in multiple ways—or contains “if/then” scenarios—it should be split into smaller, more focused stories. This keeps the backlog clean and avoids confusion later in development. The Three C's of Writing Better User Stories 1. Card The card represents the user story itself. Traditionally, teams would write stories on index cards. Today, tools like Jira, Trello, or Asana take their place. The key is that the card is just a placeholder for a conversation, not the entire requirement. It captures the essence of the story but leaves room for discussion. 2. Conversation The conversation is where the real value happens. Developers, product owners, and stakeholders discuss the story, ask clarifying questions, and uncover details that weren't written down. These discussions ensure that the team shares a common understanding of the user's needs. Without this step, the story risks being too vague or misinterpreted. 3. Confirmation The confirmation defines how the team knows the story is complete. This typically takes the form of acceptance criteria or test cases. Confirmation transforms a story from an idea into a verifiable piece of functionality. It answers the critical question: What does “done” look like? Card captures the idea. Conversation builds the understanding. Confirmation proves the work is complete. The INVEST Model for Writing Better User Stories The INVEST model is a simple but powerful checklist that helps ensure user stories are clear, practical, and actionable. Each letter represents a quality that a strong user story should have. Independent A good user story should stand on its own. That means it can be developed, tested, and delivered without being blocked by another story. Independence reduces dependencies and keeps projects moving smoothly. Negotiable User stories are not contracts carved in stone—they're open to discussion. Teams should be able to negotiate details, scope, and implementation during conversations. This flexibility encourages collaboration and prevents rigid requirements that may not fit real-world needs. Valuable If a story doesn't provide business or user value, it doesn't belong in the backlog. Every story should clearly tie back to outcomes that matter for the end-user or the organization. This keeps the team focused on delivering impact, not just features. Estimable A story should be clear enough that the team can estimate the effort to complete it. If it's too vague or too large, it can't be accurately sized. Estimable stories make sprint planning realistic and help track progress more effectively. Small Stories should be small enough to complete within a single iteration. Large stories, sometimes called “epics,” should be broken down into smaller, more manageable pieces. Small stories are easier to understand, estimate, and test. Testable Finally, a user story must be testable. The team needs to know how to verify it's “done.” This often takes the form of acceptance criteria or test cases, ensuring the functionality can be validated from the user's perspective. The INVEST model keeps stories clear, focused, and actionable. If a story fails any of these tests, refine it before moving forward. Lessons From the Trenches: Writing Better User Stories in Practice Michael highlights a recurring issue: customers often don't fully understand their “why.” They may use outdated paper trails, redundant processes, or even misuse tools they already own. Sometimes developers must reverse-engineer requirements by observing workflows, asking why at each step, and uncovering hidden pain points. Rob adds that trust plays a huge role—stakeholders may initially follow the “official” process, but only reveal their real practices after rapport is established. Avoiding Common Pitfalls Even with good intentions, stories can fall short when they are: Too vague or incomplete. Disconnected from actual business processes. Written without acceptance criteria. Michael stresses that implied requirements are dangerous. Developers should always strive for clearly defined acceptance criteria that leave no room for ambiguity or uncertainty. Practical Tips for Writing Better User Stories The hosts wrap up with actionable guidance for developers: Speak up – Don't code vague tickets without asking questions. Push for the “so that” – The business value matters most. Write acceptance criteria – Define what “done” means. Break down big stories – Smaller, testable stories are easier to validate. Stay user-focused – Keep technical details in subtasks, not in the story. Example: Bad: Add a contact form. Good: As a potential customer, I want to fill out a contact form with my name, email, and message, so that I can get in touch with the company about their services. This richer story sparks the right questions: Which fields are required? Should multiple contact methods be supported? These clarifications lead to solutions that match real needs. Final Thoughts By revisiting this subject, Rob and Michael remind us that user stories are more than backlog items—they are bridges between developers and customers. Writing better user stories keeps teams aligned, prevents rework, and ensures projects deliver meaningful results. Implied requirements are not good requirements. Defined requirements are good requirements. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Updating Developer Tools: Keeping Your Tools Sharp and Efficient Building Your Personal Code Repository Your Code Repository and Ownership of Source – Consulting Tips Using a Document Repository To Become a Better Developer The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

In this episode of This New Way, Aydin sits down with Ali Pourshahid, Chief Engineering Officer at Solace, to explore how he's woven AI into his daily routines as a technology executive. Ali shares real demos of how he uses Solace's Agent Mesh and other AI tools to:Generate security-focused slide decks from Confluence in minutesSchedule a 12-person leadership offsite without lifting a fingerTransform messy Word reports into polished heat maps for government updatesAutomate customer support workflows across Jira, CRM, and internal systemsAli also breaks down how Solace is productizing their internal AI system, why agent-to-agent communication (A2A) is critical, and how to build a culture of experimentation with “AI champions” inside your company.This is a masterclass in how executives can stop just “keeping up” with AI—and instead lead the charge.Timestamps0:58 – What is Solace and Ali's role as Head of Engineering2:09 – Ali's daily “AI deep hour” and why he treats it like a workout3:19 – Prepping for a customer security call with AI + Confluence5:14 – Auto-generated sequence diagrams and value slides in minutes9:48 – Using Microsoft Copilot to instantly format professional slides13:35 – AI as an executive assistant: scheduling a 12-person workshop17:01 – Turning unstructured Word reports into project heat maps20:07 – Building an AI champions group and lightning talks at Solace25:05 – Solace Agent Mesh: event-driven architecture for agents29:01 – Live demo: Automating Jira support tickets with agent workflows33:33 – Scaling digital employees with orchestrator agents37:08 – Why evals are critical for testing and deploying AI agents39:05 – Ali's habit: always ask “How can I do this better with AI?”40:08 – What excites Ali most about AI in the next yearTools & Technologies Mentioned:Solace Agent Mesh – Multi-agent orchestration platform built by SolaceConfluence – Wiki where AI pulls technical details for slide prepClaude & ChatGPT – LLMs used for connecting to internal toolsMCP (Model Context Protocol) – Framework for securely connecting AI to enterprise dataMicrosoft Copilot – AI inside PowerPoint, Excel, and other Office toolsMermaid – Visualization tool for generating diagrams and heat mapsA2A Protocol (Agent-to-Agent) – Open standard for agent communication donated by GoogleSubscribe at⁠ thisnewway.com⁠ to get the step-by-step playbooks, tools, and workflows.

Andrew bootstrapped Wrike and grew it from 0 to a $2.2B exit by doing the exact opposite of what every startup book tells you. No pivots. No talking to customers before launch. No narrow niche. Just 17 years of relentless focus on one problem while everyone else was pivoting every 18 months. In this episode, he breaks down exactly why bootstrapping saved his company (and why VC would have killed it), why he ignored customer development and just built in a bunker, and how manning the support phones himself became his secret product development weapon. Now building Zencoder (AI coding agents), he shares why the future isn't about replacing developers but making every human "superhuman" at their job. This is mandatory listening for any founder questioning conventional startup wisdom.Why You Should Listen:Grew to $2.2B with no pivots for 17 years while competitors kept "failing fast"How he doubled revenue every year from $0 to $100M+ ARRWhy manning support phones himself was better than any customer development processWhy copycats helped Wrike grow fasterThe future of AI agentsKeywords:Wrike, Andrew Filev, bootstrapping, 2 billion exit, product market fit, SaaS, Zencoder, AI coding agents, no pivot strategy, collaboration software00:00:00 Intro00:03:30 Moving to Silicon Valley from Russia to build for millions00:10:06 Going all-in after previous side projects failed00:11:27 Why he never pivoted once in 17 years00:18:47 Launching without talking to customers first00:24:12 Manning support phones and discovering the real roadmap00:29:01 When Microsoft Project, Basecamp, and Jira were the competition00:34:31 The only job definition—double the business every year00:54:16 Why Developers won't be replaced, and become superhuman01:01:57 The $2.2B exit and making employees' dreams come true01:04:36 Finding product-market fit at Zencoder vs Wrike01:06:55 Focus on people—everything traces back to themSend me a message to let me know what you think!

In this episode of Building Better Developers with AI, Rob Broadhead and Michael Meloche revisit their earlier discussion on defining ‘done' in Agile – how to stay on Track and Avoid Scope Creep. They explain why “done” must mean more than “I finished coding,” and they show how a shared Definition of Done (DoD) keeps teams aligned and projects on schedule. What Does “Done” Really Mean? In Agile, “Done” extends beyond writing code. It often includes: Passing unit and integration tests Receiving QA approval Deploying to staging or production Updating documentation Securing acceptance sign-off Without a clear, documented DoD, each team member may interpret “done” differently. As a result, projects risk rework, delays, and frustration. “If we ask, ‘Is it done?' we should get a clear yes or no—no ‘sort of' or ‘almost.'” – Rob Broadhead Why Ambiguity Leads to Trouble Michael points out a common problem: a developer finishes their code, marks the ticket as done, and passes it to QA—only for testers to find gaps in the requirements. A login screen ticket might say “Allow users to log in with username and password.” But does that mean: Username is case-insensitive? Special characters are allowed? Do error messages display on failure? If these details aren't defined, both the developer and tester may interpret “done” differently, leading to frustration on all sides. The Link Between “Done” and Scope Creep Rob and Michael agree: unclear definitions open the door to scope creep. Without a firm DoD, features get stuck in an endless loop of revisions: Developers feel QA keeps moving the goalposts. QA feels developers aren't meeting the requirements. Clients think the delivered feature isn't what they expected. Over time, this erodes trust and pushes delivery dates further into the future. Lessons from the Field Michael contrasts two scenarios from his career that highlight the power of a strong Definition of Done. Before an acquisition, his team worked with a crystal-clear DoD. Every ticket had precise requirements, clear acceptance criteria, and well-defined testing steps. As a result, tasks finished on time, testing followed a predictable pattern, and rework was rare. The team knew exactly when work met the agreed standards, and stakeholders trusted that “done” truly meant done. After the acquisition, the situation changed dramatically. Tickets became vague and massive in scope, often resembling open-ended “make it work” directives. Multiple teams modified the same code simultaneously, resulting in merge conflicts, inconsistent results, and unpredictable delivery schedules. Without a clear DoD, developers, testers, and stakeholders all had different ideas of what completion looked like, and work frequently circled back for revisions. The difference between the two environments came down to one factor: a clear and enforceable Definition of done. In the first scenario, it acted as a shared contract for quality and completion. In the second, the lack of it created confusion, wasted effort, and missed deadlines. Building a Strong Definition of Done The hosts outline key components every DoD should include: Code complete and reviewed – Ensures quality and shared understanding. Automated tests passing – Reduces regressions. Documentation updated – Prevents future confusion. Deployment verified – Proves it works in the target environment. Acceptance criteria signed off – Confirms alignment with the original requirements. Pro Tip: Keep your tests fresh—don't just update them to pass without meeting the real requirement. Who Owns the DoD? One person doesn't own the DoD—it's a team responsibility. Product owners, Scrum Masters, and developers should collaborate to create and update it, reviewing it regularly to adapt to evolving project needs. Making “Done” Part of the Process Once defined, your DoD should be visible and integrated into your workflow: Add it to user stories during sprint planning. Track it in tools like Jira, Trello, or GitHub. Use workflow stages that match your DoD steps—coding, testing, review, deployment, and sign-off. Michael emphasizes that personal accountability matters just as much as team accountability. Great developers hold themselves to the DoD without needing reminders. Your Challenge: Define “Done” This Week If your team doesn't have a documented Definition of Done—or if it's been more than three months since you reviewed it—set aside time this week to: Write down your current DoD. Identify where ambiguity still exists. Get agreement from the entire team. Update your workflow so that every ticket must meet the DoD before it is closed. This single step can prevent months of wasted effort and ensure your work delivers exactly what's intended. The Bigger Picture A well-defined DoD is more than a checklist—it's your guardrail against wasted effort and shifting goals. It ensures the final product matches what the client truly needs, not just what was coded. Your Definition of Done is your “why” for each task—it keeps your work focused, aligned, and valuable. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Getting It Right: How Effective Requirements Gathering Leads to Successful Software Projects The Importance of Properly Defining Requirements Changing Requirements – Welcome Them For Competitive Advantage Creating Use Cases and Gathering Requirements The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

What happens when a bunch of Palantir and Lockheed alums get fed up with how hard it is to do business with the government—and actually do something about it? You get Pryzm: the common operating system for capture.In this episode, Tyler sits down with Nick LaRovere, co-founder and CEO of Pryzm, to talk about building for the part of the defense ecosystem everyone hates (but no one can ignore): procurement. From scraping sam.gov to stitching together Salesforce, JIRA, and inboxes, Nick shares how Pryzm is bringing order to chaos—and helping both industry and government move faster.They also get into:What it really takes to build a mission-driven company—and why most give upThe hidden cost of stovepiped teams and siloed dataHow policy, budget, and capture are finally starting to talk to each otherWhy talent and team dynamics are just as critical as the tech you're building

Asgaut Mjølne Söderbom and Ola Hast, two developers with Sparebank1 speak about their journey towards continuous deployment and pair programming. During the conversation, they share how they use the "waste clock" to identify areas of improvement or how TDD helps them deliver high-quality code. Read a transcript of this interview: https://bit.ly/4lNvYgI Subscribe to the Software Architects' Newsletter for your monthly guide to the essential news and experience from industry peers on emerging patterns and technologies: https://www.infoq.com/software-architects-newsletter Upcoming Events: InfoQ Dev Summit Munich (October 15-16, 2025) Essential insights on critical software development priorities. https://devsummit.infoq.com/conference/munich2025 QCon San Francisco 2025 (November 17-21, 2025) Get practical inspiration and best practices on emerging software trends directly from senior software developers at early adopter companies. https://qconsf.com/ QCon AI New York 2025 (December 16-17, 2025) https://ai.qconferences.com/ QCon London 2026 (March 16-19, 2026) https://qconlondon.com/ The InfoQ Podcasts: Weekly inspiration to drive innovation and build great teams from senior software leaders. Listen to all our podcasts and read interview transcripts: - The InfoQ Podcast https://www.infoq.com/podcasts/ - Engineering Culture Podcast by InfoQ https://www.infoq.com/podcasts/#engineering_culture - Generally AI: https://www.infoq.com/generally-ai-podcast/ Follow InfoQ: - Mastodon: https://techhub.social/@infoq - X: https://x.com/InfoQ?from=@ - LinkedIn: https://www.linkedin.com/company/infoq/ - Facebook: https://www.facebook.com/InfoQdotcom# - Instagram: https://www.instagram.com/infoqdotcom/?hl=en - Youtube: https://www.youtube.com/infoq - Bluesky: https://bsky.app/profile/infoq.com Write for InfoQ: Learn and share the changes and innovations in professional software development. - Join a community of experts. - Increase your visibility. - Grow your career. https://www.infoq.com/write-for-infoq

In this Marketing Over Coffee: Katie Robbert returns to talk Project Management, Software Development Lifecycle, Wednesday, and more! Direct Link to File Project Management, The List: Asana, JIRA, Monday, Trello, MS Project, Wrike, Basecamp, Airtable, Excel Project management vs. Task Management Project management vs. Digital Asset Management vs. Community Building Applying Software Development Lifecycle Practices […] The post What’s In Your Project Management Toolbox? appeared first on Marketing Over Coffee Marketing Podcast.

Anamaria Ungureanu: Building Self-Awareness in Overly-Technical Product Owners Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Master Storyteller Anamaria highlights a Product Owner who excelled at storytelling and vision communication, making every team member feel aligned with project goals. This exceptional PO consistently explained the "why" behind requirements and painted compelling pictures of how the team's current work would create future value. Their storytelling ability kept the team engaged and motivated, demonstrating how great Product Owners apply agile mindset principles to create shared understanding and purpose. The Bad Product Owner: The Monologue Specialist Anamaria describes a technically-skilled Product Owner who transitioned from a tech lead role but fell into the anti-pattern of excessive monologuing during sprint planning sessions. This PO, despite good intentions, overwhelmed the team with lengthy technical details, causing developers to withdraw from interactions and leaving them confused about project purposes. Through one-on-one coaching focused on building self-awareness and establishing working agreements, Anamaria helped this PO learn to communicate more effectively and engage collaboratively with the team. Self-reflection Question: How do you help Product Owners transition from technical expertise to effective team communication, and what signs indicate when detailed explanations become counterproductive monologues? [The Scrum Master Toolbox Podcast Recommends]

Anamaria Ungureanu: Tracking Scrum Team Behavioral Evolution Over Time Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anamaria defines Scrum Master success by focusing on team behavioral trends and performance evolution over time. She monitors how teams increase trust with stakeholders, demonstrate commitment, and apply agile behaviors consistently. Her approach emphasizes seeking regular feedback from stakeholders and conducting honest self-assessments to ensure the Scrum Master role is truly maximizing team performance. Success isn't measured by a single moment but by sustained positive change in team dynamics and delivery capabilities. Featured Retrospective Format for the Week: Stop/Start/Continue with Enhanced Focus Anamaria recommends the classic Stop/Start/Continue format but emphasizes the importance of varying the questions and bringing both quantitative and qualitative data to drive meaningful conversations. She suggests picking specific themes for each retrospective (like testing) and ensuring that discussions lead to concrete, actionable outcomes rather than just surface-level feedback. Self-reflection Question: How do you currently measure your effectiveness as a Scrum Master, and what trends in your teams indicate genuine progress versus superficial compliance? [The Scrum Master Toolbox Podcast Recommends]

Anamaria Ungureanu: Practical Strategies for Organizational Tool Rollouts Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anamaria shares her approach to successfully implementing JIRA across an organization by focusing on practical value rather than forcing adoption. Her strategy involved identifying early believers within teams, conducting open discussions to gather feedback, and demonstrating concrete benefits like improved dependency management. Rather than trying to convince resisters, she concentrated on working with willing teams to showcase the tool's value, providing real-time support during implementation, and ensuring team members felt supported throughout the transition. Her method emphasizes being present to answer questions immediately and building momentum through successful early adopters. Self-reflection Question: When leading organizational change, how do you balance addressing resistance with amplifying the voices of those ready to embrace new approaches? [The Scrum Master Toolbox Podcast Recommends]

In this episode of The Big Impression, we're joined by James Rothwell, managing director of brand marketing at Kinective Media. Rothwell walks us through what's changed since launch — from major brand partnerships and custom content integrations to a headline-making alliance with JetBlue. With over 110 million traveler profiles and 63 million MileagePlus members, Kinective is fast becoming one of the most compelling new players in commerce media. Episode TranscriptPlease note, this transcript  may contain minor inconsistencies compared to the episode audio. Damian Fowler (00:00):I'm Damian Fowler.Ilyse Liffreing (00:01):And I'm Ilyse Liffreing.Damian Fowler (00:02):And welcome to this edition of The Big Impression.Ilyse Liffreing (00:09):Today we're checking back in on one of the boldest moves in airline media, connected media by United Airlines as they've redefined what's possible in the world of Traveler Media Networks.Damian Fowler (00:22):Our guest is James Rothwell, managing director of brand marketing at Connective Media. James and his team are helping United leverage the power of 110 million traveler profiles, create new opportunities for brands across the entire customer journey.Ilyse Liffreing (00:38):We actually spoke with Connective on this podcast just last year and just a week after they launched. A lot has happened since then from major brand partnerships to rapid innovation in tech content and measurement, and today we're catching up on what's new. So let's get into it.Damian Fowler (00:57):So James, this time last year, United had just launched Connective Media. It was June, 2024 at CAN, and it was the first airline media network. Could you walk us through what's happened since then? How has the network grown? How has it attracted brand campaigns and how is it working?James Rothwell (01:20):Yeah, absolutely. And thank you Damian, for having me on. This is great to be here. We just celebrated our first birthday, which is a wonderful thing. We're engaging with so many different types of brands who are interested in reaching a premium traveler audience. We've seen some success in most of the key verticals that you would imagine, and then some surprising ones too. And obviously it's a slam dunk for a travel brand or a destination brand, but those non-endemic brands, the non-endemic advertisers who are trying to reach travelers, no matter where they are in their journey or even in between journeys, we're finding really interesting use cases, really interesting targeting options and ways for them to be able to reach them across all of our screens. And on,Damian Fowler (02:08):Let's get into it a little further. Can you give us some examples? And you mentioned non endemics as well, but maybe we could start with the endemics and then move on to the non endemics.James Rothwell (02:17):No, absolutely. I think travel as a category is a growth sector right now. I think ever since the pandemic, people have been looking to explore the world and get out of the, I mean, they were cooped up for quite a while there, and so travel's never been more popular. Like any industry, you've got to break through the noise and the options that you have out there. Right? World's a big place.(02:43):Luckily we fly to a lot of different places. We have over 330 different destinations. One really interesting case study that we've just completed was with the Cayman Islands tourist board, and they were looking to drive passengers travelers to the Cayman Islands, and they worked with us across all of our media, and we were able to do closed loop attribution based on the bookings that were then made to those destinations. So for us, measurement and measurability is incredibly strong in the travel sector and the travel space. We were able to see basically with Cayman Islands, that 9,000 bookings came from exposure to the ads that ran across email, across our club lounges and in our entertainment seat back screens on the planes. So we were able to drive awareness, intent, and then conversion, and we were able to track that and they saw a 13 times return on an ad spend against that campaign. We were incredibly happy with that. They were incredibly happy with that. We obviously made some travelers very happy to go enjoy the wonderful blues ocean around the Cayman Islands.Damian Fowler (03:58):Yeah, there's something nice when you see that on screen. You'reJames Rothwell (04:01):Like that, I'm going to go there. Yeah, that looks nice. That one sells itself. ItIlyse Liffreing (04:05):Does. So you mentioned non-endemic brands too. That's really interesting.James Rothwell (04:09):Yeah, I mean, we're all travelers, right? We all got on a plane to be here in Cannes. It doesn't define us, but certainly it helps to give context and potentially insights around who we are as individuals and what we like to spend our money on where we like to spend our time. And so that translates into a really interesting audience segment for different brands. So we've had a lot of luck and a lot of success with luxury brands who want to reach, especially front of plane individuals. B2B brands has been a real boon for us as well. Business decision makers, they're looking to find those individuals and we can find 'em on the planes in the clubs and through different digital channels as well. And so that's been a really interesting sector that we've been able to really capitalize on, and I think they've been able to see some significant growth on that. And we work with, for example, JIRA, which is an Atlassian product, and they did a full omnichannel activation with us and they saw some fantastic results there.Ilyse Liffreing (05:16):Very cool. Could you describe that a little bit more, how, I guess you worked almost in a custom way, it sounds like With JiraJames Rothwell (05:26):For that one was very custom. In fact, they had their own branding moment and wanted to use some of that branding and creativity and plug it into the inflight entertainment screen. So we created a custom channel for them with curated content behind it, which then obviously gave them a branding moment and an opportunity to drive their messaging with more engagement. So that was a very custom moment, but also an opportunity for us to do very targeted work to find the right audience members throughout the journey.Ilyse Liffreing (05:56):We spoke with Mike Petre on this podcast just about a year ago, A week after you guysJames Rothwell (06:02):Launched. That's right.Ilyse Liffreing (06:03):It seems that you're moving fast and obviously moving on to things like custom solutions and everything like that. What else is new in the past 12 monthsJames Rothwell (06:12):Where to start? We've been bringing on a significant amount of partners, not only on the technical side, but also on the content side. So most recently we did a deal with Spotify. We're very excited about that partnership. Again, from a content perspective and an engagement perspective, that gives us a whole new set of ways and deeper engagement from people while they're on the planes. It's also an opportunity for a loyalty aspect of that as well. And we'll talk a little bit about how Mileage Plus comes into our overall offering, but if you sign up for Spotify Premium, there's a Mileage Plus component to that. We are the first airline to offer audio books and video podcasts within our planes. There's a lot going on in the loyalty space. We are working with many partners to be effectively integrated into our loyalty program with that will also be a media component as well. So this marriage of loyalty and media together is been a real, it's been very successful in terms of not only helping to drive awareness of those campaigns and those opportunities for Mileage plus members to convert, but also to drive media value for those individual brands. So Vivid Seats is another recent partner of ours where we are able to give mileage plus members the opportunity to earn miles as they buy tickets to entertainment. But you can imagine a world where for those types of companies, we know where those individuals are going to(07:41):At those destinations. Those companies know how many seats are available at a particular location. Can we match that data and make really customized targeted advertising campaigns to say, okay, we see you're going to Vegas, here are some seats available when you get there. So that opportunity of matching data with our partners from a targeted perspective and then a loyalty perspective is really limitless in terms of what the opportunity is there.Damian Fowler (08:08):Let me just ask you, partnerships like this seem hugely valuable in this space. What else are you seeing?James Rothwell (08:15):One of the partnerships that we're super excited about is a very recent announcement with JetBlue. We will be working with JetBlue in a number of different ways. Again, loyalty will be a component of that where we are able to, a JetBlue customer can use United Miles to fly on JetBlue and vice versa. There will be a component that will extend to airport and gate availability down the road. There's a commerce play part as part of that where JetBlue will be powering commerce for us for ancillary products like hotels, cruises, cars, et cetera. And then where it's very exciting for the Connected Media group is that we will be effectively selling JetBlue audiences under the connected media roof that will sit alongside our United Media and United audiences. So the combination of that obviously is a scaled audience across different geographies where JetBlue is stronger in the northeast where we are not as strong. So very kind of complimentary in terms of the audience. And that obviously from an advertiser perspective is great because that's more scale. It's one less phone call to make in a world where there's 280 different media networks that kind of consolidation or rather that opportunity to create an airline audience at scale. We think there's massive opportunity there, and we're talking to a number of other airlines about that opportunity.Damian Fowler (09:36):And when you talk about at scale, you've got 63 million mileage plus members, so that's aJames Rothwell (09:42):Serious, yeah. And 174 passengers over the year. I think JetBlue is around 40, soDamian Fowler (09:49):74 million. Yeah.James Rothwell (09:50):Yeah, 174 million. And then you add 40 million of JetBlue you're getting up there in terms of hundreds of millions of audience members that we can now get in front of. That's a serious proposition.Ilyse Liffreing (10:00):Yeah, it's a great partnership really in a lot of ways. Almost a surprising one too, because you guys are competitors but are also helping each other out in ways. AndJames Rothwell (10:13):Again, it's a very complimentary partnership. I think they're strong in places where we don't have the same coverage. And so it works from that perspective. At the airline level, I think what's most interesting for me is we think we might be the first commerce media player to bring a, I wouldn't even call 'em competitor. I would call 'em a pier,(10:35):A pier into the garden. And this is not a walled garden. This is an anti-Wall garden straight. We've built this technology stack purpose built for the airline. We've built it so others don't have to. And we think by bringing more individuals and more airlines into this world, and it could extend to travel partners more broadly than just airlines, we think all boats will rise. I should probably say planes will fly, but we think there's value in, again, creating scale, creating efficiency for buyers, and ultimately sort of making the whole thing a little bit more streamlined.Damian Fowler (11:14):Yeah, yeah. We like that idea that especially when we look at advertisers and media buyers, the idea that everyone benefits from partnerships like this, so it's not like we're it locking you out. That idea of opening up, it's the value prop for media buys is huge.James Rothwell (11:35):Yeah, it's very new. So we're still figuring out all of the logistics. It'll start on the back seat screens and offsite, how we merge those and deduplicate those audiences through technology partners like LiveRamp is still being figured out, but we're very excited about the proposition and we'll start selling offsite later in the year. And then moving on to Seatback screens in 2026.Damian Fowler (12:01):Now, you did mention some metrics here, but we're just going to press you a little further on that. One of the virtues of Connected Media networks is that ability to tie back purchases to customers and some of the campaigns or partnerships you've mentioned. How is that working? What kind of visibility do you have?James Rothwell (12:20):So we work with a number of different measurement partners, Kantar di nata. We've just started working with Adelaide, which is an attention based measuring partner. And recent tests on that is looking pretty good. You can imagine we do have people literally strapped in by their seat belts and the screen is right in front of them. So the viewability is pretty strong, the attention is very strong too. So we're able to prove, obviously, that as an extension of television, whether you call that a CTV or digital out-of-home screen, it's a very compelling proposition for a brand, and it's an opportunity for them to tell stories on a pretty dynamic canvas. But yeah, we work with a number of different measurement partners. We continue to expand those partners because we believe that while we can choose ones that we think are good, that's not always going to be everyone's first choice. And so we want to be able to create flexibility and brands and agencies to bring their own partners to the table. And so over time, we'll integrate more and more of those partners so that again, measurability and measurement is enabled for all in the ways that they want.Ilyse Liffreing (13:29):Very cool. You were talking about how connective is offering omnichannel measurement. Are there any surprises that came out of that analysis so far?James Rothwell (13:41):Yeah, I think some of the insights that I've been most intrigued by have been around what I call the traveler mindset, this idea that individuals may act a little differently when they're in the middle of their journey. And a couple of reasons for that hypothesis. I think if you think about maybe you are a business traveler, your company's paying for your flight, your hotel, probably a little bit of your food if not all, while you're gone. I think people think they've got a little extra change in their pocket. Maybe they'll feel a little bit more open to advertising, open to brands being part of that journey and maybe even convinced that they should go out and actually spend some money on that brand. Obviously there's always the opportunity for those people who've got their sunglasses and making that a purchase in the airport, but I think it goes beyond that. What was really intriguing though for me was we did some analysis around business travelers and noticed that business travelers are actually more likely to respond to advertising than leisure travelers, which for me was a little counterintuitive because I thought business travelers might tune that out given how frequent they are. They're more likely to be frequent flyers, right?(14:54):But I think they may be a little bit more attuned to the environment they're in as opposed to maybe a leisure traveler or AER traveler who's going with their family and they're having to look after the kids. They're a little distracted, or maybe they're zoning out because they can't wait to get to the beach or back home, but the business traveler is a little bit more tuned in. And so I think that's why we've seen so much success with B2B brands because of that insight and that response.Ilyse Liffreing (15:24):And to me, it does sound like there's B2B brands are having kind of a moments, and I think this is across all categories, but it sounds like you're seeing that too, that B2B brands are even driven to the plane beer.James Rothwell (15:40):Yeah, I think in general, B2B marketing as digital has matured, B2B marketing looks a lot like B2C marketing. There's not a huge amount of difference. And brands, there are business brands that really invest a significant amount of money in that brand. And you don't have to look too far from across the sports world to see how many brands are investing in high profile sporting events and wanting to reach influencers and business decision makers. I think we have a great audience for that. So I think we are another choice for brands to be able to engage with them.Damian Fowler (16:14):Quick question here. On that note, do you have any brand partnerships with sports teamsJames Rothwell (16:18):At the United level? We do. We work with a number of different teams across the nation, obviously usually associated a lot more aligned with our hubs where we have a lot more exposure. And so yeah, lots of different professional sports teams. And then obviously when it comes to things like NCAA tournaments, we do a lot of fun marketing around that. If your team unexpectedly goes all the way, you're going to have to hop on a plane, well, we can figure we help you out with that, or you can cancel your flight and don't worry about it. We will take care of you if your team crashes out.Damian Fowler (16:55):Moving on here, to zoom out a little bit and look at the landscape, the big picture, as it were from, should we say 30,000 feet? Let's do it. Terrible. I love it. You wouldn't believe how many plane analogy Canal. Get the pun every, I'm sure you can every day. Lemme ask you for your favorite plane analogy at the end ofJames Rothwell (17:10):Something,Damian Fowler (17:11):But you've likened connectives personalization to Netflix's style recommendation engine, but with rich signals as more brands enter the traveler media space, and we don't necessarily have to name them, what do you see as United's distinct advantage?James Rothwell (17:28):I'm going to highlight another partnership here because I think it will illuminate the audience on where this is going. So we announced our partnership with starlink recently, and we are scaling starlink out across the fleet. That will take some time because we have to take those planes out of rotation, install the hardware, but we did a recent test and got hardcore gamers and hardcore streamers, and we were doing shopping and testing it, and they were literally trying to break it and they couldn't break it. And it was absolutely flawless super fast. That is a game changer because now you can do everything on the ground at 30,000 feet. And there's been a lot of questions about, does that mean we're going to have to take Zoom calls on the planes? And the good news is no, I think you can listen, but I don't think you can talk. So that's kind of the rule there. But yeah, we had people FaceTiming with their moms on that flight, but the reason I bring that up is because that is going to effectively create a whole world of hyper-personalization that just wasn't possible before. The technology that again exists at zero feet will be at 30,000 feet. And so you think about what that means from an advertising perspective, every screen becomes addressable. We can do programmatic delivery against thoseSpeaker 4 (18:53):ScreensJames Rothwell (18:54):And we can create shoppable moments, brand integrations. It unlocks a huge amount of content opportunities as well. Now you can stream live sports, you can stream anything you want on the ground in the air. So that's where I think we already have an advantage in that we have an amazing audience, an omnichannel offering and hours of attention. We're going to supercharge that attention with incredible content and amazing brand integration opportunities and advertising opportunities.Damian Fowler (19:25):We have these rapid fire hot seat questions. You're not strapped in or anything, sorry. Terrible. Another airline analogy. This is one we like to ask. What is it that you are obsessed with figuring out right now about the marketplace you're in?James Rothwell (19:40):I'm obsessed with, I think just continuing to find out more about the audience that we get to engage with every day. I have the pleasure of not only being head of marketing for Connected Media, but I also mileage Plus. And so I'm curious every day about how I can understand more about our loyal customers, how we can enrich their experiences with us and enrich their lives more broadly. Because again, it doesn't stop with the journey from others. How do we engage with them in authentic and compelling ways in a very noisy media marketplace, but also try and get them to continue to think about Mileage Plus and the airline on a more regular basis, not just when they have to travel.Ilyse Liffreing (20:29):Yeah. What would you say is missing from the market and needs to be solved?James Rothwell (20:37):What's missing from the market? I don't think it's missing. It just needs to continue to evolve, and that's measurement. I think no one's cracked the code. It feels like every time we get close, the move a little bit, and as more and more first party data driven networks crop up, it becomes more and more relevant for us to solve the attribution game. And I think even when I understood retail media networks to be the answer to all of that because of closed loop attribution, my understanding is that is still not figured out. That's not still solved. And if retailers who operate at that lower end of the funnel and point of sale haven't figured it out, then that's challenging for the industry because we've got a long way to go still.Damian Fowler (21:21):You mentioned you had a favorite. Do you have any favorite airline? Do you have any favorite airline analogies or even jokes?James Rothwell (21:29):I try to avoid the jokes because that's a tricky one. No, I think a lot of what I talked about today, we were excited to announce it. We're still building, so I would say we're still building the plane while we're flying it.Damian Fowler (21:42):That's a good one. Yeah.Ilyse Liffreing (21:42):Yeah, we use that one all the time.Damian Fowler (21:46):In the business, it works very well.Ilyse Liffreing (21:48):Bad worlds, I would say.Damian Fowler (21:54):And that's it for this edition of The Big Impression.Ilyse Liffreing (21:56):This show is produced by Molten Hart. Our theme is by Love and caliber, and our associate producer is Sydney Cairns.James Rothwell (22:03):And remember, we did some analysis around business travelers and noticed that business travelers are actually more likely to respond to advertising than leisure travelers.Damian Fowler (22:15):I'm Damian. And I'm Ilyse. And we'll see you next time.

Anamaria Ungureanu: The Tech Lead Who Nearly Destroyed the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anamaria describes a seven-member software team that initially seemed engaged but began self-destructing when a senior tech lead refused to embrace transparency and knowledge sharing principles.  The situation escalated when this key team member's four-day absence completely blocked the team's ability to deliver, creating a dangerous single point of failure. Through careful retrospective facilitation and strategic motivation techniques, including offering the specialist new learning opportunities while gradually transferring their legacy knowledge to teammates, Anamaria helped the team overcome knowledge silos and establish sustainable collaboration patterns. Featured Book of the Week: Never Split the Difference by Chris Voss Anamaria recommends “Never Split the Difference” by Chris Voss, a negotiation masterpiece because it taught her essential communication strategies for establishing trust and navigating tense situations. She emphasizes that negotiation is a critical Scrum Master skill, and Voss's techniques help build rapport with stakeholders while managing difficult conversations that arise during team transformations and organizational change initiatives. Self-reflection Question: What knowledge silos exist in your teams, and how might you motivate specialists to share their expertise while providing them with new growth opportunities? [The Scrum Master Toolbox Podcast Recommends]

Anamaria Ungureanu: Goal Clarity—The Missing Piece in Agile Team Performance Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anamaria shares her experience working with a platform implementation team that appeared engaged but was actually struggling in silence. Despite initial assumptions that everything was fine, the team's quiet demeanor masked their lack of understanding about project goals and deliverables.  Through strategic intervention including goal clarification with the Product Owner, confidence level assessments, and story mapping sessions, Anamaria helped transform a disengaged team into one capable of successful delivery. Her approach emphasized the importance of fostering constructive conflict, asking open questions during sprint planning about demo expectations, and facilitating better PO-team interactions to create transparency and shared understanding. In this episode, we refer to User Story Mapping and the concept of Gemba, or Gemba Walk Self-reflection Question: How might your teams be silently struggling, and what signs should you watch for to identify when apparent engagement actually masks confusion or disengagement? [The Scrum Master Toolbox Podcast Recommends]

Joelle Tegwen: Business Analyst to Product Owner—More Than a Title Change Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Collaborative Visionary Joelle worked with an exceptional Product Owner at a medical company who was leading their team into a new way of working. This PO understood both the vision piece of the work and the importance of experimentation, recognizing that the team was responsible for figuring out how to solve the problems they were trying to tackle. Working within a Large Scale Scrum framework, they demonstrated patience while collaborating with skilled team members to improve how they worked together. Rather than complaining to the team about performance issues, this PO collaborated directly with the Scrum Master to address challenges. Most importantly, they maintained crystal clear focus on customer value, ensuring every decision and direction connected back to what would truly benefit the end user. The Bad Product Owner: The JIRA Manager Joelle describes the problematic pattern of Business Analysts who receive a title change to Product Owner without understanding the fundamental shift in role and responsibilities. These individuals continue to see themselves as scribes rather than visionaries, treating their primary job as managing JIRA instead of setting a vision for where the product should go. They typically lack understanding of meaningful metrics and rely on gut-feel prioritization rather than data-driven decisions. Most critically, they fail to communicate about problems to solve or establish a clear North Star for the team. Joelle recommends providing these POs with structured formats for Epics and features that start with hypothesis, problem, and measures, helping them think at higher levels than just user story management. Self-reflection Question: Whether you're a Product Owner or work closely with one, how might you help elevate the conversation from task management to vision and problem-solving? [The Scrum Master Toolbox Podcast Recommends]