Podcasts about product managers

We explore what may be the fastest-moving technological shift dentistry has faced in decades and why most practice owners are still underestimating how quickly the ground is moving beneath them. While many dentists are using ChatGPT to write emails, draft social posts, or answer quick questions, the conversation argues that's barely one percent of what's now possible. The discussion digs into the rise of agentic AI, autonomous systems that take action rather than simply generate responses. Blake and Shane break down how AI is moving past the chatbot stage and becoming a true operational partner, capable of running workflows, automations, data analysis, content creation, and the endless repetitive tasks that quietly eat hours inside a dental practice. They also tackle the practical side most people skip, like knowing which model to reach for, why connections and context matter more than clever prompting, and how to avoid drowning in half-baked projects. But they issue a clear warning. AI is not a shortcut around leadership, systems, or operational excellence. Dentists who lack clear workflows, documented SOPs, and defined outcomes will simply automate chaos. The practices that win won't be the most technically advanced. They'll be the ones with the cleanest systems, the strongest foundations, and the willingness to learn alongside a community of peers. Peter, Blake, and Shane also get honest about the loneliness many dentists carry as practice owners, the value of AI as a non-judgmental thinking partner, and why community matters more than ever during periods of rapid change. They share real examples of AI already saving hours every week, helping teams execute faster, and creating leverage that simply wasn't possible a few years ago. If you've been experimenting with AI but still feel like you're using a fraction of its potential, this one is for you. This episode leads into the first-of-its-kind AI workshop on Sunday, August 9th at The Phoenician, held on the heels of the Bulletproof Summit. DESCRIPTION The Bulletproof Dental Podcast Episode: 444 HOST: Dr. Peter Boulden GUESTS: Blake McClellan and Shane McElroy (All In Practice Growth) In this episode, Dr. Peter Boulden sits down with Blake and Shane to discuss the future of AI in dentistry and why the next wave of innovation is about far more than chatbots and content creation. They explore agentic AI, workflow automation, SOP development, practice efficiencies, and the role community plays in helping dentists stay ahead of rapid technological change. The conversation provides practical examples of how AI can create leverage inside a dental practice while highlighting the common mistakes many practice owners make when implementing new technology. Whether you're just getting started with AI or already experimenting with advanced tools, this episode offers a practical roadmap for understanding where the technology is headed and how to position your practice for the future. TAKEAWAYS AI is evolving far faster than most dentists realize Community accelerates learning and implementation Agentic AI goes beyond chatbots by taking action, not just generating responses SOPs and workflows are the foundation of successful AI adoption AI cannot replace clarity, leadership, or operational discipline The best use cases often involve saving time on repetitive tasks AI can help practices create leverage without sacrificing quality Dentists should focus on outcomes rather than chasing every new tool Workflow mapping makes automation significantly more effective AI can become a powerful thinking partner for practice owners The future belongs to practices that combine human connection with technological efficiency Small improvements compounded over time can create significant competitive advantages TIME STAMPS 00:00 Introduction & Why AI Matters Right Now 02:10 The Origin of the Dental AI Summit 03:31 Why Community Is the Key to AI Adoption 04:45 Partnering with Bulletproof to Bring AI to Dentistry 06:00 AI Is Evolving Hour by Hour 07:49 The Difference Between AI Curiosity and AI Implementation 08:45 From AI Novelties to Real Practice Applications 11:04 Creating Leverage Inside Your Practice 13:10 Why Most Dentists Don't Know Where to Start 14:13 Days in AI Equal Months Ahead 17:42 The Biggest Opportunity for Dental Practices 20:06 Real-World AI Use Cases in Dentistry 22:08 Chatbots vs. AI Agents 24:35 How to Choose the Right AI Tools 26:24 Common Mistakes Dentists Make With AI 30:15 Context, Data, and Better AI Results 34:52 Innovative AI Applications You Can Use Today 45:15 Why SOPs Matter More Than Prompts 47:18 Mapping Workflows Before Automation 50:27 Using AI as a Product Manager 51:26 The Lone Wolf Syndrome in Dentistry 53:25 AI as a Coach, Mentor, and Thinking Partner 56:44 Practical Steps for Embracing AI 01:00:42 The Future of AI in Dentistry 01:02:08 Preparing for the Dental AI Summit 01:05:00 Final Thoughts & Event Details   REFERENCES Dental AI Summit Claude AI Grok AI OpenClaw AI Bulletproof Practice Growth Summit

Why does Product Marketing look so different in Europe, and why copying US playbooks often leads to the wrong outcomes?In this episode, I sit down with Rory, Product Marketing Director consultant, with 13+ years of experience in PMM, across top tech companies such as Google, YouTube and Pleo. Europe Isn't Silicon Valley: Together, we unpack what truly shapes Product Marketing in Europe today, and why this context is driving the rise of fractional PMM roles.In this conversation, you'll learn:

Our HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Recorded live at our SAP Customer Council in Berlin, this episode features Fernanda Rodrigues in conversation with Frank Harder, Product Manager for SAP Cloud ERP at Testo. Testo is a family-owned leader in high‑tech measurement devices from Germany's Black Forest, serving industries such as pharma, food, biotech, analytics, and more, with connected products and strong cloud‑based data analysis. Frank explains how the company is transitioning from legacy ERP to SAP Cloud ERP, starting with sales organizations worldwide and now operating in nine countries. This is the fifth episode in our Customer Council Berlin Series. Follow and subscribe on Spotify or Apple Podcasts so you never miss an update. On Spotify, join the conversation using the episode's Q&A and Poll; on Apple Podcasts, a quick rating or review helps others discover the show. Have a question, topic suggestion, or want to connect with the team? Write to us at insides4@sap.com — we read every message.

Começar na área de Produto é empolgante, mas também desafiador. No episódio de hoje, Rubia e Su compartilham 10 dicas valiosas que elas gostariam de ter recebido no primeiro ano como Product Managers.  Descubra como entender o contexto antes de entregar, a importância das pessoas antes das features, como aprender seu produto como uma usuária, e por que a execução consistente é sua principal moeda no início da carreira. Além disso, reflita sobre como construir a PM que você quer ser.  Destaques do episódio:  Como criar um plano de 30-60-90 dias alinhado com seu gestor.  A importância de investir tempo conhecendo seu time e stakeholders.  Benchmark como ferramenta de onboarding.  A relevância de uma entrega E2E para demonstrar autonomia.  Expor-se além da zona de conforto para crescer como profissional.  Se você está começando na área de Produto ou conhece alguém que está, este episódio é para você! 

In this episode, Dave and Jamison answer these questions: My company follows scrum, with daily standups. We got a new scrum master. He is very formal and procedural and I struggle with our daily meetings. He goes through a long list of assigned tickets, asking each ticket owner about status and info on progress. We are all engineers with many years of experience but it feels like we are in the kindergarten. We don't have deep expertise about each others work. It is important to know what each of us is doing more or less, but going deep in these issues makes me disconnect, and I think these meetings are above all very good to signal blocking points and ask for help. A recitation of tickets and work being done is not their purpose. On top of that, most days it takes 25-30 mins to go through all the issues. Am I being difficult complaining about this? I tried to be polite when I raised the issue but I was told more or less that this way is better for the company. Is it common in the industry to go through dailys like this? Thanks a lot, guys, you do great work and I look forward to the SW/industry podcast that makes me laugh the most! Hi! Long-time listener here, I remember Jamison mentioning this podcast on JS Jabber and I've been listening ever since. Best part of my week! In my current organisation I have a tech lead role on a small, internal platform team. Our “customers” are mainly other engineers. Due to several re-orgs, I have over the years worked with a number of Product Managers and Engineering Managers who have all had one thing in common: they don't understand the technical domain we work in very well. You could say we have “Product Managers” who do not understand the “Product”. At the same time, these people are expected to interact with stakeholders, set the platform vision, manage the roadmap and backlog, prioritise risks, write documentation, do demos, etc. In the end, a lot of this work falls through to me. I do the work, but have also received negative feedback from my skip level that I need to do a better job keeping the product manager and engineering manager in the loop. I just got a new EM and am heading into our first expectations setting meeting. How can best express that my expectation is that the roadmap for a technical platform team should be managed by someone technical? Do you think product managers have a role on internal platform teams?

As product management becomes increasingly data-driven and AI-powered, one human capability is growing in importance: emotional intelligence. In this episode, you'll discover why emotional intelligence is a critical complement to data, analytics, and AI, how it helps product managers and product leaders create better products and build stronger relationships, and why it may have a greater impact on product success than intellectual ability alone. You'll also learn practical techniques for strengthening your emotional intelligence—from increasing self-awareness and self-management to developing empathy, active listening, and conflict-resolution skills.

What does it really take to move from survival mode into a life of confidence, purpose, and personal ownership? In this episode of Daily Influence, Gregg-Brooke Koleno sits down with Arti Agarwal, full-time Product Manager at Accenture and founder of Empowering Minds, Transforming Souls. Arti shares her deeply personal journey from growing up in a traditional Indian middle-class family and losing her father at 17, to becoming a mindset coach helping others overcome scarcity thinking, self-doubt, and victim mentality. Together, they explore how mindset shapes our reality, why many people unknowingly operate from “victim energy,” and practical ways to reclaim ownership of your life. Arti also shares simple but powerful habits—including gratitude, self-talk, discipline, and acceptance—that can help anyone shift toward a more abundant and empowered mindset. If you've ever felt stuck, overwhelmed, or trapped in survival mode, this conversation offers relatable wisdom and actionable insights to help you take your next step forward. In This Episode: • How childhood experiences and financial pressure can create scarcity thinking • Signs you may be operating in “victim energy” without realizing it • Why taking responsibility for your emotions changes everything • The role of gratitude, discipline, and positive self-talk in personal growth • How acceptance becomes the first step toward transformation • Why becoming your own cheerleader matters more than outside validation Memorable Takeaway: “Unless and until we are able to accept totally what is happening with us, we cannot truly change it.” – Arti Agarwal Tune in for a meaningful conversation about mindset, resilience, emotional responsibility, and creating a life aligned with who you truly are. Connect with Arti: artiashokagarwal10@gmail.com https://www.linkedin.com/in/artiagarwalba/

