Podcasts about Agile

Natalia Curusi: When Your Technical Expertise Becomes Your Biggest Scrum Master Weakness 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 thought my technical background was my biggest strength, but I understood that this was my biggest weakness—I was coming into stand-ups saying 'I know how we need to fix that issue,' and I was a Scrum Master." - Natalia Curusi   Natalia stepped into her first blended role as team leader and Scrum Master full of confidence. With years of programming experience behind her, she believed she could guide her team through any technical challenge. But during morning stand-ups, she found herself suggesting solutions, directing technical approaches, and sharing her expertise freely. The team listened—after all, she was their former leader. They implemented her suggestions, but when those solutions failed, the team didn't have the thinking process to adapt them to their context.  Natalia realized she was preventing the team's learning and ownership by taking control away from them. The turning point came when she made a deliberate choice: she selected the most technical person on the team to become the technical authority and committed to never stepping on his feet again. From that moment forward, she focused purely on the Scrum Master role—asking questions, fostering collaboration, and shutting up to listen actively.  Years later, that technical lead followed her to another job, and they remain friends to this day. Natalia learned that her contribution wasn't about giving solutions—it was about keeping the team from losing ownership of their work.   Self-reflection Question: When you attend your team's daily stand-up, are you contributing to collaboration, or is your contribution keeping the team from owning their work?   [The Scrum Master Toolbox Podcast Recommends]

What does it really mean to build an AI-forward company that is still deeply human-first? In this episode, host Susan Diaz and senior HR leader and mentor culture advocate Helen Patterson talk about jobs, guardrails, copyright, environmental impact, and why mentorship and connection matter more than ever in the age of AI. Episode summary Susan is joined by Helen Patterson, founder of Life Works Well, senior HR leader, and author of the upcoming book Create a Mentor Culture. They start with a Y2K flashback and draw a straight line from past tech panics to today's AI headlines. Helen shares why she sees AI as the latest evolution of technology as an enabler in HR - another way to clear the admin and grunt work so humans can focus on growth, development, and real conversations. From there, they dig into: The tension between "AI will kill jobs" and tens of thousands of new AI policy and governance roles already posted. How shadow AI shows up when organizations put in blanket "no AI" rules and people just reach for their phones anyway. The very real issues around privacy, copyright, and intellectual property when staff feed proprietary material into public models. The less-talked-about environmental impact of AI and why leaders should demand better facts and more intentional choices from tech providers. In the second half, Helen brings the conversation back to humanity: mentorship as a counterweight to disconnection, her One Million Mentor Moments initiative, and how everyday "micro-mentoring" at work can help people adapt to rapid change instead of being left behind. They close with practical examples of using AI for good in real life - from travel planning and research to late-night dog-health triage - without letting it replace judgement. Key takeaways This isn't our first tech panic. From Y2K to applicant tracking systems, HR has always framed tech as an enabler. GenAI is the newest layer, not an alien invasion. Looking back at history helps calm "sky is falling" narratives. Jobs are changing, not simply disappearing. Even as people worry about AI-driven job loss, platforms like Indeed list tens of thousands of AI policy and governance roles. The work is shifting toward AI-forward skills in every function. Blanket "no AI" rules don't work. When organizations ban external tools or insist on only one locked-down platform, people quietly use their own devices and personal stacks anyway - creating shadow AI with real privacy and IP risk. Guardrails and education beat prohibition. Copyright and confidentiality need more than vibes. Without clear guidance, staff will copy proprietary frameworks or documents into public models and re-badge them. Leaders need simple, well-communicated philosophies about what must not go into AI tools. Environmental impact is part of human-first. Training and running large models consumes energy. The real solution will be systemic (how tech is built and powered), but individuals and organizations can still use AI more efficiently, just like learning not to leave all the lights on. Mentorship is the ultimate human technology. Helen's work on Create a Mentor Culture and One Million Mentor Moments reframes mentoring as everyday, one-conversation acts that share wisdom, reduce fear, and help people reskill for an AI-forward world. Tech should support that, not replace it. Upskilling beats layoffs. When roles change because of AI, the most human-first response isn't to cut people loose, it's to invest in learning, mentoring, and redeployment so existing talent can grow into new, AI-augmented roles. Use AI to simplify life, not complicate it. From planning multi-country trips to triaging whether the dog really needs an emergency vet visit, smart everyday use of AI can save time, money, and anxiety - freeing up more space for the work and relationships that actually matter. Episode highlights [00:01] Susan sets the scene: 30 episodes in 30 days to build Swan Dive Backwards in public. [00:39] Helen's intro: Life Works Well, heart-centred high-performance cultures, and her focus on mentorship. [03:43] What an AI-forward and human-centred organisation looks like in practice. [04:00] Y2K memories and why today's AI panic feels familiar. [06:11] 25–35K AI policy jobs on Indeed and what that says about the future of work. [07:49] Jobs lost vs jobs created—and why continuous learning is non-negotiable. [15:19] The danger of "everyone is using AI" with no strategy or safeguards. [19:25] Shadow AI, personal stacks, and why hard bans don't stop experimentation. [21:13] A real-world IP scare: proprietary material pasted into GPT and re-labelled. [23:06] GPT refusing to summarise a book for copyright reasons—and why that's a good sign. [24:03] The case for a simple AI philosophy doc: purpose, principles, and communication. [25:24] Environmental concerns, fact-checking, and the server-room-to-laptop analogy. [30:17] New social media laws for kids and what they signal about tech accountability. [30:41] One Million Mentor Moments: why one conversation can change a career. [31:22] From elite programmes to everyday mentor cultures inside organisations. [35:01] AI for mentoring and coaching: bots, big-name gurus, and internal use cases. [36:30] Using AI for travel planning, research, and everyday life admin. [37:35] Susan's story: using AI to triage a dog-health scare instead of doom-scrolling vet sites. [38:37] Life Works Well's roots in work–life harmony and simplifying with tech. [39:35] Where to find Helen online and what's next for her book. If you're leading a team (or a whole organization), use this episode as a prompt to ask: Where are we treating AI as a tool in service of humanity - and where are we forgetting the human first? Do our people actually know what's OK and not OK to put into AI tools? How could we use mentorship - formal or informal - to help our people navigate this shift instead of fearing it? Connect with Susan Diaz on LinkedIn to get a conversation started.   Agile teams move fast. Grab our 10 AI Deep Research Prompts to see how proven frameworks can unlock clarity in hours, not months. Find the prompt pack here. You can connect with Helen Patterson on LinkedIn and follow her work on Create a Mentor Culture and One Million Mentor Moments via lifeworkswell.ca

Most leaders talk about AI in terms of pilots, projects, and one-off tools. In this solo episode, host Susan Diaz explains why that mindset stalls adoption - and introduces the idea of an AI flywheel: a simple, compounding loop of audit → training → personalized tools → ROI that quietly turns experiments into momentum across your whole organisation. Episode summary Susan opens by contrasting how most organizations approach AI - pilots, isolated chatbots, a few licences to "see what happens" - with how enduring companies build flywheels that compound over time. Borrowing from Jim Collins' Good to Great, and examples like Amazon's recommendation engine, she reframes AI from "one big launch" to a heavy wheel that's hard to move at first, but almost impossible to stop once it's spinning. She then introduces her AI flywheel for organizations, built on four moving pillars: Audit - reality-check where AI already lives in tools, workflows, risks, and guardrails. Training - raise the floor of AI literacy so more people can safely experiment. Personalised tools and workflows - move beyond generic prompts into department- and workflow-specific systems. ROI tracking - measure time saved, errors reduced, risk reduced, and adoption so the story keeps getting funded. Instead of a linear checklist, these components form a loop - each turn of the wheel making the next easier, and creating an unfair advantage for organizations that start early. Finally, Susan adds the outer ring: human-first culture and governance as the operating system around the flywheel - psychological safety, champions and mentors, and values like equity that ensure AI momentum doesn't quietly recreate hustle culture or leave people behind. She closes with practical questions any leadership team can use this week to start their own AI flywheel. Key takeaways Projects start and end. Flywheels don't. Treating AI as a string of pilots and vendor launches creates start–stop energy. Designing a flywheel turns every experiment into input for the next win. A flywheel is heavy at first - but gains unstoppable momentum. Like a giant metal train wheel, it needs a lot of initial force, but each full turn adds speed. AI works the same: early experiments feel slow, compounding learning later feels unfairly fast. The AI flywheel has four core pillars: Audit - map current tools, workflows, risks, and guardrails; discover hidden wins and power users. Training - treat AI like financial literacy: a minimum viable level for everyone so they can ask better questions and prompt more effectively. Personalised tools & workflows - stop asking "Which LLM?" and start asking "Which steps in this 37-step process should AI do?" Workflow first, tool second. ROI tracking - measure time saved, errors reduced, faster time to market, risk reduction, and % of AI-augmented workflows so leaders keep investing. Culture is the operating system around the flywheel. Without psychological safety, people hide experiments. Without support, power users burn out. Values like equity matter: who's getting trained, who has access, and who you're helping reskill. Governance should feel like guidance, not punishment. You don't build an AI flywheel in a day. You start with one audit, one workflow, one dashboard that makes things more transparent - and commit to one small centimetre of momentum at a time. Episode highlights [00:02] Why "we're piloting a chatbot" is not a strategy. [01:34] Flywheel 101: the train-wheel analogy and why momentum beats one-off effort. [03:19] Amazon's recommendation engine as a classic business flywheel. [05:02] Applying Jim Collins' Good to Great flywheel lens to AI initiatives. [05:30] From big bang ERP-style AI projects to small, compounding loops. [08:00] Introducing the four pillars: audit, training, personalised tools, ROI. [08:53] Audit as reality check: surfacing hidden wins and DIY power users. [11:14] Training as "raising the floor" of AI literacy. [14:08] Workflow-first thinking and the myth of the single all-powerful agent. [17:33] ROI stories: error reduction, faster time to market, and risk reduction. [20:19] Culture as outer ring: psychological safety, champions, values in action. [23:06] Starting your flywheel: three questions for your leadership team. Use this episode as a design tool, not just a definition. Grab a whiteboard with your leadership team and map: Where are we already auditing, training, personalising tools, and measuring ROI - however informally? Where is the wheel broken, or missing entirely? What's one centimetre of movement we can create this quarter - one audit, one workflow, one dashboard - to start our AI flywheel turning? Connect with Susan Diaz on LinkedIn to get a conversation started.   Agile teams move fast. Grab our 10 AI Deep Research Prompts to see how proven frameworks can unlock clarity in hours, not months. Find the prompt pack here.  

BONUS: The Agile Organization as a Learning System Think Like a Farmer, Not a Factory Manager "Go slow to go fast. If you want to go somewhere, go together as a team. Take a farmer's mentality."   Simon contrasts monoculture industrial thinking with the permaculture approach of Joel Salatin. Industrial approaches optimize for short-term efficiency but create fragile systems. Farmer thinking recognizes that healthy ecosystems require patience, diversity, and nurturing conditions for growth. The nervous system that's constantly stressed never builds much over time—think of the body, trust the body, let the body be a body. Value Masters, Not Scrum Masters "We need value masters, not Scrum Masters. Agile is a useful tool for delivering value, but value itself is primary. Everything else is secondary—Agile included."   Tom makes his most provocative point: if you asked a top manager whether they'd prefer an agile person or value delivery, the answer is obvious. Agile is one tactic among many for delivering value—not even a necessary one. The shift required is from process mastery to value mastery, from Scrum Masters to people who understand and can deliver on critical stakeholder values. The DOVE Manifesto "I wrote a paper called DOVE—Deliver Optimum Values Efficiently. It's the manifesto focusing on delivering value, delivering value, delivering value."   Tom offers his alternative to the Agile Manifesto: a set of principles laser-focused on value delivery. The document includes 10 principles on a single page that can guide any organization toward genuine impact. Everything else—processes, frameworks, methodologies—are secondary tools in service of this primary goal. Read Tom's DOVE manifesto here.  Building the Glue Between Social and Physical Technology "Value is created in interactions. That's where the social and physical technology meet—that joyous boundary where stuff gets done."   Simon describes seeing the world through two lenses: physical technology (visible tools and systems) and social technology (culture, relationships, the air we breathe). Eric Beinhoeker's insight is that progress happens at the intersection. The Gilbian learning loops provide the structure; trust and human connection provide the fuel. Together, they create organizations that can actually learn and adapt.   Further Reading To Support Your Learning Journey Resources & Further Reading Explore these curated resources to deepen your understanding of strategic planning, value-based management, and transformative organizational change.    

What does modern sales leadership look like when AI is in the mix? In this episode, host Susan Diaz and sales leadership coach Kirsten Schmidtke unpack how AI and humanity can peacefully coexist in sales, why scale starts with clarity and process (not tools), and how leaders can shift from output-obsessed hustle to outcome-focused, identity-level leadership in an AI-forward world. Episode summary Susan sits down with sales leadership consultant Kirsten Schmidtke to talk about AI, scale, and the "identity-level shifts" leaders need to make in modern sales. They start at the intersection of mindset and skillset - why AI is now part of the sales skill stack, but can't replace the human mindset, judgment, and presence required to sell well. Kirsten shares how sales organizations have moved from using AI as a basic copy/research tool to embedding LLMs in meetings, CRMs, and internal platforms, and even building their own AI features once they deeply understand their market and product. From there, they zoom out to the trust recession, spammy AI outreach, and the difference between being AI first and AI forward. They discuss AI as a way to free people into their zone of genius (hello, The Big Leap), the historical pattern of tech disruption and new job creation, and why AI should be seen as a massive upgrade to human potential - not a replacement. In the second half, they dig into scale and operations: why AI will only scale chaos if you don't have clear goals, processes, and SOPs. Why many sales orgs still lack documented sales and go-to-market processes. And how documenting before automating is the hidden unlock for using AI well. Kirsten closes with her identity-based leadership model (be → do → have), her outcome-over-output philosophy, and practical invitations for leaders who want to use AI to reduce burnout instead of fuelling hustle culture. Key takeaways Modern sales lives at the intersection of AI and humanity. AI is becoming part of the sales skillset, but the mindset - who you are being as a leader or seller - still drives how effectively those tools get used. Sales orgs have evolved past AI as copy tool. Early use was mostly email drafting and light research. Now teams are: choosing an LLM of choice (ChatGPT, Copilot, Perplexity, etc.) and tailoring it to their sales strategy embedding AI in meeting tools to surface questions and summaries in real time building AI into internal platforms based on deep knowledge of market, product, and GTM. We're in a trust recession - and lazy AI is making it worse. Spray-and-pray LinkedIn DMs and generic AI pitches erode trust and make buyers more sceptical and confused. Being AI forward means intentional, human-centred use of AI, not pushing AI for its own sake. AI should move you toward your zone of genius, not further into busywork. Borrowing from Gay Hendricks' The Big Leap, Kirsten and Susan talk about AI as a way to strip away tasks in your zones of incompetence/competence so you can spend more time in your zone of genius - and potentially unlock higher human experiences and contribution. Scale requires clarity and process before tools. AI isn't a magic scale button. Without a clear what and why, it can't help with the how. Leaders must: define the outcome and purpose of what they're scaling decide what not to do document the current process (SOPs) before asking AI to automate or optimise it. Otherwise AI just scales the chaos. Most salespeople are executors, not system builders. They're brilliant at doing the thing - calls, meetings, negotiation - but often not trained to design processes and ops. Pairing them with ops-minded people (and AI) to document and structure their best practices is where real scale lives. Identity-level leadership: be → do → have. Instead of "when I have the title, I'll be a leader", Kirsten coaches leaders to start with identity: "I am the leader of an AI-forward sales organization." That identity shapes thinking, then actions, then results. Shift from output to outcomes to avoid AI-fuelled burnout. If you treat AI as a way to cram more tasks into the same day, you just recreate hustle culture. Focusing on outcomes (what actually changes for customers, teams, and the business) allows you to use AI to create space - for thinking, rest, and higher-value work - instead of filling every spare minute. Episode highlights [00:01] Meeting Kirsten and why you can't talk about modern sales without talking about AI. [01:07] Mindset + skillset at the intersection of AI and humanity in sales. [02:35] How sales orgs first used AI as a copy / research tool—and what's changed. [04:45] Embedding AI in meetings and tools vs building AI features in-house. [06:11] The "spray and pray" LinkedIn problem and AI's role in the trust recession. [08:53] Being "AI forward" instead of "AI first." [10:39] Why humans remain safe: discernment, judgment, spidey senses, and taste. [11:39] Arianna Huffington, Thrive, and using AI to free time for human development. [13:19] The Big Leap and using AI to move into your zone of genius. [17:01] Tech history, job loss, and why we're in the messy middle of another big shift. [19:34] What scale really means: more impact with less time and effort. [20:33] Why AI can't fix a lack of clarity—and how it can accidentally add work. [23:32] "AI will scale the chaos" if you skip documentation and SOPs. [25:08] Salespeople as executors, not ops designers, and the power of pairing them with systems people. [27:47] Branding, buyer clarity, and why AI can't replace the hard work of positioning. [31:00] Identity-level shifts for leaders: adopting "I am…" statements. [35:21] AI and burnout: from productivity for productivity's sake to outcome-focused leadership. [37:25] Newtonian vs Einstein time and rethinking how we use the time AI frees. [39:59] "Outcome over output" as a leadership mantra in the age of AI. [40:38] Kirsten's invitation: a Sales Leader Power Hour to work on your mindset and identity. If you're leading a sales team - or are the sales team - and you're feeling the tension between AI, scale, and leadership start here: Pick one sales process and document it end-to-end. Identify one step where AI could genuinely reduce effort or time. Ask, "Who do I need to be as a leader of an AI-forward sales org?" and let that identity shape your next move. Connect with Susan Diaz on LinkedIn to get a conversation started.   Agile teams move fast. Grab our 10 AI Deep Research Prompts to see how proven frameworks can unlock clarity in hours, not months. Find the prompt pack here. To go deeper on mindset and identity shifts, connect with Kirsten Schmidtke on LinkedIn and book a Sales Leader Power Hour here: https://www.kirstenschmidtke.com/sales-leader-power-hour   

