Podcasts about Agile

As a marketing leader, you often spend so much time on the strategies and tactics that keep your brand growing that it's difficult to keep up with what's going on in the background with the platforms and the companies behind them. While agility requires a flexible technology stack, it also requires a leadership mindset that can distinguish market noise from genuine strategic opportunity, and filter out the hype to understand the shifts that can impact customers and the bottom line. The ability to pivot your people, processes, and platforms in response to major market shifts is no longer a nice to have, but rather a competitive advantage. Today, I'm excited to talk with our 2026 Resident Expert on the CX and MarTech platform landscape. We're going to focus on the business and business opportunities that mergers, acquisitions, and big moves in the market provide to these platforms' customers. Our focus today is going to be a recap of market activity in 2025 with an eye towards what to expect in 2026. To help me discuss this topic, I'd like to welcome, Bill Staikos, Founder at Be Customer Led.About Bill Staikos Bill Staikos on LinkedIn: https://www.linkedin.com/in/billstaikos/ Resources Be Customer Led: https://becustomerled.com/ Take your personal data back with Incogni! Use code AGILE at the link below and get 60% off an annual plan: https://incogni.com/agile The Agile Brand podcast is brought to you by TEKsystems. Learn more here: https://www.teksystems.com/versionnextnow Catch the future of e-commerce at eTail Palm Springs, Feb 23-26 in Palm Springs, CA. Go here for more details: https://etailwest.wbresearch.com/Drive your customers to new horizons at the premier retail event of the year for Retail and Brand marketers. Learn more at CRMC 2026, June 1-3. https://www.thecrmc.com/ Enjoyed the show? Tell us more at and give us a rating so others can find the show at: https://advertalize.com/r/faaed112fc9887f3 Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstromDon't miss a thing: get the latest episodes, sign up for our newsletter and more: https://www.theagilebrand.showCheck out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. https://www.missinglink.company

Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Bamidele Farinre Founder of No Ceiling Consulting, a biomedical scientist, STEM expert, agile project manager, and advocate for professional development, mentorship, and removing internal and systemic limitations (“ceilings”). They discuss her STEM background, the evolving role of AI in science, the meaning of “no ceilings,” navigating personal and professional barriers, mentorship, setbacks, agile leadership, and how individuals—especially people of color—can create opportunity even in the face of bias and structural limitations.

Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Bamidele Farinre Founder of No Ceiling Consulting, a biomedical scientist, STEM expert, agile project manager, and advocate for professional development, mentorship, and removing internal and systemic limitations (“ceilings”). They discuss her STEM background, the evolving role of AI in science, the meaning of “no ceilings,” navigating personal and professional barriers, mentorship, setbacks, agile leadership, and how individuals—especially people of color—can create opportunity even in the face of bias and structural limitations.

Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Bamidele Farinre Founder of No Ceiling Consulting, a biomedical scientist, STEM expert, agile project manager, and advocate for professional development, mentorship, and removing internal and systemic limitations (“ceilings”). They discuss her STEM background, the evolving role of AI in science, the meaning of “no ceilings,” navigating personal and professional barriers, mentorship, setbacks, agile leadership, and how individuals—especially people of color—can create opportunity even in the face of bias and structural limitations.

Juliana Stepanova: When a Former Skeptic Calls to Say "Now I Know What You Did" — Defining Scrum Master Success Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Juliana, now I know what you did that time. It was so amazing work. Sometimes the work of the Scrum Master, you cannot measure it in real numbers, because the work of the Scrum Master is dependent on the persons who are working with the team." - Juliana Stepanova   Juliana shares a story that captures the often invisible nature of Scrum Master success. For a year and a half, she worked with a distributed team across Europe, and one colleague in her office would repeatedly ask—half joking, half serious—"Juliana, what do you do here? Why are you getting a salary? I don't see any improvements."  Eight months after that colleague moved to another company, he called her with a revelation: working in a team without effective Scrum Mastering made him finally understand the value she had created. This delayed recognition highlights a fundamental challenge: Scrum Master success often can't be measured in real numbers because it depends on enabling others. Juliana's practical approach is to set three main focus areas every three months, aligned with team and company needs.  She tracks concrete progress—like implementing a Definition of Done across multiple teams—and measures whether specific goals are achieved. She even asks in job interviews: "How will you measure my success in three or six months?" Without this intentional focus and self-measurement, she says, "it's truly hard to see what you're really doing."   Self-reflection Question: What three focus areas would you choose for the next three months, and how would you know you've succeeded in each? Featured Retrospective Format for the Week: Wedding Retro Juliana recommends the Wedding Retro format from Retromat, and when she mentions the name, people immediately smile—which is exactly the point. The format uses the traditional wedding saying "something old, something new, something borrowed, something blue" to structure reflection: Something Old represents practices that are working and should continue; Something New covers areas for improvement or experimentation; Something Borrowed invites the team to identify ideas from other teams or departments worth adopting; and Something Blue addresses blockers, risks, and issues.  Juliana loves this format because the playful framing creates positive emotions from the start, disarming tension and making people more open to genuine reflection. "If you laugh at the start of the retrospective," she explains, "you're ready for a much better retrospective than if you're tense and anxious." She uses this exercise "all over the time," even outside her Scrum Master work.   [The Scrum Master Toolbox Podcast Recommends]

Agile Is Not a Process. It's How Smart Teams Think.Most people think agile is Jira boards, sprints, standups, and sticky notes.Here's the thing.Those are just tools.Agile is a mindset about how work *should* move in a world that refuses to stay predictable.If you've ever worked on a project where requirements changed, deadlines shifted, or priorities flipped overnight, you already know why traditional project management struggles.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/

Juliana Stepanova: Trust Over Escalation — A Patient Approach to Difficult PO Relationships 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 team still believes it could be solved with proper communication to the PO. My idea is to really try, in a supportive way, to build trust, to encourage communication, and to come to the solution as a team altogether. This is like a win-win situation." - Juliana Stepanova   Juliana brings a challenge that many Scrum Masters will recognize: a Product Owner who doesn't want to be coached and whose behaviors are undermining Scrum rituals. The situation is complicated by organizational structure—the Scrum Master reports to the people department while the PO reports to the product department, creating misaligned directions with no common leadership thread.  The PO arrives at refinement meetings unprepared, writing user stories on the spot while eight team members sit idle for hours. When Juliana explores the root cause, she discovers the PO is genuinely overwhelmed with responsibilities outside the team. But here's the twist: this newly promoted PO is proud of the role and resistant to accepting help, preferring to say "just wait, I will manage it."  Rather than escalating—which Juliana notes would damage trust for years or potentially lose the PO entirely—she advocates for a patient, collaborative approach. The experiment she designs focuses on engaging more deeply with the PO's activities to understand which tasks could be delegated or eliminated, while continuing to build trust through support rather than confrontation. The team maintains hope that the PO will eventually accept help, choosing persistence over escalation.   In this segment, we talk about coaching Product Owners and building trust.   Self-reflection Question: When facing a resistant stakeholder, do you default to escalation, or do you invest in building the trust that enables genuine collaboration?   [The Scrum Master Toolbox Podcast Recommends]

Juliana Stepanova: The Slippery Slope — How Small Compromises Lead Teams to Abandon Scrum Entirely Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "If you have it like once, you think it's okay. But it starts to change our mindset in the way that these rules, these frameworks could be changed. And with the small stuff that it's not correct, within half a year, Scrum will not work at all." - Juliana Stepanova   Juliana describes a pattern she witnessed in an experienced seven-person development team that had practiced Scrum for years. It began innocuously: the daily standup stretched from 15 to 30 minutes because the team was larger. Then came the skipped retrospectives during release phases—"we don't have time today." Each compromise seemed reasonable in isolation, but together they formed a slippery slope that eventually dismantled the entire framework. The root cause often lies outside the team: misaligned Scrum rituals across multiple teams, company-wide meetings that override sprint events, and pressure from management to prioritize immediate fires over process discipline. Once the brain accepts that "we can skip it for a good reason," finding the next good reason becomes easier and easier. Juliana emphasizes a crucial distinction: teams that actively choose Scrum—those who approach management saying "we want to try this"—naturally protect the framework. They understand its value from personal conviction. When Scrum is imposed rather than chosen, the team lacks the intrinsic motivation to defend it against organizational pressure, making the slippery slope almost inevitable.   In this segment, we talk about the challenges of organizational alignment and protecting Scrum events.   Self-reflection Question: What small compromises has your team made to the Scrum framework, and are they leading you toward a slippery slope where the entire process may eventually be abandoned? Featured Book of the Week: Startup, Scaleup, Screwup by Jurgen Appelo Juliana recommends Startup, Scaleup, Screwup by Jurgen Appelo as her go-to resource for Scrum Masters and Agile Coaches. The book contains 42 tools designed to accelerate business growth, presented in accessible chapters that cover the most essential knowledge for agile practitioners. What sets this book apart for Juliana is its scope: it addresses not just team-level concerns but company-wide perspectives. "Sometimes Scrum Masters don't pay so much attention to the company level or between departments," she explains. "In this book, you'll find normal tools which you can apply all over the company, not only for the team." She uses it constantly for inspiration and recommends reading it at least once—though she returns to it repeatedly for reference.   [The Scrum Master Toolbox Podcast Recommends]

We've spent years trying to make our chatbots sound more human, which is great. But what if the larger goal should have also been to make them as useful as possible while we're at it? Agility requires more than just adopting the latest technology; it demands a fundamental rethinking of customer engagement, moving from reactive responses to proactive problem-solving. Today, we're going to talk about the next evolution of AI in customer service. As more companies turn to automation to manage scale and efficiency, the real challenge isn't just implementing a chatbot; it's ensuring that technology actively solves problems and enhances the customer relationship, rather than just deflecting tickets. To help me discuss this topic, I'd like to welcome, Alan Ranger, VP Marketing at NiCE Cognigy. About Alan Ranger Alan Ranger is VP of Marketing at NiCE Cognigy, the global leader in enterprise AI agents. With over 30 years of experience in tech, Alan has led growth strategies at both startups and public software companies. At NiCE Cognigy, he helps organizations adopt AI that delivers real business value reducing costs while improving customer satisfaction. Prior to NiCE Cognigy, Alan led global market development at LivePerson, where he helped double revenues. He now leads NiCE Cognigy's expansion in the US and UK and works closely with clients to deploy AI that scales. Alan Ranger on LinkedIn: https://www.linkedin.com/in/aranger/ Resources NiCE Cognigy: https://www.cognigy.com Take your personal data back with Incogni! Use code AGILE at the link below and get 60% off an annual plan: https://incogni.com/agile The Agile Brand podcast is brought to you by TEKsystems. Learn more here: https://www.teksystems.com/versionnextnow Catch the future of e-commerce at eTail Palm Springs, Feb 23-26 in Palm Springs, CA. Go here for more details: https://etailwest.wbresearch.com/Drive your customers to new horizons at the premier retail event of the year for Retail and Brand marketers. Learn more at CRMC 2026, June 1-3. https://www.thecrmc.com/ Enjoyed the show? Tell us more at and give us a rating so others can find the show at: https://advertalize.com/r/faaed112fc9887f3 Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstromDon't miss a thing: get the latest episodes, sign up for our newsletter and more: https://www.theagilebrand.showCheck out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. https://www.missinglink.company

Juliana Stepanova: The 90-Minute Retrospective Disaster That Taught Me Servant Leadership 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.   "It's not my job to find the points to improve. My job is to help the team find them, to interact their communication, to start thinking about the improvements, and not pushing them into my exercises." - Juliana Stepanova   Juliana shares a humbling experience from her first year as a Scrum Master that transformed how she approaches facilitation. She had meticulously prepared what she believed was a brilliant 90-minute retrospective—carefully designed exercises, content tailored to the sprint, everything by the book. Yet when she asked the team for feedback at the end, they delivered a crushing verdict: "It was the worst retro ever." The disconnect wasn't about the quality of preparation but about whose perspective drove the design. Juliana had crafted the session based on her observations and assumptions about what the team needed, rather than asking them what they actually wanted to discuss.  This experience crystallized a fundamental insight about servant leadership: the difference between leading and servant leading. Today, Juliana prepares at least twice as many tools and exercises as she needs for any workshop, ready to pivot based on the room's energy and the team's expressed needs. She opens sessions with questions about expectations, aligning with the team's mood while setting appropriate boundaries. The failure taught her that even the most carefully prepared facilitation can miss the mark when it doesn't serve what the team actually needs in that moment.   Self-reflection Question: When was the last time you asked your team what they wanted from a retrospective before you designed it, and how might their input change your approach?   [The Scrum Master Toolbox Podcast Recommends]