// Le 2 juillet prochain à Paris, rejoignez Diffly, Lucca, Tomorro, Crossbeam, Partoo, Advizeo, Skillup et 100+ leaders Sales, Marketing & Product pour une après-midi dédiée aux nouvelles dynamiques de décision B2B, à l'impact de l'IA dans les équipes Revenue et aux insights qui font vraiment la différence sur vos deals. Réservez votre place ICIC'est 100% gratuit (mais place limitées !) //Recruter un PMM, est souvent perçu comme un “nice to have”. Mais à quel moment cela devient une nécessité pour structurer sa stratégie marketing et accélérer la croissance ?Olivia Jorel, CMO chez Trainme, partage les coulisses de la structuration de son équipe marketing et les raisons qui l'ont poussée à créer un premier poste de PMM.Elle revient sur un contexte initial avec un marketing peu structuré et très cloisonné avec les sales, jusqu'à la mise en place d'une organisation plus alignée et orientée performance. Dans cet échange, Olivia nous explique :

Dave Martin has spent more than two decades in product leadership, with a string of C-suite roles, a couple of exits and a book, The Product Momentum Gap, to his name. He is also dyslexic and ADHD, and has built a career while masking the effort it takes to "think normal". In this episode he makes the case that the advice handed to neurotypical leaders often fails the roughly half of tech workers who are neurodivergent, and lays out a practical playbook for landing your message, leading the room and progressing without pretending to be someone else. Chapters00:00) Welcome, and Dave's background in product(02:03) "I've been masking it": faking thinking normal(02:37) The meeting where your idea is ignored, then credited to someone else(03:28) AI as a "spell check for influence"(04:07) The myth that growth requires pretending to be neurotypical(05:15) Why standard leadership advice fails neurodivergent leaders(06:45) Executive presence, signal presence and signal drift(07:57) Is this universal, or specific to neurodivergence?(09:48) From "dumb kid" to writing C++ at ten(11:27) When a word processor flipped his Fs to As(13:24) The trap: leading with detail(15:42) The boardroom moment that gets you labelled "not strategic"(17:05) Designing for re-tell: what the room repeats when you leave(18:19) Three mistakes that kill your influence(19:36) The CALM framework(21:32) Authority and the signal prep exercise(22:14) Three questions: outcome, one-line recommendation, re-tell(24:44) "Minutes not months": seeding the line that gets repeated(26:56) Learning: vulnerability and psychological safety(28:27) Momentum, well-being and burnout(31:21) Why burnout is a leadership fault(32:01) Mia's story: the head of product who wanted to be CPO(34:20) Recognising the trigger and practising signal prep(37:06) When stakeholders started calling her strategic(38:31) The opposite trap: abandoning detail entirely(39:22) Why some leaders step back into IC roles(41:16) Free training and AI as your spell checker for influence(42:26) Closing thoughtsKey takeaways— Authenticity is not the goal; deliberate communication is. Dave's central provocation is that "be your authentic self" assumes everyone in the room thinks the way you do. For a leader who sees patterns instantly and works in deep, hyperfocused bursts, behaving authentically can mean failing to explain the obvious and struggling to empathise with those who need the journey, not just the destination.— The symptoms are universal, the tax is not. Everybody's message gets lost in meetings. What separates neurodivergent leaders is the cognitive cost of noticing that drift and correcting it. As Randy and Dave agree, the tools discussed here help everyone, but the impact is far larger for those paying the higher tax.— Leading with detail is the career trap. The very trait that makes someone an exceptional individual contributor, the ability to go deep and surface every edge case, can sink them in the boardroom. — Answer a strategic question with edge cases and you are labelled "not executive" with alarming speed, and undoing that label takes months of work.— CALM is the alternative. Clarity, authority, learning and momentum, delivered calmly. Authority comes from being clear on the outcome and the ask, asking for support and guidance rather than permission, and not feeling obliged to justify every edge case.— Signal prep is the practical tool. Three questions: what do I need from this room; what is my one-line recommendation; and what will they repeat when I am not in the room. A bonus question for higher-stakes meetings asks what the room feels now and how you want them to feel when you leave.— Design for re-tell. Dave's example of a leader who reduced a lengthy objective to "minutes not months for our customers", and repeated it, is the clearest illustration. That phrase, not someone else's reframe, is what got repeated in the room afterwards.— Well-being underpins momentum. Dave nearly named the framework around well-being. Without a sustainable pace, leaders cannot lead, and the unprocessed meeting that keeps you awake at 3am is a momentum problem. He frames widespread tech burnout as a leadership failure, because leaders set the expectation.— AI is a spell checker for influence. Just as a word processor turned Dave's Fs into As without changing his brain, AI tooling can help neurodivergent leaders translate their thinking into the right language for the room, supporting the communication without doing the thinking or the judgement for them.Our HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Entrevista de Leandro Gabin a Isabel Botta, product manager en Balanz, sobre el balance que deja el cierre del mes y opciones para invertir el medio aguinaldo.

What if the role that has defined a generation of tech careers disappears within five years? In this inaugural episode of the fifth year of the CPO Rising Series, Products That Count Founder & Managing Partner SC Moatti and Resident CPO Renee Niemi make their boldest prediction yet: the product manager as we know it will be replaced by the product builder by 2030. Drawing on conversations with over 1,500 CPOs this year alone, Renee unpacks what is driving the shift, what separates good CPOs from great ones from the best, and why for companies that do not get ahead of this transition, the risk is not just competitive. It is existential.

It's been about 2 years and 3 mo since I was infamously laid off from my dream product manager job at Discord. And today, I finally sit with my old manager to talk about life after layoffs. Derek Yang is now a Principal Product Manager at Roblox, and before that he was at YouTube, Twitch, Yik Yak, Facebook, and Discord where he was also my last ever corporate manager. In this ep, we talk about: → What it actually means to "make it" in tech (spoiler: he still doesn't think he has)→ the performance review that humbled him and forever changed → how he approaches his career→ why working hard is not enough and what actually gets you recognized→ what he gave up becoming a new dad→ and why sustainability is his whole era right nowThis episode is for anyone who has ever put their whole heart into their work and still felt like it wasn't enough. Derek is one of the most thoughtful people I know and I learned something new about him even after years of friendship.→ Find Derek on LinkedIn:https://www.linkedin.com/in/dereklyangSubmit your Coworker Confessions

Have you ever stopped to think about the technology powering almost every text box you interact with online? Whether you're applying for a job, drafting a legal contract, publishing content, or updating a website, there's a good chance a rich text editor is quietly working behind the scenes. In this episode of Tech Talks Daily, I caught up with Fredrik Danielsson, Product Manager at TinyMCE, to discuss how one of the internet's most widely used editing platforms is evolving for the AI era. Frédéric shares the remarkable story behind TinyMCE, a tool that traces its roots back to the early days of the web and has played a role in creating much of the internet's human-generated content. From the days of hand-coded websites and Flash applications to today's AI-powered content workflows, we explore how the company has continually adapted to changing developer and user needs. Our conversation focuses on the launch of TinyMCE AI and why the company believes artificial intelligence belongs inside the content creation experience rather than in a separate chatbot window. We discuss the hidden productivity costs of constantly switching between applications, copying and pasting content between AI assistants and business tools, and why bringing AI directly into the editor creates a more natural and efficient workflow. We also examine the growing challenges around AI governance, content ownership, compliance, and accountability. As organizations race to adopt AI tools, how can they maintain visibility into which content was AI-assisted, who made changes, and how information flows through the business? Frédéric explains why features such as revision history, track changes, and audit trails may become increasingly important as regulations and expectations mature. Along the way, we discuss context-aware AI, model flexibility, developer experience, and the future of content creation. Frédéric also shares his thoughts on why AI adoption is becoming more natural for everyday users and what the next phase of AI-powered productivity could look like as these tools become deeply embedded in the software people already use. If AI is changing how we create, edit, review, and collaborate on content, what happens when the editor itself becomes the smartest participant in the room? And how will that reshape the way we work over the next few years?

Njegos Ilic: The "Painting by Numbers" Scrum Master vs. The Quiet Leader Who Made the Team Self-Sufficient In this episode, we refer to the concepts of Scrum Master as facilitator and team empowerment. The Bad Scrum Master: The "Painting by Numbers" Approach That Leaves Product Owners Working Alone 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.   "You basically feel totally alone because you are trying to deliver value as a team, but if nobody asks anything and nobody challenges anything, you end up defining everything yourself." - Njegos Ilic   Njegos describes the worst Scrum Master anti-pattern he's witnessed: the "painting by numbers" Scrum Master who runs every ceremony by the book — dailies, refinements, plannings, retros, reviews — but without understanding the purpose behind any of them. The meetings become a reporting cycle: "What did you do yesterday?" with no interaction, no challenging, no real engagement. From the product owner's perspective, this is devastating. Njegos describes feeling completely alone — trying to deliver value as a team while nobody engages, nobody asks questions, nobody pushes back on assumptions. The downstream effect is predictable: gaps that could have been caught early with a single conversation only surface during development or after deployment. Worse, the lack of engagement creates doubt and overthinking — the product owner starts over-defining requirements because there's no feedback loop, which reinforces the very passivity that caused the problem.   Self-reflection Question: Are the ceremonies on your team creating genuine engagement and learning — or have they become a reporting cycle that nobody actually needs? The Great Scrum Master: The Quiet, Impactful Leader Who Made the Team Self-Sufficient 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 best Scrum Masters I worked with were invisible — they knew always when to speak, they sensed the pulse of the team, and they weren't afraid to jump in when needed." - Njegos Ilic   The best Scrum Masters Njegos has worked with share a common trait: they were almost invisible. They didn't dominate meetings or insert themselves where they weren't needed. But they were always present — sensing the team's pulse, knowing when to step in, unafraid to say "we're out of time, let's take this offline." They were knowledgeable about the product, which earned them genuine respect from developers. And perhaps most powerfully, they delegated facilitation itself. Njegos shares an example where a Scrum Master introduced a round-robin system: when new developers joined the team, everyone took turns facilitating meetings — planning, retros, dailies. This wasn't just delegation for efficiency; it was empowerment by design. Team members who facilitated a retrospective suddenly understood how hard it is to lead one. That empathy changed how they participated when someone else was facilitating. The Scrum Master remained the guide, but the team grew its own capacity to self-organize.   Self-reflection Question: If your Scrum Master disappeared tomorrow, would your team know how to facilitate its own ceremonies — and if not, what does that say about how the role is being used?   [The Scrum Master Toolbox Podcast Recommends]