BONUS: Quality 5.0—Quantifying the "Unmeasurable" With Tom Gilb and Simon Holzapfel Clarification Before Quantification "Quantification is not the main idea. The key idea is clarification—so that the executive team understands each other."   Tom emphasizes that measurement is a means to an end. The real goal is shared understanding. But quantification is a powerful clarification tactic because it forces precision. When someone says they want a "very fast car," asking "can we define a scale of measure?" immediately surfaces the vagueness. Miles per hour? Acceleration time? Top speed? Each choice defines what you're actually optimizing for. The Scale-Meter-Target Framework "First, define a scale of measure. Second, define the meter—the device for measuring. Third, set numbers: where are we now, what's the minimum to survive, and what does success look like?"   Tom's framework makes the abstract concrete:   Scale of measure: What dimension are you measuring? (e.g., time to complete task) Meter: How will you measure it? (e.g., user testing with stopwatch) Past/Status: Where are you now? (e.g., currently takes 47 seconds) Tolerable: What's the minimum acceptable? (e.g., must be under 30 seconds to survive) Target/Goal: What does success look like? (e.g., 15 seconds or less)   Many important concepts like "usability" decompose into 10+ different scales of measure—you're not looking for one magic number but a set of relevant metrics. Trust as the Organizational Hormone "Change moves at the speed of trust. Once there's trust, information flows. Once information flows, the system comes to life and can learn. Until there's trust, you have the Soviet problem."   Simon introduces trust as the "human growth hormone" of organizational change—it's fast, doesn't require a user's manual, and enables everything else. Low-trust environments hoard information, guaranteeing poor outcomes. The practical advice? Make your work visible to your manager, alignment-check first, do something, show results. Living the learning cycle yourself builds trust incrementally. And as Tom adds: if you deliver increased critical value every week, you will build trust.   About Tom Gilb and Simon Holzapfel   Tom Gilb, born in the US, lived in London, and then moved to Norway in 1958. An independent teacher, consultant, and writer, he has worked in software engineering, corporate top management, and large-scale systems engineering. As the saying goes, Tom was writing about Agile before Agile was named. In 1976, Tom introduced the term "evolutionary" in his book Software Metrics, advocating for development in small, measurable steps. Today, we talk about Evo, the name Tom uses to describe his approach. Tom has worked with Dr. Deming and holds a certificate personally signed by him. You can listen to Tom Gilb's previous episodes here.    You can link with Tom Gilb on LinkedIn    Simon Holzapfel is an educator, coach, and learning innovator who helps teams work with greater clarity, speed, and purpose. He specializes in separating strategy from tactics, enabling short-cycle decision-making and higher-value workflows. Simon has spent his career coaching individuals and teams to achieve performance with deeper meaning and joy. Simon is also the author of the Equonomist newsletter on Substack. And you can listen to Simon's previous episodes on the podcast here.    You can link with Simon Holzapfel on LinkedIn.  

I figured it was about time I addressed this one. You can’t breathe without taking in some serious AI hype right now. How much is fluff and smoke, and how much is real? AND…how will this apply to Agile? Will AI Save Agile? Great question. I have a few gut-level reactions to this. First, I think there’s a gold-rush feel to what’s going on right now. With any new technology, especially the monumental ones, there’s always speculation that this ‘changes the game forever’. But that can’t always be true. On the one hand, AI has a lot of issues. But its early stages. I think the biggest threat is the unbridled greed that goes with mass adoption. Who’s regulating the copyrights of the material AI is trained on? Who makes sure that AI doesn’t recommend or do dangerous or immoral things? But the big question I have is “why would you want so much stuff created by robots?” I can’t articulate why, but I know I don’t want to read a book or watch a play written and mounted by robots. And hey, if LLM’s need our inventions to grow, learn and innovate, what happens when we no longer create ‘things’? AI’s Role in Agility As of this writing, so much of the conversation is about using AI to take the rote tasks out of a Scrum Master’s day…preparing reports or briefs, summarizing retrospectives, and writing user stories. But there’s also discussion that maybe AI can replace Scrum Masters and Coaches. That’s a little scary for those of us who hold or want to occupy these roles in the future. So maybe someday AI can plan our sprints, produce empirical estimates, and even hold coaching conversations. But Will AI Save Agile? That supposes that the solution to all of our current Agile pains have a known solution. After all, we can’t code or teach things that we have no certain knowledge of. And until we do, it would impossible for AI to magically fix what’s wrong with Agile in 2026. That’s still very much a human concern. Stay tuned – I’ll be exporing more about AI’s role in the future of Agile in some upcoming episodes as I learn more… **THE ALL NEW FORGE LIGHTNING** 12 Weeks to elite leadership! https://learning.fusechamber.com/forge-lightning **CREATE A PROFITABLE BUSINESS FROM YOUR AGILE SKILLS WITH FORGE GENESIS** Everything you need to ideate, validate, market, and sell to enterprise OR consumers. https://learning.fusechamber.com/the-forge-genesis **JOIN MY BETA COMMUNITY FOR AGILE ENTREPRENEURS AND INTRAPRENEURS** The latest wave in professional Agile careers. Get the support you need to Forge Your Freedom! Join for FREE here: https://learning.fusechamber.com/offers/Sa3udEgz **CHECK OUT ALL MY PRODUCTS AND SERVICES HERE:** https://learning.fusechamber.com **ELEVATE YOUR PROFESSIONAL STORYTELLING – Now Live!** The most coveted communications skill – now at your fingertips! https://learning.fusechamber.com/storytelling **JOIN THE FORGE*** New cohorts for Fall 2025! Email for more information: contact@badassagile.com **BREAK FREE OF CORPORATE AGILE!!*** Download my FREE Guide and learn how to shift from roles and process and use your agile skills in new and exciting ways! https://learning.fusechamber.com/future-of-agile-signup We’re also on YouTube! Follow the podcast, enjoy some panel/guest commentary, and get some quick tips and guidance from me: https://www.youtube.com/c/BadassAgile ****** Follow The LinkedIn Page: https://www.linkedin.com/showcase/badass-agile ****** Our mission is to create an elite tribe of leaders who focus on who they need to become in order to lead and inspire, and to be the best agile podcast and resource for effective mindset and leadership game. Contact us (contact@badassagile.com) for elite-level performance and agile coaching, speaking engagements, team-level and executive mindset/agile training, and licensing options for modern, high-impact, bite-sized learning and educational content. If you liked this episode, you should check out: Episode 240 – Why Big Agile Fails Non-Conformity is the Key To Your Agile Future Episode 151 – What's Next?

In this episode, Avanish and Antonio discuss:BBVA's data transformation journey, including the strategic decision in 2017 to create a global data function at the executive committee level reporting to the CEO and ChairmanBuilding hybrid data architecture combining centralized lake house (AWS) with data mesh approaches to balance agility and control across global operations in regulated environmentsThe "eight robots" framework—a top-down AI transformation agenda targeting the most critical parts of BBVA's value chain, from digital client relationships to banker productivity to risk underwritingHow BBVA defines data democratization as "responsible access" not "open access," implementing strict governance while enabling self-service analytics in a highly regulated industryReal-world AI impact: solutions reducing tasks from 11 minutes to less than 1 minute, generative assistant "Blue" serving 20+ million clients in Spain and Mexico, and IVR improvements saving minutes to secondsThe partnership and ecosystem strategy leveraging enterprise-focused innovation through AWS, OpenAI, Google Gemini, and vertical solution providers to increase speed of learning and innovationWhy the "mode in this cycle is learning—how fast you can learn, how fast you can test hypotheses"—embracing experimentation and continuous improvement as models rapidly evolveAntonio's vision for the future: using AI and data to expand bankarization globally, serving underserved populations and fueling economic growth for families and businessesAbout the host:Avanish Sahai is a Tidemark Fellow and served as a Board Member of Hubspot from 2018 to 2023; he currently serves on the boards of Birdie.ai, Flywl.com and Meta.com.br as well as a few non-profits and educational boards. Previously, Avanish served as the vice president, ISV and Apps partner ecosystem of Google from 2019 until 2021. From 2016 to 2019, he served as the global vice president, ISV and Technology alliances at ServiceNow.  From 2014 to 2015, he was the senior vice president and chief product officer at Demandbase.  Prior to Demandbase, Avanish built and led the Appexchange platform ecosystem team at Salesforce, and was an executive at Oracle and McKinsey & Company, as well as various early to mid-stage startups in Silicon Valley.About Antonio Bravo, Global Head of Data at BBVAAntonio started his career in 2009 as a consultant focused in Technology, Media and Telecom. There he had the opportunity to learn how (mobile) internet growth blurs barriers between different industries and makes them converge. One of those industries is finance. He joined BBVA in 2011 to be part of its transformation strategy, and since then he has had different jobs. Started working in the Strategy & M&A area, with focus on the BBVA Ventures team (today Propel) investing in fintech startups, continued with a role in Digital Banking Strategy team, and later in 2015 assumed the responsibility of Business Development in South America (Argentina, Chile, Colombia, Perú, Venezuela, Uruguay and Paraguay).He also held the responsibility of Agile Organization until July 2019, focused in scaling the Agile methodology through-out the entire organization, more than 33.000 people including holding and countries, to improve quality, time to market, productivity and team engagement.From July 2019 until September 2021 he held the responsibility of IT Strategy & Control within BBVA, a function that manages some of the core IT functions at a global level, such as IT strategy, finance, vendor management, PMO, first line of defense and IT spin-offs.Since September 2021 he holds the position of Head of Sustainability Strategy & Business Development, where he contributes to the design of the strategic plan for all segments and manages investment in descarbonization funds. In January 2024 he was also appointed as Head of Corporate and Investment Banking Strategy, Industrial client coverage and cross border business.In January 2025 was appointed Global Head of Data at BBVA. Antonio is responsible of leading the transformation of the Group towards a data-driven company.About BBVA:BBVA is a global financial services group founded in 1857. The bank is present in more than 25 countries, has a strong leadership position in the Spanish market, is the largest financial institution in Mexico and it has leading franchises in South America and Turkey. In the United States, BBVA also has a significant investment, transactional, and capital markets banking business.BBVA contributes with its activity to the progress and welfare of all its stakeholders: shareholders, clients, employees, providers and society in general. In this regard, BBVA supports families, entrepreneurs and companies in their plans, and helps them to take advantage of the opportunities provided by innovation and technology. Likewise, BBVA offers its customers a unique value proposition, leveraged on technology and data, helping them improve their financial health with personalized information on financial decision-making.About TidemarkTidemark is a venture capital firm, foundation, and community built to serve category-leading technology companies as they scale.  Tidemark was founded in 2021 by David Yuan, who has been investing, advising, and building technology companies for over 20 years.  Learn more at www.tidemarkcap.com.LinksFollow our host, Avanish SahaiLearn more about Tidemark

AI is transforming software development—redefining roles, creativity, and community, while challenging developers to embrace ambiguity, orchestrate specialized agents, and stay human through empathy and curiosity. Will AI make developers more creative, or will we forget how the machine really works under the hood?This week Dave, Esmee , Rob sit down with Scott Hanselman, VP Developer Community at Microsoft for a wildly energetic, deeply human, and brilliantly practical conversation about how AI is reshaping software development and what that means for creativity, careers, and all industries. TLDR00:30 – Scott Hanselman introduced as a special guest from Microsoft Ignite 2025.02:16 – Scott discusses how AI is fundamentally redesigning all industries.09:50 – Don't anthropomorphize AI, I want the computer from Star Trek!15:30 – Delegation: contrasting the roles of humans and agents.18:30 – The importance of supporting early career growth and learning.26:30 – Why specificity matters in AI and coding.35:30 – Making AI delightful and fun.45:30 – Always put humans first in AI development.46:00 – Each morning I think about lunch. GuestScott Hanselman: https://www.hanselman.com/The Hanselminutes Podcast: https://www.hanselman.com/podcasts with over 1025 podcasts! HostsDave Chapman: https://www.linkedin.com/in/chapmandr/Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman: https://www.linkedin.com/in/chapmandr/ SoundBen Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Tom Lillywhite, SVP of Sales at Naveo Commerce, outlines how the company delivers fast, flexible, and human-centered tech solutions for grocery retailers. Naveo Commerce positions itself as a lightweight, highly agile middleware layer that connects complex systems without the heavy lift of full-stack platforms. Tom explains how they help both large chains and independent retailers simplify e-commerce operations, streamline data workflows, and accelerate time to market. He dives into the value of clarity, human-focused design, and long-term partnerships in a market crowded with fragmented tools. The episode offers sharp insights into avoiding complexity traps, improving customer experience, and building tech that actually reflects real-world retail

BONUS: Testing as Measurement—Why Bug-Hunting Misses the Point With Tom Gilb and Simon Holzapfel The Revelation That Almost Caused a Car Crash "Tom said like 10 sentences in a row, kind of like a geometric proof, that just so blew my mind I almost drove off the road. I realized I had wasted hundreds of hours in boardrooms arguing about errors of which we were aware of perhaps 10%."   Simon shares the moment Tom's framework clicked for him. The insight? Traditional testing—finding bugs and defects—is the wrong focus entirely. It's a programmer's view of the world. Managers don't care about bugs; they care about results, about improvements in their business. Tom calls this shift moving from "testing" to "measurement of enhanced or increased value at every cycle." The American Toast Problem "How do we make toast in America? We burn the toast, and then we pay someone to scrape off the black bits off the bread."   Vasco invokes Deming's classic analogy to describe traditional software testing. The entire testing-at-the-end approach is fundamentally wasteful. Instead, Tom advocates for continuous measurement against quantified values. If you expected 3% progress toward your goals this week and didn't get it, you've learned something critical: your strategy needs to change. If you did get it, keep going with confidence. Four Questions at Every Checkpoint "Where are we going? Where are we now? Where should we have been at this point? And why is there a gap?"   Drawing from fighter pilot doctrine, these four questions should be asked at every micro-cycle—not just at quarterly reviews. Fighter pilots ask these questions every minute during critical missions, with clear abort criteria if answers are unacceptable. Most organizations have no abort criteria for their strategies at all, guaranteeing they'll discover failures far too late.   About Tom Gilb and Simon Holzapfel   Tom Gilb, born in the US, lived in London, and then moved to Norway in 1958. An independent teacher, consultant, and writer, he has worked in software engineering, corporate top management, and large-scale systems engineering. As the saying goes, Tom was writing about Agile before Agile was named. In 1976, Tom introduced the term "evolutionary" in his book Software Metrics, advocating for development in small, measurable steps. Today, we talk about Evo, the name Tom uses to describe his approach. Tom has worked with Dr. Deming and holds a certificate personally signed by him. You can listen to Tom Gilb's previous episodes here.    You can link with Tom Gilb on LinkedIn    Simon Holzapfel is an educator, coach, and learning innovator who helps teams work with greater clarity, speed, and purpose. He specializes in separating strategy from tactics, enabling short-cycle decision-making and higher-value workflows. Simon has spent his career coaching individuals and teams to achieve performance with deeper meaning and joy. Simon is also the author of the Equonomist newsletter on Substack. And you can listen to Simon's previous episodes on the podcast here.    You can link with Simon Holzapfel on LinkedIn.

What can Agile leaders learn from the Marines? In this episode, Tanner Wortham joins Brian to share how principles of military leadership—like building authority into the trenches, experimenting under pressure, and prioritizing shared mission over ego—map surprisingly well to modern Agile teams.