Lean-Agile is easy to talk about but hard to pull off in a “chunky” corporate. Hear practical strategies for navigating layers, budgets, and oversight, keeping teams moving, communicating vision, handling legacy data, fostering experimentation, and leveraging AI—actionable advice for project managers making Agile work at scale.

Agile Failed Us After 18 Months - Here we go...On month eighteen, our average lead time crossed 27 days. Production defects doubled. A supposedly minor release missed its window by three weeks.Nothing had “broken.” Velocity charts still looked healthy. Every ceremony was running on time. But releases slowed, confidence eroded, and engineers stopped believing what the board said.This hurt because customers felt it immediately. Bugs lived longer, features arrived stale, and every delay came with an explanation no one trusted anymore.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/

What if the biggest risk to your marketing AI strategy isn't the technology itself, but the org chart it's fracturing? Agility requires more than just speed; it demands a framework of trust and collaboration. When it comes to AI, this means your ability to innovate is directly tied to your ability to partner effectively across the organization, especially with IT and security. Today, we're going to talk about a critical tension point in the modern enterprise: Marketing is moving at the speed of AI, adopting powerful, often low-code tools to drive results. But this speed creates new complexities and risks, disrupting traditional roles and processes. Success is no longer just about having the best tech stack; it's about forging a strategic partnership between the CMO and IT leaders to balance innovation with governance, and productivity with security. To help me discuss this topic, I'd like to welcome, Renu Upadhyay, Chief Marketing Officer at Omnissa. About Renu Upadhyay Renu Upadhyay is senior vice president of Marketing at Omnissa, leading global marketing strategy, demand generation, product and solution marketing and brand to establish Omnissa as the leading digital work platform company. Renu is an experienced technology marketer with a deep understanding of products, industry, and customers spanning mobile, wireless networking and collaboration solutions across large and mid-size organizations. Prior to Omnissa, she served as vice president of Marketing for VMware's End-user Computing (EUC) business. In that role, she led marketing strategy and was responsible for customer messaging, demand, content marketing, sales and technical enablement, and product pricing strategy. She oversaw marketing programs and campaigns for EUC's comprehensive portfolio of solutions including employee engagement programs. Prior to VMware, Renu held senior product marketing roles at leading companies including Good Technology, Cisco Systems and AT&T Wireless. ,Yes,This will be completed shortly Renu Upadhyay on LinkedIn: https://www.linkedin.com/in/renuupadhyay/ Resources Omnissa: https://www.omnissa.com/ Take your personal data back with Incogni! Use code AGILE at the link below and get 60% off an annual plan: https://incogni.com/agile The Agile Brand podcast is brought to you by TEKsystems. Learn more here: https://www.teksystems.com/versionnextnow Catch the future of e-commerce at eTail Palm Springs, Feb 23-26 in Palm Springs, CA. Go here for more details: https://etailwest.wbresearch.com/Drive your customers to new horizons at the premier retail event of the year for Retail and Brand marketers. Learn more at CRMC 2026, June 1-3. https://www.thecrmc.com/ Enjoyed the show? Tell us more at and give us a rating so others can find the show at: https://advertalize.com/r/faaed112fc9887f3 Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstromDon't miss a thing: get the latest episodes, sign up for our newsletter and more: https://www.theagilebrand.showCheck out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. https://www.missinglink.company

Agile in Construction: The Product Owner Role in Construction—Voice of the Customer Across Every Phase With Felipe Engineer-Manriquez 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. In this episode, we refer to Extreme Ownership by Jocko Willink and Team of Teams by General Stanley McChrystal, as well as our Agile in Construction episodes. The Great Product Owner: Bringing the Voice of the Customer to Every Decision "I want you to think like the owner, and bring that to the team meetings, because we can't have the owner in the meetings with us." - Felipe Engineer-Manriquez   The Product Owner role in construction is radically different from software—and Felipe has learned to find it in unexpected places. When Jeff Sutherland told his class to "tear up your business cards" because only three roles exist (Developer, Scrum Master, Product Owner), construction people were confused. Felipe's approach: ask the team who can bring the voice of the customer. Sometimes it's the superintendent, interfacing daily with charge nurses and doctors in a working hospital. Sometimes it's a project executive. Rarely, it's the project manager. The key is that the PO role changes across phases because every day in construction is brand new—the building is physically taking shape. Felipe studied military leadership in Extreme Ownership and Team of Teams and found strong product owner culture—leaders who brought customer voice to cell-level teams against hierarchical norms. Great product owners speak in terms of what the customer wants, transforming how teams prioritize and align naturally.   Self-reflection Question: Who on your team currently embodies the voice of the customer, and how might you coach them to bring that perspective more explicitly to every team interaction? The Bad Product Owner: When Gut Decisions Override Value "Value is a beneficial transformation of materials, information, or a combination of both. Let's not do things that don't transform information or materials." - Felipe Engineer-Manriquez   Felipe shares a powerful anti-pattern: owners who make gut decisions based on past project trauma without checking if conditions are still true. On a $100 million project, an owner repeatedly introduces work that doesn't add value—reacting to bad things that happened on previous projects, even when those conditions no longer exist. The result? Teams waste time on activities that don't transform materials or information. Felipe teaches teams an industrial engineering definition of value: "a beneficial transformation of materials, information, or a combination of both." Status updates that don't change behavior are waste. Markings on metal decking that will be buried under 5 inches of concrete are waste. The fix? Make the backlog visible and ask: "Where should we zipper this in so it has the most impact on transforming materials or information?" For construction, prioritization always comes back to getting the right materials in place, one time, at the right time—not touching things twice.   Self-reflection Question: When stakeholders introduce work based on past experiences, how do you help them evaluate whether those conditions still apply to the current situation?   [The Scrum Master Toolbox Podcast Recommends]

Agile in Construction: Team Happiness as the True Measure of Scrum Master Success in Construction With Felipe Engineer-Manriquez 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 teams that are having fun and are light-hearted, making jokes—these are high-performing teams almost 99% of the time. But the teams that are overly sarcastic or too quiet? They're burning out." - Felipe Engineer-Manriquez   Felipe offers a refreshingly human definition of success for Scrum Masters: team happiness. After years of traumatic experiences in construction—days when he pounded his steering wheel in frustration during his commute—Felipe developed what he calls being a "human thermometer." He can sense a team's emotional state within 5 minutes of being with them. His proxy for success is a simple Likert scale of 1-5: 5 is Nirvana (working at Google with massages), and 1 is wanting to jump out the window. Felipe emphasizes that most people in construction internalize stress and push it down, so you have to ask directly. When he asked an estimator this question, the man quietly admitted he was at a 2—ready to walk away. Without asking, Felipe would never have known. The key insight: schedule improvements happen as teams move closer to a 5. And the foundation of it all? Understanding. "People do not have an overt need to be loved," Felipe shares from his Scrum training. "They have an overt need to be understood." A successful Scrum Master meddles appropriately, runs toward problems, and focuses on understanding teammates before trying to implement change.   Self-reflection Question: If you asked each of your team members to rate their happiness from 1-5 today, what do you think they would say, and what would you learn that you don't currently know? Featured Retrospective Format for the Week: Start/Stop/Keep Felipe's favorite retrospective format is Start/Stop/Keep—but his approach to introducing it is what makes the difference. He connects it to something construction teams already know: the post-mortem. He explains the morbid origin of the term (surgeons standing around a dead patient discussing what went wrong) to emphasize the seriousness of learning. Then he reframes the retrospective as a recurring post-mortem—a "lessons learned" cycle. Start: What should we begin doing that will make things better? Stop: What should we no longer do that doesn't add value? Keep: What good things are we doing that we want to maintain? Felipe uses silent brainstorming so everyone has time to think, then makes responses visible on a whiteboard or digital display. The cadence scales with sprint length—45 minutes for a week, 2 hours for two weeks, half a day for a month. His current team committed to monthly retrospectives and pre-writes their Start/Stop/Keep items, making the facilitated session efficient and focused.   [The Scrum Master Toolbox Podcast Recommends]

When an AI agent makes a decision that costs your company millions in a lawsuit, who do you fire? Agility requires both the speed to adopt new technologies like AI agents, as well as the foresight to build the guardrails that prevent that speed from driving your brand off a cliff. Today, we're going to talk about the hidden crisis brewing behind the AI revolution: the accountability gap. As companies race to replace roles with autonomous AI agents, a critical question is being ignored: when an agent makes a biased, unethical, or simply wrong decision that harms a customer or an employee, who is actually responsible? This isn't a future problem; it's happening right now, and it poses a massive threat to brand trust, customer relationships, and legal standing. To help me discuss this topic, I'd like to welcome, Albert Castellana, Co-Founder & CEO at GenLayer. About Albert Castellana Albert Castellana on LinkedIn: https://www.linkedin.com/in/acastellana/ Resources GenLayer: https://www.genlayer.com Take your personal data back with Incogni! Use code AGILE at the link below and get 60% off an annual plan: ⁠https://incogni.com/agile⁠  The Agile Brand podcast is brought to you by TEKsystems. Learn more here: https://www.teksystems.com/versionnextnow Drive your customers to new horizons at the premier retail event of the year for Retail and Brand marketers. Learn more at CRMC 2026, June 1-3. https://www.thecrmc.com/ Enjoyed the show? Tell us more at and give us a rating so others can find the show at: https://ratethispodcast.com/agile Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstrom Don't miss a thing: get the latest episodes, sign up for our newsletter and more: https://www.theagilebrand.show Check out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. https://www.missinglink.company

Agile in Construction: The DOWNTIME Strategy—Eliminating Waste Before Adding Process With Felipe Engineer-Manriquez 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.   "My first rule is that I will do no harm. And if something goes wrong, I will take full responsibility with leadership. My neck is literally on the line." - Felipe Engineer-Manriquez   Felipe shares his change strategy for introducing Lean and Agile into construction projects, and it starts with an unexpected principle borrowed from Hippocrates: do no harm. He explicitly tells teams this promise, putting his neck on the line to build trust. But the real magic happens in what comes next: instead of adding new processes, Felipe first helps teams stop doing things. Using the DOWNTIME acronym (Defects, Overproduction, Waiting, Transportation, Inventory, Motion, Excess processing), he identifies wasteful activities that don't add value. In construction, 60-80% of every dollar doesn't add value from the customer's perspective—compared to manufacturing (above 50% value) or agriculture (90% value). Felipe's approach: eliminate waste first to create excess capacity, then introduce new processes. On a project that was 2 years behind schedule with lawyers already engaged, he spent just 5 minutes with the team defining a visible milestone goal on a whiteboard. Two weeks later, they met their schedule and improved by 4 days—the first time ever. The superintendent said, "Never in the entire time I've worked here have we ever met a schedule commitment." The secret? Free up capacity before adding anything new.   In this episode, we refer to the 8 wastes video by Orbus and WIP limits.   Self-reflection Question: Before introducing your next process improvement, what wasteful activity could you help your team stop doing to free up the capacity they need to embrace change?   [The Scrum Master Toolbox Podcast Recommends]

Hiring for Scrum roles is harder than it looks. Making the wrong call can derail an Agile transformation before it even starts. In this episode, Brian and Cort unpack what to actually look for in Scrum Masters, Product Owners, and Developers—beyond the job title and shiny certifications.

Spotify never used the Spotify Model - and neither should you. In this $2 billion episode, Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel take a cutting torch to one of big-A-Agile's most beloved organizational myths - the Spotify Model! We're doing invasive surgery to see what's inside beyond the over-hyped squads, tribes, chapters, and guilds that have been copied by companies the world over. ...but what if we found out that the inside was hollow? What if we found out that the Spotify Model was never even live and tested by Spotify?