Njegos Ilic: Why Measuring Your Product Bets Is the Key to Product Owner Success 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.   "If you cannot measure what you build, you will just be depending on who is screaming the loudest and using your gut feeling — which is not a good thing long term." - Njegos Ilic   Njegos defines product owner success through three pillars: the ability to measure product bets, deep knowledge of the industry and product, and the humility to admit mistakes and be challenged. The measurement piece is central — without it, he argues, you're flying blind, making decisions based on opinions rather than evidence, reacting to whoever screams loudest rather than what the data shows. But Njegos is honest that not every environment makes measurement easy. Some companies lack the tooling, the culture, or the historical infrastructure to set up proper analytics. In those situations, he turns to user interviews as the next best thing — getting direct feedback from users, even though he acknowledges that opinions are still limited without data to fact-check them against. His most powerful suggestion: invite the whole team to user interviews, not just the product trio. When developers hear directly from users, they connect to real-world problems, and conversations during refinements become richer and more grounded.   In this episode, we refer to The Mom Test by Rob Fitzpatrick and Shift: From Product to People by Michael Dougherty and Pete Oliver-Kruger.   Self-reflection Question: How do you currently measure whether the features you shipped actually delivered the value you expected — and if you can't measure it, what's your fallback? Featured Retrospective Format for the Week: Start With a Relaxing Exercise Njegos doesn't advocate for a specific retrospective template — and that's the point. From his product owner perspective, he values retrospectives that begin with a relaxing, informal exercise to set the tone. Not everything needs to feel like business as usual. This casual opening allows people to connect as humans first, which opens them up to think differently about what they learned during the sprint. Njegos is candid about the reality: some teams love icebreakers, while others find them childish and just want to get to the point. His advice is to sense the pulse of the team and adapt. The format matters less than whether it creates an environment where people can be honest about what went well, what didn't, and what to improve. A Scrum Master who reads the team's vibe and adjusts accordingly — that's what makes the difference.   [The Scrum Master Toolbox Podcast Recommends]

// Le 2 juillet prochain à Paris, rejoignez Diffly, Lucca, Tomorro, Crossbeam, Partoo, Advizeo, Skillup et 100+ leaders Sales, Marketing & Product pour une après-midi dédiée aux nouvelles dynamiques de décision B2B, à l'impact de l'IA dans les équipes Revenue et aux insights qui font vraiment la différence sur vos deals. Réservez votre place ICIC'est 100% gratuit (mais place limitées !) //Le PMM doit-il être rattaché au Marketing ? Et surtout : comment mesurer concrètement son impact business ?Olivia partage le retour d'expérience très concret de TrainMe sur le recrutement d'une PMM : clarification des responsabilités avec les équipes Marketing, collaboration avec les Sales, évolution du messaging… mais aussi la fameuse question de la mesure de l'impact du PMM.Olivia nous explique comment son équipe a structuré cette collaboration au fil des mois, les ajustements nécessaires et les résultats observés côté business.

In this episode of The Pet Food Science Podcast Show, Ashwath Bendre, Product Manager at Umami Bioworks, and Vincent Krudde, Head of Alternative Protein Program at Nutreco, discuss cultivated protein and its role in pet nutrition. They explain how cell-based seafood is produced, customized for nutrient profiles, and positioned to improve sustainability, protein diversity, and supply security. Discover how this emerging technology could shape the future of pet food. Listen now on all major platforms!“Cultivated protein is the same real animal protein at a molecular level, produced through a different technology that allows controlled and efficient cell growth.” - Ashwath BendreMeet the guests: Ashwath Bendre is a Product Manager at Umami Bioworks, a Singapore-based marine biotechnology company developing cultivated seafood. He holds an MBA from Nanyang Technological University and a Master of Science in Food Science from The University of British Columbia, with experience in quality assurance and supply chain operations.Vincent Krudde is Head of the Alternative Protein Program at Nutreco, a global animal nutrition company. He holds an MBA from INSEAD and a degree in Applied Physics from Delft University of Technology, with experience in strategy consulting and global business leadership focused on sustainable protein innovation.Liked this one? Don't stop now — Here's what we think you'll love!Don't miss the chance to be part of the Pet Food Inner Circle!Join now and connect with leading experts in pet nutrition: https://petfoodinnercircle.com/What will you learn:(00:00) Highlight(01:23) Introduction(04:15) Cell cultivation process(10:04) Nutrient customization(14:22) Feed efficiency comparison(18:35) Sustainability potential(21:23) Scaling challenges(25:23) Final QuestionsThe Pet Food Science Podcast Show is trusted and supported by innovative companies like:* Trouw Nutrition* Kemin- DietForge- Biorigin- Rangen Group

Njegos Ilic: How a Miro Board Experiment Changed the Way His Team Understood the Big Picture 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.   "Every feature is a product bet. I would call this a process bet — just try to see what works best for you." - Njegos Ilic   Njegos shares a change story from his time working with a tech lead who had previously been a Scrum Master — a partnership that made all the difference. Together, they introduced a simple but powerful change: visualizing the team's work on a Miro board instead of relying on a standard ticket board with cards and status columns. They mapped out concepts, connected ticket numbers to a visual representation of how different pieces of work fit together, and used this board during dailies and refinements to track progress in context. The change wasn't imposed top-down — Njegos and his tech lead simply said, "Give us one sprint to try this. If it doesn't work, we drop it." The result was immediate: dailies became more engaging, the team could see how their individual work connected to the bigger picture, and Njegos found it much easier to track progress as a visual thinker. His advice for Scrum Masters and product owners who want to introduce something similar is refreshingly simple — frame it as a "process bet," just like you'd frame a product bet. Try it, measure what happens, and if it doesn't work, drop it and try something else. The willingness to experiment with your own process is a prerequisite for experimenting with the product itself.   Self-reflection Question: What "process bet" has your team been avoiding — and what would it take to just try it for one sprint?   [The Scrum Master Toolbox Podcast Recommends]

Barry O'Reilly is an entrepreneur, author, and founder of Nobody Studios, an early-stage venture studio focused on building AI companies. Over the last six years he has worked with founders, executives and enterprise leadership teams to rethink how organisations operate in the age of generative AI, while simultaneously building and launching companies inside the studio model.A former startup advisor and executive coach, Barry has spent the last several years studying why most AI transformations fail despite enormous investment. Through his coaching and advisory work with leaders from companies including American Airlines, Skyscanner, and Slack, Barry has developed practical frameworks for improving decision-making, reducing administrative overhead, and increasing what he calls "decision velocity".In this episode, Barry explains why AI adoption fails when companies focus on tools instead of behaviour change, why judgment is becoming the most important human skill, and how teams can use AI to improve collaboration rather than replace people.Key takeaways — Most AI transformations fail because organisations start with tools instead of behaviours. Installing AI software does not change how people work, make decisions or collaborate. — The most effective AI use cases amplify a person's natural way of working. Barry realised he produced better writing by talking through ideas and using transcription tools instead of forcing himself into traditional writing workflows. — Capturing meetings, conversations and decisions as structured data creates long-term organisational intelligence. Every interaction becomes a reusable asset that improves preparation, follow-through, and future decision-making. — Leaders must role-model AI adoption themselves. Organisations see better outcomes when executives openly experiment with tools, share lessons learned, and create psychological safety around adoption. — Decision velocity matters more than raw productivity. Teams improve when they arrive prepared, make decisions faster, reduce reversals, and spend more time solving meaningful problems instead of handling administration. — AI should be used to challenge thinking, not replace it. The most valuable prompts ask for blind spots, alternative scenarios, and pressure tests rather than definitive answers. — Teams working with AI outperform individuals working with AI. Barry cites research showing that collaborative ideation with AI produces significantly stronger outcomes than isolated use. — Productivity gains are meaningless if they simply create more exhaustion. The real opportunity is creating space for reflection, slow thinking, and better judgment. — Judgment is the critical human capability organisations cannot outsource. If people stop exercising judgment and rely entirely on AI-generated answers, they gradually erode their ability to make decisions under uncertainty.Chapters 1:03 — Building AI companies at Nobody Studios 3:16 — Why AI transformations fail 5:05 — The danger of focusing on tools 6:35 — Discovering natural workflows with AI 8:51 — Turning conversations into data assets 12:02 — Measuring successful AI adoption 13:14 — Why leaders must role-model behaviour change 18:39 — Decision velocity as a leadership metric 21:33 — Escaping administrative overload 23:02 — Why leaders need time to think 26:54 — What CFOs are worried about 28:08 — Can AI replace startup teams? 29:45 — Why distribution still matters most 33:13 — Capturing and synthesising ideas with AI 34:38 — Using AI to challenge your thinking 37:11 — Avoiding top-down AI-driven strategy 39:00 — Why teams plus AI outperform individuals 42:31 — The problem with AI-generated certainty 43:12 — Preserving human judgment 44:55 — Hiring for judgment and decision-making 47:19 — Final reflections on leadership and AIOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Njegos Ilic: Why the Product Trio Breaks the Hand-Off Mentality That Kills Team Engagement 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.   "I can't change people, but I can definitely involve them." - Njegos Ilic   Njegos describes a pattern he's encountered multiple times as a product owner: teams where engagement is almost nonexistent. He walks into a refinement session, presents ideas, asks for feedback — and gets crickets. Nobody pushes back, nobody asks questions, nobody challenges the assumptions. The result is a product owner working in isolation, defining everything alone, only to discover gaps during development that could have been caught early with a single conversation. Njegos is honest about the limits of what any one person can do — you can't change people's personalities, and expecting a Scrum Master to do so is unrealistic. But what you can do is involve people. His approach when joining a new team: don't come in announcing how things will work. Instead, learn how the team already works, meet them where they are, and then find ways to fit new concepts into their existing rhythm. For the non-negotiable things — the red lines — he's precise, open, and always provides an alternative rather than just pushing his way.   In this segment, we talk about Discovery and Delivery and the Product Trio concept.   Self-reflection Question: When you join a team meeting and get silence instead of feedback, do you assume agreement — or do you treat it as a signal that something deeper needs to change? Featured Book of the Week: Inspired by Marty Cagan Njegos recommends Inspired by Marty Cagan as the book that most shaped his approach to product ownership. He highlights the entire SVPG series — including Empowered and Transformed (available as the Product is Hard SVPG Box Set) — but points to the Product Trio concept as especially powerful. As Njegos puts it, the Product Trio — bringing together a product manager, a tech lead, and a designer — removes the hand-off mentality where each discipline works in isolation. Instead of the product owner defining everything alone and handing it to the team, the trio shapes problems together during discovery, so that by the time work reaches the team, there's shared understanding of why they're building something, not just what to build.   [The Scrum Master Toolbox Podcast Recommends]