Midway through a 30-episodes-in-30-days podcast-to-book sprint, host Susan Diaz gets honest about what's working, what's hard, and how she's actually using AI as a thinking partner, draft machine, pattern spotter, and quiet project manager - plus what leaders can learn from this for their own AI experiments.   Episode summary This solo episode is a behind-the-scenes check-in from Susan's "completely unhinged" (her words) experiment to record 30 episodes in 30 days as the raw material for her next book. Nine episodes into twelve days, she talks candidly about fatigue, capacity, and why she refused to skip this recording even though she could have. She pulls back the curtain on the very practical ways she's using AI to structure ideas, draft assets, spot patterns across episodes, and manage the subtle project/energy load of a sprint like this. Then she zooms out to translate those lessons for founders and teams: why consistency beats intensity, why experiments are allowed to be small and honest, and why capacity has to be part of your AI strategy instead of an afterthought. Key takeaways This sprint is a live experiment in sustainability, not heroics. The goal isn't to "win" 30 episodes perfectly, it's to see what pace, support, and structure actually make ambitious AI-powered work sustainable for a real human. AI is a thinking partner first. Susan uses voice input in her LLM to dump messy thoughts, then asks it to shape them into outlines, angles, and talking points so she's never facing a blank page. (Pro tip: the built-in mic usually cuts off around five minutes - annoying but survivable.) Drafting support is where AI shines next. From show notes to extra research points to contextualising guest insights, custom GPTs help expand and refine ideas so she can focus on judgement and voice instead of first drafts. Pattern spotting turns episodes into chapters. By feeding multiple conversations into AI and asking for common threads or how ideas map to her core pillars, she can see where book chapters naturally want to live - and build something far more cohesive than her first, fully manual book. AI also helps with energy management. It quietly supports the admin around the sprint: drafting guest emails, summarizing notes, organizing ideas, and helping her see where there's too much on the go so she can re-plan. For organizations, three big lessons emerge: Consistency beats intensity - small, steady steps with AI are better than unsustainable bursts. Experiments can be small and honest - you don't need a centre of excellence to start. A one-hour training or a tiny workflow tweak counts. Capacity is strategy - pretending people have unlimited time and energy guarantees failure. Designing AI work around real capacity gives it a chance to stick. Good AI literacy lowers the cost of entry and raises the quality of thinking. Used well, AI doesn't replace your brain, it gives your best ideas a better chance of making it out of your head and into the world. Episode highlights [00:02] Setting the scene: a 30-episode sprint at the end of 2025 to get the book out of her head. [01:43] Nine episodes in twelve days, fatigue, and choosing to show up anyway. [03:21] Why the sprint mirrors how leaders feel about AI: "We know it matters… but keeping the pace is hard." [05:02] Using AI as a structure-building thinking partner via voice dumps and outlines. [05:30] The five-minute mic limit, word-vomit sessions, and how AI turns fuzz into flows. [07:02] Drafting support: research, context around guests, and custom GPTs for show assets. [07:44] Pattern spotting across episodes to find the book's real chapters and through-lines. [09:18] Why this AI-supported book will be "twice, thrice, ten times" better than the first one. [10:24] Energy and project management: emails, reflections, and organising all the moving pieces. [11:46] Lesson 1 – consistency over intensity for teams experimenting with AI. [13:29] Lesson 2 – small, honest experiments beat grand, delayed programs. [13:59] Lesson 3 – capacity as a core part of AI strategy, not a footnote. [15:01] Gentle prompts for listeners: where you're already experimenting, where AI can remove friction, and who your inside champions are. Use this episode as a mirror, not a mandate. Ask yourself and your team: Where are we already experimenting with AI, even in tiny ways? How could AI remove friction from that work instead of adding pressure? Who are our quiet inside champions - and what support or validation could we offer them this week? Answer even one of those honestly, and you're already moving from vague AI interest to real AI literacy. Connect with Susan Diaz on LinkedIn to get a conversation started. Agile teams move fast. Grab our 10 AI Deep Research Prompts to see how proven frameworks can unlock clarity in hours, not months. Find the prompt pack here.

BONUS: Continuous Strategy Engineering—Beyond Waterfall Planning With Tom Gilb and Simon Holzapfel Strategy Professors Are Decades Behind "The professors of strategy have no clue as to what Evo is. They are locked in decades ago, waterfall mode."   Tom's analysis is stark: the people teaching strategy in business schools haven't undergone the same agile transformation that software development experienced. They still think in terms of 5-year plans that get tested at the end—a guaranteed recipe for discovering failure too late. The alternative? Decompose any large strategy into weekly value delivery steps. And if you think that's impossible, ask any AI to do it for you—it will produce 52 reasonable weekly increments in about a minute. Why OKRs Aren't Enough for Complex Systems "If you're doing small-scale stuff that OKRs were designed for, like planning your personal work 14 days hence, OKRs are wonderful. If you're designing the air traffic control system for Europe, they're just too simple."   Tom distinguishes between tools appropriate for personal productivity and those needed for complex organizational strategy. OKRs force some thinking, which is good, but they weren't designed for—and have never been adapted to—large-scale systems engineering. His paper "What is Wrong with OKRs?" documents roughly 100 gaps between simple OKRs and what robust value requirements actually require. Check out Tom Gilb's paper on what's wrong with OKR's and how to fix it.  The Missing Alignment Layer "We have no mental model for most of leadership about how you actually align people around clear vision."   Simon introduces the concept of a Hoshin-Kanri "sprinkler" system—imagine strategic clarity flowing from the top and misting over everyone's desk as alignment. Most organizations lack anything resembling this. They have Moses descending from expensive consultant retreats with tablets, but no continuous two-way flow of strategic information. The result? Teams work hard on things that don't matter while critical values go unaddressed. About Tom Gilb and Simon Holzapfel   Tom Gilb, born in the US, lived in London, and then moved to Norway in 1958. An independent teacher, consultant, and writer, he has worked in software engineering, corporate top management, and large-scale systems engineering. As the saying goes, Tom was writing about Agile before Agile was named. In 1976, Tom introduced the term "evolutionary" in his book Software Metrics, advocating for development in small, measurable steps. Today, we talk about Evo, the name Tom uses to describe his approach. Tom has worked with Dr. Deming and holds a certificate personally signed by him. You can listen to Tom Gilb's previous episodes here.    You can link with Tom Gilb on LinkedIn    Simon Holzapfel is an educator, coach, and learning innovator who helps teams work with greater clarity, speed, and purpose. He specializes in separating strategy from tactics, enabling short-cycle decision-making and higher-value workflows. Simon has spent his career coaching individuals and teams to achieve performance with deeper meaning and joy. Simon is also the author of the Equonomist newsletter on Substack. And you can listen to Simon's previous episodes on the podcast here.    You can link with Simon Holzapfel on LinkedIn.

Building street cred is a valuable skill for any aspiring agile leader. I'll give you 3 ways to start building it and 3 sets of activities to help you get this going in the New Year!Agile leadership coaching is not dead. Folks still want to understand how to make things work and and do them better. This podcast will NEVER go away! I may run out of audio topics for Agile or Scrum Product Owners, but many of you who have been on this journey for a while have probably progressed or are progressing.So 2026 will be a HUGE year for Planet Product Owner. I can't wait to share with you what we are going to do so check back from time to time!Of course, if you like this episode or this podcast, be sure to tell a friend! If you don't like it, tell me!scott@planetproductowner.orgI wouldn't mind getting more reviews and more followers on TikTok and YouTube, so how about that...?Oh! And don't forget - Time is running out!Sign up for the upcoming 2 day virtual Certified Scrum Product Owner course here!And be sure to check out the new Planet Product Owner website! Lots of things coming in 2026!https://www.scrumalliance.org/courses-events/search/coursedetail?id=202512214

Escape Room Style Mobbing is a real collaboration pattern many teams run into, even if they do not have a name for it yet. In this episode of the Mob Mentality Show, we break down the spectrum between two very different mobbing modes: fast, noisy, interruption-heavy “escape room” mobbing and the quieter, deliberate, research-first approach some teams rely on instead. Across the conversation, they share concrete examples from dozens of mobs they have been part of over the years. You will hear what actually happens in high-energy mobs that optimize for speed, flow, and rapid experiments. You will also hear what shifts when a team leans into slow, deep thinking, deep learning, cautious change, and single-threaded communication. The episode digs into the real tradeoffs: - When interruptions accelerate discovery and when they create friction or waste - Why some teams thrive in a “pull everyone in now” environment while others feel overwhelmed or blocked by the noise - Why the same people might switch styles depending on context, psychological safety, or the kind of problem they are solving You will also hear how teams manage learning in each mode, how business expectations can map with the mob's behavior, how different personalities respond to high-octane collaboration, and why both styles can be healthy when used intentionally in the right context rather than by accident. If you work on Agile teams, practice Mob Programming, care about delivery flow, or you simply want to understand why your team's collaboration energy swings from chaotic to quiet, this episode gives you language and mental models you can use right away. FYI: Video and Show Notes: https://youtu.be/kZ9yH5Fibn4 

In every organization there's at least one person quietly doing wild things with AI - working faster, thinking bigger, and building their own personal AI stack. In this episode, host Susan Diaz explains how to find those secret power users, support them properly, and turn their experiments into an organizational advantage (without burning them out or making them your unpaid AI help desk). Episode summary This solo episode is a field guide to the people already living in your organization's AI future. Susan starts by painting the familiar picture of the "suspiciously fast" teammate whose work is cleaner, more strategic, and clearly powered by AI - even if no one has formally asked how. She names them for what they are: AI power users who have built quiet personal stacks and are effectively acting as your R&D lab for AI. From there, she walks through: How to spot these people through audits, language, manager input, and usage data. Why most organizations ignore or accidentally exploit them. A practical three-part framework - Recognition, Resourcing, Routing - to turn power users into supported AI champions instead of secret heroes headed for burnout. The equity implications of who gets seen as a "champion" and how to ensure your AI leaders reflect the diversity of your workforce. She closes with a simple champion blueprint and a piece of homework that any founder, leader, or manager can act on this week. Key takeaways You already have AI power users. The question isn't "Do they exist?" It's "Where are they, and what are we doing with them?" Power users are your unofficial R&D lab. They're not theorising about AI. They're testing it inside real workflows, finding what breaks, and figuring out how to prompt effectively in your specific context. They are rarely the most technical people. Your best champions are often people closest to the work - sales, customer-facing roles, operations - who are simply determined to figure it out. Not just IT. If you ignore them, three things happen: They get tired of doing extra work with no support. Their workflows stay trapped in their heads and personal accounts. Your organization misses the chance to scale what's working. Use the 3 Rs to turn power users into champions: Recognition - Name the role (AI Champions/Guides), make their contribution visible, and invite them into strategy and training conversations. Resourcing - Give them real time (10-20% of their week), adjust workload and goals, and reward them properly - ideally with money, training, and access. Routing - Turn personal hacks into shared assets: playbooks, Looms, internal training, and workflows embedded in L&D or ops. Connect - don't overload - your champions. Give them a direct line to IT, security, legal, and leadership so they can sanity-check ideas and inform strategy, without becoming the AI police. Equity matters here. If you only see loud voices and people closest to power, you'll miss quiet experimenters, women, and people of colour who may be building brilliant systems under the radar. Use multiple ways (surveys, nominations, self-identification) to surface a diverse group of champions. Champions must be guides, not gatekeepers. Their role is to make it easier and safer for others to experiment - not to punish or shut people down. A simple champion blueprint: identify → invite → define → resource → amplify. Done well, your champions become the bridge between today's experimentation and tomorrow's AI strategy. Episode highlights [00:02] The "suspiciously fast" colleague and what their behaviour is telling you. [02:00] Personal AI stacks and why Divers "swan dive backwards" into AI without waiting for permission. [03:37] The risk of ignoring power users: burnout, trapped knowledge, and missed scaling opportunities. [05:03] Why power users are effectively your AI research and development lab. [06:33] How to surface power users through better audit questions, open-ended prompts, and usage data. [07:25] Listening for phrases like "I built a system for that" and "I just play with this stuff because I'm a geek." [08:25] Using managers and platform data to spot a small cluster of heavy AI users. [09:37] The danger of quietly turning champions into unpaid AI help desks. [10:33] The 3 Rs: Recognition, Resourcing, and Rooting. [11:18] What real recognition looks like—naming, invitations to strategy, and public acknowledgement. [12:05] Resourcing: giving champions time, adjusting workloads, and updating job descriptions. [13:14] Rooting: creating playbooks, Looms, and embedding workflows into L&D and ops. [14:29] Connecting champions with IT, security, legal, and leadership. [15:45] The equity lens: who gets seen as a champion and who's missing. [17:16] The risk that women and marginalised groups get left behind and automated first. [18:30] Using surveys, nominations, and explicit invitations to diversify your champion group. [19:07] Why champions should be guides, not AI police or gatekeepers. [19:47] The 5-step "champion blueprint": identify, invite, define, resource, amplify. [22:15] Your homework: talk to one secret power user this week and ask how you can make space for their experimentation. Think of one person in your organization who's already that secret AI power user. This week, have a conversation that goes beyond "cool, can you do that for everyone?" and into "This is important. How can we make space for you to keep experimenting like this and help others learn from you?" That's the first step in building your AI champion program - whether or not you call it that yet. Connect with Susan Diaz on LinkedIn to get a conversation started. Agile teams move fast. Grab our 10 AI Deep Research Prompts to see how proven frameworks can unlock clarity in hours, not months. Find the prompt pack here. 

Stephen Clark of Ars Technica joins me to talk about a ton of stories in the news—Jared Isaacman was back in front of Congress, a few Starliner flights have been cut from the ISS manifest, Starship received environmental approval to proceed at SLC-37, Zhuque-3 almost stuck its first landing attempt, the Soyuz launch pad fell apart at Baikonur, and the Space Force has a new mission naming scheme.This episode of Main Engine Cut Off is brought to you by 32 executive producers—Matt, Fred, Kris, Natasha Tsakos, Josh from Impulse, Better Every Day Studios, Joakim, Joel, Ryan, The Astrogators at SEE, Tim Dodd (the Everyday Astronaut!), Heiko, Jan, Theo and Violet, Donald, Pat, Will and Lars from Agile, Lee, Russell, Joonas, Warren, Steve, Frank, Stealth Julian, David, and four anonymous—and hundreds of supporters.TopicsAuthor: Stephen Clark - Ars TechnicaNASA nominee appears before Congress, defends plans to revamp space agency - Ars TechnicaCongress warned that NASA's current plan for Artemis “cannot work” - Ars TechnicaNASA seeks a “warm backup” option as key decision on lunar rover nears - Ars TechnicaIt's official: Boeing's next flight of Starliner will be allowed to carry cargo only - Ars TechnicaA spectacular explosion shows China is close to obtaining reusable rockets - Ars TechnicaBefore a Soyuz launch Thursday someone forgot to secure a 20-ton service platform - Ars TechnicaRivals object to SpaceX's Starship plans in Florida—who's interfering with whom? - Ars TechnicaSpaceX on X: “We've received approval to develop Space Launch Complex-37 for Starship operations at Cape Canaveral Space Force Station. Construction has started. With three launch pads in Florida, Starship will be ready to support America's national security and Artemis goals as the world's…”Attack, defend, pursue—the Space Force's new naming scheme foretells new era - Ars TechnicaThe ShowLike the show? Support the show on Patreon or Substack!Email your thoughts, comments, and questions to anthony@mainenginecutoff.comFollow @WeHaveMECOFollow @meco@spacey.space on MastodonListen to MECO HeadlinesListen to Off-NominalJoin the Off-Nominal DiscordSubscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhereSubscribe to the Main Engine Cut Off NewsletterArtwork photo by Blue OriginWork with me and my design and development agency: Pine Works

BONUS: Impact Engineering—Finding Agile's Lost North Star With Tom Gilb and Simon Holzapfel The Clarity Problem: Why Organizations Start with "Fuzzy B*S*!" "Everybody seems to start from a position of fuzzy b*s*. Nice-sounding words. Management does it, professors do it, politicians do it. And they don't even feel very guilty about it."   Tom Gilb doesn't mince words when describing how most organizations define their objectives. The fundamental problem isn't a lack of ambition—it's a lack of clarity. When leaders are asked about their critical values like "extremely high security" or "employee happiness," they typically respond with circular definitions that provide no actionable direction. Tom's approach starts by exposing this gap and then demonstrating that any value—no matter how "soft" or intangible it seems—can be quantified. Using AI tools, he's shown clients over 1,400 different ways to measure human happiness alone. Why Agile Lost Its North Star "Agile's lost its North Star because the economic problems it was trying to solve within the organization are now mismatched with the digital world."   Simon Holzapfel offers a structural analysis: Agile developed primarily to allay the concerns of pre-digital capital—investors who needed reassurance that their money wouldn't disappear into failed projects. But today's digital economy operates differently. Capital now moves like a service (SaaS model), and innovation is fundamentally stochastic—you can't predict when breakthroughs will happen. Organizations using flow-focused tools when the real problem is value creation are applying yesterday's solutions to today's challenges. The First Step: Quantify Your Critical Values "If you ask AI to quantify employee happiness a hundred different ways, it will do it in one minute for free. So you can no longer be in denial."   The path forward starts with brutal honesty about what your organization actually cares about. Tom's approach involves:   Identifying the top 10 critical stakeholder values Defining clear scales of measure for each Establishing where you are now (status) Setting where you need to be to survive (tolerable level) Defining what success looks like (target/goal level)   This isn't about adding bureaucracy—it's about creating shared clarity that enables everyone to row in the same direction.   About Tom Gilb and Simon Holzapfel   Tom Gilb, born in the US, lived in London, and then moved to Norway in 1958. An independent teacher, consultant, and writer, he has worked in software engineering, corporate top management, and large-scale systems engineering. As the saying goes, Tom was writing about Agile before Agile was named. In 1976, Tom introduced the term "evolutionary" in his book Software Metrics, advocating for development in small, measurable steps. Today, we talk about Evo, the name Tom uses to describe his approach. Tom has worked with Dr. Deming and holds a certificate personally signed by him. You can listen to Tom Gilb's previous episodes here.    You can link with Tom Gilb on LinkedIn    Simon Holzapfel is an educator, coach, and learning innovator who helps teams work with greater clarity, speed, and purpose. He specializes in separating strategy from tactics, enabling short-cycle decision-making and higher-value workflows. Simon has spent his career coaching individuals and teams to achieve performance with deeper meaning and joy. Simon is also the author of the Equonomist newsletter on Substack. And you can listen to Simon's previous episodes on the podcast here.    You can link with Simon Holzapfel on LinkedIn.