Agile in Construction: Over-Commitment and Silence—The Deadly Duo Destroying Your Teams With Felipe Engineer-Manriquez 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 don't think people are bad. They don't self-destruct because they're bad. What I do see is people getting crushed in terribly bad systems." - Felipe Engineer-Manriquez   Felipe shares a powerful insight about team dysfunction: teams don't self-destruct because of bad people—they get crushed by broken systems. On a hospital construction project, he witnessed a dangerous pattern: over-commitment coupled with silence. People would commit to pouring concrete on Thursday when there wasn't even rebar in place—a physical impossibility. But psychological safety was so low that no one could say the emperor had no clothes. Felipe's approach? Ask obvious questions that break the pattern. "Don't you need this so you can do that?" This simple question, framed with verb-noun phrases, surfaces what cannot be spoken. He positions himself as "just a simple, dumb general contractor" who doesn't understand—creating safety for others to speak truth. The turning point comes when you slow down, make work visible, and allow people to say no. As Felipe puts it: "For real accountability, if people are not allowed to say no, then they actually can't make a real promise." Silence is not alignment, and saying yes in low-trust environments is actually hiding from accountability.   In this segment, we talk about psychological safety and systems thinking in team dynamics.   Self-reflection Question: When you see a team over-committing to impossible deadlines, what question could you ask that surfaces the truth without putting individuals at risk? Featured Book of the Week: The Goal by Eliyahu Goldratt Felipe chose The Goal by Eliyahu Goldratt as the most transformative book of his early lean career. He describes it as "the number one game changer"—a fictional story that teaches the Theory of Constraints in a way you can internalize. The famous "Herbie story" within the book illustrates how helping the slowest part of a process speeds up the entire system. Felipe emphasizes that Theory of Constraints is often skipped in Scrum training when classes run out of time, leaving many credentialed Scrum Masters without this essential knowledge. He uses these principles daily with the Last Planner System in construction—creating visual boards that look like Gantt charts (because construction loves schedules) but function like Scrum boards with days of the week instead of "to do, doing, done."   [The Scrum Master Toolbox Podcast Recommends]

Story Point Estimations are failing your Team! - Here We Go Again...Story Pointing wasn't a completely novel idea. It evolved out of the Delphi method — a research technique that helped drive consensus and forecasting built on collective wisdom. In 1950s, RAND Corporation began using it as a way to forecast the effect of technology on warfare.So, it wasn't just an idea dreamed up by someone in the Agile community randomly — no. It's actually based on a scientific approach. Something that's been applied and true in other disciplines for many, many years.And, when Scrum needed a prescriptive technique to help the Teams estimate and measure the amount of work the Team could consistently deliver Sprint after Sprint, this became a recommended approach.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/

Unlock the Power of Human-Centric AI for Your Business. In this episode of Agile in Action, host Bill Raymond sits down with Bill Ryan, founder and partner at Sync(d) AI, to explore how businesses can leverage AI to work smarter, not harder. Discover how AI is transforming the way small businesses operate, from creating comprehensive marketing plans in hours instead of weeks, to implementing intelligent agentic workflows that automate repetitive tasks while keeping humans in the loop. What you will learn: ✅ The human-centric approach to AI implementation that enhances rather than replaces your team ✅ How agentic AI and autonomous workflows can streamline business processes ✅ Real-world examples, including how a global bottling company uses AI to optimize inventory and reduce environmental impact ✅ Practical steps to get started with AI in your organization ✅ The importance of governance and responsible AI use Whether you're a company of 10 looking to punch above your weight or an established business ready to scale, this conversation offers actionable insights on implementing AI thoughtfully and effectively. Key Takeaway: Start small, choose one problem to solve, and build from there.

For many legal professionals, one of the most persistent sources of stress isn't the complexity of the law itself but the uncertainty that permeates daily work. Not knowing who's doing what, when something is actually done, or whether it's been done correctly.In this episode, I'm tackling this uncertainty head-on by showing you how to create explicit quality standards that serve as a stabilizing force for your practice with simple, easy-to-implement tools. You'll learn how to create fit-for-purpose quality standards, why explicit policies reduce rework, and practical guidance on developing these standards in the context of your current work without trying to boil the ocean.Get full show notes, transcript, and more information here: agileattorney.com/104Take your law practice from overwhelmed to optimized with GreenLine LegalFollow along on LinkedIn: linkedin.com/in/johnegrant

For years, we've heard about AI transforming software development. But what if that same level of agentic, AI-driven collaboration could be applied not just to writing code, but to writing your entire go-to-market playbook? Agility requires that your go-to-market teams operate at the speed of insight, not at the speed of manual data entry and fragmented workflows. This means empowering them with tools that don't just provide data, but automate action based on strategic intent. Today, we're going to talk about the concept of an 'agentic' go-to-market platform, where AI doesn't just assist, but actively collaborates with sales and marketing teams to automate entire workflows, from strategy to execution. To help me discuss this topic, I'd like to welcome, Marcio Arnecke, Chief Marketing Officer at Apollo.io. About Marcio Arnecke As Apollo.io's Chief Marketing Officer, Marcio Arnecke brings a visionary approach to scaling high-growth B2B SaaS marketing in the AI-driven sales landscape. With over two decades of experience driving revenue acceleration across global markets, he has consistently transformed early-stage technology companies into market-defining brands. Hisexpertise in AI-powered go-to-market strategies uniquely positions him to accelerate Apollo's mission of empowering sales teams through intelligent data and automation. Previously, he played a pivotal role in scaling marketing functions at SaaS giants like Intercom and Zendesk, where he drove remarkable growth from $40M to $1.7B, culminating in a successful IPO that raised $100 million in 2014. Leveraging his comprehensive background in demand generation, product marketing, and strategic storytelling, Marcio is focused on positioning Apollo as the go-to AI sales platform for SMB and mid-market teams. His approach combines data-driven insights with targeted narrative strategies, translating Apollo's technological capabilities into practical business value. Drawing from his global experience across Silicon Valley and international markets, Marcio aims to expand Apollo's brand and demonstrate how AI can meaningfully improve sales engagement for growing businesses. Marcio holds advanced degrees from Stanford University's Graduate School of Business and Golden Gate University, complemented by a BS in Business Administration from Universidade Feevale in Brazil. Marcio Arnecke on LinkedIn: https://www.linkedin.com/in/marcioarnecke/ Resources Apollo.io: https://www.apollo.io Take your personal data back with Incogni! Use code AGILE at the link below and get 60% off an annual plan: https://incogni.com/agile  The Agile Brand podcast is brought to you by TEKsystems. Learn more here: https://www.teksystems.com/versionnextnow Catch the future of e-commerce at eTail Palm Springs, Feb 23-26 in Palm Springs, CA. Go here for more details: https://etailwest.wbresearch.com/ Drive your customers to new horizons at the premier retail event of the year for Retail and Brand marketers. Learn more at CRMC 2026, June 1-3. https://www.thecrmc.com/ Enjoyed the show? Tell us more at and give us a rating so others can find the show at: https://ratethispodcast.com/agile Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstrom Don't miss a thing: get the latest episodes, sign up for our newsletter and more: https://www.theagilebrand.show Check out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com The Agile Brand is produced by Missing Link—a Latina-owned strategy-driven, creatively fueled production co-op. From ideation to creation, they craft human connections through intelligent, engaging and informative content. https://www.missinglink.company

Agile in Construction: Stop Teaching and Start Doing—The Secret to Agile Adoption in Construction With Felipe Engineer-Manriquez 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 forgot a couple key things. Number one, they don't have the enthusiasm and love for these new ways of working like I do because they didn't understand the problem that they were in." - Felipe Engineer-Manriquez   Felipe shares a powerful failure story from his early days adopting Lean and Agile in construction. After discovering Jeff Sutherland's "Red Book" and experiencing incredible results using Scrum with his 4-year-old son on a weekend project, he was eager to bring these methods to his construction team. The problem? He immediately went into teaching mode. His boss Nate and the rest of the team wanted nothing to do with Scrum—they Googled it, saw it was "a software thing," and shut down completely. This is what Felipe now calls the "Not Invented Here Syndrome"—people resist ideas that don't originate from their domain. The breakthrough came when Felipe stopped teaching and started doing. He calls it the "ninja Scrum approach"—embodying the processes and tools without labeling them, making work visible, and delivering results.  When he managed $25 million worth of scopes using these methods silently, one project manager named Tom stopped him and said, "We've never come to a project where people held their promises." Within a year, even his resistant boss Nate acknowledged the transformation in a post-mortem review. The lesson: don't teach until people pull for the teaching.   In this episode, we refer to NoEstimates and Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland.   Self-reflection Question: When you introduce new practices to a team, do you wait until they pull for the teaching, or do you default to explaining before they've seen the value?   [The Scrum Master Toolbox Podcast Recommends]

Time to Stop Doing and Start Leveraging Agile Let’s get real about the current state of Agile in our industry and what it means for your career. I get the fear and uncertainty many of us are feeling. We’re seeing pay cuts, shrinking opportunities, and the sense that the “glory days” of Agile might be over. But it’s not the end. Agile as a mindset and practice isn’t going away anytime soon. Companies still value Agile, even if it’s not feeding hype and dollars into it the way they once were. We’re now at the mature end of adoption curve. Like any other tech trend, the “new frontier” phase might be over, but there is lasting value in your Agile skills. As long as you’re leveraging Agile for the benefit of customers and shareholders, rather than policing framework rules. There are two main paths forward: you can leverage your Agile experience entrepreneurially by bringing it to new business areas, or you can help organizations connect Agile to real business outcomes, especially as companies struggle to harness technologies like AI. The future is about leveraging Agile and integrating it into business operations for tangible results, not following the mechanics. Waiting for the perfect new role isn’t a strategy. It’s time to get creative, gritty, and proactive. There are no well-worn paths here. You’ll have to use your skills of experimentation and continuous learning to restore momentum in your career. If you’ve been feeling stuck or like it’s time to give up on Agile, it’s time to think differently and seize new opportunities. Time to shift to Leveraging Agile. **GET THE BUSINESS OUTCOMES PARTNER PLAYBOOK** Learn how to deliver undeniable ROI that saves your job and accelerates your future https://learning.fusechamber.com/outcomes-partner-playbook **FORGE GENESIS IS HERE** All the skills you need to stop relying on job postings and start enjoying the freedom of an Agile career on YOUR terms. First cohort starts in Jan 2026 https://learning.fusechamber.com/forge-genesis **THE ALL NEW FORGE LIGHTNING** 12 Weeks to elite leadership! https://learning.fusechamber.com/forge-lightning **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.