Daniel Wyrzykowski is a Product Manager at Mend.io. In this episode, he joins host Paul John Spaulding to discuss the AI-generated dependency problem plaguing the industry right now, including slopsquatting, information ecosystems as supply chain risk, and more. Securing The Build is brought to you by Mend.io, the leading application security solution, helping organizations reduce application risk efficiently. To learn more about our sponsor, visit https://mend.io.

Njegos Ilic: Why Saying Yes to Every Stakeholder Request Is the Fastest Way to Fail as a Product Owner 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 game is rigged because they are strong personalities, they want to get things done, but you don't have a magic stick — it's really hard to deliver results if you cannot say no." - Njegos Ilic   Njegos shares a failure from early in his career as a product owner in startup environments, where he found himself saying yes to every stakeholder request. Working with strong-willed founders who expected things done their way, Njegos fell into the trap of trying to please everyone — building everything that was asked without pushing back. The result was predictable: scattered priorities, no room to pivot, and a product backlog driven by the loudest voice in the room rather than real user needs. But Njegos frames this failure with a perspective that product owners at any stage can learn from. He compares the learning process to watching children learn to walk — stumbling and falling is not a sign of weakness, it's a necessary step in the process of growing. His advice to product owners currently stuck in this pattern: don't try to avoid failures too hard, because you might prevent yourself from learning the most important lessons. Instead, treat failure as a feedback loop — something happened, you can measure it, and you can change your approach. The key is doing the actual work of reflection: What did I do? What should have been different? What wasn't possible to change, and why?   Self-reflection Question: When was the last time you said yes to a stakeholder request even though your gut told you it wasn't the right call — and what would it take for you to say no next time?   [The Scrum Master Toolbox Podcast Recommends]

En este programa te hablo de las novedades de La Sportiva para 2027. Serán 3 modelos que verán la luz en marzo de 2027.Te explico lo más relevante de estos 3 modelos, tras mi conversación con Tobías G., Product Manager de La Sportiva.(5:53) Prodigio PRO 2(9:00) Talento(13:36) Talento PROContacto:juan@ellaboratoriodejuan.com

Gwendoly Espe, Product Manager at Yaskawa Solectria Solar, discusses the technical and commercial advantages of DC-coupled solar-plus-storage systems at utility scale. The conversation covers DC versus AC coupling architecture, energy harvest optimization through clipping recovery, and Yaskawa's American-manufactured PVS 500 inverter solution. Additional topics include NABCEP-accredited training programs, FEOC compliance, and the growing role of solar storage in powering data centers and supporting grid stability.   Topics Covered Yaskawa Solectria Solar www.solectria.com Inverter Converter DC Coupling AC Coupling Energy Yield DC = Direct Current AC = Alternating Current Utility Scale Solar Utility Grid Microgrid Ercot DER = Distributed Energy Resources AI = Artificial Intelligence ESS = Energy Storage System Data Center Recharge with Solectria FEOC = A Foreign Entity of Concern   Reach out to Gwendoly Espe here: LinkedIn: www.linkedin.com/in/gwendolyespe Website: www.solectria.com   Learn more at www.solarSEAN.com and be sure to get NABCEP certified by taking Sean's classes at www.heatspring.com/sean www.solarsean.com/esipexam

Podcast: ICS Cyber Talks PodcastEpisode: Liron Ner VP Engineering & Oren Valdman ResiliOTech product manager @DVplan on Cyber Risk AssessmentPub date: 2026-05-19Get Podcast Transcript →powered by Listen411 - fast audio-to-text and summarizationהשגרה המקובלת בעולמות אבטחת המידע מבוססת על מחזוריות מתמדת: ביצוע סקר סיכוני סייבר, גיבוש תוכנית פעולה, תיקון פערים ומבדקי חדירות – תהליך החוזר חלילה מדי 12 עד 18 חודשים. למרות ההתקדמות הטכנולוגית בתחום הגנת הסייבר, סקר סיכוני הסייבר נותר אחד התהליכים הבודדים שכמעט ולא השתנו. הוא עדיין נשען במידה רבה על הידע האישי של הסוקר, מומחיותו והמתודולוגיה הנבחרת על ידו. בעתיד הקרוב מגמה זו עשויה להשתנות, עם כניסתם לשימוש של מודלי שפה גדולים במוצר כמו רזיליוטק לעיבוד תשובות משאלונים והצלבתן מול מתקפות סייבר בפועל, סקרי סיכונים אחרים ותקני התעשייה המקובלים. נחשון פינקו מארח את לירון נר, סמנכ"ל הנדסה וטכנולוגיה, ואת אורן ולדמן, מנהל מוצר רזילויוטק בחברת די.וי פלאן בדיון על אופטימיזציה של סקרי סיכוני סייבר במטרה להשיג תוצאות טובות יותר, תוכניות עבודה יישומיות ותיקון פערים אפקטיבי.  The podcast and artwork embedded on this page are from Nachshon Pincu, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

In this episode of Reboot IT, host Dave Coriale sits down with Vinnu Deshetty, Product Manager at the American Chemical Society, Event ROI Coach, and longtime PCMA instructor, to discuss the evolving role of technology in events. They explore how AI is reshaping planning and analytics, how associations can better serve exhibitors and attendees, and why intentional innovation matters more than ever. Vinnu shares practical insights on avoiding “shiny tech syndrome,” aligning tech with business goals, and using data to drive meaningful outcomes. The conversation highlights the importance of purpose-driven decisions in delivering real value from events. Themes and Topics: The Current State of Event Technology Events are operating “between four and five” in tech adoption, reflecting strong progress with room for improvement. Associations are balancing traditional goals like attendance with new expectations for engagement and personalization. AI is accelerating innovation while increasing complexity in tool selection. Purpose-Built Event Tech (Not One-Size-Fits-All) Technology is now tailored to planners, attendees, and exhibitors instead of being one broad solution. Vendors are solving specific pain points like workflows, engagement, and lead generation. Comparing solutions is more complex because platforms are no longer “apples to apples.” AI's Growing Impact on Event Operations AI is reducing manual work, like building session schedules.  Systems can learn from past data such as session ratings and attendance trends.  Predictive analytics and real-time insights are becoming more common in decision-making.  Data Strategy: Start with Intent Organizations often collect too much data without a clear purpose. Defining the questions upfront is critical to making data actionable. Focusing on a few key goals prevents teams from trying to “boil the ocean.” Exhibitor Expectations and ROI Pressure Exhibitors are asking sharper questions about ROI and measurable outcomes. Associations compete with alternative marketing channels for sponsor dollars. Integrated systems now provide better insights into lead generation and attendee behavior. Change Management and Innovation Mindset Innovation requires intentional planning, not just adopting “shiny” tools. Pilot programs and incremental changes help reduce risk. Understanding stakeholder impact is essential before rolling out new technology. 