Sprint Planning or Sprint Guessing?Welcome to sprint planning — that magical 90-minute meeting (that always becomes 3 hours) where:Developers turn into psychicsProduct managers become game show hostsProduct owners stare into a backlog like it's a crystal ballSound familiar?For many Agile teams, sprint planning isn't the crisp, focused ritual described in books. It's often more ambiguous, chaotic, and filled with guessing than anyone wants to admit.So… are you really planning? Or just giving your best estimate in a business suit?How to connect with AgileDad:- [website] ⁠https://www.agiledad.com/⁠- [instagram] ⁠https://www.instagram.com/agile_coach/⁠- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

This episode tackles the complex challenge of applying the hardware-centric clauses of ISO 13485 to Software as a Medical Device (SaMD). Adnan Ashfaq, founder of Simply Medica, joins Etienne Nichols to dissect how traditional standards intended for physical manufacturing must be creatively interpreted for the virtual world of software development, where apps update weekly and cloud-based systems evolve in real-time. The conversation zeroes in on the often-muddy areas of production and service provision (Clause 7.5), emphasizing that these clauses are far from non-applicable, requiring a "virtual manufacturing space" mindset.A significant focus is placed on the Software of Unknown Provenance (SOUP), treating these building blocks as purchased components that require robust supplier evaluation and validation, bridging Clause 7.5 (production) with Clause 7.4 (purchasing). The discussion extends to crucial concepts like the Software Bill of Materials (SBoM), the complexity of Agile vs. Waterfall approaches within the standard's framework, and the essential role of the new FDA Computer Software Assurance (CSA) guidance in risk assessment.Beyond production, the experts explore the application of resource management (Clause 6), specifically addressing infrastructure, contamination control (malware/ransomware), and the critical need for a well-documented Design Transfer to Production (Clause 7.3.8) evidenced by a complete software release package, including all 62304 requirements. The episode provides actionable insights for quality and compliance professionals struggling to maintain speed and innovation while strictly adhering to regulatory requirements.Key Timestamps01:45 - The changing landscape: Why traditional MedTech rules struggle with modern software updates.03:50 - Historical context of ISO 13485 and its non-distinction between hardware/software.05:05 - Starting Point: Clause 7.5 (Production and Service Provision) and the "Virtual Manufacturing Space" concept.06:20 - Unpacking Software of Unknown Provenance (SOUP) and its link to Clause 7.4 (Purchasing).08:35 - The necessity of validating the development environment (GitHub/GitLab) and building blocks.11:10 - Applying Clause 4.1.6 (Software Validation) to SOUP items and master validation plans.12:20 - Applicable vs. Non-Applicable Clauses: Sterilization/Cleanliness vs. Installation.13:55 - Clause 4.2.3 (Medical Device File) for SaMD: E-labels, UDI, System Architecture, and SBoM.16:30 - Cybersecurity controls and the manufacturer's responsibility for identifying state-of-the-art standards.17:35 - Defining "Production" for continuously updating software and managing significant vs. non-significant changes.20:15 - Clash of Standards: Agile development, ISO 13485, and the missing documentation for version control risk assessment.21:30 - Clause 6.3 & 6.4 (Resource & Work Environment): Looking at data security, access controls, and contamination (malware/ransomware).24:45 - Clause 7.3.8 (Design Transfer to Production): The need for a formal software release package and the importance of the Software Design Trace Matrix.26:00 - The 16 essential documents needed to meet IEC 62304 requirements.27:10 - Production controls when the user influences the outcome (customizable features,...

Should leaders ever say "don't bring me problems, bring me solutions"? Bob Galen and Josh Anderson challenge binary thinking in leadership. Learn when this controversial phrase empowers developing leaders versus when it shuts people down. Discover the concept of "problem support" and why great leaders aren't answer machines or gatekeepers. Josh shares how asking "what do you think?" unlocked dormant expertise. Bob explains why situational awareness matters more than rigid rules. Essential listening for leaders tired of oversimplified leadership advice and anyone judging leaders with black-and-white thinking.The LinkedIn post that inspired this discussionStay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

(04:11) Brought to you by JellyfishAI tools alone won't transform your engineering org. Jellyfish provides insights into AI tool adoption, cost, and delivery impact – so you can make better investment decisions and build teams that use AI effectively. See for yourself at jellyfish.co/platform/ai-impact.Are you managing your team the same way you did five years ago? With AI agents now part of the workforce, the old playbook no longer applies.In this episode, Jurgen Appelo, author of “Human Robot Agent” and creator of Management 3.0 and unFIX, challenges conventional thinking about management, organizational design, and the future of work in the AI era. He explains why rigid frameworks like Scrum are becoming bottlenecks to AI speed and why he believes we need to completely rethink how organizations operate.The conversation dives into the concept of creating “fast tracks” for AI agents while maintaining “slow tracks” for human collaboration. Jurgen also breaks down why team sizes are shrinking and why professionals must move beyond T-shaped skills to become M-shaped, multidisciplinary workers to remain relevant. He also shares his controversial take on why Scrum is “done” and why he trusts AI more than the average human when solving complex problems.Key topics discussed:Managing systems vs people in hybrid human-AI teamsWhy patterns beat frameworks for organization designWhy Scrum is done: adapting Agile for the AI eraM-shaped workers: the new multidisciplinary skillFast and slow tracks: redesigning work for AIWhy AI outperforms average humans at complex problemsCritical thinking as the essential leadership skillThe new optimal team size and dynamic reteamingTimestamps:(00:00:00) Trailer & Intro(00:02:20) Career Turning Points: Seven-Year Career Pivots(00:05:29) Origins of Management 3.0(00:08:31) Managing Systems, Not People(00:12:35) Everlasting Management Principles(00:17:21) unFIX: Patterns Over Frameworks(00:24:27) Core unFIX Patterns(00:31:39) Pipedrive Case Study: unFIX in Action(00:38:16) M3K: Merging Management 3.0 and unFIX(00:41:33) Skeptical Enthusiast: Balanced AI Perspective(00:47:18) Co-Creating with Humans and Machines(00:51:51) From T-Shaped to M-Shaped Workers(00:56:38) Why I Trust AI More Than Humans(01:00:19) Scrum is Done (Not Dead)(01:05:50) Redesigning Organizations for AI: Fast and Slow Tracks(01:09:25) 3 Tech Lead Wisdom_____Jurgen Appelo's BioJurgen Appelo is an author, speaker, and entrepreneur who helps leaders rewire their organizations for AI-driven leadership and autonomous digital agents. Recognized by Inc.com as a Top 50 Leadership Expert and Top 100 Leadership Speaker, he bridges opposing worldviews: human ingenuity and AI, leadership versus governance, stability with innovation, and individual growth fueling collective success. As founder of The unFIX Company (and previously founder of Management 3.0 and co-founder of Agile Lean Europe), Jurgen pioneers the future of work through stories, games, tools, and practices that challenge conventional thinking.Follow Jurgen:LinkedIn – linkedin.com/in/jurgenappeloWebsite – jurgenappelo.comSubstack – substack.jurgenappelo.com Human Robot Agent – https://jurgenappelo.com/pages/human-robot-agentLike this episode?Show notes & transcript: techleadjournal.dev/episodes/242.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Send us a textCheck us out at:  https://www.cisspcybertraining.com/Get access to 360 FREE CISSP Questions:  https://www.cisspcybertraining.com/offers/dzHKVcDB/checkoutGet access to my FREE CISSP Self-Study Essentials Videos:  https://www.cisspcybertraining.com/offers/KzBKKouvA single malicious insider flipped Disney menus to Wingdings and tampered with allergy labels—proof that weak offboarding and sloppy access can turn small privileges into big threats. We take that lesson and translate it into a practical roadmap for secure software: clear requirements, security controls in design, disciplined code reviews, honest UAT, and change management that prevents chaos and rollback roulette.From there, we compare the major development models through a security lens. Waterfall shines when predictability and compliance evidence are non‑negotiable, with strong documentation and defined testing phases. Spiral brings a risk-first mindset, iterating through planning, analysis, engineering, and evaluation so teams can learn early and pivot with purpose. Agile and DevSecOps embed security into user stories, definition of done, and sprint reviews, using short cycles, prioritized backlogs, and continuous testing to catch vulnerabilities before they calcify into technical debt.We also put structure around improvement. The Capability Maturity Model shows how to move from ad hoc heroics to standardized, measurable, and optimized practices that satisfy auditors and reduce incidents. The IDEAL model guides change itself—initiate with sponsorship, diagnose gaps, establish plans and metrics, act through implementation and training, and learn via feedback and retrospectives—so security improvements stick. Throughout, we share practical tips: how to weigh security controls against usability, why executive support unlocks real progress, and how to choose the right lifecycle for your risk, regulation, and release cadence.If you're preparing for the CISSP or leading teams that ship software, this is your playbook for building security into every step without slowing down what matters. Enjoyed the conversation? Subscribe, share with a teammate, and leave a review with your biggest SDLC win—or your most painful lesson.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Scott Smith: Empathy and Availability Define Excellent Product Ownership Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Always Present, Always Available, Always Curious "They are always present. They always make themselves available for team members that need them." - Scott Smith   Scott is currently working with a Product Owner who exemplifies what great PO collaboration looks like. This person is always present—not just physically but mentally engaged with the team's work and challenges. They make themselves available for team members who need them, responding actively on the team chat and interacting consistently.  What makes this PO stand out is their empathy and curiosity. Instead of being defensive when questions arise or challenges emerge, they lean into helping the team understand and solve problems. They show genuine curiosity about what the team is experiencing, asking questions and exploring solutions together rather than dictating answers.  This PO understands that their role isn't to be the smartest person in the room but to be the most available, most collaborative, and most curious. The result is a team that feels supported and empowered, with clear direction and someone who genuinely helps them answer the hard questions. Scott's experience with this PO demonstrates that presence, availability, empathy, and curiosity are the foundations of great Product Owner work.   Self-reflection Question: How present and available are you to your team, and do you approach their questions with curiosity or defensiveness? The Bad Product Owner: Never There When the Team Needs Direction "The PO was never present. The team had lack of clarity, and vision, and had no direction or someone who would help answer those questions." - Scott Smith   Scott has also experienced the opposite extreme—a Product Owner who was never present. This absence created a cascade of problems for the team. Without regular access to the PO, the team lacked clarity about priorities, vision, and direction. They had questions that went unanswered and decisions that couldn't be made.  The result was frustration and a team that couldn't move forward effectively. An absent PO creates a vacuum where uncertainty thrives. Teams end up making assumptions, second-guessing decisions, and feeling disconnected from the purpose of their work.  The lack of someone who can help answer strategic questions or provide guidance means the team operates in the dark, building things without confidence that they're building the right things. Scott's experience highlights a fundamental truth about Product Ownership: presence isn't optional.  Teams need a PO who shows up, engages, and stays connected to the work. Without that presence, even the most skilled team will struggle to deliver value because they can't align their efforts with the product vision and customer needs.   Self-reflection Question: If your team were asked whether you're present and available as a Product Owner or Scrum Master, what would they say?   [The Scrum Master Toolbox Podcast Recommends]

Live from the iconic Venetian in Las Vegas, we're rolling out an exclusive mini-series dedicated to AWS re:Invent 2025!Tune in as we sit down with AWS visionaries and take the pulse of the industry on everything shaping the future, Cloud innovation, GenAI, Agents, and the hottest trends making waves.And because what happens in Vegas doesn't always stay in Vegas, we'll spill the latest news, insider buzz, and a little Strip-side gossip to keep things spicy. Dave, Esmee, and Rob wrap up their final AWS re:Invent 2025 conversation with Mustafa Isik, Chief Technologist for Sovereignty at AWS, discussing digital sovereignty and its growing regional importance. They close the event with reflections from Matthew Gillard, co-founder of Cuidado Connect and co-host of Cloud Dialogues, along with insights from the team. TLDR01:29 – Meet Mustafa Isik and hear his keynote highlights04:05 – In-depth discussion with Mustafa31:35 – Exploring the line between science fiction and science fact36:26 – Introduction to Matthew Gillard38:55 – Matt shares his re:Invent reflections from a developer's perspective52:12 – The team looks back on re:Invent 20251:00:02 – The team's take on science fiction versus science fact GuestsMustafa Isik: https://www.linkedin.com/in/codesurgeon/Matt Gillard: https://www.linkedin.com/in/mattgillard/ https://cloud-dialogues.com/HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Live from the iconic Venetian in Las Vegas, we're rolling out an exclusive mini-series dedicated to AWS re:Invent 2025!Tune in as we sit down with AWS visionaries and take the pulse of the industry on everything shaping the future, Cloud innovation, GenAI, Agents, and the hottest trends making waves.And because what happens in Vegas doesn't always stay in Vegas, we'll spill the latest news, insider buzz, and a little Strip-side gossip to keep things spicy. Dave, Esmee, and Rob continue their discussion with Scott Mullins, MD Financial Services at AWS, on how the sector is rapidly embracing cloud, AI, automation, and real-time data to drive agility and stay compliant. TLDR00:30 – Meet Scott Mullins and hear about his re:Invent experience05:00 – Deep dive conversation with Scott25:56 – Fiiction with The Jetsons GuestScott Mullins: https://www.linkedin.com/in/escottmullins/ HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Scott Smith: Using MIRO to Build a Living Archive of Learning 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.   "We're in a servant leadership role. So, ask: is the team thriving? That's a huge indication of success." - Scott Smith   For Scott, success as a Scrum Master isn't measured by velocity charts or burn-down graphs—it's measured by whether the people are thriving. This includes everyone: the development team and the Product Owner.  As a servant leader, Scott's focus is on creating conditions where teams can flourish, and he has practical ways to gauge that health. Scott does a light touch check on a regular basis and a deeper assessment quarterly. Mid-sprint, he conducts what he calls a "vibe" check—a quick pulse to understand how people are feeling and what they need. During quarterly planning, the team retrospects and celebrates achievements from the past quarter, keeping and tracking actions to ensure continuous improvement isn't just talked about but lived. Scott's approach recognizes that success is both about the work being done and the people doing it. When teams feel supported, heard, and valued, the work naturally flows better. This people-first perspective defines what great servant leadership looks like in practice.   Self-reflection Question: How often do you check in on whether your team is truly thriving, and what specific indicators tell you they are? Featured Retrospective Format for the Week: MIRO as a Living History Museum "Use the multiple retros in the MIRO board as a shared history museum for the team." - Scott Smith   Scott leverages MIRO not just as a tool for running retrospectives but as a living archive of team learning and growth. He uses MIROVERSE templates to bring diversity to retrospective conversations, exploring the vast library of pre-built formats that offer themed and structured approaches to reflection. The magic happens when Scott treats each retrospective board not as a disposable artifact but as part of the team's shared history museum.  Over time, the accumulation of retrospective boards tells the story of the team's journey—what they struggled with, what they celebrated, what actions they took, and how they evolved. This approach transforms retrospectives from isolated events into a continuous narrative of improvement. Teams can look back at previous retros to see patterns, track whether actions were completed, and recognize how far they've come. MIRO becomes both the canvas for current reflection and the archive of collective learning, making improvement visible and tangible across time.   [The Scrum Master Toolbox Podcast Recommends]

How often do you catch yourself wishing you could keep up, lead better, or just breathe for a minute, only to feel like the world's changing too fast, and you're already behind? If you nodded along, you are SO not alone. Pete Van Overwalle, has coached leaders through all kinds of change, from big corporate shifts to building businesses from scratch. Did you know your adaptability intelligence (AQ) may be the key factor that keeps your people focused on possibility instead of just playing catch-up in times of crisis? We're tackling why adaptability matters right now more than ever, and what gets in the way of leaders who know it's important but "just don't have time." You'll walk away knowing the 3 markers of true adaptability, how to measure and build your own adaptability, plus fun, real-world strategies like integrating learning into your daily work and tapping into the power of play. By the end of this episode, you won't just understand your relationship with change, you'll be equipped to strengthen your adaptability, resilience, and confidence, no matter what challenges come your way.   Chapter Highlights (00:00) How Leaders Fall Behind Without Time to Learn: Addressing fears about keeping up with constant change (02:18) Strategies for Integrating Leadership Development Into Daily Work: Building learning into your routine (05:10) Why Adaptability is the Ultimate Leadership Skill: Pete's journey and what every leader needs right now (07:40) Adaptability Quotient Explained: What is the Adaptability Quotient (AQ) and why does it matter as much as IQ and EQ (12:13) The Three Markers of Real Adaptability: How they work together (14:18) Do Leaders Overestimate Their Own Adaptability? The risk of blind spots and assessment tips (17:29) Proven Strategies to Create Space for Inner Work (19:03) The Power of Play in Learning and Leadership: How using play boosts memory, engagement, and teamwork (22:53) How To Assess and Improve Your Own AQ: Tangible steps to measure and grow your adaptability (26:27) Agile vs. Adaptable Leadership: Understanding the crucial difference (27:31) Mindset, Grit, Resilience, and Unlearning: Key traits and habits for thriving in disruption (32:22) Final Empowering Message: Keep calm, adapt on, what changes for you and your team   Connect with Pete van Overwalle https://www.linkedin.com/in/pete-vanoverwalle/ https://omni-tp.com/   About Andrea Butcher Andrea Butcher is a visionary business leader, executive coach, and keynote speaker—she empowers leaders to gain clarity through the chaos by being MORE of who they already are. Her experiences—serving as CEO, leading at an executive level, and working in and leading global teams—make her uniquely qualified to support leadership and business success. She hosts the popular leadership podcast, Being [at Work] with a global audience of over 600,000 listeners and is the author of The Power in the Pivot (Red Thread Publishing 2022) and HR Kit for Dummies (Wiley 2023).   Connect with Andrea https://www.abundantempowerment.com/ Connect with Andrea Butcher on LinkedIn  https://www.linkedin.com/in/leaderdevelopmentcoach/   Abundant Empowerment Upcoming Events https://www.abundantempowerment.com/events            

Live from the iconic Venetian in Las Vegas, we're rolling out an exclusive mini-series dedicated to AWS re:Invent 2025!Tune in as we sit down with AWS visionaries and take the pulse of the industry on everything shaping the future, Cloud innovation, GenAI, Agents, and the hottest trends making waves.And because what happens in Vegas doesn't always stay in Vegas, we'll spill the latest news, insider buzz, and a little Strip-side gossip to keep things spicy. Dave, Esmee, and Rob kick off their conversation with Tanuja Randery, Managing Director for Europe, the Middle East & Africa (EMEA), diving into cloud innovation and the call to re:Accelerate Europe. TLDR00:49 – Introduction to Tanuja Randery03:29 – Keynote highlights with Tanuja and a deep-dive conversation31:00 – Imaginary tech and Star Trek GuestTanuja Randery: https://www.linkedin.com/in/tanuja-randery/ HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Live from the iconic Venetian in Las Vegas, we're rolling out an exclusive mini-series dedicated to AWS re:Invent 2025!Tune in as we sit down with AWS visionaries and take the pulse of the industry on everything shaping the future, Cloud innovation, GenAI, Agents, and the hottest trends making waves.And because what happens in Vegas doesn't always stay in Vegas, we'll spill the latest news, insider buzz, and a little Strip-side gossip to keep things spicy.Dave, Esmee, and Rob bring a double-feature conversation on industry innovation—first with Rob Boetticher, Global Technology Leader for Automotive and Manufacturing, followed by Howard Gefen, GM of the Energy and Utilities Industry Business Unit at AWS. TLDR00:42 – Rob Boetticher & Howard Gefen introduced02:00 – Rob's keynote highlights07:52 –  The future of automotive innovation with Rob23:32 – Tech fiction examples25:59 – Howard Gefen introduced28:00 – Howard's keynote highlights31:04 – Howard on the future of Energy and Utilities50:14 – Tech fiction examples GuestRob Boetticher: https://www.linkedin.com/in/robert-boetticher/Howard Gefen: https://www.linkedin.com/in/hgefen/ HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Scott Smith: Building a Coaching Service Where Survey Scores Become Living Improvement 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.   "Success is about feedback from coaching clients." - Scott Smith   Scott is tackling one of the most challenging aspects of organizational transformation: turning annual survey results into continuous improvement. Working with a domain of about 30 people, Scott is exploring how to create a coaching service that doesn't just react to once-a-year data but actively drives ongoing growth. The typical pattern in many organizations is familiar—conduct an annual survey, review the scores, maybe have a few discussions, and then wait another year. Scott is experimenting with a different approach.  He's setting up a coaching service that focuses on real-time feedback from the people being coached, making improvement a living practice rather than an annual event. The strategy starts with a pilot, testing the concept before scaling across the entire domain. Scott's measure of success is pragmatic and human-centered: feedback from coaching clients. Not abstract metrics or theoretical frameworks, but whether the people receiving coaching find value in what's being offered.  This approach reflects a fundamental principle of Agile coaching—start small, experiment, gather feedback, and iterate based on what actually works for the people involved. Scott is building improvement infrastructure that puts continuous learning at the center, transforming how organizations think about growth from an annual checkbox into an ongoing conversation.   Self-reflection Question: If you were to implement a coaching service in your organization, how would you measure its success beyond traditional survey scores?   [The Scrum Master Toolbox Podcast Recommends]

In this episode, I was lucky enough to interview Joel Montvelisky, co-founder and Chief Product Officer of PractiTest.Joel shares his unlikely journey from Costa Rica to the world of software testing. He talks about becoming a Cowboys fan in the 1970s, stumbling into QA because it paid slightly better than bartending, and eventually discovering that testing was far more than bug hunting—it was about improving products, reducing risk, and helping teams release with confidence. He reflects on the evolution of QA from the dot-com era to modern Agile and DevOps practices, the absence of formal QA education, and how conferences and early industry leaders helped him realize that testing is, in fact, a real profession with deep methodology and purpose.Joel also shares the origin story of PractiTest, born from a gap he saw between enterprise tools like Quality Center and teams struggling to manage testing with spreadsheets. He explains how the company's very first customer found them before they even had a way to accept payments, how founder-led sales carried them for years, and why meaningful testing requires both intention and mindfulness—something he practices personally to stay focused as someone diagnosed with ADHD later in life. Hear how Joel Montvelisky turned unexpected beginnings into a career shaping the future of QA in this episode of The First Customer!Guest Info:PractiTesthttps://www.practitest.com/Joel Montvelisky's LinkedInhttps://www.linkedin.com/in/joelm3/Connect with Jay on LinkedInhttps://www.linkedin.com/in/jayaigner/The First Customer Youtube Channelhttps://www.youtube.com/@thefirstcustomerpodcastThe First Customer podcast websitehttps://www.firstcustomerpodcast.comFollow The First Customer on LinkedInhttp://www.linkedin.com/company/the-first-customer-podcast/

Are You Protecting Your Team Against the Right Thing? - Mike CohnA lot has been written and said about the responsibility of a Scrum Master to protect the team.Examples of protecting the team typically involve running interference with well-meaning but overzealous product owners, stakeholders, and managers. Teams run into trouble all the time from people who want it all now or who keep adding more work in the middle or a sprint. Scrum Masters keep all that noise away so that the team can focus on delivery.But if you are only focused on problems coming from squeaky wheels, you're missing one of the biggest dangers out there: complacency.Agile is about continually getting better. I don't care how good a team is today; if they aren't better a year from now, they're not agile.Complacency can creep in when a team sees some initial improvement from adopting an agile approach. Team members will notice how improved they are and think that's enough.But there's almost always room for further improvement.Some teams become complacent about their process and stop looking for ways to deliver more value each iteration. Still other teams become complacent in seeking out new engineering practices that could make the team even better.Protect your team from complacency by setting high expectations and encouraging the team to set even higher expectations of their own performance.Teams that refuse to settle for the status quo are teams that advance from good to great.How to connect with AgileDad:- [website] ⁠https://www.agiledad.com/⁠- [instagram] ⁠https://www.instagram.com/agile_coach/⁠- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

Live from the iconic Venetian in Las Vegas, we're rolling out an exclusive mini-series dedicated to AWS re:Invent 2025!Tune in as we sit down with AWS visionaries and take the pulse of the industry on everything shaping the future, Cloud innovation, GenAI, Agents, and the hottest trends making waves.And because what happens in Vegas doesn't always stay in Vegas, we'll spill the latest news, insider buzz, and a little Strip-side gossip to keep things spicy. Dave, Esmee, and Rob continue their conversation with Tim Murnin, Head of Industry & Partner Strategy at AWS, exploring the evolving role of the CIO, adoption delays, and how trends vary across different sectors. TLDR00:36 – Welcome back with Tim Murnin and the team's highlights from the AWS re:Invent 2025 keynote08:04 – In-depth conversation with Tim, exploring key insights32:05 – Where fact meets fiction, including a look at the flying carGuestTim Murnin: https://www.linkedin.com/in/timmurnin/ HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Live from the iconic Venetian in Las Vegas, we're rolling out an exclusive mini-series dedicated to AWS re:Invent 2025!Tune in as we sit down with AWS visionaries and take the pulse of the industry on everything shaping the future, Cloud innovation, GenAI, Agents, and the hottest trends making waves. And because what happens in Vegas doesn't always stay in Vegas, we'll spill the latest news, insider buzz, and a little Strip-side gossip to keep things spicy. Dave, Esmee, and Rob start their conversation with Chandra Pinapala, Director Global Strategic Partners, to explore why strong partnerships are essential for success in Cloud and AI. TLDR00:40 – Back in Las Vegas with highlights from the AWS re:Invent 2025 keynote12:07 – Meet Chandra Pinapala and dive deep into the conversation35:10 – A playful leap into the world of fiction GuestChandra Pinapala: https://www.linkedin.com/in/chandrapinapala/ HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

In this fascinating episode, we dive deep into the world of agile hardware development with Gregor Gross, a civil engineer who runs Alpha-board, a PCB design service company in Berlin, Germany. Gregor shares his unique perspective on applying agile principles to hardware projects, where you can't just hit compile and get a new increment.We explore the practical challenges of agile hardware development, from structuring contracts differently to breaking complex PCBs into testable modules and shields. Gregor discusses the importance of mixed hardware-software teams, the role of automated documentation, and why his engineers resist pair programming despite its proven benefits. The conversation also touches on the cultural barriers to adopting agile practices in traditional hardware companies and the innovative approaches needed to make agile hardware development work in a service provider context.Key Topics[02:30] Introduction to Alpha-board and agile hardware development services[05:15] Defining agile principles: functionality-focused development and prioritization[12:45] Contract challenges: moving from fixed-price to hourly service contracts[18:20] Practical agile hardware: breaking PCBs into testable modules and shields[25:10] Mixed teams and automated documentation for hardware-software collaboration[32:40] The pair programming experiment: better results but team resistance[38:55] Customer expectations and the need for end-user access in agile projects[44:30] Version control and Git integration for hardware design workflowsNotable Quotes"We are probably the only service provider in Germany that offers agile hardware development because I don't see so many people speaking about it." — Gregor Gross"Software is soft, hardware is hard. I was waiting to say that." — Gregor Gross"My experience from pairing was they work harder. They feel like they observe themselves... but there wasn't any mistakes. And actually they themselves said they were surprised by how much they did because they did more than twice what they expected." — Gregor Gross"It's better to have different shields and modules that have some of the functionality. And so you can start iterating through these functionalities and test them." — Gregor GrossResources MentionedAlpha-board - Gregor's PCB design and agile hardware development service companyZephyr OS - Real-time operating system mentioned for prototyping with sample boardsKiCad - Open source EDA tool recommended for mixed teams and transparencyAndrew Greenberg's KiCon Presentation - Presentation on schematic style guides for better readability You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click hereAre you looking for embedded-focused trainings? Head to https://agileembedded.academy/Ryan Torvik and Luca have started the Embedded AI podcast, check it out at https://embeddedaipodcast.com/

In this Mob Mentality Show episode, we sit down with Abid Qureshi for a candid and eye-opening look at what Agile Software Development was meant to be versus what the industry turned it into. If you've ever wondered why “Agile” feels bloated today, why teams still struggle to adapt quickly, or why universities are still teaching outdated models like Waterfall, this conversation will hit home. Abid shares his perspective on why the original movement focused on lightweight methods, experimentation, and uncovering better ways of developing software. He explains how the software industry drifted toward heavyweight processes and off-the-shelf frameworks, and what gets lost when organizations treat Agile as a set of fixed best practices (independent of a code context) instead of an ever evolving software craft. He also challenges long-held assumptions about technical excellence, design, and the true sources of agility in modern software development. We dig into: - The contrast between early agile software development and what “Agile” represents today. - Why the title “Agile Manifesto” is misleading and what the document was actually about. - How advances in technology, object-oriented programming, automated testing, and continuous integration made genuine agility possible. - Why real adaptability comes from reducing the cost of change, not adding more process. - The danger of scaling up bureaucracy instead of scaling down and improving engineering practices. - How non-technical contributors sometimes unlock unconventional, high-value ideas that technical experts overlook. - Why many higher education programs still teach waterfall-style thinking and how that hurts new developers entering the industry. - The missed opportunity for universities to lead innovation in software development instead of echoing outdated industry norms. If you care about XP, Lean thinking, software craftsmanship, technical excellence, or getting back to the heart of agility, this episode offers a practical and refreshing reset. Abid's stories and insights challenge the assumptions that hold teams back and point toward a more grounded, engineering-driven approach to modern software development. Video and Show Notes: https://youtu.be/nJI-veSJdkQ  

Scott Smith: Why Great Scrum Masters Create Space for Breaks 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.   "Think of the people involved. Put yourself in the shoes of the other." - Scott Smith   Scott found himself in the middle of rising tension as voices escalated between the Product Owner and the development team. The PO was harsh, emotions were running high, and the conflict was intensifying with each exchange. In that moment, Scott knew he had to act.  He stepped in with a simple but powerful reminder: "We're on the same team." That pause—that momentary break—allowed everyone to step back and reset. Both the PO and the team members later thanked Scott for his intervention, acknowledging they needed that space to cool down and refocus on their shared outcome.  Scott's approach centers on empathy and perspective-taking. He emphasizes thinking about the people involved and putting yourself in their shoes. When tensions rise, sometimes the most valuable contribution a Scrum Master can make is creating space for a break, reminding everyone of the shared goal, and helping teams focus on the outcome rather than the conflict. It's not about taking sides—it's about serving the team by being the calm presence that brings everyone back to what matters most.   Self-reflection Question: When you witness conflict between team members or between the team and Product Owner, do you tend to jump in immediately or create space for the parties to find common ground themselves? Featured Book of the Week: An Ex-Manager Who Believed "It was about having someone who believed in me." - Scott Smith   Scott's most influential "book" isn't printed on pages—it's a person. After spending 10 years as a Business Analyst, Scott decided to take the Professional Scrum Master I (PSM I) course and look for a Scrum Master position. That transition wasn't just about skills or certification; it was about having an ex-manager who inspired him to chase his goals and truly believed in him. This person gave Scott the confidence to make a significant career pivot, demonstrating that sometimes the most powerful catalyst for growth is someone who sees your potential before you fully recognize it yourself. Scott's story reminds us that great leadership isn't just about managing tasks—it's about inspiring people to reach for goals they might not have pursued alone. The belief and encouragement of a single person can change the trajectory of someone's entire career.   [The Scrum Master Toolbox Podcast Recommends]

Welcome to another episode of Our Agile Tales, Navigating World Crises: The Agile-Law-AI Alliance in Action!In this continuation of our conversation with Ondřej Dvořák, CEO of AgiLawyer and COPS Solutions, we go deeper into how you actually run and scale an agile, cross-border legal-aid initiative in the middle of a war. If the first episode was about launching Linking Help, this one is about surviving the scale-up.Ondřej walks us through the messy, very human side of scaling legal aid for Ukrainian refugees: from dealing with thousands of requests in a language he didn't speak, to building a “clearing desk” and help desk function led by Ukrainian lawyers, to teaching volunteer lawyers across multiple countries how to work in a pull-based, Kanban system when they're used to command-and-control and assigned work.We explore how culture and ways of working showed up in very concrete ways - why France “just got it” from day one, while countries like Romania needed more support and education before becoming top performers. Ondřej talks about how simplifying the Kanban system (fewer columns, fewer concepts, one clear task: connect the person to a lawyer) was crucial to onboarding busy legal professionals quickly in a crisis.We also dig into scaling patterns: how they expanded country by country, used “early adopter” lawyers to grow local networks, and centralized the help desk while keeping case work decentralized. From there, the conversation shifts to constraints: the difficulty of fundraising for legal aid (which is hard to “picture”), differences in how pro bono is treated across jurisdictions, and the legal and ethical challenges of using AI to support legal work, especially questions of accountability and liability when AI-generated guidance might be wrong.If you're interested in how Agile, Kanban, and crisis-driven decision-making play out in the real world, across borders, cultures, and regulatory systems, then this episode is a rich case study in making agility practical, humane, and scalable beyond software.Episode Outline00:00 Introduction & recap of Part 101:05 The language barrier: Ukrainian requests and the need for a “clearing desk”07:58 Designing the help desk workflow10:45 Teaching lawyers a new way of working: pull vs. command-and-control13:12 Culture in action: why France “just worked” and Romania needed more coaching16:00 Simplifying Kanban for legal work18:48 Scaling country by country: early adopters, bar associations, and building local communities22:10 Centralized help desk, decentralized service: funding, hiring Ukrainian students, and managing demand24:55 Business model and funding constraints: the challenge of raising money for legal aid26:10 Legal and AI constraints: pro bono differences, AI-assisted legal opinions, and accountability28:30 Reflections on crisis as a catalyst and the future of global, AI-supported legal aid29:07 ConclusionAbout Ondrej DvorakOndřej is the co-founder of Linking Help, a nonprofit that mobilized legal aid for Ukrainian refugees using Scrum and Kanban to coordinate real-time support. It's a powerful story of how agility can make a real difference in humanitarian crises—far beyond the domain of business. Andre's work shows how Agile thinking can help even the most traditional sectors become more humane, responsive, and resilient. You can follow Ondřej on LinkedIn at https://www.linkedin.com/in/ondrej-dvorak-agile/Visit us at https://www.ouragiletales.com/about

Scott Smith: The Spotlight Failure That Taught a Silent Lesson About Recognition 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.   "Not everybody enjoys the limelight and being called out, even for great work." - Scott Smith   Scott was facilitating a multi-squad showcase with over 100 participants, and everything seemed to be going perfectly. Each squad had their five-minute slot to share achievements from the sprint, and Scott was coordinating the entire event. When one particular team member delivered what Scott considered fantastic work, he couldn't help but publicly recognize them during the introduction.  It seemed like the perfect moment to celebrate excellence in front of the entire organization. But then his phone rang. The individual he had praised was unhappy—really unhappy. What Scott learned in that moment transformed his approach to recognition forever. The person was quiet, introverted, and conservative by nature.  Being called out without prior notice or permission in front of 100+ people wasn't a reward—it was uncomfortable and unwelcome. Scott discovered that even positive recognition requires consent and awareness of individual preferences. Some people thrive in the spotlight, while others prefer their contributions to be acknowledged privately. The relationship continued well afterward, but the lesson stuck: check in with individuals before publicly recognizing them, understanding that great coaching means respecting how people want to be celebrated, not just that they should be celebrated.   Self-reflection Question: How do you currently recognize team members' achievements, and have you asked each person how they prefer to be acknowledged for their contributions?   [The Scrum Master Toolbox Podcast Recommends]

What happens when you've built an amazing team and then have to leave? Bob Galen and Josh Anderson explore the guilt, emotion, and complexity of leadership transitions. Learn why good leaders struggle most with leaving while bad leaders walk away without a second thought. Josh shares his gut-wrenching experience leaving Dude Solutions, Bob discusses how to maintain relationships through transitions, and both hosts reframe departure around legacy and the coaching tree concept. If leaving your team hurts, you probably did it right. Essential listening for any leader facing a career transition. Stay Connected and Informed with Our NewslettersJosh Anderson's "Leadership Lighthouse"Dive deeper into the world of Agile leadership and management with Josh Anderson's "Leadership Lighthouse." This bi-weekly newsletter offers insights, tips, and personal stories to help you navigate the complexities of leadership in today's fast-paced tech environment. Whether you're a new manager or a seasoned leader, you'll find valuable guidance and practical advice to enhance your leadership skills. Subscribe to "Leadership Lighthouse" for the latest articles and exclusive content right to your inbox.Subscribe hereBob Galen's "Agile Moose"Bob Galen's "Agile Moose" is a must-read for anyone interested in Agile practices, team dynamics, and personal growth within the tech industry. The newsletter features in-depth analysis, case studies, and actionable tips to help you excel in your Agile journey. Bob brings his extensive experience and thoughtful perspectives directly to you, covering everything from foundational Agile concepts to advanced techniques. Join a community of Agile enthusiasts and practitioners by subscribing to "Agile Moose."Subscribe hereDo More Than Listen:We publish video versions of every episode and post them on our YouTube page.Help Us Spread The Word: Love our content? Help us out by sharing on social media, rating our podcast/episodes on iTunes, or by giving to our Patreon campaign. Every time you give, in any way, you empower our mission of helping as many agilists as possible. Thanks for sharing!

BONUS: When AI Knows Your Emotional Triggers Better Than You Do — Navigating Mindfulness in the AI Age In this thought-provoking conversation, former computer engineer and mindfulness leader Mo Edjlali explores how AI is reshaping human meaning, attention, and decision-making. We examine the critical question: what happens when AI knows your emotional triggers better than you know yourself? Mo shares insights on remaining sovereign over our attention, avoiding dependency in both mindfulness and technology, and preparing for a world where AI may outperform us in nearly every domain. From Technology Pioneer to Mindfulness Leader "I've been very heavily influenced by technology, computer engineering, software development. I introduced DevOps to the federal government. But I have never seen anything change the way in which human beings work together like Agile." — Mo Edjlali   Mo's journey began in the tech world — graduating in 1998, he was on the front line of the internet explosion. He remembers the days before the internet, watched online multiplayer games emerge in 1994, and worked on some of the most complicated tech projects in federal government. Technology felt almost like magic, advancing at a logarithmic rate faster than anything else. But when Mo discovered mindfulness practices 12-15 years ago, he found something equally transformative: actual exercises to develop emotional intelligence and soft skills that the tech world talked about but never taught. Mindfulness provided logical, practical methods that didn't require "woo-woo" beliefs — just practice that fundamentally changed his relationship with his mind. This dual perspective — tech innovator and mindfulness teacher — gives Mo a unique lens for understanding where we're headed. The Shift from Liberation to Dependency "I was fortunate enough, the teachers I was exposed to, the mentality was very much: you're gonna learn how to meditate on your own, in silence. There is no guru. There is no cult of personality." — Mo Edjlali   Mo identifies a dangerous drift in the mindfulness movement: from teaching independence to creating dependency. His early training, particularly a Vipassana retreat led by S.N. Goenka, modeled true liberation — you show up for 10 days, pay nothing, receive food and lodging, learn to meditate, then donate what you can at the end. Critically, you leave being able to meditate on your own without worshiping a teacher or subscribing to guided meditations. But today's commercialized mindfulness often creates the opposite: powerful figures leading fiefdoms, consumers taught to listen to guided meditations rather than meditate independently. This dependency model mirrors exactly what's happening with AI — systems designed to make us rely on them rather than empower our own capabilities. Recognizing this parallel is essential for navigating both fields wisely. AI as a New Human Age, Not Just Another Tool "With AI, this is different. This isn't like mobile computing, this isn't like the internet. We're entering a new age. We had the Bronze Age, the Iron Age, the Industrial Age. When you enter a new age, it's almost like knocking the chess board over, flipping the pieces upside down. We're playing a new game." — Mo Edjlali   Mo frames AI not as another technology upgrade but as the beginning of an entirely new human age. In a new age, everything shifts: currency, economies, government, technology, even religions. The documentary about the Bronze Age collapse taught him that when ages turn over, the old rules no longer apply. This perspective explains why AI feels fundamentally different from previous innovations. ChatGPT 2.0 was interesting; ChatGPT 3 blew Mo's mind and made him realize we're witnessing something unprecedented. While he's optimistic about the potential for sustainable abundance and extraordinary breakthroughs, he's also aware we're entering both the most exciting and most frightening time to be alive. Everything we learned in high school might be proven wrong as AI rewrites human knowledge, translates animal languages, extends longevity, and achieves things we can't even imagine. The Mental Health Tsunami and Loss of Purpose "If we do enter the age of abundance, where AI could do anything that human beings could do and do it better, suddenly the system we have set up — where our purpose is often tied to our income and our job — suddenly, we don't need to work. So what is our purpose?" — Mo Edjlali   Mo offers a provocative vision of the future: a world where people might pay for jobs rather than get paid to work. It sounds crazy until you realize it's already happening — people pay $100,000-$200,000 for college just to get a job, politicians spend millions to get elected. If AI handles most work and we enter an age of abundance, jobs won't be about survival or income — they'll be about meaning, identity, and social connection. This creates three major crises Mo sees accelerating: attacks on our focus and attention (technology hijacking our awareness), polarization (forcing black-and-white thinking), and isolation (pushing us toward solo experiences). The mental health tsunami is coming as people struggle to find purpose in a world where AI outperforms them in domain after domain. The jobs will change, the value systems will shift, and those without tools for navigating this transformation will suffer most. When AI Reads Your Mind "Researchers at Duke University had hooked up fMRI brain scanning technology and took that data and fed it into GPT 2. They were able to translate brain signals into written narrative. So the implications are that we could read people's minds using AI." — Mo Edjlali   The future Mo describes isn't science fiction — it's already beginning. Three years ago, researchers used early GPT to translate brain signals into written text by scanning people's minds with fMRI and training AI on the patterns. Today, AI knows a lot about heavy users like Mo through chat conversations. Tomorrow, AI will have video input of everything we see, sensory input from our biometrics (pulse, heart rate, health indicators), and potentially direct connection to our minds. This symbiotic relationship is coming whether we're ready or not. Mo demonstrates this with a personal experiment: he asked his AI to tell him about himself, describe his personality, identify his strengths, and most powerfully — reveal his blind spots. The AI's response was outstanding, better than what any human (even his therapist or himself) could have articulated. This is the reality we're moving toward: AI that knows our emotional triggers, blind spots, and patterns better than we do ourselves. Using AI as a Mirror for Self-Discovery "I asked my AI, 'What are my blind spots?' Human beings usually won't always tell you what your blind spots are, they might not see them. A therapist might not exactly see them. But the AI has... I've had the most intimate kind of conversations about everything. And the response was outstanding." — Mo Edjlali   Mo's approach to AI is both pragmatic and experimental. He uses it extensively — at the level of teenagers and early college students who are on it all the time. But rather than just using AI as a tool, he treats it as a mirror for understanding himself. Asking AI to identify your blind spots is a powerful exercise because AI has observed all your conversations, patterns, and tendencies without the human limitations of forgetfulness or social politeness. Vasco shares a similar experience using AI as a therapy companion — not replacing his human therapist, but preparing for sessions and processing afterward. This reveals an essential truth: most of us don't understand ourselves that well. We're blind navigators using an increasingly powerful tool. The question isn't whether AI will know us better than we know ourselves — that's already happening. The question is how we use that knowledge wisely. The Danger of AI Hijacking Our Agency "There's this real danger. I saw that South Park episode about ChatGPT where his wife is like, 'Come on, put the AI down, talk to me,' and he's got this crazy business idea, and the AI keeps encouraging him along. It's a point where he's relying way too heavily on the AI and making really poor decisions." — Mo Edjlali   Not all AI use is beneficial. Mo candidly admits his own mistakes — sometimes leaning into AI feedback over his actual users' feedback for his Meditate Together app because "I like what the AI is saying." This mirrors the South Park episode's warning about AI dependency, where the character's AI encourages increasingly poor decisions while his relationships suffer. Social media demonstrates this danger at scale: AI algorithms tuned to steal our attention and hijack our agency, preventing us from thinking about what truly matters — relationships and human connection. Mo shares a disturbing story about Zoom bombers disrupting Meditate Together sessions, filming it, posting it on YouTube where it got 90,000 views, with comments thanking the disruptors for "making my day better." Technology created a cannibalistic dynamic where teenagers watched videos of their mothers, aunts, and grandmothers being harassed during meditation. When Mo tried to contact Google, the company's incentive structure prioritized views and revenue over human decency. Technology combined with capitalism creates these dangerous momentum toward monetizing attention at any cost. Remaining Sovereign Over Your Attention "Traditionally, mindfulness does an extraordinary job, if you practice right, to help you regain your agency of your focus and concentration. It takes practice. But reading is now becoming a concentration practice. It's an actual practice." — Mo Edjlali   Mo identifies three major symptoms affecting us: attacks on focus/attention, polarization into black-and-white thinking, and isolation. Mindfulness practices directly counter all three — but only if practiced correctly. Training attention, focus, and concentration requires actual practice, not just listening to guided meditations. Mo offers practical strategies: reading as concentration practice (asking "does anyone read anymore?" recognizing that sustained reading now requires deliberate effort), turning off AirPods while jogging or driving to find silence, spending time alone with your thoughts, and recognizing that we were given extraordinary power (smartphones) with zero training on how to be aware of it. Older generations remember having to rewind VHS tapes — forced moments of patience and stillness that no longer exist. We need to deliberately recreate those spaces where we're not constantly consuming entertainment and input. Dialectic Thinking: Beyond Polarization "I saw someone the other day wear a shirt that said, 'I'm perfect the way I am.' That's one-dimensional thinking. Two-dimensional thinking is: you're perfect the way that you are, and you could be a little better." — Mo Edjlali   Mo's book OpenMBSR specifically addresses polarization by introducing dialectic thinking — the ability to hold paradoxes and seeming contradictions simultaneously. Social media and algorithms push us toward one-dimensional, black-and-white thinking: good/bad, right/wrong, with me/against me. But reality is far more nuanced. The ability to think "I'm perfect as I am AND I can improve" or "AI is extraordinary AND dangerous" is essential for navigating complexity. This mirrors the tech world's embrace of continuous improvement in Agile — accepting where you are while always pushing for better. Chess players learned this years ago when AI defeated humans — they didn't freak out, they accepted it and adapted. Now AI in chess doesn't just give answers; it helps humans understand how it arrived at those answers. This partnership model, where AI coaches us through complexity rather than simply replacing us, represents the healthiest path forward. Building Community, Not Dependency "When people think to meditate, unfortunately, they think, I have to do this by myself and listen to guided meditation. I'm saying no. Do it in silence. If you listen to guided meditation, listen to guided meditation that teaches you how to meditate in silence. And do it with other people, with intentional community." — Mo Edjlali   Mo's OpenMBSR initiative explicitly borrows from the Agile movement's success: grassroots, community-centric, open source, transparent. Rather than creating fiefdoms around cult personalities, he wants mindfulness to spread organically through communities helping communities. This directly counters the isolation trend that technology accelerates. Meditate Together exists specifically to create spaces where people meditate with other human beings around the world, with volunteer hosts holding sessions. The model isn't about dependency on a teacher or platform — it's about building connection and shared practice. This aligns perfectly with how the tech world revolutionized collaborative work through Agile and Scrum: transparent, iterative, valuing individuals and interactions. The question for both mindfulness and AI adoption is whether we'll create systems that empower independence and community, or ones that foster dependency and isolation. Preparing for a World Where AI Outperforms Humans "AI is going to need to kind of coach us and ease us into it, right? There's some really dark, ugly things about ourselves that could be jarring without it being properly shared, exposed, and explained." — Mo Edjlali   Looking at his children, Mo wonders what tools they'll need in a world where AI may outperform humans in nearly every domain. The answer isn't trying to compete with AI in calculation, memory, or analysis — that battle is already lost. Instead, the essential human skills become self-awareness, emotional intelligence, dialectic thinking, community building, and maintaining agency over attention and decision-making. AI will need to become a coach, helping humans understand not just answers but how it arrived at those answers. This requires AI development that prioritizes human growth over profit maximization. It also requires humans willing to do the hard work of understanding themselves — confronting blind spots, managing emotional triggers, practicing concentration, and building genuine relationships. The mental health tsunami Mo predicts isn't inevitable if we prepare now by teaching these skills widely, building community-centric systems, and designing AI that empowers rather than replaces human wisdom and connection.   About Mo Edjlali   Mo Edjlali is a former computer engineer, and also the founder and CEO of Mindful Leader, the world's largest provider of Mindfulness-Based Stress Reduction training. Mo's new book Open MBSR: Reimagining the Future of Mindfulness explores how ancient practices can help us navigate the AI revolution with awareness and resilience.   You can learn more about Mo and his work at MindfulLeader.org, check out Meditate Together, and read his articles on AI's Mind-Reading Breakthrough and AI: Not Another Tool, but a New Human Age.

Daniel is joined by Chris Morrison, vice president of product marketing at Agile Analog, the customizable analog IP company. Chris has over 18 years' experience developing strong relationships with key partners across the semiconductor industry and delivering innovative analog, digital, power management and audio products.… Read More

Charu Roy, Chief Product Officer at Enlil, shares her extensive journey in the software industry, which began in the late 1980s and evolved into her leadership role in medtech. Charu discusses her role at Enlil, where she oversees the development of an AI-powered platform to enhance medical device lifecycle management. She emphasizes the importance of understanding customer needs, fostering team potential, and ensuring cybersecurity in medtech software solutions. With profound insights on her career growth, leadership style, and the technological advancements propelling the industry forward, Charu's story is an inspiring tale of innovation and dedication to improving lives.  Guest links: https://enlil.com/ |  https://www.linkedin.com/company/enlil-inc/ Charity supported: ASPCA Interested in being a guest on the show or have feedback to share? Email us at theleadingdifference@velentium.com.  PRODUCTION CREDITS Host & Editor: Lindsey Dinneen Producer: Velentium Medical   EPISODE TRANSCRIPT Episode 069 - Charu Roy [00:00:00] Lindsey Dinneen: Hi, I'm Lindsey and I'm talking with MedTech industry leaders on how they change lives for a better world. [00:00:09] Diane Bouis: The inventions and technologies are fascinating and so are the people who work with them. [00:00:15] Frank Jaskulke: There was a period of time where I realized, fundamentally, my job was to go hang out with really smart people that are saving lives and then do work that would help them save more lives. [00:00:28] Diane Bouis: I got into the business to save lives and it is incredibly motivating to work with people who are in that same business, saving or improving lives. [00:00:38] Duane Mancini: What better industry than where I get to wake up every day and just save people's lives. [00:00:42] Lindsey Dinneen: These are extraordinary people doing extraordinary work, and this is The Leading Difference. Hello and welcome back to another episode of The Leading Difference podcast. I'm your host Lindsey, and today I'm absolutely delighted to introduce you to Charu Roy. Charu is the Chief Product Officer at Enlil, where she leads product strategy, vision, and execution for the company's AI powered medtech development platform. With over two decades of experience building and scaling enterprise software products, Charu brings deep industry expertise in product management, user-centered design, and go to market leadership. Before Enlil, she held senior product roles at industry leaders, including Epicor, Oracle, I-2 Technologies slash Aspect Development, HP and Agile Software, where she drove software innovation across enterprise cloud SaaS and data driven solutions. Known for her ability to align customer needs with business strategy, she is passionate about delivering products that transform complex industries and enable measurable impact. Well, welcome, Charu, to the conversation today. I'm so excited to be speaking with you. [00:01:54] Charu Roy: Thank you so much for having me. I'm very really excited about being here on this podcast. [00:02:00] Lindsey Dinneen: Oh, awesome. Yeah. Well, I would love, if you wouldn't mind starting off by sharing a little bit about yourself, your background, and what led you to medtech. [00:02:10] Charu Roy: Sure. As every other sort of person who gets into the software world, I came in a while back in 1987 to 89, where I did Master's in Computer Science at University of Louisiana. That was my first introduction to America, really. And computer science brought me to the Bay Area where I worked at HP, Hewlett Packard. In those days, it was called Scientific Instruments Division in Palo Alto. And there I programmed robotic hands to, to sort of move that, the vial from samples, drug samples from athletes so that they could get tested for drugs. So, I didn't know the importance of all this. It was my first job. I enjoyed myself seven years, you know, software programming, really, and understood how a large company works. And then slowly I started getting a little bored. So I went on to my next startup and was involved in the same kind of principles that drive things today. So I just sort of built my way up. In terms of the software, I joined different groups, ran consulting services, ran engineering, and sort of worked myself up through the ranks and into sort of more decision making capabilities, and you know, continued to join companies and learn new things and leave them for some better opportunities. So I moved from Hewlett Packard to a startup that was called Aspect Development, which got sold to I-2 Technologies for $9.3 billion in those days. So, you know, I went through that acquisition, trying to understand the market, what kind of software triggers buying, you know-- so sort of just the software aspects of how to sell software, how to develop software, how to deploy it. So in general, I was learning all of the ropes until I came to Agile PLM, which is a company which, very popular company which made it very sort of easy to deploy software, especially software called Product Lifecycle Management. So I was -- here, I was in and out of companies, learning and understanding the world of software until I fell into med device companies being my customers. So med device being our customers meant, you know, a lot more strictness, a lot more process, with the software itself. So here I was trying to now go through those kind of features, trying to understand what med device needed when they were building products. So, from Agile, I went to Conformia. Again, it was the same, it was regulatory product for wine, spirits and pharma --very adjacent to med device. But again, it was the same thing about how to be provide, how to provide a traceable platform where our customers can trace there, the make of the wine or make of the spirit, or make of a pharma drug or make off of med device. All the principles underlying it are the same because it's a regulated product at the end of the day, but so that's how I kind of fell into it, and I enjoyed every bit of that until I got acquired by Oracle. And so I continued at Oracle doing the same thing over and over again; rebuilt the same products again at Oracle in the clouds, and I was managing the old Agile products. So it's an interesting journey where I was, you know, started off as a software programmer. And I didn't know anything about, you know, the use cases until the time I sort of joined Oracle and understood my customers better. And that's how I came in there. And of course I was at Epicor and finally I made my way to Enlil, which is a very small company, and I'm doing the same thing again. It's just with a different set of customers, very small to medium sized companies. So that's how my career sort of spanned 30 years. [00:06:11] Lindsey Dinneen: Wow. Oh my goodness. Well, there is so much to dive into all of that. Thank you for sharing. It's so cool to hear about all of the winding paths that lead us to maybe, you know, where we're meant to be in, in any given season. And yeah, I just love learning about it. So, okay. So I'm curious, you know, way back when did you like growing up, did you always have an interest in computers and computer science? Is this something you knew you wanted to get into? [00:06:40] Charu Roy: Not at all, actually it was a suggestion, and in those days, parents kind of suggested that you be a engineer or a doctor or a chartered accountant. The choices were very limited. And so my father said, "you will do computer science." And I said, "okay." And there I was and there was no, no sort of emotional attachment to any of those professions. And, I liked it well enough to continue, and I found it was easy enough to understand the principles and work at it. So yeah, there was no-- you know, in these days I think kids are training themselves like by seven or eight to program. And I'm seeing, you know, machine language I mean AI, ML, LLMs being taught to seven year olds and sort of trying to shape them, but in those days it was just some very simple choices, I guess. So, yeah, not a very romantic story. I was never programming younger in my younger days, but I think you know, compared to all the choices youngsters have these days, but just fell into it. [00:07:44] Lindsey Dinneen: Sure. Oh, how fun. You know, even though, yes, it was somewhat prescribed for you, at least originally, and I'm so glad that you fell in love and it ended up being a happy place for you because... [00:07:57] Charu Roy: Yeah, and I think I fell in love with the customer, how customers reacted to the software. I didn't fall in love with the software delivery process or anything else, but it was just the way customers said, "oh, I like that. It's gonna make it easier for me to do something. I'm having a tough time tracking it on paper. I just hate it what I'm doing right now, and your software will help." So I think that's a part that makes me feel really pleased that okay it's going into some good hands and it's going to be used. [00:08:30] Lindsey Dinneen: Yes, by people who really appreciate and value what you can contribute, what maybe comes --at this point, I guess-- naturally to you. And so it's, you're able to translate somebody's ideas or dreams into a really tangible solution. [00:08:48] Charu Roy: Yeah. And in fact, somebody's pain points, like they're really sort of, trying their best to use little resources they might have, wasting a lot of time on either tracking something on paper or in emails. And I think those are the kind of pain points that I really like to understand and say, "Hey, will the software help really help your day to day life? Will it make it easier to find things?" I think that's where I find my sort of biggest thrill of when a customer says, "Yes, you shaved off three hours of my time by giving me this efficient system." [00:09:26] Lindsey Dinneen: Nice. Yeah. Oh my goodness. Yes , and the products that you're making are indeed life impacting and make a difference. And that is rewarding because you know that the work you --do all work is important, but it's really fun when you get to know personally the impact that you get to have. [00:09:45] Charu Roy: Right, right. [00:09:46] Lindsey Dinneen: Yeah. Yeah. So, okay, so I'm, I'd love to dive in a little bit more to your current company and role and learn about that, and how you're helping, you're still helping people you know, win through this. [00:10:00] Charu Roy: So, yes, absolutely. Enlil is part of Shifamed, the portfolio. Shifamed invests in med device devices typically, so ophthalmology devices or cardio devices. Enlil came about as an enterprise software company within the portfolio because they realized that they needed some software to throw all their data into, right? So they had early designs, prototype data. They might have had some user requirements, what kind of standards they might have to follow. So all those were floating about, again, in emails and paper. Enlil came in saying that we can store this data more successfully, more cleanly in a structured fashion so that our users can find that data. And this becomes really important as the med device company moves on and tries to apply for regulatory approval at that time, they need all that history and the data behind the device. And they wanna be able to find it easily and present it to auditors. So, Enlil's a structured way of describing all the data that the customer has and being able to find it easily and then run their audits using the data. So it's a very crucial part of their lifecycle, their product lifecycle. And so it's really important for us to be secure, reliable, available, 24/7. All of that applies to us and basically defines how they go about driving their product lifecycle. [00:11:34] Lindsey Dinneen: Yeah. Well, and you know, one thing that stood out to me when you were talking about that was of course the security aspect. And as we all know, we're, we're probably much more so than in the past, hyper aware of the critical need for cybersecurity and the role it plays specifically in medical device technology. And I'm curious if you could speak a little bit more to that particular element. [00:11:55] Charu Roy: Yeah, we have a lot of layers of security, you know, right from the folks who are accessing the software. The software is hosted in a well-known, reputable cloud service environment. So apart from them providing us cybersecurity and access control and everything else, we have another set of layers on top of that. So our users are vetted and they all have a password. People can be invited and not just sort of show up. So, there's a lot of control of what they can see and can do. Every button sort of, you know, has a role behind it or a layer of control. So not everyone can do everything and press any and all buttons. So, security is at many levels. And we also have a lot of audit trails, e-signatures, and so on. So everything is done to protect the data, and audits are run regularly by them and by us to make sure that nobody who's supposed to be, you know, people who are not supposed to see the data, don't see the data. [00:13:01] Lindsey Dinneen: Yeah. Excellent. Yeah, I know that's just something that is, should be at least, on the forefront, especially of startups' minds as they're thinking about this and working towards having a really secure device. So it sounds like you've built in all of that safeguarding really well and really intentionally. So, so, okay, so I know that -- well, there's a few things that really stood out to me on your LinkedIn profile, and I'm just curious if we could dive into a couple things. One was, I love how you said that you're "passionate about teams and people delivering to their full potential," and I was wondering if you could speak a little bit more to that. [00:13:42] Charu Roy: Yeah, so, you know, along the years I've noticed that people in my team, the team members, they're there, they're working hard, but I do like to understand what's making them tick, what might they be wanting to do, which they haven't got gotten to do yet. Can we unlock some potential, some skill, some talent? And I think that comes about by sort of just talking about it , trying to give them openings about, "Hey, look, I've got this cool project or this cool feature. Any thoughts on that?" Just to understand, are they happy doing what they're doing, or is there something more they could do? And so I think that human touch, you know, is -- it was given to me, or at least it was taught to me by some mentors along the way. And I think that's a part that I really like to explore and see how can teams do better, not just in a numbers, not just turnaround features and releases on time, but are they happy doing it? Did they contribute something meaningful along the way? Did they feel they grew in the process? Did they feel they were recognized for some new responsibilities that they may not have stepped up for in some other companies? So that's a feeling I'm trying to always give them and sort of hoping that we contribute to their growth, not just the company and the bottom line. [00:15:02] Lindsey Dinneen: Yeah, that's critical and key,, and really speaks to who you are as a leader. And I'm actually very curious, you know, you mentioned earlier having kind of worked your way up at HP and then, you know, that may be opening some doors for you for of course, your future opportunities, and I'm curious, what has your own leadership journey looked like? Has, does leadership come naturally to you? Have you spent a lot of, you know, time and resources, whatever, developing those skill sets or how did that work for you? [00:15:29] Charu Roy: I think I was thrown into the deep end of the pool several times, you know, like, so I kicked into the pool, so to learn to swim. So similarly I was made to take on responsibility pretty much the very beginning. So I kind of knew that there were certain things expected that I should be doing, can be doing and then this introspection saying that, did I give the right amount of energy to that particular responsibility and did I do well? So just a lot of introspection and being able to understand, did I do well as a leader? But I've been honing it, honing skills. I mean, nothing out of an MBA school, nothing out of, you know, college that helped me. I think it was just about pure interest in psychology, pure interest in humans, you know, just being able to connect and how did I make them feel? How did they make me feel in those interactions? And is that, was that good? Was there something we could do to incorporate more people to get that feeling of ownership or anything? So it wasn't a, you know, by rote or something that I learned in a school. It was more of just sort of. Being thrown into situations where I had to come out of it somewhat gracefully and some somewhat feeling like I had also learned along the way. [00:16:46] Lindsey Dinneen: Yeah. Yeah, that, that's wonderful and incredible. And I think, you know, you mentioned learning along the way, and one thing also that stood out to me was, the recommendations on your profiles are so lovely for you. And two things stood out: they, one thing was somebody mentioned you're always learning, which is a gift in and of itself. And then the other thing was you're always letting others succeed. And that's such a beautiful gift and I'm wondering if you could talk more about both of those as well. [00:17:16] Charu Roy: Yeah, I think it's not about just me being sort of the boss and being able to tell people what to do, though I think success comes from enabling or encouraging the teams to again contribute without any barriers, any levels, or politics. I love the fact that we are in a small company, and I can say safely that, you know, politics --in larger companies there are politics. People are always trying to sort of be showing that they are very valuable. But in a small startup, it's very quickly apparent that there are certain valuable players there and startups, everybody is valuable, right? So I think being able to encourage the team members to do what they think is best for the problem to solve it. And of course, there are reasons why you can't sometimes accept the solution, but the fact that they're thinking about it and the fact they're able to openly express their opinions and say, "No, you're wrong, Charu." I think this is the way to do it. I love that. I think, somebody disagrees with me in a meeting, I just think that's the best thing that could have happened as a style of management. Because I'm not, you know, insecure in that sense. I don't sulk afterwards. I have had bosses and so on who don't like that kind of, you know, disagreements in public. And I think that's a part where I beg to differ, and I want to have people say what they think, what are they feeling, what are the problems, really the truth, and fix it, really. So I think it's less waste of a time when people are honest, and get to the point, and we are able to solve it together rather than hide behind, you know, facades, I guess. [00:19:01] Lindsey Dinneen: Yeah, that's beautiful. And yeah, I've often said for me personally, that, you know, more heads are better than one. I mean, I could have a, an opinion on whatever it is that we're talking about, but really, until we collaborate and start sharing those ideas and those thoughts and opinions , all of a sudden those kinds of sparks happen where, you know, you start with one thing and then it, and then somebody else catches that and they take it even to the next level and it just keeps going. And it's so cool to see the creativity and problem solving and innovation that comes from allowing those conversations. [00:19:36] Charu Roy: Yes, exactly. Creativity and innovation. You've said it so well. That comes with smart people being in the same room, arguing, not agreeing, and then something comes out of that, right? I mean, either your thoughts get clearer because you've seen every side of the coin and you're able to say, "Okay, I know the pros and cons and we can go this way, knowing the full effect of what we are going to do." So I think surrounding myself with smart people who have varied opinions, I think that's a beauty and a blessing really. [00:20:12] Lindsey Dinneen: Yes it is, and you've nailed it with varying opinions. You know, it's easy to get yourself into a situation-- and not necessarily intentionally-- but just it's easy to give into a situation where you've surrounded yourself with people who all kind of have the same opinions on things. And so inviting those conversations to take place that might be difficult, might be challenging, might be frustrating at times, but allowing for that and being open to other points of view and experience. I mean, that's the beauty of a really good collaborative environment is all of those varying opinions that don't necessarily match yours. [00:20:50] Charu Roy: Yes, exactly. Exactly. [00:20:52] Lindsey Dinneen: Yeah. Yeah. So, okay, so looking back, could 10-year-old you have ever imagined where you'd end up today? [00:21:00] Charu Roy: No, absolutely not. I thought I wanted to be a doctor or something vague. 10-year-old me was climbing trees and eating guavas off the trees in Delhi. So it was really crazy childhood. And you know, it wasn't filled with studies and rules and stuff. So I think coming to this, a country when I was young, being able to absorb everything, the culture, the of course the education itself and being able to sort of grow within the companies that I joined, i, I think that was the journey that I was sort of a pointing more towards rather than the childhood me. The childhood me was horrible, I think. [00:21:46] Lindsey Dinneen: Oh man. Honest reflection right there. That's awesome. Yeah, okay. Are there any moments that really stand out to you, perhaps with your current position or, you know, something in your past where you really thought, "Wow, what I'm doing makes a difference. I am in the right industry, at the right time, in the right place." [00:22:07] Charu Roy: I think it's the technology now that, you know, speaking from a technical viewpoint of shipping software, meaning full software, more easily, the time is now. I feel that the culmination of everything I've learned about pain points and users and customers, all of that's culminating in in the product that I'm managing right now, using new technologies, having the right technologies to choose from and being able to propel that software forward to our users. I feel that, "Wow, what a time to be a product officer really, when we have so many choices and being able to be able to apply that to real world problems and real pain points." I had the same pain points 20 years ago, even 30 years ago, but we couldn't do much. We had to, you know, write painful programs. We had to write database queries and, you know, things like that. It was quite painful, I would say. And then now to see all the tools where we can create things overnight and be able to ship it to customers, just hitting the nail on the head. We had to experiment a lot in the old days but I think the time now is is really special. We are on an sort of an industrial revolution or a computer science revolution here with the AI, MML, the LLMs, being able to do so much with probably less resources than before. So. [00:23:39] Lindsey Dinneen: Yeah. So seeing the impact of the work and getting to not have it be so painful. [00:23:45] Charu Roy: Yes. It used be very painful and now I'm thinking, I think we're at the right time, right place now with this product. And it's not just about the products. It's the kind of help we are getting as software professionals to help deliver software and support our users. I think that's really special and I, we are still learning, we're still trying to understand all the technologies that are available to us and how can we make our lives easier and our customers feel that we've solved some problems for them. [00:24:14] Lindsey Dinneen: Yeah, absolutely. And I think that there's just, it is really wonderful again-- just to, to circle back to this kind of been a running theme of getting to be able to experience for the end user or with the end user, that moment of, "Oh wow, I needed this is so helpful and it's gonna make a difference." [00:24:36] Charu Roy: Yeah. I remember in my past, same sort of software tracking wine being made. And that software was pretty cool. It, it used to track where the wine sat and which barrel for how long. And so the pleasure of talking to wine makers, and being able to show them how the software track the progress of the wine and being able to print out a label at the very end for them, saying that "this wine sat in these bottles or these barrels for a while," and that technology application for a simple, naive user, I thought that was it. That was the, you know, the culmination of all the learnings that I had over the years to be able to explain the software so easily to a end user who might be a distiller or a winemaker or somebody, a farmer. I thought that was pretty cool. And that since then, of course, technology has changed, but I think we're beginning to see the effect on a naive user, which we couldn't do, you know, 30 years ago. [00:25:37] Lindsey Dinneen: Yeah, absolutely. Oh my goodness. That is, it is so cool. And I love the work you're doing and just learning all about your history so far and just exciting to see where it's gonna end up too, and as you continue along your career path, but pivoting the conversation a little bit just for fun. Imagine that you were to be offered a million dollars to teach a masterclass on anything you want, could be within your area of expertise, it doesn't have to be. What would you choose to teach? [00:26:06] Charu Roy: I would probably think about teaching psychology of the individual. I don't have a PhD or a even basic courses in psychology, but I just love the fact that, you know, you can apply psychology, figure out how a user might or somebody might react to something that you say, do, think so I, if it was a master class and I'd be teaching you know, teaching more about life interactions, you know, ordinary interactions. How can they be made more meaningful, more fruitful, using psychological tricks or phrases? I don't know all of those things, but I would really think that I could teach that based on, you know, facial expressions, body mannerisms, or body-- what do they call it, sort of, you know, criminal stories. They read your mind based on certain mannerisms of flutter viol. So yes, psychology is a masterclass I would teach, but more applied to daily interactions, maybe work situations and being able to use psychology better to improve your own work relationships with people and even just general interactions. Yeah, so that would be my attempt at being a psychologist and eventually be a criminal psychologist. [00:27:28] Lindsey Dinneen: Yes. Oh my goodness. That would be so interesting. Yeah, I love that idea. And the masterclass sounds fabulous, so I'm signing up whenever you do it. [00:27:37] Charu Roy: Okay, I'll go get my degrees for it then. [00:27:40] Lindsey Dinneen: Right, right, right. Yeah. Ah, details. Awesome. How do you wish to be remembered after you leave this world? [00:27:50] Charu Roy: This is something that I've always felt deeply about. It's not what you say or what you do, it's how you make people feel, that Maya Angelo said that this much nicer than what I'm saying, but and I've had a few people say this to me, saying that, "We worked together 30 years ago, but that day you made me feel good." And I don't even remember what I said, what I did, but the fact that they remember me for what I made them feel. The fact that somebody also told me that they "don't avoid me when I'm walking up to them because, because I make them feel like things are okay, things are good, however bad the problem is." So they say that with other people they would duck and, you know, go away in the opposite direction. But with me they're waiting for me to come up to them. I'd like to continue that, that feeling that somebody feels like, "Hey, you are coming up to them and you just make them feel good in some fashion." Nothing else. I think that feeling, if I could evoke in people, they say, "Oh yeah, she made me feel good that day. I don't know what she said, but she made me feel good." That's enough. [00:29:01] Lindsey Dinneen: Yeah, that, yes, that is more than enough. What a beautiful legacy. Yeah, and then final question, what is one thing that makes you smile every time you see or think about it? [00:29:15] Charu Roy: I think my dogs smile. I would say he's got missing teeth and so when he looks at me when I first come, you know, come back home and he is smiling almost, and he is sniffling and, you know, trying to sneeze and smile at the same time. Oh my God, what kind of a character dog this is? So that makes me smile and laugh the whole time, especially the missing teeth. Poor thing. He doesn't understand that his teeth are missing because of me, and yet he's smiling at me, so. [00:29:50] Lindsey Dinneen: That is so sweet and cute. Oh my goodness. I love, I know somebody at one point said, "You know, dogs don't actually smile." I don't believe them. They smile. [00:30:00] Charu Roy: They smile and they choke while they smile because my dog has a small nose, I guess. So he chokes when he smiles, and so he is choking, and he is smiling, and this missing teeth there. I was like, "Oh my God." [00:30:16] Lindsey Dinneen: Oh my goodness. Yes. I mean, that would just I, yes, I can just sort of picture this. I love, love dogs and so I'm just picturing this and I, that would bring me joy every single day, definitely. Excellent. Well, this has been such a wonderful time spent with you today. Thank you for sharing your stories and your journey and your advice, and I really appreciate some of those in particular, your leadership advice, and the impact that you can have as a leader, inviting the collaboration, having conversations that encourage people to have varying opinions and maybe outright disagree with you. I love what you're wanting to, you know, wanting your legacy to be, and so that's how you're intentionally showing up in the world. And so I just wanna thank you so, so very much for being here. We're really grateful to have you. [00:31:10] Charu Roy: Thank you, and thank you so much for your intelligent questions and insightful questions that go above and beyond just you know, a company and it's gold. It's there, there's something so human about your questions-- and I love when I'm like, "Oh my goodness, this is so, so interesting to see in this day and age, somebody taking the time to ask such questions" and I really appreciate you for that. [00:31:36] Lindsey Dinneen: Oh, thank you. Well, I really appreciate that feedback too, because it's, you know, you come up with an idea-- speaking of sometimes echo chambers, you come up with an idea and you think, "Oh, this is how I'd like to go about this, but does it resonate with somebody else?" So that's delightful to hear. [00:31:51] Charu Roy: Fantastic, thank you, thank you for having me. [00:31:54] Lindsey Dinneen: And we're so honored to be making a donation on your behalf as a thank you for your time today to the American Society for the Prevention of Cruelty to Animals, which is dedicated to preventing animal cruelty in the United States. So thank you for choosing that organization to support Thank you so much, and gosh, I just wish you the most continued success as you work to change lives for a better world. And to all of our listeners for tuning in, I wanna thank you for being here as well. And if you're feeling as inspired as I am right now, I'd love it if you'd share this episode with a colleague or two, and we'll catch you next time. [00:32:31] Charu Roy: Thank you. [00:32:32] Dan Purvis: The Leading Difference is brought to you by Velentium Medical. Velentium Medical is a full service CDMO, serving medtech clients worldwide to securely design, manufacture, and test class two and class three medical devices. Velentium Medical's four units include research and development-- pairing electronic and mechanical design, embedded firmware, mobile app development, and cloud systems with the human factor studies and systems engineering necessary to streamline medical device regulatory approval; contract manufacturing-- building medical products at the prototype, clinical, and commercial levels in the US, as well as in low cost regions in 1345 certified and FDA registered Class VII clean rooms; cybersecurity-- generating the 12 cybersecurity design artifacts required for FDA submission; and automated test systems, assuring that every device produced is exactly the same as the device that was approved. Visit VelentiumMedical.com to explore how we can work together to change lives for a better world.

In this episode we're in conversation with Manjit Singh, the president and founder of Agilious and an instructor at ACT-IAC Academy. They delve into the importance of agile frameworks, particularly scrum, for government IT acquisition and modernization. Manjit shares his extensive technical background and the significance of scrum mastery in managing projects efficiently. He discusses the role of a Scrum Master, common misconceptions, the importance of asking the right questions, and the impact of emerging technologies like AI. The episode also highlights continuous upskilling and the value of lean principles in achieving productivity.Subscribe on your favorite podcast platform to never miss an episode! For more from ACT-IAC, follow us on LinkedIn or visit http://www.actiac.org.Learn more about membership at https://www.actiac.org/join.Donate to ACT-IAC at https://actiac.org/donate. Intro/Outro Music: See a Brighter Day/Gloria TellsCourtesy of Epidemic Sound(Episodes 1-159: Intro/Outro Music: Focal Point/Young CommunityCourtesy of Epidemic Sound)

Accelerating cloud adoption to drive innovation across domains like space, identity, and naval systems presents unique challenges. Success depends on aligning organizational culture, governance, financial models, and regulatory frameworks to enable collaboration, scalability, and software-defined capabilities.  This week, Dave, Esmee, and Rob speak with Danny Polaine, Chief Information Officer at Thales, about the strategic shift to cloud technologies in a high-security sector like defense and the unique challenges that come with it. TLDR:00:52 – Introduction to Danny Polaine03:35 – Rob is confused about the AI privacy dilemma07:40 – Exploring tech in high-security sectors with Danny35:34 – The biggest challenge isn't tech, it's people adapting to new ways of working44:55 – Reflections on the CIO role and a fun story about singing waiters at a wedding Guest Danny Polaine: https://www.linkedin.com/in/danny-polaine-5713454/?originalSubdomain=uk  HostsDave Chapman: https://www.linkedin.com/in/chapmandr/Rob Kernahan: https://www.linkedin.com/in/rob-kernahan/Esmee van de Giessen: https://www.linkedin.com/in/esmeevandegiessen/ ProductionMarcel van der Burg: https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman: https://www.linkedin.com/in/chapmandr/ SoundBen Corbett: https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:  https://www.linkedin.com/in/louis-corbett-087250264/ 'Cloud Realities' is an original podcast from Capgemini

Blue Origin is fresh off an incredible few weeks—a successful second launch and first landing of New Glenn, followed by an exciting unveil of upgrades to the vehicle, including an enormous new version, New Glenn 9x4.This episode of Main Engine Cut Off is brought to you by 32 executive producers—Lee, Natasha Tsakos, Fred, Will and Lars from Agile, Ryan, Stealth Julian, Pat, Heiko, Kris, Jan, Better Every Day Studios, Theo and Violet, Matt, Josh from Impulse, Russell, Joel, Warren, Joonas, Joakim, Tim Dodd (the Everyday Astronaut!), Donald, David, Frank, Steve, The Astrogators at SEE, and four anonymous—and hundreds of supporters.TopicsBlue Origin's New Glenn rocket came back home after taking aim at Mars - Ars TechnicaJeff Bezos on X: “Good overview of the landing. We nominally target a few hundred feet away from Jacklyn to avoid a severe impact if engines fail to start or start slowly. We'll incrementally reduce that conservatism over time. We are all excited and grateful for yesterday…”New Glenn Update | Blue OriginBooster 18 suffers anomaly during proof testing - NASASpaceFlight.comSenate Commerce Committee schedules hearing on Isaacman renomination - SpaceNewsLawmakers writing NASA's budget want a cheaper upper stage for the SLS rocket - Ars TechnicaThe ShowLike the show? Support the show on Patreon or Substack!Email your thoughts, comments, and questions to anthony@mainenginecutoff.comFollow @WeHaveMECOFollow @meco@spacey.space on MastodonListen to MECO HeadlinesListen to Off-NominalJoin the Off-Nominal DiscordSubscribe on Apple Podcasts, Overcast, Pocket Casts, Spotify, Google Play, Stitcher, TuneIn or elsewhereSubscribe to the Main Engine Cut Off NewsletterArtwork photo by JAXAWork with me and my design and development agency: Pine Works

I’m launching new cohorts for The Forge Lightning and The Forge Genesis. Go to https://learning.fusechamber.com to find out more and register today. What’s The Latest in Badass Leadership? Something is definitely up. People are angrier, meaner, less fulfilled, less patient and more intolerant. Manners and decorum are taking a back seat to ego and impulse. I won’t get into where I think this is all coming from, but I do know one thing. If you want to make things better, the fastest way is to set an example with Badass Leadership. For a leader to set a powerful example, they have to be in control of their emotions. You have to let situations bounce off of you – including criticism, failure, unfairness, difficulty and conflict. Technically, it doesn’t have to “bounce off of you”, but the badass leader must be in charge of their response to situations like these. That means you’re aware of how situations affect you. You understand your default reactions, and learn how to subvert them. It means you know what is important to you as a leader, and never allow your ego (or your emotions) to take precedence over your vision. It’s never been more important to let your badass leadership shine. What Is Badass Leadership? Thinking back to some very early episodes, Badass Leadership refers to the qualities that a highly seasoned and powerful leader possesses. You are not influenced by currents and tides, nor the opinions of others. You can see clearly where you want to go, and are willing to experiment in an effort to get there. You don’t value being right. You don’t need credit, acclaim, wealth or fame in exchange for what you do. Your leadership is about serving. That means bringing clear value to those who need it the most. At its core, Badass Leadership is about strength. Steadiness, especially in the face of adversity, is a sign of great wisdom and power. Having the humility to realize you’re not perfect, but on a path to mastery, is key. When you’ve begun to master emotional control in yourself, you’ll notice something very cool happening. You can notice it in others. If you’ve been working on emotional control in yourself, you can then use your wisdom and experience to help others. That’s what Badass Leadership is all about. Here’s some episodes touching on Badass Leadership I thought you might also enjoy: The Forge – Badass Agile Immersion Experience Career Freedom with Forge Genesis Episode 168 – The 13 Qualities Of A Badass Leader (Revisited) **JOIN MY BETA COMMUNITY FOR AGILE ENTREPRENEURS AND INTRAPRENEURS** The latest wave in professional Agile careers. Get the support you need to Forge Your Freedom! Join for FREE here: https://learning.fusechamber.com/offers/Sa3udEgz **CHECK OUT ALL MY PRODUCTS AND SERVICES HERE:** https://learning.fusechamber.com **THE ALL NEW FORGE LIGHTNING** 12 Weeks to elite leadership! https://learning.fusechamber.com/forge-lightning **ELEVATE YOUR PROFESSIONAL STORYTELLING – Now Live!** The most coveted communications skill – now at your fingertips! https://learning.fusechamber.com/storytelling **JOIN THE FORGE*** New cohorts for Fall 2025! Email for more information: contact@badassagile.com **BREAK FREE OF CORPORATE AGILE!!*** Download my FREE Guide and learn how to shift from roles and process and use your agile skills in new and exciting ways! https://learning.fusechamber.com/future-of-agile-signup We’re also on YouTube! Follow the podcast, enjoy some panel/guest commentary, and get some quick tips and guidance from me: https://www.youtube.com/c/BadassAgile ****** Follow The LinkedIn Page: https://www.linkedin.com/showcase/badass-agile ****** Our mission is to create an elite tribe of leaders who focus on who they need to become in order to lead and inspire, and to be the best agile podcast and resource for effective mindset and leadership game. Contact us (contact@badassagile.com) for elite-level performance and agile coaching, speaking engagements, team-level and executive mindset/agile training, and licensing options for modern, high-impact, bite-sized learning and educational content.

Sara Di Gregorio: Coaching Product Owners from Isolation to Collaboration Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Using User Story Mapping to Break Down PO Isolation "One of the key strengths is the ability to build a strong collaborative relationship with the Scrum team. We constantly exchange feedback, with the shared goal of improving both our collaborating and the way of working." - Sara Di Gregorio   Sara considers herself fortunate—she currently works with Product Owners who exemplify what great collaboration looks like. One of their key strengths is the ability to build strong collaborative relationships with the Scrum team. They don't wait for sprint reviews to exchange feedback; instead, they constantly communicate with the shared goal of improving both collaboration and ways of working.  These Product Owners involve the team early, using techniques like user story mapping after analysis phases to create open discussions around upcoming topics and help the team understand potential dependencies. They make themselves truly available—they observe daily stand-ups not as passive attendees but as engaged contributors. If the team needs five minutes to discuss something afterward, the Product Owner is ready. They attend Scrum events with genuine interest in working with the team, not just fulfilling an attendance requirement. They encourage open dialogue, even participating in retrospectives to understand how the team is working and where they can improve collaboration. What sets these Product Owners apart is their communication approach. They don't come in thinking they know everything or that they need to do everything alone. Their mindset is collaborative: "We're doing this together." They recognize that developers aren't just executors—they're users of the product, experts who can provide valuable perspectives.  When Product Owners ask "Why do you want this?" and developers respond with "If we do it this way, we can be faster, and you can try your product sooner," that's when magic happens. Great Product Owners understand that strong communication skills and collaborative relationships create better products, better teams, and better outcomes for everyone involved.   Self-reflection Question: How are your Product Owners involving the team early in discovery and analysis, and are they building collaborative relationships or just attending required events? The Bad Product Owner: The Isolated Expert Who Thinks Teams Just Execute   "Sometimes they feel very comfortable in their subject, so they assume they know everything, and the team has only to execute what they asked for." - Sara Di Gregorio   Sara has encountered Product Owners who embody the worst anti-pattern: they believe they don't need to interact with the development team because they're confident in their subject matter expertise. They assume they know everything, and the team's job is simply to execute what they ask for. These Product Owners work isolated from the development team, writing detailed user stories alone and skipping the interesting discussions with developers. They only involve the team when they think it's necessary, treating developers as order-takers rather than collaborators who could contribute valuable insights.  The impact is significant—teams lose the opportunity to understand the "why" behind features, Product Owners miss perspectives that could improve the product, and collaboration becomes transactional instead of transformational. Sara's approach to addressing this anti-pattern is patient but deliberate. She creates space for dialogue and provides training with the Product Owner to help them understand how important it is to collaborate and cooperate with the team. She shows them the impact of including the team from the beginning of feature study.  One powerful technique she uses is user story mapping workshops, bringing both the team and Product Owner together. The Product Owner explains what they want to deliver from their point of view, but then something crucial happens: the team asks lots of questions to understand "Why do you want this?"—not just "I will do it."  Through this exercise, Sara watched Product Owners have profound realizations. They understood they could change their mindset by talking with developers, who often are users of the product and can offer perspectives like "If we do it this way, we can be faster, and you can try your product sooner."  The workshop helps teams understand the big picture of what the Product Owner is asking for while helping the Product Owner reflect on what they're actually asking. It transforms the relationship from isolation to collaboration, from directive to dialogue, from assumption to shared understanding.   In this segment, we refer to the User Story Mapping blog post by Jeff Patton.   Self-reflection Question: Are your Product Owners writing user stories in isolation, or are they involving the team in discovery to create shared understanding and better solutions?   [The Scrum Master Toolbox Podcast Recommends]