In this episode, Bill Scherkenbach, one of W. Edwards Deming's closest protégés, and host Andrew Stotz discuss why leadership decisions shape outcomes far more than frontline effort. Bill draws on decades of firsthand experience with Deming and with businesses across industries. Through vivid stories and practical insights, the conversation challenges leaders and learners alike to rethink responsibility, decision-making, and what it truly takes to build lasting quality. Bill's powerpoint is available here. TRANSCRIPT 0:00:02.2 Andrew Stotz: My name is Andrew Stotz, and I'll be your host as we dive deeper into the teachings of Dr. W. Edwards Deming. Today, I'm continuing my discussions with Bill Scherkenbach, a dedicated protégé of Dr. Deming since 1972. Bill met with Dr. Deming more than a thousand times and later led statistical methods and process improvement at Ford and GM at Dr. Deming's recommendation. He authored the Deming Route to Quality and Productivity at Deming's behest and at 79, still champions his mentor's message: Learn, have fun, and make a difference. The discussion for today is, I think we're going to get an answer to this question. And the question is: Where is quality made? Bill, take it away.   0:00:44.9 Bill Scherkenbach: Where is quality made? I can hear the mellifluous doctor saying that. And the answer is: In the boardroom, not on the factory floor. And over and over again, he would say that it's the quality of the decisions that the management make that can far outweigh anything that happens on the shop floor. And when he would speak about that, he would first of all, because he was talking to the auto industry, he would talk about who's making carburetors anymore. "Nobody's making carburetors because it's all fuel injectors," he would say. And anyone who has been following this, another classic one is: Do you ever hear of a bank that failed? Do you think that failed because of mistakes in tellers' windows or calculations of interest? Heck no. But there are a whole bunch of other examples that are even more current, if you will. I mean, although this isn't that current, but Blockbuster had fantastic movies, a whole array of them, the highest quality resolutions, and they completely missed the transition to streaming. And Netflix and others took it completely away from them because of mistakes made in the boardroom. You got more recently Bed Bath & Beyond having a great product, a great inventory.   0:02:51.4 Bill Scherkenbach: But management took their eyes off of it and looked at, they were concerned about stock buybacks and completely lost the picture of what was happening. It was perfect. It was a great product, but it was a management decision. WeWork, another company supplying office places. It was great in COVID and in other areas, but through financial mismanagement, they also ended up going bust. And so there are, I mean, these are examples of failures, but as Dr. Deming also said, don't confuse success with success. If you think you're making good decisions, you got to ask yourself how much better could it have been if you tried something else. So, quality is made in the boardroom, not on the factory floor.   0:04:07.9 Andrew Stotz: I had an interesting encounter this week and I was teaching a class, and there was a guy that came up and talked to me about his company. His company was a Deming Prize from Japan winner. And that was maybe 20, 25 years ago. They won their first Deming Prize, and then subsidiaries within the company won it. So the actual overall company had won something like nine or 10 Deming Prizes over a couple decades. And the president became...   0:04:43.5 Bill Scherkenbach: What business are they in?   0:04:45.5 Andrew Stotz: Well, they're in...   0:04:47.0 Bill Scherkenbach: Of winning prizes?   0:04:48.7 Andrew Stotz: Yeah, I mean, they definitely, the CEO got the distinguished individual prize because he was so dedicated to the teachings of Dr. Deming. And he really, really expanded the business well, the business did well. A new CEO took over 15 years ago, 10 years ago, and took it in another direction. And right now the company is suffering losses and many other problems that they're facing. And I asked the guy without talking about Deming, I just asked him what was the difference between the prior CEO and the current one or the current regimes that have come in. And he said that the prior CEO, it was so clear what the direction was. Like, he set the direction and we all knew what we were doing. And I just thought now as you talk about, the quality is made at the boardroom, it just made me really think back to that conversation and that was what he noticed more than anything. Yeah well, we were really serious about keeping the factory clean or we used statistics or run charts, that was just what he said, I thought that was pretty interesting.   0:06:06.7 Bill Scherkenbach: Absolutely. And that reminds me of another comment that Dr. Deming was vehement about, and that was was the management turnover. Turnovers in boardrooms every 18 months or so, except maybe in family businesses. But that's based on the quality of decisions made in the boardroom. How fast do you want to turn over the CEOs and that C-suite? So it's going to go back to the quality is made in the boardroom.   0:06:50.0 Andrew Stotz: Yeah, and I think maybe it's a good chance for me to share the slide that you have. And let's maybe look at that graphic. Does that makes sense now?   0:07:00.9 Bill Scherkenbach: Sure, for sure.   0:07:02.2 Andrew Stotz: Let's do that. Let's do that. Hold on. All right.   0:07:15.8 Bill Scherkenbach: Okay, okay, okay. You can see on the top left, we'll start the story. I've got to give you a background. This was generated based on my series of inputs and prompts, but this was generated by Notebook LM and based on the information I put in, this is what they came up with.   0:07:48.6 Andrew Stotz: Interesting.   0:07:50.1 Bill Scherkenbach: Based on various information, which I think did a fairly decent job. In any event, we're going to talk about all of these areas, except maybe the one where it says principles for active leadership, because that was the subject of a couple of our vlogs a while ago, and that is the three foundational obligations. And so the thing is that quality, even though Dr. Deming said it was made in the boardroom, one of the problems is that management did not know what questions to ask, and they would go, and Dr. Deming railed against MBWA, management by walking around, primarily because management hadn't made the transition to really take on board what Dr. Deming was talking about in profound knowledge. And that is, as you've mentioned, setting that vision, continually improving around it, and pretty much absolutely essential was to reduce fear within the organization.   0:09:25.9 Bill Scherkenbach: And so management by walking around without profound knowledge, which we've covered in previous talks, only gets you dog and pony shows. And with the fear in the organization, you're going to be carefully guided throughout a wonderful story. I mentioned I was in Disney with some of my granddaughters over the holidays, and they tell a wonderful story, but you don't ever see what's behind the scenery. And management never gets the chance because they really haven't had the opportunity to attain profound knowledge. So that's one of the things. I want to back up a little bit because Dr. Deming would... When Dr. Deming said quality is made at the top, he only agreed to help companies where the top management invited him, he wasn't out there marketing. If they invited him to come in, he would first meet with them and they had to convince him they were serious about participating, if not leading their improvement. And given that, that litmus test, he then agreed to work with them. Very few companies did he agree to on that. And again as we said, the quality of the decisions and questions and passion that determine the successfulness of the company. And so.   0:11:40.0 Andrew Stotz: It made me think about that letter you shared that he was saying about that there was, I think it was within the government and government department that just wasn't ready for change and so he wasn't going to work with it. I'm just curious, like what do you think was his... How did he make that judgment?   0:12:00.0 Bill Scherkenbach: Well, it wasn't high enough. And again, I don't know how high you'd have to go in there. But quite honestly, what we spoke about privately was in politics and in the federal government, at least in the US, things change every four years. And so you have management turnover. And so what one manager, as you described, one CEO is in there and another one comes in and wants to do it their way, they're singing Frank Sinatra's My Way. But that's life….   0:12:49.3 Andrew Stotz: Another great song.   0:12:50.7 Bill Scherkenbach: Another, yes.   0:12:52.1 Andrew Stotz: And it's not like he was an amateur with the government.   0:12:57.5 Bill Scherkenbach: No.   0:13:00.3 Andrew Stotz: He had a lot of experience from a young age, really working closely with the government. Do you think that he saw there was some areas that were worth working or did he just kind of say it's just not worth the effort there or what was his conclusions as he got older?   0:13:16.9 Bill Scherkenbach: Well, as he got older, it might, it was the turnover in management. When he worked for Agriculture, although agriculture is political, and he worked for Census Bureau back when he worked there, it wasn't that political, it's very political now. But there was more a chance for constancy and more of a, their aim was to do the best survey or census that they could do. And so the focus was on setting up systems that would deliver that. But that's what his work with the government was prior to when things really broke loose when he started with Ford and GM and got all the people wanting him in.   0:14:27.0 Andrew Stotz: I've always had questions about this at the top concept and the concept of constancy of purpose. And I'm just pulling out your Deming Route to Quality and Productivity, which, it's a lot of dog ears, but let's just go to chapter one just to remind ourselves. And that you started out with point number one, which was create constancy of purpose towards improvement of product and service with the aim to become competitive, stay in business and provide jobs. One of my questions I always kind of thought about that one was that at first I just thought he was saying just have a constancy of purpose. But the constancy of purpose is improvement of product and service.   0:15:13.6 Bill Scherkenbach: Well, yes and no. I mean, that's what he said. I believe I was quoting what his point number one was. And as it developed, it was very important to add, I believe, point number five on continual improvement. But constancy of purpose is setting the stage, setting the vision if you will, of where you want to take the company. And in Western management, and this is an area where there really is and was a dichotomy between Western and Eastern management. But in Western management, our concept of time was short-term. Boom, boom, boom, boom. And he had a definite problem with that. And that's how you could come up with, well, we're going to go with this fad and that fad or this CEO and that CEO. There was no thinking through the longer term of, as some folks ask, "what is your aim? Who do you think your customer base is now?" don't get suckered into thinking that carburetors are always going to be marketable to that market base. And so that's where he was going with that constancy of purpose. And in the beginning, I think that was my first book you're quoting, but also, in some of his earlier works, he also spoke of consistency of purpose, that is reducing the variation around that aim, that long-term vision, that aim.   0:17:19.2 Bill Scherkenbach: Now, in my second book, I got at least my learning said that you've got to go beyond the logical understanding and your constancy of purpose needs to be a mission, a values and questions. And those people who have who have listened to the the previous vlogs that we've had, those are the physiological and emotional. And I had mentioned, I think, that when when I went to GM, one of the things I did was looked up all the policy letters and the ones that Alfred Sloan wrote had pretty much consistency of three main points. One, make no mistake about it, this is what we're going to do. Two, this is why we're going to do it, logical folks who need to understand that. And to give a little bit of insight on on how he was feeling about it. Sometimes it was value, but those weren't spoken about too much back then. But it gave you an insider view, if you will. And so I looked at that, maybe I was overlooking. But I saw a physiological and emotional in his policy letters.   0:19:00.7 Bill Scherkenbach: And so that's got to be key when you are establishing your vision, but that's only the beginning of it. You have to operationalize it, and this is where management has to get out of the boardroom to see what's going on. Now, that's going to be the predictable, and some of your clients, and certainly the ones over in Asia, are speaking about Lean and Toyota Production System and going to the Gemba and all of those terms. But I see a need to do a reverse Gemba and we'll talk about that.   0:19:49.6 Andrew Stotz: So, I just want to dig deeper into this a little bit just for my own selfish understanding, which I think will help the audience also. Let's go back in time and say that the, Toyota, let's take Toyota as an example because we can say maybe in the 60s or so, they started to really understand that the improvement of product quality, products and service quality and all that was a key thing that was important to them. But they also had a goal of expanding worldwide. And their first step with that maybe was, let's just say, the big step was expanding to the US. Now, in order to expand to the US successfully, it's going to take 10, maybe 20 years. In the beginning, the cars aren't going to fit the market, you're going to have to adapt and all that. So I can understand first, let's imagine that somebody says our constancy of purpose is to continuously improve or let's say, not continuously, but let's just go back to that statement just to keep it clear. Let's say, create constancy of purpose towards improvement of product and service with the aim to become competitive, stay in business and provide jobs.   0:21:07.2 Andrew Stotz: So the core constancy in that statement to me sounds like the improvement. And then if we say, okay, also our vision of where we want to be with this company is we want to capture, let's say, 5% of the US market share within the next 15 years or five or 10 years. So you've got to have constancy of that vision, repeating it, not backing down from it, knowing that you're going to have to modify it. But what's the difference between a management or a leadership team in the boardroom setting a commitment to improvement versus a commitment to a goal of let's say, expanding the market into the US. How do we think about those two.   0:21:53.6 Bill Scherkenbach: Well as you reread what I wrote there, which is Dr. Deming's words and they led into the, I forget what he called it, but he led into the progression of as you improve quality, you improve productivity, you reduce costs.   0:22:33.6 Andrew Stotz: Chain reaction.   0:22:34.5 Bill Scherkenbach: Yeah, the chain reaction. That's a mini version of the chain reaction there. And at the time, that's what people should be signing up for. Now the thing is that doesn't, or at least the interpretations haven't really gone to the improvement of the board's decision-making process. I mean, where he was going for was you want to be able to do your market research because his sampling and doing the market research was able to close the loop to make that production view a system, a closed-loop system. And so you wanted to make sure that you're looking far enough out to be able to have a viable product or service and not get caught up in short-term thinking. Now, but again, short-term is relative. In the US, you had mentioned 10 or 20 years, Toyota, I would imagine they still are looking 100 years out. They didn't get suckered into the over-committing anyway to the electric vehicles. Plug-in hybrids, yes, hybrids yes, very efficient gas motors, yes. But their constancy of purpose is a longer time frame than the Western time frame.   0:24:27.1 Andrew Stotz: Yeah, that was a real attack on the structure that they had built to say when they were being told by the market and by everybody, investors, you've got to shift now, you've got to make a commitment to 100% EVs. I remember watching one of the boardroom, sorry, one of the shareholder meetings, and it's just exhausting, the pressure that they were under.   0:24:55.2 Bill Scherkenbach: Yep, yep. But there... Yeah.   0:25:00.0 Andrew Stotz: If we take a kid, a young kid growing up and we just say, look, your main objective, and my main objective with you is to every day improve. Whatever that is, let's say we're learning science.   0:25:17.3 Bill Scherkenbach: You're improving around your aim. What is your vision? What are you trying to accomplish? And that obviously, if you're you're saying a kid that could change otherwise there'd be an oversupply of firemen.   0:25:38.5 Andrew Stotz: So let's say that the aim was related to science. Let's say that the kid shows a really great interest in science and you're kind of coaching them along and they're like, "Help me, I want to learn everything I can in science." The aim may be a bit vague for the kid, but let's say that we narrow down that aim to say, we want to get through the main topics of science from physics to chemistry and set a foundation of science, which we think's going to take us a year to do that, let's just say. Or whatever. Whatever time frame we come up with, then every day the idea is, how do we number one improve around that aim? Are we teaching the right topics? Also, is there better ways of teaching? Like, this kid maybe learns better in the afternoon and in the morning, whereas another kid I may work with works better in another... And this kid likes five-minute modules and then some practical discussion, this kid likes, an hour of going deep into something and then having an experiment is when we're talking about improvement, is the idea that we're just always trying to improve around that aim until we reach a really optimized system? Is that what we're talking about when we're talking about constancy of purpose when it comes to improving product and service?   0:27:14.4 Bill Scherkenbach: Well there's a whole process that I take my clients through in coming up with their constancy of purpose statement. And the board should be looking at what the community is doing in the next five years, 10 years, where the market is going, where politics is going, all sorts of things. And some of it. I mean, specifically in the science area, it's fairly well recognized that the time of going generation to generation to generation has gone from years to maybe weeks where you have different iterations of technology. And so that's going to complicate stuff quite honestly, because what was good today can be, as Dr. Deming said, the world could change. And that's what you've got to deal with or you're out of business. Or you're out of relevance in what you're studying. And so you have to... If you if you have certain interests, and the interests are driven... It's all going to be internal. Some interests are driven because that's where I hear you can make the most money or that's where I hear you can make the most impact to society or whatever your internal interests are saying that those are key to establishing what your aim is.   0:29:25.7 Andrew Stotz: Okay. You've got some PowerPoints and we've been talking about some of it. But I just want to pull it up and make sure we don't miss anything. I think this is the first text page, maybe just see if there's anything you want to highlight from that. Otherwise we'll move to the next.   0:29:43.0 Bill Scherkenbach: No I think we've we've covered that. Yeah, yeah. And the second page. Yeah, I wanted to talk and I only mentioned it when the Lean folks and the Agile folks talk about Gemba, they're pretty much talking about getting the board out. It's the traditional management by walking around, seeing what happens. Hugely, hugely important. But one of the things, I had one of my clients. Okay, okay. No, that's in the the next one.   0:30:29.4 Andrew Stotz: There you go.   0:30:30.7 Bill Scherkenbach: Okay, yeah. I had one of one of my clients do a reverse Gemba. And that is, that the strategy committee would be coming up with strategies and then handing it off to the operators to execute. And that's pretty much the way stuff was done in this industry and perhaps in many of them. But what we did was we had the operators, the operating committee, the operations committee, sit in as a peanut gallery or a, oh good grief. Well, you couldn't say a thing, you could only observe what they were doing. But it helped the operators better understand and see and feel what the arguments were, what the discussions were in the strategy, so that they as operators were better able to execute the strategy. And so not the board going out and down, but the folks that are below going up if it helps them better execute what's going on. But vice versa, management can't manage the 94%, and Dr. Deming was purposely giving people marbles, sometimes he'd say 93.4%. You know the marble story?   0:32:37.5 Andrew Stotz: I remember that [laughter]. Maybe you should tell that again just because that was a fun one when he was saying to, give them marbles, and they gave me marbles back.   0:32:45.7 Bill Scherkenbach: Yeah, yeah, yeah. Well, he said there was this professor in oral surgery that said there was a an Asian mouse or cricket, whatever, that would... You put in your mouth and they would eat all of the... Be able to clean the gums of all the bacteria better than anything. And described it in detail. And that question was on the test. Okay, please describe this mouse procedure. And he said all of the people, or a whole bunch of people except one, gave him back exactly step by step that he had taught. And one said, Professor, I've talked to other professors, I've looked around, I think you're loading us, that's what Deming said. And so he made the point that teaching should not be teachers handing out marbles and collecting the same marbles they they handed out. And so to some extent, he was testing, being overly precise.   0:34:12.8 Bill Scherkenbach: He wanted people to look into it, to see, go beyond as you were speaking of earlier, going beyond this shocking statement that there perhaps is some way that that really makes sense. So he wants you to study. Very Socratic in his approach to teaching in my opinion. And any event, management can't understand or make inputs on changing what the various levels of willing workers, and you don't have to be on the shop floor, you can be in the C-suite and be willing workers depending on how your company is operating. Go ahead.   0:35:12.0 Andrew Stotz: So let me... Maybe I can, just for people that don't know, Gemba is a Japanese word that means "the actual place," right? The place where the value is created.   0:35:23.8 Bill Scherkenbach: Sure.   0:35:26.2 Andrew Stotz: And the whole concept of this was that it's kind of almost nonsense to think that you could sit up in an office and run something and never see the location of where the problem's happening or what's going on. And all of a sudden many things become clear when you go to the location and try to dig down into it. However, from Dr. Deming context, I think what you're telling us is that if the leader doesn't have profound knowledge, all they're going to do is go to the location and chase symptoms and disrupt work, ultimately...   0:36:02.0 Bill Scherkenbach: Get the dog and pony shows and all of that stuff. And they still won't have a clue. The thing is...   0:36:08.6 Andrew Stotz: So the objective at the board level, if they were to actually go to the place, the objective is observation of the system, of how management decisions have affected this. What is the system able to produce? And that gives them a deeper understanding to think about what's their next decision that they've got to make in relation to this. Am I capturing it right or?   0:36:40.2 Bill Scherkenbach: Well there's a lot more to it, I think, because top management, the board level, are the ones that set the vision, the mission, the values, the guiding principle, and the questions. And I think it's incumbent on the board to be able to go through the ranks and see how their constancy of purpose, the intended, where they want to take the place is being interpreted throughout the organization because, and I know it's an oversimplification and maybe a broad generalization, but middle management... Well, there are layers of management everywhere based on their aim to get ahead, will effectively stop communication upstream and downstream in order to fill their particular aim of what they want to get out of it. And so this is a chance for the top management to see, because they're doing their work, establishing the vision of the company, which is the mission, values and questions, they really should be able to go layer by layer as they're walking around seeing how those, their constancy, their intended constancy is being interpreted and executed. And so that's where beyond understanding how someone is operating a lathe or an accountant is doing a particular calculation, return on invested capital, whatever.   0:38:47.5 Bill Scherkenbach: Beyond that, I think it's important for management to be able to absolutely see what is happening. But the Gemba that I originally spoke about is just the other way. You've got the strategy people that are higher up, and you have the operations people that are typically, well, they might be the same level, but typically lower. You want the lower people to sit in on some higher meetings so they have a better idea of the intent, management's intent in this constancy of purpose. And that will help them execute, operationalize what management has put on paper or however they've got it and are communicating it. It just helps. So when I talk about Gemba, I'm talking the place where the quality is made or the action is. As the boardroom, you need to be able to have people understand and be able to see what's going on there, and all the way up the chain and all the way down the chain.   0:40:14.4 Andrew Stotz: That's great one. I'm just visualizing people in the operations side thinking, we've got some real problems here and we don't really understand it. We've got to go to the actual place, and that's the boardroom[laughter]. It's not the factory line.   0:40:31.7 Bill Scherkenbach: Yes. Absolutely. And if the boardroom says you're not qualified, then shame on you, the boardroom, are those the people you're hiring? So no, it goes both ways, both ways.   0:40:46.8 Andrew Stotz: Now, you had a final slide here. Maybe you want to talk a little bit about some of the things you've identified here.   0:40:53.4 Bill Scherkenbach: Okay, that's getting back to, in the logical area of this TDQA is my cycle: Theory, question, data, action. And it's based on Dr. Deming and Shewhart and Lewis saying, where do questions come from? They're based on theory. What do you do with questions? Well, the answers to questions are your data. And you're just not going to do nothing with data, you're supposed to take action. What are you going to do with it? And so the theory I'm going to address, the various questions I've found helpful in order to, to some extent, make the decisions better, the ability to operationalize them better and perhaps even be more creative, if you will. And so one of the questions I ask any team is, have you asked outside experts their opinion? Have you included them? Have you included someone to consistently, not consistently, but to take a contrarian viewpoint that their job in this meeting is to play the devil's advocate? And the theory is you're looking for a different perspective as Pete Jessup at Ford came up with that brilliant view of Escher's.   0:42:47.1 Bill Scherkenbach: Different perspectives are going to help you make a better decision. And so you want to get out of the echo chamber and you want to be challenged. Every team should be able to have some of these on there. What's going to get delayed? The underlying theory or mental model is, okay, you don't have people sitting around waiting for this executive committee to come up with new things, time is a zero-sum game. What's going to get delayed and what are they willing to get delayed if this is so darn important to get done? Decision criteria. I've seen many teams where they thought that the decision would be a majority rule. They discuss and when it came down to submit it, they said, "no, no, this VP is going to make the decision." And so that completely sours the next team to do that. And so you have to be, if you're saying trust, what's your definition of trust? If the people know that someone is going to make the decision with your advice or the executive's going to get two votes and everyone else gets one, or it's just simple voting.   0:44:35.3 Bill Scherkenbach: The point is that making the decision and taking it to the next level, the theory is you've got to be specific and relied on. Team turnover, fairly simple. We spoke about executive turnover, which was a huge concern that Dr. Deming had about Western management. But at one major auto company, we would have product teams and someone might be in charge of, be a product manager for a particular model car. Well, if that person was a hard charger and it took product development at the time was three and a half years, you're going to get promoted from a director level to a VP halfway through and you're going to screw up the team, other team members will be leaving as well because they have careers. You need to change the policy just to be able to say, if you agree that you're going to lead this team, you're going to lead it from start to finish and to minimize the hassle and the problems and the cost of turnover, team turnover. And this is a short list of stuff, but it's very useful to have a specific "no-fault policy."   0:46:20.6 Bill Scherkenbach: And this is where Dr. Deming speaks about reducing fear. I've seen teams who know they can really, once management turns on the spigot and says, let's really do this, this is important, the team is still hesitant to really let it go because that management might interpret that as saying, "well, what are you doing, slacking off the past year?" As Deming said, "why couldn't you do that if you could do it with no method, why didn't you do it last year?" but the fear in the organization, well, we're going to milk it. And so all of these things, it helps to be visible to everyone.   0:47:23.0 Andrew Stotz: So, I guess we should probably wrap up and I want to go back to where we started. And first, we talked about, where is quality made? And we talked about the boardroom. Why is this such an important topic from your perspective? Why did you want to talk about it? And what would you say is the key message you want to get across from it?   0:47:47.1 Bill Scherkenbach: The key message is that management thinks quality's made in operations. And it's the quality of the... I wanted to put a little bit more meat, although there's a lot more meat, we do put on it. But the quality of the organization, I wanted to make the point depends on the quality of the decisions, that's their output that top leaders make, whether it's the board or the C-suite or any place making decisions. The quality of your decisions.   0:48:28.9 Andrew Stotz: Excellent. And I remember, this reminds me of when I went to my first Deming seminar back in 1990, roughly '89, maybe '90. And I was a young guy just starting as a supervisor at a warehouse in our Torrance plant at Pepsi, and Pepsi sent me there. And I sat in the front row, so I didn't pay attention to all the people behind me, but there was many people behind me and there was a lot of older guys. Everybody technically was pretty much older than me because when I was just starting my career. And it was almost like these javelins were being thrown from the stage to the older men in the back who were trying to deal with this, and figure out what's coming at them, and that's where I kind of really started to understand that this was a man, Dr. Deming, who wasn't afraid to direct blame at senior management to say, you've got to take responsibility for this. And as a young guy seeing all kinds of mess-ups in the factory every day that I could see, that we couldn't really solve. We didn't have the tools and we couldn't get the resources to get those tools.   0:49:47.9 Andrew Stotz: It just really made sense to me. And I think the reiteration of that today is the idea, as I'm older now and I look at what my obligation is in the organizations I'm working at, it's to set that constancy of purpose, to set the quality at the highest level that I can. And the discussion today just reinforced it, so I really enjoyed it.   0:50:11.2 Bill Scherkenbach: Well, that's great. I mean, based on that observation, Dr. Deming many times said that the master chef is the person who knows no fear, and he was a master chef putting stuff together. And we would talk about fairly common knowledge that the great artists, the great thinkers, the great producers were doing it for themselves, it just happened that they had an audience. The music caught on, the poetry caught on, the painting caught on, the management system caught on. But we're doing it for ourselves with no fear. And that's the lesson.   0:51:11.8 Andrew Stotz: Yeah. Well, I hope that there's a 24-year-old out there right now listening to this just like I was, or think about back in 1972 when you were sitting there listening to his message. And they've caught that message from you today. So I appreciate it, and I want to say on behalf of everyone at the Deming Institute, of course, thank you so much for this discussion and for people who are listening and interested, remember to go to deming.org to continue your journey. And of course, you can reach Bill on LinkedIn, very simple. He's out there posting and he's responding. So feel free if you've got a question or comment or something, reach out to him on LinkedIn and have a discussion. This is your host, Andrew Stotz, and I'm going to leave you with one of my favorite quotes from Dr. Deming, and it doesn't change. It is, "people are entitled to joy in work."