MacPaw's Maria Polishchuk, Head of Business Development and  and Product Manager Pavlo Haidamak, discuss Setapp's new expansion beyond its traditional subscription model. They explain new individual app purchases, developer subscription options, AI Gateway integration, app review standards, and support for indie and vibe-coded apps. The discussion covers developer challenges such as discovery, monetization, security, and how Setapp aims to help with those factors as well as giving customers more software choices.  MacVoices is supported by Joe Kissell's Take Control Live: Taming Big Tech. Joe will spotlight the influence of today's biggest tech companies and what you can do about it. Joe will cut through the noise and deliver clear, useful guidance on privacy, security, convenience, and control. Sign up now. Show Notes: Chapters: 0:00] Introduction to Setapp's new direction[1:16] Changes coming to Setapp[2:16] AI Gateway for developers[3:06] What AI Gateway means for subscribers[4:27] Bring-your-own-key options[5:37] Why Setapp is adding individual app purchases[7:26] Managing subscriptions and purchases in one place[8:13] Distribution challenges for indie developers[10:03] App review, safety, and quality standards[12:31] Vibe-coded apps and commercial readiness[14:50] Marketing and discovery for new developers[17:25] AI Gateway's role in reducing developer friction[19:01] Distribution across Setapp, App Store, and developer sites[21:39] Subscription and lifetime license options[23:10] UX guidance and support for developers[25:30] Supporting both customers and developers[28:33] Revenue share and developer fees[29:20] Whether apps might leave the membership model[30:51] Curation and app quality in the expanded marketplace[34:37] Membership continuity and upcoming trials[35:43] Advice for aspiring developers[37:38] Closing thoughts and developer call-to-action Guests: Maria Polishchuk is the Head of Business Development for MacPaw. Pavlo Haidamak is Product Manager at MacPaw. Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Mastodon:     https://mastodon.cloud/@chuckjoiner      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The pound has lost 95% of its purchasing power since 1971. Every fiat currency in history has eventually gone to zero. Bitcoin might be the first money that actually holds its value — and building the financial services around it is what Piotr, Product Manager at Xapo Bank, has spent years working on.In this episode, Jordan sits down with Piotr to explore:How Piotr Bedkowski went from ING Bank sceptic to fully orange-pilled BitcoinerWhy Xapo Bank only holds USD and BTC — and why that's a deliberate choiceThe case for borrowing against Bitcoin instead of selling itHow Xapo's underground vaults earned the nickname "Fort Knox of Bitcoin"Why rehypothecation of collateral is off the table at Xapo — full stopEarning yield and monthly Bitcoin income from your existing stackWhat the "iPhone moment" for global Bitcoin adoption might actually look likeWhy Bitcoin-backed lending rates should, in theory, be the lowest in the worldTIMESTAMPS:00:00 Intro — Bitcoin is currency for the people01:00 Welcome and Piotr's background02:00 Joining Xapo Bank and building wealth products04:00 Bitcoin-backed lending and yield on Bitcoin06:00 Discovering Bitcoin twice — and why most people do09:00 Looking for the next Bitcoin (and why that's a mistake)10:00 Currency debasement — Argentina, Europe, and everywhere else13:00 The history of money and why fiat always fails17:00 What Xapo Bank is actually building and why19:00 Self-custody vs. custodial — meeting people where they are22:00 Inside Xapo's vaults — the Fort Knox of Bitcoin27:00 MPC security and why transactions are now near-instant32:00 How Xapo decides what products to build next38:00 Bitcoin-backed cards and what's coming42:00 Zero rehypothecation — and why it matters44:00 The iPhone moment and Bitcoin's next ten years48:00 Why Bitcoin-backed lending rates should be the lowest

Max Anderson is a seasoned product executive with a proven track record of bringing successful technology products to market in the consumer privacy, data management, and marketing space. Prior to Ketch, Max was the Director of Product Management at Krux. After joining Salesforce as part of the Krux acquisition, Max ran data privacy and consumer identity products at Salesforce, including the rollout of their industry-leading GDPR solution set. Prior to Krux, Max was a Product Manager at IPG Mediabrands, where he was responsible for multiple successful advertising measurement products. In this episode… Getting consent and opt-out compliance right requires more than adding a cookie banner or standalone webform. It requires consent tools, consumer identifiers, and downstream third-party systems to work in concert. Regulators are looking closely at whether a consumer's choice follows them across devices, browsers, and the systems where their data is collected and used. When those pieces do not connect, an opt-out can be incomplete, putting companies at risk of regulatory enforcement. So, what does it take to build a complete and compliant consumer opt-out experience?  Identity management is central to effective consent and opt-out compliance because consumer choices need to be honored at the person level, across devices and browsers. Privacy rights forms and consent tools also need to connect, so an opt-out request reaches the CMP controlling tag firing on the site. When data has moved to third-party advertising and marketing vendors, companies need to understand whether they can flow that opt-out downstream. Yet many third-party platforms do not provide privacy APIs or consent-related controls, and building integrations with them can be challenging. Companies should test the process by submitting an opt-out through the webform, returning to the website, and checking whether browser data collection events still happen that could facilitate cross-context behavioral advertising.  In this episode of She Said Privacy/He Said Security, Jodi and Justin Daniels talk with Max Anderson, Co-founder and Head of Product at Ketch, about navigating consent and opt-out compliance gaps. Max explains why identity management matters when honoring consumer choices across devices and browsers, and how disconnected privacy rights forms and consent tools can leave opt-outs incomplete. He also describes the challenges companies face when flowing opt-outs down to third-party advertising and marketing vendors and shares practical steps companies can take to assess vendor controls, cross-device exposure, and the areas that may create enforcement risk. 

MacPaw's Maria Polishchuk, Head of Business Development and  and Product Manager Pavlo Haidamak, discuss Setapp's new expansion beyond its traditional subscription model. They explain new individual app purchases, developer subscription options, AI Gateway integration, app review standards, and support for indie and vibe-coded apps. The discussion covers developer challenges such as discovery, monetization, security, and how Setapp aims to help with those factors as well as giving customers more software choices.  MacVoices is supported by Joe Kissell's Take Control Live: Taming Big Tech. Joe will spotlight the influence of today's biggest tech companies and what you can do about it. Joe will cut through the noise and deliver clear, useful guidance on privacy, security, convenience, and control. Sign up now. Show Notes: Chapters: 0:00] Introduction to Setapp's new direction [1:16] Changes coming to Setapp [2:16] AI Gateway for developers [3:06] What AI Gateway means for subscribers [4:27] Bring-your-own-key options [5:37] Why Setapp is adding individual app purchases [7:26] Managing subscriptions and purchases in one place [8:13] Distribution challenges for indie developers [10:03] App review, safety, and quality standards [12:31] Vibe-coded apps and commercial readiness [14:50] Marketing and discovery for new developers [17:25] AI Gateway's role in reducing developer friction [19:01] Distribution across Setapp, App Store, and developer sites [21:39] Subscription and lifetime license options [23:10] UX guidance and support for developers [25:30] Supporting both customers and developers [28:33] Revenue share and developer fees [29:20] Whether apps might leave the membership model [30:51] Curation and app quality in the expanded marketplace [34:37] Membership continuity and upcoming trials [35:43] Advice for aspiring developers [37:38] Closing thoughts and developer call-to-action Guests: Maria Polishchuk is the Head of Business Development for MacPaw. Pavlo Haidamak is Product Manager at MacPaw. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Dan Ciruli is VP and General Manager of Cloud Native at Nutanix. A computer science graduate of UC Berkeley, Dan spent a decade in engineering before pivoting to product management in 2003, a role that barely had a name when he started. Since then he has held product leadership positions at EMC and Google, where he was part of the team that helped create Kubernetes and open source Google's cloud infrastructure.He was a founding member of the OpenAPI Initiative and a steering committee member for the Istio service mesh project, and has spent the last two decades with one foot in commercial product development and one in the open source community.In this episode, Dan explains why open source is not a charity exercise, how companies actually make money from code they give away for free, and what product managers get wrong when they tell their engineers to avoid it.Key takeaways— Open source is not crowdsourcing from individuals — much of the contribution comes from companies investing on the clock, because broad adoption benefits everyone more than proprietary lock-in.— The CNCF succeeded because it created a neutral space where the largest and smallest organisations felt equally safe contributing and consuming. That structure — not the code itself — is what made cloud native computing universal.— Being a product manager in open source requires the same core instinct as any other PM role: understanding the why. The difference is that your engineers may work for a competitor, and your roadmap is not entirely yours to control.— AI is multiplying the capability of both good actors and bad actors in open source security. The answer is not to slow adoption but to keep a credible human in the loop — someone with accumulated trust, judgement and accountability.— Before open sourcing your own work, be clear on how your company will make money, articulate it concisely for leadership, and then find at least one other organisation — even a competitor — willing to join you. A consortium signals a standard. A solo release signals a gamble.Chapters1:16 — From engineering to product management3:11 — Bridging open source and commercial work5:05 — The origin of Kubernetes at Google6:35 — How Nutanix embraces open source7:16 — The crowdsourcing misconception8:51 — Why the CNCF changed everything11:25 — Building a defensible moat in open source12:13 — The business models behind free code14:18 — Managing roadmaps you don't fully control15:04 — When your competitor writes your code16:04 — The CEO who wore his secrets around his neck18:13 — Developing an open source strategy19:37 — The one question every PM must ask22:44 — What is the CNCF?23:34 — AI, open source and the security arms race29:45 — Chop wood, carry water: the human in the loop31:48 — Advice for PMs running open source products33:15 — Harnessing a community you don't manage34:38 — Should you open source your own work?36:35 — How messy does it really get?39:33 — Linux is an anti-patternOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Seu time está perdendo produtividade pela falta de padrão na documentação e processos? Neste conteúdo, recebemos Guilherme Mendonça, Product Manager da dti digital, que compartilha como sua equipe transformou o caos da documentação dispersa em uma solução que revolucionou o planejamento e refinamento de projetos. Ele revela uma abordagem inovadora que não só resolveu problemas internos, mas também se tornou diferencial competitivo para os clientes da empresa. Ficou curioso? Então, dê o play!Assuntos abordados:Gestão de conhecimento corporativo;Centralização de informações dispersas;Hierarquia de confiança em dados;Redução de tempo em documentação;Mapeamento de dependências;Automação de roteiros de teste.Links importantes:NewsletterDúvidas? Nos mande pelo LinkedinContato:  osagilistas@dtidigital.com.brOs Agilistas é uma iniciativa da dti digital, uma empresa WPP #iaaplicada 

BONUS: Your Developers Got 20x Faster — Now Watch Your Product Managers' Heads Explode Clarke Ching is "The Bottleneck Guy" — and he just spotted the bottleneck that AI is about to create in every software organization. It's not in the code. It's inside the heads of the people who decide what gets built. In this conversation, Vasco and Clarke unpack why speeding up developers with AI tools pushes the real constraint upstream — onto product managers, designers, and leaders — and what to do before cognitive overload crushes the people your organization depends on most. Every Business Has a Bottleneck — Most Are in the Wrong Place "Every single client I have is a detective puzzle. We're looking for this quiet killer sitting inside their business, siphoning off money. And if you look at them without the idea of going 'where's the bottleneck?' — you mistake the busyness for productivity."   Clarke approaches Theory of Constraints like a detective story, not a physics lecture. Every business has a bottleneck — the narrowest point that chokes throughput. The question isn't whether you have one, it's whether it's in the right place. In software development, Clarke argues, the bottleneck should almost always be the developers. Not because they're slow, but because they're the pacing resource — like the aircraft carrier in a naval fleet that sets the speed for everything else. When developers are the bottleneck, the people upstream (product managers, designers, architects) have time to curate high-quality, high-value inputs. The people downstream (testers, ops) can deliver fast feedback. Everything flows. But when the bottleneck drifts somewhere else — and nobody notices — everyone gets busy, nothing flows, and the organization mistakes that busyness for productivity. Clarke's latest book, The Speed Book, lays out how to find where your bottleneck actually is and move it to where it belongs. AI Just Moved the Bottleneck — And Nobody's Talking About It "Just imagine one person trying to feed 100 developers. It's ridiculous. Everyone goes, 'oh, that's just crazy.' But that's kind of going to be what it's like."   Here's the problem: AI coding tools — Claude Code, Cursor, Copilot — are making developers dramatically faster. If a team of 5 developers becomes 20x more productive, that's the equivalent of 100 developers. But you still have one product manager feeding them. The bottleneck hasn't disappeared — it's moved upstream. And when a bottleneck moves to the people who make product decisions, three things happen: they cut corners on requirements (shipping half-baked ideas because the team can turn them around fast), they feed developers busy work just to keep them occupied, and — worst of all — they lose the time needed to push through complexity to find elegance. Clarke references Steve Jobs's insight: Apple kept working past "peak complexity" until they reached "peak simplicity." That's where great products come from. But a product manager juggling work for 100 developers has no time for that journey. Elegance goes out the window. Why Giving AI to Product People Almost Makes Things Worse "If you want to wear your dog out so she sleeps, don't take her for long walks. Make the dog think. Brain games exhaust the dog faster than running."   The obvious fix — give product people AI tools too — sounds right but misses the point. AI can handle the easy parts of product work: drafting user stories, generating specs, compiling research. That's the equivalent of taking the dog for a run. But the hard parts — the deep thinking about what to build, why it matters, how features interact — that's brain work. And brain work is exhausting in a way that volume work is not. Clarke works with senior leaders whose biggest challenge is pacing themselves. Heavy cognitive lifting burns through energy fast — your brain consumes 30-40% of your body's glucose when you're thinking hard. When AI handles the easy work, the proportion of your day spent on exhausting brain work jumps from maybe 15-20% to 50% or more. It's like lifting weights for six hours straight. You don't get stronger — you break down. On top of that, product people go from coordinating one stream of work to juggling many simultaneous initiatives. Clarke calls these "idea grenades" — and when you're juggling chainsaws with grenades attached, you start dropping things. The Real Danger: Going in the Wrong Direction, 100x Faster "If you change the relative capacities and make some of them much, much faster, the bottleneck's gonna move. My next book, jokingly, is gonna be called 'Who Moved My Bottleneck?'"   There's an amplification effect that makes this worse than a simple throughput problem. An error in a line of code affects one line. An error in a design document ripples into hundreds of lines. An error at the strategic level — building the wrong features entirely — can be a disaster for the company. Now add AI speed to that equation. Overwhelmed product people making rushed decisions don't just slow things down — they point the entire organization in the wrong direction, and AI-powered developers execute that wrong direction at 20x speed. As Clarke puts it: you crash into the mountain, faster. The fundamental Theory of Constraints insight applies: if you speed up a non-bottleneck resource, you don't speed up the system. You just create more work-in-progress, more chaos, and more cognitive load for whoever the real bottleneck is. Four Experiments to Try Before Cognitive Crush Hits Your Team "Quality will come from actually slowing down. Money, profits will come from slowing down, building very good products, focusing on why we're building these products, not just how do we keep the AIs working."   Clarke offers four practical experiments for teams navigating this shift:   Get product people working with AI — as a thought partner, not a turbo boost. Teach them to delegate the routine work to AI so they can protect their cognitive energy for the decisions that actually matter. Think of AI as a delegation tool, not a productivity multiplier. Help product people find their sustainable pace. Like Clarke's gym trainer who said "don't come five days a week or you'll never come back" — the people doing heavy cognitive lifting need to pace themselves. Old-school agile called this sustainable pace. It's never been more relevant. Don't try to keep developers (or AI) busy all the time. The instinct to maximize utilization is the instinct that creates the problem. With AI, you're renting capacity by the minute, not paying salaries. Use it at the pace of good product thinking, not at maximum throughput. Turn the tap on and off as needed. Measure what matters: value delivered, not stories completed. If 60-70% of features rarely get used today, imagine what happens when you 20x the feature output without improving the decision quality upstream. More features, more waste — at scale. About Clarke Ching Clarke Ching is "The Bottleneck Guy" — a Theory of Constraints and lean expert who wrote Rolling Rocks Downhill, the agile+lean business novel that never mentions agile, and The Bottleneck Rules. Born in New Zealand, he spent 20 years abroad (15 of them in Scotland) before returning home. He's spent decades helping teams find and manage the one constraint that controls everything else. LinkedIn   You can link with Clarke Ching on LinkedIn.  

Featured Interview: This is a big month! The Muscle Car Place welcomes a brand-new sponsor to the network this month, but this partnership is about far more than advertising banners and product mentions. We’re trying to be a part of something BIG. I sat down with Bridney Jordan, Property Brands and Product Manager for Lexani, […] The post TMCP #648: Bridney Jordan and the Inside Baseball World of Tires for Daily's, Trucks and Enthusiast Rubber! first appeared on The Muscle Car Place.

Adam Creeger is the CTO of Slate and creator of iLoom (pronounced “il-LOOM”). His leadership experience at Meta, Greenhouse, and Frame.io not only informs Slate's transformation into an AI-native organization, but also shapes the way AI influences product strategy, engineering workflows, and operational models. Throughout his conversation with Sean and Dan, Adam argues that becoming AI native is not about layering AI features onto existing products. Instead, it requires companies to rethink how software is designed, built, and operated – from the ground up. His perspective offers a practical framework for product leaders navigating AI-driven transformation. Here's what else we learned: ‘AI Native' Requires Organizational Reinvention AI native organizations are willing to rethink every layer of their business, Adam says. Rather than adding AI features superficially, AI native organizations redesign workflows, team structures, and customer experiences around AI capabilities. He emphasized that AI transformation changes not only products, but also how people contribute inside organizations. “To be AI native requires this deep exercise in re-imagination and not just imagination,” Adam continues. “In an AI native company – from the day-to-day operations to the ‘who does what' – the roles and the owners of things are going to look very different.” AI is expanding participation across teams, enabling designers, support teams, and non-engineers to contribute directly to product delivery. That shift signals a major change for modern software organizations. AI and the Future of the Software Development Life Cycle (SDLC) Our conversation then turned to an exploration of how AI is already changing the traditional software development lifecycle. Years ago, Agile development emerged because humans had historically struggled to fully reason through complex systems before implementation. “I've realized that Agile was really a mitigation of a few things, mostly that we humans are limited in our abilities to reason through abstract concepts,” Adam says. “So when we thought about a software project, we didn't have the ability to see around corners and understand the problems we'd face – until it was real, until you really started playing with it. Turns out that many of those challenges are very solvable by AI, allowing us to go much deeper into the problem space without ever writing a line of code. In addition, AI-assisted planning allows teams to revisit some waterfall-style thinking, but with dramatically faster iteration and validation cycles. Product Managers’ New Role: Communicate Context Importantly, AI is actually elevating the role of product managers, Adam offers. Rather than acting primarily as tactical decision-makers, product leaders can (and should) focus on providing context that enables teams to make informed decisions independently. “More than ever, the product manager has become a role about providing context,” he adds. “PMs should be elevated to a much more strategic role, understanding the long-term vision and helping to translate that to engineers.” Adam also feels that PMs should be using AI to communicate ideas about the product vision much more effectively. That evolution creates a faster and more collaborative product environment. Teams can evaluate real implementations earlier, gather customer feedback sooner, and align around outcomes instead of specifications alone. [05:54] What it means to be ‘AI native’. Conceptually, it’s same as digital native from when the internet was born many years ago. In the abstract sense, I see AI native being about the folks and the companies that are either just starting in the age of AI where everything they do is shaped by the existence of AI and their ability to use AI. [15:08] Is waterfall making a comeback? Oh man, this is one of my favorite topics. Growing up in the industry, waterfall was always like the evil thing. But with AI-assisted coding or agentic coding, you can go really deep, create a much bigger scope, and deliver it much more quickly…and it resembles more of a waterfall mentality. [21:51] The PM’s primary role: providing context. The product manager more than ever has become a role about providing context. The most powerful thing PMs can do in an organization is provide context to other people. [25:49] Exploring Adam’s iloom tool, and how it can help. Hear a quick story from Adam about how he used his iloom tool to create — and demo — a new product feature during a call with his customer success team. [28:47] Swarms. What are they, and how do they work? A swarm is a number of AI agents working together in a very collaborative way with the potential of real-time communication between them. [35:03] Avoiding ‘AI slop’ to defend and elevate a brand’s quality bar. Slate is creating a tool that makes it very difficult to create AI slop. This is a valuable proposition to brands that care deeply about what gets produced in their name. The post 187 / AI Native: Reimagining Product Roles and Development Cycles, with Adam Creeger appeared first on ITX Corp..