Are you a nice leader or a kind leader? It might sound like the same thing, but Bob and Josh break down why the difference could be holding you back from becoming the leader your team actually needs.Using a Venn diagram from The Caring Techie, they explore the uncomfortable truth that being "nice" often means avoiding conflict, telling people what they want to hear, and prioritizing short-term comfort over long-term growth. Being "kind," on the other hand, means doing the right thing even when it's uncomfortable, setting boundaries, and being honest even at the risk of conflict.Bob shares a recent moment where he chose the nice path instead of the honest one—and why it still bothers him. Josh talks about the weight of leadership responsibility and why he'd rather have a difficult conversation than look back years later knowing he failed someone by staying silent.They also tackle the concept of getting "pickled"—how organizations slowly brine you into niceness until you stop asking the hard questions and stop saying what needs to be said. Drawing from Jeff Watts' book "Calm Rebel Leadership," they discuss how to find your center, recognize how far you've drifted, and start the slow work of crawling back to genuine, honest leadership.The takeaway? Don't flip the switch overnight. Baby steps, consistency, and the courage to be kind over nice will serve you and your team far better in the long run.Calm Rebel Leadership by Geoff WattsHarvard Business Review - "Is Your Leadership Style Too Nice?"The Caring Techie - Nice vs Kind Venn DiagramStay 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