In the private sector, product teams pick their customers, generate demand, and ship into something close to a green field. In the public sector, none of that holds. Ayushi Roy — Chief Program Officer at New America's New Practice Lab and a lecturer at the Harvard Kennedy School — joins Randy to unpack what changes when your user base is already sitting in front of you, your scrutiny is congressional, and the right answer is sometimes to delete ten systems rather than build an eleventh.Drawing on her work on IRS Direct File, the Children's Health Insurance Program (CHIP), the Illinois childcare voucher system, and a text-based 911 alternative that rolled out to 800,000 students across 13 universities, Ayushi makes the case for a distinct public-sector product playbook: thin-slicing for safe failure, designing for the lowest digital denominator, separating design problems from engineering problems, and treating unbuilding as a first-class option.Chapter markers01:48 — From aid monitoring in Jordan to digital delivery03:37 — Why she built a text-based alternative to 91106:33 — From a rollout to 800,000 students to Oakland City Hall08:58 — What the New Practice Lab does, and what a CPO does inside a think tank11:06 — Why private-sector product playbooks don't transliterate14:03 — No marketing, no early adopters: latent demand and the curb cut effect14:40 — Oakland's eviction tool, MacBooks, and the lowest digital denominator17:30 — Thin-slicing IRS Direct File without losing Congress22:36 — Building executive sponsorship that allows safe failure23:41 — Product vs service: the rest of the job that isn't writing code26:09 — Illinois childcare vouchers: when modernising the form makes things worse29:22 — Design problems, engineering problems, and the laptop-hinge analogy33:18 — Can AI prototyping close the policy–implementation gap?35:40 — The FAFSA simplification crisis and the case for bilingual builders37:31 — Unbuilding: how a request for a 15th CHIP system became one to remove ten41:18 — What keeps her goingOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Software delivery clarity has become one of the most important competitive advantages for engineering organizations. Teams are shipping faster, AI-assisted development is compressing implementation timelines, and traditional project management systems are struggling to keep pace with modern software delivery realities. During the conversation with Alex Polyakov, one idea surfaced repeatedly: most project management systems promise visibility but fail to provide actual operational clarity. Teams still discover delays too late. Executives still receive bad news at the last possible moment. Developers still spend excessive time updating systems rather than building software. That disconnect is exactly what inspired Alex to rethink how engineering organizations manage software delivery. About Alex Polyakov Alex Polyakov is the founder of Project Simple AI, a platform focused on improving transparency and discipline across software delivery workflows. With more than 25 years of experience spanning software engineering, architecture, product management, entrepreneurship, and startup leadership, Alex brings a deeply practical perspective to modern development operations. He has worked as an Application Developer, Senior Engineer, Tech Lead, Software Architect, Solutions Architect, Product Manager, Entrepreneur, and Startup Founder. Today, his focus is helping engineering teams gain visibility and operational discipline without adding unnecessary complexity. Alex also hosts the "Let's Talk Agile" podcast on YouTube, where he discusses modern software development challenges and Agile transformation realities. LinkedIn: https://www.linkedin.com/in/alexpolyakov/ Why Software Delivery Clarity Still Doesn't Exist Most organizations believe they have visibility because they use Jira, Azure DevOps, or similar tools. In reality, they have tracking systems, not visibility systems. Alex described modern project management tools as "glorified Excel sheets." That description lands because many engineering teams recognize the pattern immediately. Endless ticket hierarchies, fields, statuses, and sprint rituals often create administrative complexity without improving confidence. The core issue is simple: status updates depend on human behavior. Developers forget to update tickets. Teams delay reporting problems. Managers discover schedule risks only when deadlines are already compromised. The tooling creates an illusion of control while actual delivery risk remains hidden. That creates a dangerous operating environment for leadership. A founder or executive can solve a delivery problem early. They can reduce scope, renegotiate timelines, allocate additional staff, or re-sequence priorities. But once a team waits until the final week to communicate delays, most strategic options disappear. Visibility is not the same thing as documentation. Visibility means understanding delivery risk early enough to respond. Software Delivery Clarity Requires Behavioral Design One of the most interesting concepts from the discussion was the idea that project management is partly behavioral science. Most tools allow teams to skip critical disciplines. Teams can start work before decomposition. They can mark tasks complete without validating outcomes. They can carry partially defined requirements into implementation. Alex's approach flips that model entirely. Instead of giving teams unlimited flexibility, the system enforces operational readiness. Work cannot begin without decomposition. Timelines cannot exist without estimates. Completion cannot happen without verifying a definition of done. This is important because software organizations often assume process problems are communication problems. In reality, many are workflow design problems. If a system permits ambiguity, ambiguity becomes normalized. If a system requires clarity, clarity becomes operational behavior. Why AI Makes Software Delivery Clarity More Important AI-assisted development changes the economics of software delivery. Implementation cycles are shrinking dramatically. Tasks that previously required days may now take hours. Boilerplate code generation, scaffolding, testing support, and architectural suggestions accelerate execution speed. That acceleration creates a new challenge. If implementation becomes faster, bottlenecks move upstream and downstream. Requirements gathering, coordination, prioritization, testing, and validation suddenly become the limiting factors. This means organizations can no longer rely on heavyweight process management structures built for slower delivery cycles. When implementation speeds increase but operational visibility stays static, delivery chaos accelerates instead of improving. The transcript discussion highlighted a critical reality many organizations are only beginning to recognize: AI amplifies existing operational weaknesses. A disorganized engineering team using AI becomes a faster disorganized engineering team. That is why delivery clarity matters more now than it did during earlier Agile transformations. The Simplicity Principle Behind Better Delivery Alex outlined several operational principles that simplify software execution dramatically. Software Delivery Clarity Starts with Prioritization Teams should know exactly what matters most. Priority order should not be vague or political. If only one item can ship, teams must know which item wins. That sounds obvious, but many organizations operate with dozens of simultaneous "critical" initiatives. Clear sequencing eliminates organizational confusion. Software Delivery Clarity Depends on Finishable Work Teams should not start work that they cannot complete. This principle directly attacks excessive work in progress — one of the most common hidden inefficiencies in software organizations. Partially completed work creates coordination overhead, testing delays, context switching, and reporting confusion. Smaller, decomposed work creates measurable progress. Software Delivery Clarity Improves Team Accountability Alex also challenged pre-assigned work structures. When work is individually distributed too early, collaboration weakens. Teams lose shared ownership. Visibility becomes fragmented across individuals instead of remaining centralized around delivery goals. That perspective aligns closely with modern product-oriented engineering cultures where collaboration and flow matter more than rigid task ownership. Before adding new process layers, evaluate whether your current workflow already contains unnecessary coordination overhead. Why Simpler Engineering Systems Scale Better Many organizations assume maturity means adding process. The conversation suggested the opposite. Mature engineering organizations often remove unnecessary friction instead of introducing more operational complexity. Simplicity improves adoption, consistency, and decision-making speed. This becomes especially important in high-growth environments. As teams scale, communication overhead compounds rapidly. Every unnecessary workflow step multiplies across developers, product managers, QA engineers, architects, and leadership stakeholders. Simple systems reduce cognitive load. That reduction creates operational focus. The goal of project management is not to track work forever. The goal is to deliver valuable software predictably. Conclusion Software delivery clarity is not about more dashboards, more ceremonies, or more ticket customization. It is about creating operational confidence. Alex Polyakov's perspective challenges many assumptions that modern engineering organizations accept as normal. Teams do not necessarily need more process. They need better behavioral systems, clearer visibility, stronger prioritization, and simpler operational structures. As AI continues accelerating implementation speed, organizations that simplify coordination and improve transparency will gain a meaningful competitive advantage. The future of software delivery may not belong to the teams with the most process sophistication. It may belong to the teams with the clearest operational discipline. Stay Connected: Join the Developreneur Community

Daniel Wyrzykowski is a Product Manager at Mend.io. In this episode, he joins host Paul John Spaulding to discuss prompt injection, including what it is, whether it's the new SQL injection, and more. Securing The Build is brought to you by Mend.io, the leading application security solution, helping organizations reduce application risk efficiently. To learn more about our sponsor, visit https://mend.io.

Pourquoi vos utilisateurs sont déçus alors que votre produit tient ses promesses ?C'est souvent là que se cache le vrai problème : un décalage entre ce que vous racontez… et ce que vos utilisateurs vivent réellement.Dans cet épisode, je reçois Hélène et Doriann, qui travaillent main dans la main sur des sujets de Product Marketing et de Product Design pour aider les entreprises à aligner promesse, expérience et adoption.Ensemble, ils partagent leur approche terrain pour faire collaborer ces deux fonctions souvent silotées.Vous allez notamment découvrir :

Meet Ryan Patterson, product manager at Premier Data, a fast-growing sports technology startup that's closing the gap between elite-level analytics and grassroots sport.Ryan's path into sport is anything but linear. From scanning groceries at Woolworths at age 15, to progressively building his university qualifications across three degrees, a Bachelor of Business that evolved into Sport Management, and then a double degree adding Sport Science once he realised data analytics was where his future lay, Ryan has consistently leaned into what excited him rather than following a predetermined plan. Alongside his studies, he represented Deakin University on study tours in India and Chicago, always looking to make the most out of every opportunity in front of him.Over six years, he's worked his way through four distinct roles at Premier Data from casual coder to Product Manager, while simultaneously spending seven Australian Opens in the Ball Kids Ops team at Tennis Australia. Ryan has sat courtside for Grand Slam finals, worked inside Collingwood's coaches' box, been featured in a Netflix documentary at the AO, and helped build a startup from 20 games to 250 games a week.But his real superpower? Saying yes before he knew the answer, starting small, and staying long enough to grow into something bigger than he imagined.Tune in to this week's episode to hear exactly how he did it!We cover:(3:18) - Interview starts(5:18) - Quick-fire questions(11:02) - How the study trip to India and Chicago added to Ryan's university experience(15:13) - Ryan's internship with Collingwood FC(18:22) - How Ryan landed his role in the Ball Kid Operations team at the Australian Open(26:31) - Coolest moments from Ryan's time at the Australian Open(28:59) - How Ryan manages his roles across the AO and Premier Data(30:14) - What is Premier Data(37:18) - How Ryan progressed to his current role as Product Manager(41:47) - What does Ryan's look like on a day-to-day basis(45:41) - How Premier Data builds partnerships with new sports(48:50) - Challenges Ryan faced breaking into sport(51:14) - Advice Ryan would give his younger self(52:50) - Impact of mentors on Ryan's journey(56:20) - How to land a job as a Sport Product Manager in the next 30 days(59:06) - Biggest 'Pinch Me' moment in Ryan's career(01:00:00) - What would Ryan's life look like if he didn't work in sport(01:00:42) - What's something we might lose from sport in the next 10 years(01:02:21) - Ryan's question for the next guestIf you liked this ep, give these a go next:#227: How to be a Performance Analyst for Pro Tennis Players with Shane Linayage#257: How the AFL analyse their data with Dat Visualisation Lead, Penny Privett#288: How to be a champion data competitions coordinator with Ashleigh Newton-SpenceWant a job in sport? Click here.Follow SportsGrad on socials: LinkedIn | Instagram | TikTokFollow Reuben on socials: LinkedIn | Instagram | TikTokThanks for listening, much love! Hosted on Acast. See acast.com/privacy for more information.