Artemis II is on the pad, and I can't stop thinking about it. So I guess listen to me think in the open? Also, a ton of Blue Origin news—the next flight of New Glenn will feature a flown booster, they've announced constellation plans under the name TeraWave, and Tory Bruno has left ULA to join the team at Blue.This episode of Main Engine Cut Off is brought to you by 33 executive producers—Matt, Fred, Will and Lars from Agile, Kris, Lee, Jan, Frank, Miles O'Brien, Josh from Impulse, Theo and Violet, Ryan, Joakim, Stealth Julian, Heiko, Tim Dodd (the Everyday Astronaut!), Better Every Day Studios, Joel, Steve, Joonas, The Astrogators at SEE, Pat, Warren, Natasha Tsakos, Russell, David, Donald, and four anonymous—and hundreds of supporters.TopicsNASA's Moonbound Artemis II Rocket Reaches Launch Pad - NASAFinal Steps Underway for NASA's First Crewed Artemis Moon Mission - NASAIs Orion's heat shield really safe? New NASA chief conducts final review on eve of flight. - Ars TechnicaBlue Origin makes impressive strides with reuse—next launch will refly booster - Ars TechnicaNew Glenn-3 to Launch AST SpaceMobile's BlueBird Satellite | Blue OriginBlue Origin on X: “Our lunar lander is headed to the Lone Star State! ⭐ Blue Moon MK1 departed from Florida today, bound for @NASA_Johnson's Thermal Vacuum Chamber A, where it will undergo testing at the same facility as the Apollo spacecraft.”Another Jeff Bezos company has announced plans to develop a megaconstellation - Ars TechnicaFirst Take: What We Think Blue Origin's TeraWave Actually Is (and Isn't)In a surprise announcement, Tory Bruno is out as CEO of United Launch Alliance - Ars TechnicaBlue Origin on X: “We're pleased to announce that @torybruno is joining Blue Origin as president, National Security, reporting to CEO Dave Limp. Tory will spearhead our newly formed National Security Group.”The 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

Cristina Cranga: Coaching Product Owners From Output Obsession to Value Conversations 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.   In this episode, we refer to the work of Esko Kilpi on conversations and episodes on Nonviolent Communication (NVC) on the podcast. The Great Product Owner: A People Person Who Clarifies Before Deciding   "He was comfortable saying 'I don't know yet. What do you think?' It was a bi-directional conversation, not just one-way." - Cristina Cranga   The best Product Owner Cristina worked with was fundamentally a people person and a leader—human skills, not just hard skills. What made him exceptional was his approach to conversation: he started by clarifying the problem first, then decided. By doing this, he separated requests from decisions and made trade-offs explicit.  He was comfortable admitting uncertainty, asking "What do you think?" and engaging the team in co-creation rather than issuing directives. Cristina emphasizes that between the PO and Scrum Master, there's a special bond—a strong leadership partnership that teams look to as a reference. She highlights the concept of "ask more, say less": when you ask questions, you collect information that leads to better, more validated decisions.  The communication process, as outlined in Nonviolent Communication by Marshall Rosenberg, has four components: observation, feelings, needs, and requests. Great POs embody this by treating uncertainty as part of their job, engaging teams more deeply, and connecting work to value rather than just output.   Self-reflection Question: How often does your Product Owner ask "What do you think?" and what would change if they separated requests from decisions more explicitly? The Bad Product Owner: Output Obsession and the Velocity Trap "Success is measured by how much is delivered, not what changes. Teams get faster, but not smarter." - Cristina Cranga   The worst Product Owner anti-pattern Cristina has witnessed is output obsession—measuring success by how much is delivered rather than what actually changes for users or the business. When velocity replaces outcomes as the primary metric, teams get faster but not smarter. Faster doesn't equal smarter. This anti-pattern is particularly dangerous in an AI-accelerated environment where delivery speed is no longer a constraint. The challenge for practitioners is shifting this mindset. The strongest POs make different choices: they own their decisions at the team level, make decisions explicit, treat uncertainty as part of the job, and connect work to value. When POs break free from output obsession, the results are powerful: faster alignment, no decision hallucinations, more engaged teams willing to experiment, and genuine connection between work and value.   In this segment, we refer to Nonviolent Communication by Marshall Rosenberg.   Self-reflection Question: If you removed velocity from your team's dashboard tomorrow, what conversations would emerge about actual value delivered?   [The Scrum Master Toolbox Podcast Recommends]

I talk with David Flanagan, aka Rawkode, about his new opinionated Tech Matrix that helps you navigate the overwhelming CNCF landscape. https://rawkode.academy/technology/matrix

Give Us FeedbackIn this episode, we talk about what it takes to make change stick—especially when “Agile transformation” becomes a label instead of real progress. We cover the common pitfalls, the role of culture and middle management, and why clear goals, real investment, and continuous improvement matter. The takeaway: lasting change comes from resilience, adaptation, and empowered change agents—not a one-time rollout.Join Shawna Cullinan, Jörg Pietruszka,  Diana Larsen,  Sheila Eckert, Sheila McGrath, April Mills,  Hendrik Esser, Ray Arell, and all the callers to the monthly live event as we explore this topic.  For details on the next live event or how to support our show, please visit  acnpodcast.org.Support the show

Casey Dreier of The Planetary Society joins me to talk about the NASA FY2026 budget, the early days of the Administrator Isaacman era, and how we feel going into Artemis II.This episode of Main Engine Cut Off is brought to you by 33 executive producers—Matt, Fred, Will and Lars from Agile, Kris, Lee, Jan, Frank, Miles O'Brien, Josh from Impulse, Theo and Violet, Ryan, Joakim, Stealth Julian, Heiko, Tim Dodd (the Everyday Astronaut!), Better Every Day Studios, Joel, Steve, Joonas, The Astrogators at SEE, Pat, Warren, Natasha Tsakos, Russell, David, Donald, and four anonymous—and hundreds of supporters.TopicsCasey Dreier | The Planetary SocietyThe Planetary SocietyYou just saved NASA's budget | The Planetary Society2025 Impact Report | The Planetary SocietyThe 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

Cristina Cranga: Decision Quality as the True Measure of Scrum Master Effectiveness 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.   "A Scrum Master is successful when teams make better decisions, faster, with clear trade-offs—everything else is a side effect, not the job." - Cristina Cranga   Cristina offers a refreshingly clear definition of Scrum Master success for 2026: increasing the team's decision quality under accelerating change. She emphasizes that success as a term changes over time, and what mattered in previous years may not be what matters now. It's not about ceremony fluency or even making yourself unnecessary—those are side effects. The core of success is helping teams navigate complexity and AI-driven acceleration by making better decisions faster with explicit trade-offs.  Cristina describes this as an evolution from a "mechanic" role—focused on ceremonies, flow, and structure—to a strategic role. The Scrum Master elevates into a leader of team systems and human behaviors, possibly even becoming an AI integration enabler. This requires reskilling and upskilling as the environment changes. Her prompt for self-reflection: How can you orient your execution of the Scrum Master role more towards strategic aspects, focusing on decision quality as the opposite of decision hallucination?   Self-reflection Question: What would change in your daily work if you measured your success by the quality of decisions your team makes rather than the smoothness of your ceremonies? Featured Retrospective Format for the Week: Start/Stop/Continue Cristina advocates for simplicity in retrospectives, choosing the classic Start/Stop/Continue format. But she emphasizes that the format itself is secondary—what matters is the environment you create and the outcomes you achieve. Her two key conditions for any retrospective: an actionable plan and a simple conversational approach.  She challenges Scrum Masters to focus on the "how" rather than the "what"—how do you hold the space? How do you hold the silence? How do you approach disagreements? The power of Start/Stop/Continue lies in its simplicity, which frees facilitators to focus on creating psychological safety. Cristina also warns against the instinct to take ownership of action items yourself—instead, delegate to team members so they own their problems and become more committed to finding solutions.   [The Scrum Master Toolbox Podcast Recommends]

Cristina Cranga: Why Speed Without Value Creates Chaos in AI-Accelerated Teams 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.   "When output becomes cheap, value becomes harder to see. AI is amplifying this risk." - Cristina Cranga   Cristina brings a timely challenge to the table: how do Scrum Masters stay focused on value when AI tools are accelerating delivery to unprecedented speeds? Teams are delivering faster than ever—AI provides code, tests, documentation, even backlog items—but speed is no longer the constraint. The real challenge is meaning. Teams struggle to explain why their work matters to users or the business.  Cristina frames this as a shift from "delivery" as the primary keyword to "value." She suggests that Scrum Masters are evolving from facilitators of flow to protectors of intent—what she playfully calls "strategic guardians of the value chain" or even "value masters." Together with Vasco, they explore experiment ideas around building clarity of value cycles with product owners, bringing signals of value into earlier backlog work, and helping teams validate faster, not just deliver more.  The key insight: in an AI-accelerated world, the Scrum Master's role becomes more strategic, focused on ensuring teams make better decisions with clear trade-offs rather than just executing ceremonies.   Self-reflection Question: How might you help your product owner build a "clarity of value" cycle that tests ideas before they reach the development team?   [The Scrum Master Toolbox Podcast Recommends]

Planning is what stops "good intentions" turning into chaos. When teams skip planning, they don't just risk missing the deadline — they risk building the wrong thing, burning budget, and exhausting people on rework. A repeatable planning process keeps everyone aligned on outcomes, realities, actions, timelines, resources, and risks, so execution becomes calmer and faster. What is the planning process and why does it matter? The planning process is a repeatable way to define the outcome, map reality, set goals, design action steps, set timelines, allocate resources, plan contingencies, and track progress. It matters because most teams jump straight into the nitty gritty — meetings, tasks, and urgent emails — and mistake motion for progress. Post-pandemic (2020–2026), that "rush to action" has intensified as organisations face tighter budgets, hybrid teams, and faster competitive cycles. In multinationals (think Toyota-scale) you'll see more structure — governance, stage gates, and risk reviews — while SMEs and startups often rely on speed and intuition. Both can win, but both fail when they don't define "finished" early. In Japan, planning can be stronger in discipline but weaker in challenge if people copy seniors; in the US, planning can be faster but thinner if teams overvalue action. Do now: Write one sentence: "We will deliver ___ by ___ so that ___ improves." What is the first step in planning a project? The first step is defining the desired outcome so everyone shares the same destination. If the outcome is vague ("improve customer service"), the plan becomes a debate and execution becomes random. Better outcomes are specific, measurable, and tied to customer impact: reduce onboarding from 14 days to 3, cut defects by 20%, lift renewal rates by 5% by Q3. This is where leaders must "sell" the outcome, not just announce it. People aren't robots; they need to see why it matters, how it connects to strategy, and what trade-offs it requires. Use familiar frameworks to sharpen the outcome: SMART goals, OKRs (Objective + Key Results), or a simple "metric + deadline + owner." Consumer businesses may prioritise speed and experience; B2B firms may prioritise reliability and risk. Do now: Define 3 success measures (metric, deadline, owner) for your outcome. How do you assess the current situation before making a plan? You assess the current situation by establishing a clear baseline with facts, not opinions. You can't plan the route if you don't agree on the starting point. Capture the "as-is" reality: cycle time, backlog size, defect rate, conversion rate, churn, staffing capacity, supplier constraints, approval bottlenecks — whatever defines today's performance. Big firms may pull dashboards and market intelligence; smaller firms may rely on interviews and spreadsheets. Either works if it's accurate. This step prevents the classic argument later: "Did we actually improve?" It also exposes hidden constraints early (for example, a dependency on one overworked specialist, or a vendor lead time that makes your timeline impossible). Across cultures, the trap is the same: assumptions feel efficient until they prove expensive. Do now: List 10 baseline facts and agree: "This is our starting line." How should leaders set goals that actually get achieved? Leaders set achievable goals by breaking big targets into a hierarchy and translating them into weekly and daily units. A goal that can't be converted into actions is just a wish. Start with the outcome, then cascade: quarterly goals → monthly milestones → weekly targets → daily actions. Be realistic about constraints. Startups may set aggressive targets and iterate fast; regulated industries or complex global teams may need more conservative targets because governance, procurement, and compliance add time. In Japan, goal-setting can suffer if people avoid challenging targets to preserve harmony; in the US, it can suffer if targets are ambitious but under-resourced. Either way, align goals with capability, prioritise ruthlessly, and make ownership explicit. Do now: Build a "goal ladder" and assign one accountable owner per milestone. What makes action steps and time frames workable in the real world? Workable action steps name the work, the owner, the sequence, the dependencies, and the barriers — then lock them to real deadlines. This is where plans often collapse: the intent is clear, but the execution design is missing. Strong planning includes task allocation, coordination across teams, sequencing (what must happen first), supervision cadence, and known blockers. Then you set time frames that people respect by tying dates to deliverables, not vibes. Tools like a simple milestone calendar, a Gantt chart for complex work, or Agile sprints/Kanban for flow-based work can help — but the tool won't save you if "done" isn't defined. Deadlines should be explicit, shared, and reviewed, especially in hybrid teams spread across time zones. Do now: For each major step, write: owner, dependency, "definition of done," and due date. How do you plan resources, contingencies, and tracking so the plan survives surprises? Plans survive reality when they include honest resourcing, built-in contingencies, and simple tracking that warns you early. Resource planning isn't just budget — it's people, time, tools, approvals, and opportunity cost (what you stop doing to fund this). Under-counting resources creates rework and burnout. Contingencies turn "panic later" into "prepared now." Identify the top risks — supplier delays, staffing gaps, tech dependencies, scope creep — and pre-decide responses. Then track essentials: a few leading indicators (early warnings like backlog growth or missed handoffs) and lagging indicators (results like cost, quality, customer impact). This is classic PDCA (Plan-Do-Check-Act): plan carefully, execute, check frequently, and adjust fast. Do now: Define 3 risks with "If X happens, we will do Y by Z," plus 3 leading indicators to review weekly. Conclusion The planning process is not paperwork — it's how leaders create clarity, speed, and accountability. Define the outcome, baseline reality, set layered goals, design workable actions, lock timelines, allocate resources honestly, build contingencies, and track progress with early warnings. When you repeat the process, execution becomes less stressful and results become more predictable.

Cristina Cranga: Why Nice Teams Still Fail and the Power of Honest Conversations 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.   "Sometimes you can change people by only listening to them. Not giving advice—don't become an advice monster." - Cristina Cranga   Cristina shares her experience of sensing that something was off with a team but being unable to pinpoint exactly what it was. Instead of jumping to conclusions, she paused, reflected, and created an intervention plan centered on one thing: starting honest conversations. Through one-on-one discussions with team members, she discovered that the problem wasn't performance or process—it was something deeper.  Expectations weren't aligned with reality, and frustration stemmed from a company culture that didn't offer psychological safety. Cristina introduces the concept of the "advice monster"—someone who constantly tells others what they should do rather than simply listening. She emphasizes that as Scrum Masters, we need to recognize the three layers of our influence: control, influence, and no control.  Even when we can't solve problems, being present and listening can create profound change. The key is self-awareness of our own vulnerability as humans and compassion for others who might be at 80% or 10% of their mental health and energy on any given day.   In this segment, we talk about the importance of psychological safety and active listening in team dynamics.   Self-reflection Question: How often do you enter conversations with the intention of truly understanding rather than solving, and what might you discover if you listened more and advised less? Featured Book of the Week: The Fearless Organization by Amy Edmondson Cristina chose The Fearless Organization by Amy Edmondson as her most influential book because it explains what Scrum Masters see every day but struggle to name. The book provides a mental model for why teams don't speak up and how to influence behavior without forcing it. As Cristina puts it: "She explains why nice teams still fail. Silence is not always alignment and politeness—most of the time, it's distrust." The book repositions the Scrum Master role from someone focused on ceremonies to someone who creates the conditions for psychological safety. It also explains why process alone doesn't fix everything and helps Scrum Masters measure what really matters in a team.   [The Scrum Master Toolbox Podcast Recommends]

Get Brad's new book, Give First.00:00 — Cold open: “Something new is fucked up in my world every day”02:00 — The Yoda t-shirt story + the mythology of Brad Feld04:00 — “Give First” vs. “Pay it Forward”: philosophy, not obligation07:00 — Why giving isn't altruism — and how it works in complex systems10:00 — Positive-sum vs. zero-sum: tennis, trust, and long games13:00 — Does giving create outcomes, or just energy?16:00 — Why Brad writes books: longform thinking as meaning-making20:00 — Searching for meaning through mentorship and reflection23:00 — “I hate the phrase pattern recognition” — mentorship done right28:00 — The power dynamic between founders and mentors32:00 — Management through commitment, not control35:00 — Agile as an operating system for accountability38:00 — Emotional intelligence and the role of executive coaches41:00 — Mentor vs. coach vs. therapist vs. advisor45:00 — Trust as the foundation of all high-leverage relationships47:30 — Wild story: when the second floor of Sphero's building collapsed52:00 — “They can't kill you and they can't eat you” – Len Fassler's advice55:00 — Closing thoughts on being the Bill Murray of venture capital

Once you make your work visible, you can finally see how much of your work is just stuck. And while a common reaction is to think that you are the bottleneck, that thinking is actually preventing you from understanding something much more useful and ultimately less personal about bottlenecks in law firms and how work is actually flowing through your legal delivery systems. In this episode, I'm building on last week's discussion of making work visible. The focus now shifts from seeing where work is to getting work to flow. You'll learn how to find the most important place where work is getting stuck, the best way to improve flow, and why treating process improvement as a team sport and approaching it with curiosity rather than judgment will yield far better outcomes than trying to fix everything yourself. Get full show notes, transcript, and more information here: agileattorney.com/103 Take your law practice from overwhelmed to optimized with GreenLine Legal Follow along on LinkedIn: linkedin.com/in/johnegrant

Cristina Cranga: When Teams Stop Testing Reality and Fall Into Decision Hallucinations 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.   "Over time, what I notice is that teams stop testing reality. They optimize execution around constraints that might no longer exist." - Cristina Cranga   Cristina introduces a powerful concept she calls "decision hallucinations"—the perception of constraints and boundaries that aren't actually real or present. In her experience working with teams in complex matrix environments, she noticed a troubling pattern: team members would say things like "we can't change this because it's already decided" or "the priority comes from the top level" without ever verifying these assumptions.  The impact on team behavior was significant—teams stopped asking questions, stopped having conversations with stakeholders, and began operating within perceived limitations rather than actual ones. Cristina emphasizes that as Agile practitioners, our work isn't just about ceremonies and metrics—it's about supporting and facilitating decision processes.  When she encouraged teams to ask better questions like "Is this an assumption-based decision or an explicit shared choice?", something beautiful happened: options reappeared, conversations changed, and teams realized they were constrained by perception rather than reality. She uses the famous duck vs. rabbit optical illusion from psychology to illustrate how our brains can only see one reality at a time, making the case that we must constantly test our view of reality through continuous conversations with stakeholders.   In this episode, we refer to the work of Esko Kilpi on conversations and the duck vs rabbit image from psychology.   Self-reflection Question: When was the last time you challenged an assumption your team operates under, and what did you discover when you tested that reality?   [The Scrum Master Toolbox Podcast Recommends]

Matt Ezyk has decades of experience building, scaling and leading digital commerce technology and strategy at some of the most innovative companies in the world. Matt serves as Senior Director of Engineering, Ecommerce at Hanna Andersson which is a leading direct-to-consumer premium children's apparel and lifestyle brand. Prior to joining Hanna Andersson, he led digital at Pet Supermarket with oversight of product and engineering. Additionally he served as Director of Functional Architecture and Director of PMO at RafterOne (f/k/a PixelMedia) with operational oversight of teams working with iconic brands like Skechers and LL Bean. Matt also served in progressive leadership roles at Accenture, Merkle (f/k/a LiveArea) and several startups working with hundreds of global brands like Uniqlo, Disney, Revlon, Tapestry and many more. Matt brings to retailers and DTC brands a deep expertise in developing and implementing diverse end-to-end commerce strategies. In This Conversation We Discuss: [00:00] Intro[00:24] Sponsor: Taboola[01:41] Connecting tech decisions to business growth[04:36] Comparing agency and brand-side perspectives[07:24] Sponsor: Next Insurance[08:37] Delivering progress customers can feel[09:58] Choosing platforms based on business maturity[13:03] Callouts[13:13] Auditing tech to recover lost conversions[15:31] Reducing redundancy to improve performance[17:47] Evaluating third-party tools for value[19:36] Sponsor: Electric Eye[20:44] Improving conversion with UX and engineering[22:25] Augmenting team expertise with AI tools[27:46] Balancing speed with long-term scalabilityResources:Subscribe to Honest Ecommerce on YoutubeKids clothes from playtime to bedtime hannaandersson.com/Follow Matt Ezyk linkedin.com/in/mezykReach your best audience at the lowest cost! discover.taboola.com/honest/Easy, affordable coverage that grows with your business nextinsurance.com/honest/Schedule an intro call with one of our experts electriceye.io/connectIf you're enjoying the show, we'd love it if you left Honest Ecommerce a review on Apple Podcasts. It makes a huge impact on the success of the podcast, and we love reading every one of your reviews!

Certainty In Uncertain Times A turbulent world has an impact on our industry and our personal sense of purpose. Unrest, confusion, and uncertainty not only shapes markets, it bleeds into our daily work and our identities as Agile practitioners. We don't shy away from admitting how tough things feel right now: many of us are tired, a little lost, and wondering if all the skills and experience we've built still matter in a climate that doesn't seem to value what we bring. This crisis of purpose is widely shared, and it's okay to feel frustrated. The Agile community, once hailed for its energy and transformative power, is now met with skepticism, and sometimes, outright dismissal. When we start internalizing these messages, we risk stepping back, waiting for someone or something else to make things better. To make things certain again. We wait for permission. We hope for a change agent or a new visionary to lift us out of this malaise. But what if none is coming? So Who’s Gonna Save Us? This moment forces us to ask tough questions: who organizes the millions of practitioners? Who inspires, motivates, and charts the next step? Instead of lamenting the “glory days,” we explore the idea that it's up to us to fill that leadership vacuum. We create our own certainty. And yes, it's daunting. Imposter syndrome and the noise of detractors can be paralyzing, but I want to push you to see the salvation in this possibility. Like open source—we have permission to own it. To do that, we’ll need to step beyond incremental tweaks and complacency. Small changes won't cut it. We need bolder action. Perhaps creating new ways to engage leadership or communicating the value of Agile in executive terms. This may be uncomfortable, even scary, but the alternative is inertia, both in our work and within ourselves. In the face of uncertainty, we must BE certainty itself. Ultimately, we face a challenge: we must become the certainty, the leadership, and the vision the moment requires. Let’s refuse to wait for the torch to be passed. Let’s choosing to pick it up. If we're honest, Agile practitioners are change leaders by nature. The world isn't going to give us permission or clarity; we have to create it. If you enjoyed this episode, you might also enjoy: Badass Unscripted – Embody True Certainty Episode 230 – The Difference-Makers **GET THE BUSINESS OUTCOMES PARTNER PLAYBOOK** Learn how to deliver undeniable ROI that saves your job and accelerates your future https://learning.fusechamber.com/offers/AFGm3tSy/checkout **FORGE GENESIS IS HERE** All the skills you need to stop relying on job postings and start enjoying the freedom of an Agile career on YOUR terms. First cohort starts in Jan 2026 https://learning.fusechamber.com/forge-genesis **THE ALL NEW FORGE LIGHTNING** 12 Weeks to elite leadership! https://learning.fusechamber.com/forge-lightning **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.