Semiconductors power nearly everything, from AI and cloud computing to autos and basic household appliances. In this episode of the Conquer Risk Podcast Investment Series, Potomac CMO Christopher Norton and Co-CIO Dan Russo, CMT®, welcome Nick Frasse, Product Manager at VanEck, for a sharp look at one of today's most essential technologies. Learn what's fueling growth in the chip industry, how the VanEck Semiconductor ETF (SMH) delivers targeted exposure, and why this fast-moving sector continues to draw investors. Make sure you subscribe to never miss an update. Subscribe in Apple Podcasts Subscribe on Spotify Learn more about Potomac: https://potomac.com/ Read our blog: https://potomac.com/blog Disclosure: https://potomac.com/disclosures PFM- 208-20260428 Hosted on Acast. See acast.com/privacy for more information.

In this podcast episode, Diane Wiredu, Founder and Messaging Strategist for Lion Works, underscores the significance of this key element. Diane breaks down a step by step guide on effective messaging, while also providing insights on engaging customers and growing products.Our HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Join Václav Kandrnal, CEO and Co-Founder of DecisionRules, for a masterclass on the evolution of automated decision-making. A veteran of the financial world with 20 years of experience building digital banks like Zopa and MONETA, Václav is a leader who understands the high cost of rigid code. In this episode, we discuss the strategic "spin-off" of DecisionRules, the critical difference between rule inference and execution, and why giving business teams no-code control over logic is the only way for institutions to stay agile in a 2026 economy.

To celebrate the 10 Year Anniversary of the Outdoor Product Design & Development program at Utah State University, we are sharing conversations with alumni, faculty, and industry! Enjoy this conversation with OPDD alum and Product Manager at Blackstone Products, Christian Elkins. Listen to these conversations on the Highlander Podcast. https://opdd.usu.edu/podcast The Highlander Podcast is sponsored by the Outdoor Product Design & Development program at Utah State University, a four-year, undergraduate degree program that trains the next generation of product creators for the sports and outdoor industries. Learn more at opdd.usu.edu or follow the program on LinkedIn or Instagram. https://www.instagram.com/usuoutdoorproduct/ https://www.linkedin.com/company/opdd Discover the Outdoor Recreation Archive on Instagram or on USU's website. https://instagram.com/outdoorrecarchive https://library.usu.edu/archives/ora Subscribe to our ORA newsletter: https://outdoorrecarchive.substack.com/ Outdoor Recreation Archive Instagram https://www.instagram.com/outdoorrecarchive/?hl=en Episodes hosted, edited, and produced by Chase Anderson in beautiful Cache Valley, Utah. https://www.linkedin.com/in/chasewoodruffanderson/

This week, I am joined by Noah. Noah is a San Francisco–based builder, traveler, and community creator. Born to an Ethiopian family and raised just outside of Washington, D.C., he's always been drawn to new places, big ideas, and bringing people together. He graduated from Pepperdine University with a degree in Finance. By day he works in tech as a Product Manager at Google, and by night he's usually hosting something, chasing a new project, or planning his next adventure. Noah loves good conversations, spontaneous trips, staying active, and creating spaces where interesting people can meet.In this episode, we talked about how we each navigated finding our people in college and how the friendships we made then still impact us today. We discussed the importance of being open-minded and self-aware as we navigated a challenging and new environment. Tune-in to laugh, learn and appreciate our experience as college students!Please send questions and feedbacks you have to internationaliebyruth@gmail.com or DM on the Instagram page @internationaliebyruth

Prathik Roy is Product Director for Data and AI Solutions at Springer Nature, one of the world's largest academic publishing companies. A quantum chemist and material scientist by training, he spent years in R&D before gravitating towards product management — and has spent the past 12 years helping publishers understand the value locked inside their content. In this episode, Prathik makes the case that publishers are sitting on some of the most strategically valuable data in the world, and that most of them are only beginning to understand what that means in the age of AI.In this episode, we cover:(00:00) Introduction: from quantum chemistry to product management (05:00) The Schrödinger problem: why content value is increasingly unknowable (08:00) How traditional publishing metrics worked — and why they broke (11:30) The ChatGPT moment and its impact on scientific publishing (15:00) Paywalls, subscription models, and the shift to data licensing (21:30) How scientific content earns its quality — and why AI cannot just follow the citations (26:00) Why AI developers want bullet points — and what that means for content structure (29:00) New monetisation models: tokens, outcomes, and data as a service (33:00) Rights management: rights in, rights out, and why the prohibited section matters (36:30) Measuring content value when your users live inside AI systems (38:00) What to do with your content archive: extraction, licensing, and prediction marketsOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

The beverage alcohol industry is a complex beast with an intense regulatory environment and shifting consumer preferences. The foundational fuel for driving sales is product content that is always accurate and increasingly adaptive to the consumer's context - an occasion, a specific meal, their budget. With 700 - 1000 new SKUs a year, Bailie Duncan, Product Manager, Marketing Systems at Jackson Family Wines has rallied a small but mighty digital shelf team to make data a secret weapon that meets the consumer where they are, and steers them toward the right product at the right time.

Nikhyl Singhal is the founder of The Skip, a community for senior product leaders; a former product exec at Meta, Google, and Credit Karma; and a many-time founder. He's also one of the most honest, unfiltered voices on what's actually happening in product management right now.In our in-depth conversation, we discuss:1. Why the next two years will be the most chaotic period in product management history2. Why half of current product managers are at risk, and what separates those who'll do well3. Why you need to find your “moments of joy” with AI4. The “smiling exhaustion” he's seeing across the product community5. The psychological barriers that prevent people from reinventing themselves6. Why your resume's fancy logos matter less than ever, and what matters now7. His prediction that companies will shed 30,000 people and rehire 8,000—all AI-first—Brought to you by:WorkOS—Modern identity platform for B2B SaaS, free up to 1 million MAUsVanta—Automate compliance, manage risk, and accelerate trust with AI—Episode transcript: https://www.lennysnewsletter.com/p/why-half-of-product-managers-are-in-trouble—Archive of all Lenny's Podcast transcripts: https://www.dropbox.com/scl/fo/yxi4s2w998p1gvtpu4193/AMdNPR8AOw0lMklwtnC0TrQ?rlkey=j06x0nipoti519e0xgm23zsn9&st=ahz0fj11&dl=0—Where to find Nikhyl Singhal:• LinkedIn: https://www.linkedin.com/in/nikhyl• X: https://x.com/nikhyl• Podcast & Newsletter: https://skip.show• Skip Community: https://skip.community• Skip Coach: https://skip.coach• Skip.help: https://skip.help—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 Nikhyl Singhal(02:25) The big picture: what's changing for product managers(10:00) Are product leaders doing better than 2-3 years ago?(11:44) What will change in the next couple of years(14:23) How companies are changing the way they build products(15:51) What “judgment” really means for PMs(17:46) Why there won't be any more bad software(20:25) The skills you need to be effective today(23:31) Why there are more PM roles than ever(24:27) The builder versus information-mover divide(30:14) The non-builder problem(30:53) Should PMs code?(34:15) Why experienced leaders still matter(35:44) The diversity setback nobody's talking about(37:21) Why your brand doesn't matter as much anymore(39:54) How valued skills are flipping upside down(40:49) Why change is so hard for humans(43:53) The “equal disappointment” algorithm(46:39) You must cross the threshold(48:37) This chaos will settle(53:19) Finding your moment of joy(58:50) Nikhyl's AI stack and what he's building(1:00:53) The obsolescence mindset(1:05:24) Specific advice for PMs right now(1:08:58) The four jobs that will exist in the future(1:11:59) Why alignment is changing (but not disappearing)(1:15:40) How engineering is changing even more than PM(1:17:04) The surprising design plateau(1:18:49) Finding optimism in the chaos(1:21:12) Lightning round—Referenced:• Building a long and meaningful career | Nikhyl Singhal (Meta, Google): https://www.lennysnewsletter.com/p/building-a-long-and-meaningful-career• COBOL: https://en.wikipedia.org/wiki/COBOL• United Airlines: https://www.united.com• State of the product job market in early 2026: https://www.lennysnewsletter.com/p/state-of-the-product-job-market-in-ee9• Head of Growth (Anthropic): “Claude is growing itself at this point” | Amol Avasare: https://www.lennysnewsletter.com/p/anthropics-1b-to-19b-growth-run• Demis Hassabis on X: https://x.com/demishassabis• Sam Altman on X: https://x.com/sama• Dario Amodei on X: https://x.com/DarioAmodei• Cross on Prime Video: https://www.amazon.com/Cross-Season-1/dp/B0D6X7ZZHC• Jack Ryan on Prime Video: https://www.amazon.com/Tom-Clancys-Jack-Ryan/dp/B0CNDCMN8R• 24 on Prime Video: https://www.amazon.com/24-Season-1/dp/B000HPF85A• Claude Code: https://code.claude.com• Codex: https://chatgpt.com/codex• Lovable: https://lovable.dev• Sonos: https://www.sonos.com• “There are only four jobs” on X: https://x.com/yrechtman/status/2039012253341495462• Paradise on Hulu: https://www.hulu.com/series/paradise-2b4b8988-50c9-4097-bf93-bc34a99a5b4f• Lioness on Paramount+: https://www.paramountplus.com/shows/lioness• Tesla: https://www.tesla.com• Albert Einstein's quote: https://www.goodreads.com/quotes/115696-genius-is-1-talent-and-99-percent-hard-work—Recommended books:• James: https://www.amazon.com/James-Novel-Percival-Everett/dp/0385550367• The Adventures of Huckleberry Finn: https://www.amazon.com/Adventures-Huckleberry-Finn-Unabridged-Uncensored/dp/195483943X—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