Leaders don't have anyone to pick them up when they fall—so how do you generate energy when you've got nothing left? Josh and Bob share real talk about the mental battles of leadership, building your emergency support team, and why treating yourself like a "solo chief" might be the mindset shift you need. Plus: a daily ritual that transformed how Bob showed up for his teamsYou Are Worth More Than You Think - Jurgen AppeloThe Solo Chief - Jurgen AppeloStay 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!

Season 8 - crazy! Agile leadership comes from all over your organization, not just with suits, C level folks or executives. Today's episode will help set the foundations for any agile team leader to get that team and your product to a level of high performance.Whether you are a scrum master, flow coach, product owner / manager or any kind of leader in your organization, there is a foundation that I share here for you that is truly fundamental to getting a higher performing team.If you like it, tell a friend. If you don't like it, send me an email!scott@planetproductowner.org

Greg Kihlström shares groundbreaking insights into how businesses can become experience-led enterprises. With real-world examples and a focus on innovation, Greg discusses digital transformation, agile methodologies, and the pivotal role of customer and employee experiences in driving success. This is a must-listen for anyone passionate about transforming organizations and delivering exceptional value to customers and teams alike. About the Guest Greg Kihlström is a best-selling author, speaker, and entrepreneur, and serves as an advisor and consultant to top companies on marketing technology, marketing operations, and digital transformation initiatives. He has worked with some of the world's top brands, including Adidas, Coca-Cola, FedEx, HP, Marriott, Nationwide, Victoria's Secret, and Toyota. He is a multiple-time Co-Founder and C-level leader, leading his digital experience agency to be acquired in 2017, successfully exited an HR technology platform provider he co-founded in 2020, and led a SaaS startup to be acquired by a leading edge computing company in 2021. He currently advises and sits on the Board of a marketing technology startup. Relevant Links https://www.linkedin.com/in/gregkihlstrom https://www.instagram.com/theagilebrand https://www.gregkihlstrom.com Episode Summary - The Top 3 Key Learnings Four Pillars of Transformation: Effective digital transformation hinges on integrating people, processes, platforms, and data. While technology matters, success ultimately depends on how well organizations address human and procedural challenges. Agile for Transformation: Agile methodologies can look different for every organization. Focus on principles like collaboration, adaptability, and delivering business value, rather than rigidly adhering to predefined methods. Return on Experience: Investing in customer and employee experiences yields measurable benefits, such as increased customer loyalty, higher lifetime value, and improved organizational efficiency. Chapters 00:00 Introduction and Guest Welcome 00:33 Greg Kihlström's Background and Career 01:55 Values Driving Professional Life 02:54 Digital Transformation Challenges 05:11 Measuring Return on Experience 09:23 Implementing Agile Methodologies 14:10 Practical Tips for Digital Transformation 16:47 AI in Digital Transformation 22:14 Future of Customer Experience 24:23 Conclusion and Final Thoughts Please, hit the follow button and leave your feedback: Apple Podcast: https://www.cxgoalkeeper.com/apple Spotify: https://www.cxgoalkeeper.com/spotify About the host: Gregorio Uglioni is a seasoned transformation leader with over 15 years of experience shaping business and digital change, consistently delivering service excellence and measurable impact. As an Associate Partner at Forward, he is recognized for his strategic vision, operational expertise, and ability to drive sustainable growth. A respected keynote speaker and host of the well-known global podcast Business Transformation Pitch with the CX Goalkeeper, Gregorio energizes and inspires organizations worldwide with his customer-centric approach to innovation. Follow Gregorio Uglioni on Linkedin: https://www.linkedin.com/in/gregorio-uglioni/ Podcast webpage: https://www.cxgaolkeeper.com/podcast

Mohini Kissoon: The One Question That Transforms Messengers Into Product Owners The Great Product Owner: The Calm Navigator Who Shields the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "He said "no" often, but he did it with such clarity that people respected it. It's not just no—it's giving the reason why." - Mohini Kissoon   Mohini has had the privilege of working with many great Product Owners, but one stood out for his calm demeanor and ability to navigate complex situations. Whatever stakeholders threw at him, he remained professional and calm—and critically, he never transferred that pressure onto the team. He had built strong relationships with stakeholders and was the go-to person who commanded respect across the organization.  When stakeholders demanded features that didn't align with team goals, he would acknowledge the request, explain the trade-offs, and offer to revisit it once the current direction was validated. He said no often, but with such clarity and reasoning that people respected his decisions.  This Product Owner also shielded the team from ad hoc requests, handling stakeholder bypass attempts so developers could maintain focus. He would only bring truly urgent items—like compliance issues—directly to the team.  With his helicopter view, he understood how incoming work would impact different stakeholders and parts of the business. Most importantly, he was a good listener who gave the team space to grow and experiment while challenging them constructively.   Self-reflection Question: When you work with your Product Owner, do they shield the team from chaos or pass it through unfiltered—and how might you help them develop that protective capability? The Bad Product Owner: The Messenger Who Couldn't Say No 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.   "When the team would ask 'why are we building this?' the answer would be 'because sales asked for it.' There was no triaging, no challenging stakeholders—just saying yes." - Mohini Kissoon   Mohini shares a story about a Product Owner who appeared to be doing everything right on paper: attending ceremonies, responding to questions, being present for the team, and working closely with stakeholders. But the team was constantly frustrated with scope creep, and the root cause was that this Product Owner was operating as a messenger, not a decision maker. She would bring requests from stakeholders directly into the backlog with no prioritization based on value and no pushback.  Major new work would appear at sprint planning that hadn't been discussed during backlog refinement. The team was committing to 100 story points but only completing 40, with items constantly carrying over.  When Mohini was brought in to help, she asked one simple question that changed everything: "What is the vision for your product?" The Product Owner couldn't answer—because nobody had ever asked her before.  Mohini ran a product vision workshop with her and key stakeholders, created a one-page strategy identifying target users, core problems, and success metrics, and established a working agreement that backlog items must align with identified goals. She also introduced prioritization sessions involving stakeholders. The transformation came when the Product Owner finally felt equipped to say no with informed reasoning.   Self-reflection Question: Does your Product Owner have a clear product vision they can articulate, and if not, what workshop or conversation could you facilitate to help them discover it?   [The Scrum Master Toolbox Podcast Recommends]

Mohini Kissoon: The Language Test That Reveals True Team 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.   "When I see my team taking ownership of their work, taking ownership of the Scrum events, asking questions, challenging each other constructively without waiting for me—that's when I know I've done my job." - Mohini Kissoon   Mohini defines success for Scrum Masters through three distinct lenses. First, she looks for teams that take ownership—of their work, of the Scrum events, of asking questions and challenging each other constructively without waiting for her to intervene. When she can observe from the sidelines while the team self-manages, she knows she has shaped the right conditions for them to thrive.  Second, success means having metrics that demonstrate improvement over time: team happiness, flow, and how individuals have grown in their roles. These metrics aren't just for the team—they're for sharing with leadership to show the positive impact created.  Third, and perhaps most importantly, success is about creating psychological safety where team members feel comfortable disagreeing, engaging in healthy conflict, and being creative without taking things personally.  One powerful indicator Mohini uses is the language of the team: do they say "their sprint goal" or "our sprint goal"? This subtle shift from passive to possessive language reveals the true level of ownership the team has developed. It's an easy thing to observe but often missed by Scrum Masters.   Self-reflection Question: Listen carefully in your next sprint planning or daily scrum—does your team use "we" and "our" language, or do they speak about the work as something external to them? Featured Retrospective Format for the Week: Timeline Retrospective Mohini finds herself returning to the Timeline retrospective more than any other format, especially when a team has been going through something complex—a difficult sprint, a major release, or a quarterly review with a working group. The format helps people pause and reflect on what has happened before jumping into "what do we change next?" In a physical room, she draws a line on the whiteboard and invites people to add sticky notes for key moments that stood out during the period. In virtual settings, she uses a digital whiteboard. The moments can be good, bad, confusing, or stressful—anything significant. The exercise starts silently, giving everyone space to think without being influenced. Then the team walks through the timeline chronologically, sharing stories behind their notes.  What makes this format powerful is that it creates shared understanding before asking for solutions. Team members often realize that others experienced the same event differently. However, Mohini warns that the timeline can feel overwhelming when you see all the stickies on the board. The key is to build a bridge before jumping to actions: have the team identify patterns, vote on items to discuss further, and only then derive concrete actions from the prioritized items.   [The Scrum Master Toolbox Podcast Recommends]

Agile in 2026 Looks Nothing Like ScrumThat delay cost us 42,000 failed checkout attempts and a week of executive explanations. Nothing was broken in the code. The failure was procedural. The fix was ready. The sprint boundary said no.That was the moment we stopped pretending Scrum was helping us ship.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/

Mohini Kissoon: Beyond the AI Fear—Discovering What Makes Scrum Masters Truly Irreplaceable 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 real challenge isn't whether AI will replace Scrum Masters. It's whether we understand what parts of our work are actually irreplaceable—and whether we're spending our time on those things." - Mohini Kissoon   Mohini is wrestling with a challenge that's coming up repeatedly in conversations with Agile coaches and Scrum Masters: the anxiety around AI and what it means for their role. She hears questions like "Will AI replace Scrum Masters?" but believes we're asking the wrong question. The real challenge is understanding which parts of our work are truly irreplaceable and demonstrating value in those areas.  People might think that AI can generate sprint reports and analyze team metrics—so why do we need Scrum Masters? But what's missing is the human touch: reading the room, sensing unspoken tension, building trust through presence, and asking questions that shift perspectives. Mohini and Vasco explore how the Scrum Master role may have accidentally become defined by process and structure rather than impact on teams.  The solution lies in showing value through concrete metrics—demonstrating improvement in team happiness, flow, cycle time, and lead time. Scrum Masters need to use storytelling and create history that shows the before and after. They should leverage champions from teams they've worked with to share testimonials. We are like diplomats: we work through influence and need allies both inside and outside the team to support our work.   Self-reflection Question: If AI could handle all the administrative and mechanical aspects of your Scrum Master role tomorrow, what would you spend your time doing—and are you already investing enough time in those irreplaceable human elements?   [The Scrum Master Toolbox Podcast Recommends]

Mohini Kissoon: When Politeness Becomes the Enemy of Team Growth—Escaping the Conflict Avoidance Trap 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.   "Conflict isn't the enemy. It's when we're avoiding conflict that it becomes an issue for teams." - Mohini Kissoon   Mohini shares a story about the worst self-destructive pattern she has witnessed: teams that are overly polite to avoid addressing conflicts. She worked with a team that prided themselves on being collaborative and drama-free, but beneath that politeness was a hesitancy to have difficult conversations. It started small—in sprint planning, the Product Owner would propose unrealistic scope, and people would just nod and accept. Someone might say "that's quite ambitious," but no one would actually push back. In retrospectives, feedback was always wrapped in layers of positive framing. When a developer consistently delivered work that didn't meet the Definition of Done, no one called it out directly—they just quietly fixed it or worked around it. After three months, side conversations started emerging where people would pull Mohini aside to share concerns they would never voice in the room. The team was skipping the storming phase of the Tuckman model, and this avoidance eventually led to missed deadlines and frustrated stakeholders. The key learning: healthy conflict brings the energy teams need to innovate and grow.   In this segment, we talk about the Tuckman model and why the storming phase is essential for team development.   Self-reflection Question: Is your team's harmony genuine collaboration, or is it a facade hiding unspoken frustrations that will eventually surface at the worst possible moment? Featured Book of the Week: Turn the Ship Around by David Marquet Mohini discovered Turn the Ship Around by David Marquet at a time when she was working with multiple teams and feeling exhausted from being the person everyone looked to for answers. She thought that's what servant leadership meant, but she was actually creating dependency rather than capability. The book tells the story of how Marquet took command of the worst-performing submarine in the US Navy and transformed it into the best by fundamentally changing how leadership worked. "Instead of the traditional leader-follower model, he built a leader-to-leader structure where everyone was expected to think, decide, and own their work," Mohini explains.  The key insight was that we don't just empower teams—we need to build an environment where they can grow and don't need permission to excel. This shifted Mohini's approach: instead of saying "here's what I think we should do," she started asking "what have you tried so far? What do you intend to do next?" The book also emphasizes that pushing decision-making down requires providing the knowledge and context teams need to make good decisions.   [The Scrum Master Toolbox Podcast Recommends]