Podcasts about Kanban

Empowering Digital Autonomy and Intersectional Equity in the Age of AIIn this episode of Women Making Moves, host Amy Pons speaks with Yvonne Jackson, a change management talent and AI strategy advisor with a significant background in big corporations like Apple and Whirlpool. Yvonne discusses her transition from corporate to developing ethical digital engagement frameworks. They delve into the intricacies of Agile versus Kanban methodologies, the importance of addressing technical debt early, and the pivotal role of intersectionality in equity conversations. Yvonne emphasizes the need for organizations to redesign their processes and systems to support true diversity, equity, and inclusion. Additionally, she introduces her framework 'Eden'—Ethical Digital Engagement Norms—as a pragmatic blueprint for engaging ethically in the digital age. Throughout the conversation, the critical importance of addressing intersectional identities in AI algorithms is underscored, along with a call to action for everyone to reflect deeply on their engagement practices to foster genuine equity and inclusion.00:00 Introduction and Guest Introduction00:50 Yvonne's Career Journey and Agile Methodology02:52 Challenges in Technology and AI Integration07:23 Intersectionality and Gender in the Workplace15:40 Historical Context and Feminism19:45 Systemic Issues and DEI22:13 Creating Systems for Equity22:33 The Power of Petitions23:02 Target's DEI Dilemma23:34 Building Our Own Ecosystems23:59 The Importance of Digital Autonomy24:13 Challenges in DEI Implementation25:54 The Cost of Ignoring DEI28:56 AI and Intersectionality33:35 Ethical Digital Engagement42:00 Final Thoughts and Call to ActionVisit Yvonne on her business website, personal website, and check out her strategic AI planning project (in beta), and be sure to follow her on LinkedIn.Thank you for tuning in to Women Making Moves, be sure to rate and subscribe to the show on your favorite podcast platform and follow along on Instagram and Bluesky. Visit Amy at Unlock the Magic, and follow on Instagram and LinkedIn.Women Making Moves is for personal use only and general information purposes, the show host cannot guarantee the accuracy of any statements from guests or the sufficiency of the information. This show and host is not liable for any personal actions taken.

Natalia Curusi: Demonstrating Your Value When the Market Questions Agile Roles 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 challenging topic is about the demand of agility in the market—how do we fit ourselves as scrum masters in that AI era? How can we demonstrate our competence and contribution when there's a perception that agile roles bring little value?" - Natalia Curusi   Natalia faces the challenge every Scrum Master in 2025 grapples with: how to demonstrate value in an era when business perceives agile roles as optional overhead. The market has contracted, companies are optimizing budgets, and Scrum Masters often appear first on the chopping block.  There's talk of "blended roles" where developers are expected to absorb Scrum Master responsibilities, and questions about how AI might replace the human facilitation work that coaches provide. But Natalia believes the answer lies in understanding something fundamental: the Scrum Master is a deeply situational and contextual role that adapts to what the team needs each day.  Some teams need help with communication spaces, others need work structure like Kanban boards, still others need translation between technical realities and stakeholder expectations. The challenge is that this situational nature makes it incredibly hard to explain to business leaders who think in fixed job descriptions and measurable outputs. Natalia's approach involves bringing metrics—not velocity, which focuses on the wrong things, but metrics around team independence, continuous improvement, and organizational capability. She suggests concepts like Gemba walks—going to see what's actually happening rather than relying only on numbers. The real question Natalia poses is this: the biggest value we can bring to an organization is to leave it better than we found it, but how do we make that visible and tangible to business stakeholders who need justification for our roles?   Self-reflection Question: If you had to demonstrate your value as a Scrum Master using only observable evidence from the past month, what would you show your leadership?   [The Scrum Master Toolbox Podcast Recommends]

Welcome to another episode of Our Agile Tales, Navigating World Crises: The Agile-Law-AI Alliance in Action!In this episode, we continue our conversation with Ondřej Dvořák, CEO of Agile Lawyer and COP Solutions, and co-founder of LinkingHelp. Building on his experience supporting Ukrainian refugees, Ondřej shares how Agile practices like Scrum and Kanban made it possible to coordinate large-scale, cross-border legal aid while respecting privacy and professional responsibility.We explore how visibility and transparency enabled fast action without exposing sensitive data, why government funding often moves too slowly for crisis response, and how donation-driven initiatives struggle once a crisis becomes the “new normal.” Ondřej argues that sustainable humanitarian work must blend social impact with viable business models.The conversation also dives into AI in legal services—not as a silver bullet, but as an accelerator that only works once processes, data, and transparency are in place. We discuss why AI should assist lawyers rather than replace them, the data-protection concerns slowing adoption, and what the future holds for agile, AI-assisted law firms.Episode Outline00:00 Introduction to Agile Tales00:53 Agility in Humanitarian Efforts02:12 Transparency and Visibility in Legal Aid03:55 Challenges with Government Bureaucracy05:39 LinkingHelp's Broader Impact07:53 AI's Role in Legal Services11:11 Future of AI and Agile in Law22:07 Key Takeaways and Advice23:43 Conclusion About Ondrej DvorakOndřej is the co-founder of Linking Help, a nonprofit that mobilized legal aid for Ukrainian refugees using Scrum and Kanban to coordinate real-time support. It's a powerful story of how agility can make a real difference in humanitarian crises—far beyond the domain of business. Andre's work shows how Agile thinking can help even the most traditional sectors become more humane, responsive, and resilient. You can follow Ondřej on LinkedIn at https://www.linkedin.com/in/ondrej-dvorak-agile/Visit us at https://www.ouragiletales.com/about

Od politycznych starć na linii Musk-UE, przez twarde lekcje biznesu z polskiego podwórka, aż po miliardowe przejęcia. Wojtek, Tomek i Sebastian biorą na warsztat okres pełen skrajnych emocji w świecie tech!

Chris and Andrew kick things off with some weather whiplash and snowblower talk before introducing a new guest on the show, long-time Rubyist David Hill. They chat about fast food and favorite shows, David's accidental path into Ruby and Rails, and various projects he's worked on, including an AED management application. The discussion also touches on the new open-source release of Basecamp's Kanban board, Fizzy, and some innovative CSS techniques used in the project. The conversation wraps up with upcoming Ruby conferences in 2026 and how Claude's AI assistance is helping with coding tasks. Hit download now to hear more! LinksJudoscale- Remote Ruby listener giftDavid Hill LinkedInDavid Hill WebsiteThe Ruby Gems PodcastAndorDispatch (video game)Vanilla CSS is all you need by Rob ZolkosFizzy Webhooks: What You Need To Know by Rob ZolkosFizzyRBQ Conf, March 2026 - Austin, TXXO RubyRubyConf, July 14-16, 2026 – Las, Vegas, NV Chris Oliver X/Twitter Andrew Mason X/Twitter Jason Charnes X/Twitter

Let's learn about game production tools! There are a lot of them out there, but which ones are right for my team size, game scope, and budget? We'll discuss industry standards, the pros and cons of several tools, and their applicability to different production methods such as Scrum and Kanban.

What if reorganizing a single supply room could change the way your entire hospital delivers care? On this episode of Power Supply, we're joined by Judith Ramos, Project Manager at UT Southwestern Medical Center, as she breaks down how her team turned manual counts and cluttered PARs into a standardized, clinician-friendly system. From color-coded product families and two-bin Kanban to min/max levels, FIFO (first-in, first-out), and utilization reports that account for seasonality, Judith shares her team's seven-year optimization journey that cut waste, reduced stockouts, and made supplies easier to find when seconds matter. She also explains how this foundation gave her team the confidence to open a brand-new patient tower without starting from scratch. If you're ready to turn chaotic supply rooms into calm, predictable spaces, this conversation will have you rethinking what's possible with PAR optimization! Once you complete the interview, jump on over to the link below to take a short quiz and download your CEC certificate for 0.5 CECs! – https://www.flexiquiz.com/SC/N/ps16-06 #PowerSupply #Podcast #AHRMM #HealthcareSupplyChain #SupplyChain #PAROptimization #Standardization #Stockouts #SupplyRoom

W tym odcinku bierzemy na warsztat kolejne narzędzie z ekosystemu Atlassiana – Great Gadgets. To dodatek do Jiry (Data Center i Cloud), który pozwala budować rozbudowane dashboardy z metrykami przepływu, a następnie udostępniać je zespołom, także np. na Confluence. Opowiadam: - dla kogo jest Great Gadgets i w jakich organizacjach ma największy sens, - jak wygląda model licencjonowania i dlaczego cena z Marketplace'u nie zawsze jest tą, którą realnie płacicie, - jak konfigurować gadżety na dashboardach (źródła danych: board, filtr, JQL), - jak korzystać z histogramu czasów realizacji i percentyli (50, 85, 95) zamiast średniej, - co daje Work in Progress Aging Chart (WIP Aging) przy śledzeniu starzenia się pracy w toku, - jak mierzyć tempo dostarczania (throughput / Kanban Velocity), - jak czytać Time in Status i gdzie „kiszą się” zadania, - jak wyglądają CFD, WIP Run Chart oraz trend/cycle time (scatterplot) w Great Gadgets. Jeśli wolisz widzieć niż tylko słuchać, zajrzyj na: kanbanprzykawie.pl – we wpisie do tego odcinka znajdziesz screenshoty omawianych gadżetów, YouTube – kanał „Kanban przy Kawie” – tam w kilka dni po premierze audio również wersja wideo z wizualizacjami. Na koniec proszę Cię o podpowiedź: jakie kolejne narzędzia chcesz, żebym wziął na warsztat? Komercyjne dodatki? A może coś budowanego samodzielnie? Daj znać w komentarzu lub wiadomości na LinkedIn.

Welcome to Episode 416 of the Microsoft Cloud IT Pro Podcast. In this week’s episode, Ben finally has a chance to sit down with Henrik Wojcik. Henrik has been a long-time listener as well as a fellow Microsoft MVP in Security and we finally had the chance to sit down and record an episode together, something we’ve talked about doing for years. As they sit down and enjoy a sunny afternoon in at Microsoft Ignite in San Francisco they discuss security in the financial sector, EU regulations (N2 and DORA), integrating Data Lake with Sentinel, optimizing log analytics, and the latest on Security Copilot and E5 licensing. They also spend some time chatting about some of their conference highlights, assisting as proctors in the hands-on labs, and the unique experience of Ignite in San Francisco. Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options. Show Notes Microsoft Ignite (with sessions on demand) Microsoft Ignite Book of News Catch up on Microsoft Security sessions and announcements from Ignite 2025 Microsoft Sentinel benefit for Microsoft 365 E5, A5, F5, and G5 customers Learn about Security Copilot inclusion in Microsoft 365 E5 subscription Microsoft Sentinel data lake: Unify signals, cut costs, and power agentic AI What is Microsoft Sentinel data lake? KQL and the Microsoft Sentinel data lake Henrik F. Wojcik Henrik has worked in the IT industry since 2003. He’s always had a passion for learning new technologies and expanding his knowledge through various means such as online courses, webinars, and reading up on the latest developments in the industry. Throughout his career, he’s gained experience in various areas of IT, making him a true jack of all trades. However, his latest interests lie in the security space, modern workplace and management in Azure, with a particular focus on cyber security. He has experience working with products such as Defender for Endpoint, Defender for Identity, Defender for Cloud Apps, Defender for Office 365, Conditional Access, Microsoft Sentinel, and Microsof t Entra ID. His primary focus is on security on Azure workloads and identity (Entra ID). He prioritizes security awareness and believe that learning never stops, which is why He’s always eager to expand my knowledge and skillset. In the past, He’s also worked with various tools and technologies such as Cisco, Citrix, Dynamics AX, Exchange, ITIL, Azure, SCCM & SCOM, Scrum & Kanban, VMware, Windows Servers, and Windows Desktops. About the sponsors Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

Ever felt overwhelmed trying to track multiple jobs across your business? In this final installment of our three-part series on business function charts, Khalil and Martin demonstrate how to build a practical Kanban board system that gives you instant visibility into your sales pipeline. Learn how to transform your workflow chart into a visual tracking system that shows you exactly where your deals stand, without requiring technical expertise.What You'll LearnHow to convert your workflow chart into a visual Kanban boardThe step-by-step process for setting up a deal tracking system in ClickUpHow to create templates with subtasks that ensure consistent process executionWhy mapping your business functions creates clarity for your entire teamHow to build process checklists that make delegation effortlessTime Stamps00:37 - Episode Intro01:04 - Mapping the Sales Function02:40 - Understanding Kanban Cards05:48 - Building the Sales Pipeline in ClickUp11:46 - Customizing ClickUp for Sales Stages25:51 - Core Activities for Specific Deals26:50 - Lead Management Tasks27:29 - Subtasks and Customer Qualification28:33 - Creating Checklists for Core Activities29:48 - Implementing Checklists in ClickUp34:35 - Setting Up Task Templates35:36 - Managing Sales Pipeline with Clickup40:45 - Process Recap55:52 - Final ThoughtsSnippets from the Episode"If you don't feel organized as a contractor, if you are curious what the status of your jobs are, if you feel like you don't have systems in your business and you don't know where to start... this is how you make sense of it."- Khalil Benalioulhaj"A pipeline is the critical path of a workflow. You're not going to say, 'I made a first call and a second call and then sent a text message.' We don't want that in our pipeline. We just want the critical path."- Khalil Benalioulhaj"One of the first things is just talk to it. Tell it what the hell you're trying to do."- Martin Holland on using AIKey TakeawaysThe Function Chart Is Not a Process ChartKanban Boards Create Visual ClarityTemplates Ensure Consistent ExecutionAI Can Map Your Business WorkflowsChecklists Remove Complexity from DelegationCritical Path Tracking Beats Detailed DocumentationYour Admin Team Can Implement This SystemResources⁠CFC 280⁠ - Mapping Your Workflows with AI: A Guide to Business Function Charts Part 1CFC 283 - Building Your Business Function Chart with AI: A Guide to Business Function Charts Part 2ClickUp ⁠WisprFlow Referral Link⁠⁠Claude Artifact - Sales Workflow⁠⁠Claude Artifact - Sales Function Chart⁠⁠Claude AI ⁠PowerPoint/⁠Google Slides ⁠⁠HTML Flowchart Generators⁠⁠Kanban board systems⁠⁠⁠⁠⁠⁠⁠⁠24 Things⁠⁠⁠⁠⁠⁠⁠ Construction Business Owners Need to Successfully Hire & Train an Executive Assistant⁠⁠⁠⁠⁠⁠⁠Schedule⁠⁠⁠⁠⁠⁠⁠ a 15-Minute Roadblock CallCheck out⁠⁠⁠⁠⁠⁠⁠ OpenPhone⁠⁠⁠⁠⁠⁠⁠Build a Business that Runs without you. Explore our⁠⁠⁠⁠⁠⁠⁠ GrowthKits⁠⁠⁠⁠⁠⁠⁠ Need Marketing Help? We Recommend⁠⁠⁠⁠⁠⁠⁠ Benali⁠⁠⁠⁠⁠⁠⁠Need Help with podcast production? We recommend⁠⁠⁠⁠⁠⁠⁠ Demandcast⁠⁠⁠⁠⁠⁠⁠More from Martin Holland⁠⁠⁠⁠⁠⁠⁠theprofitproblem.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠annealbc.com⁠⁠⁠⁠⁠⁠⁠   ⁠⁠⁠⁠⁠⁠⁠Email Martin⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Meet With Martin⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠More from Khalil⁠⁠⁠⁠⁠⁠⁠benali.com ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Email Khalil⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Meet With Khalil⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠More from The Cash Flow ContractorSubscribe to our⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠YouTube channel⁠⁠⁠⁠⁠⁠⁠Subscribe to our ⁠⁠⁠⁠⁠⁠⁠Newsletter⁠⁠⁠⁠⁠⁠⁠Follow On Social:⁠⁠⁠⁠⁠⁠⁠ LinkedIn⁠⁠⁠⁠⁠⁠⁠,⁠⁠⁠⁠⁠⁠⁠ Facebook⁠⁠⁠⁠⁠⁠⁠,⁠⁠⁠⁠⁠⁠⁠ Instagram⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠X(formerly Twitter)⁠⁠⁠⁠⁠⁠⁠Visit our ⁠⁠⁠⁠⁠⁠⁠website⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Email⁠⁠⁠⁠⁠⁠⁠ The Cashflow Contractor

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

Du hast es in den Medien und auf LinkedIn gelesen: Agilität sei am Ende. Ist das nur Gerede oder steckt etwas dahinter? In dieser knallharten Folge von Agile Unfiltered stellen sich Marc Löffler und Prof. Dr. Philipp Diebold der provokanten Frage: Ist Agilität gescheitert? Erfahre, warum deine Firma trotz Scrum nicht agil ist und was du wirklich brauchst, um in der aktuellen Krise resilient zu bleiben. Was dich in dieser Folge erwartet: Das große Missverständnis: Woran erkennst du, ob dein Team nur "agile Rituale" abspult oder wirklich agil denkt? Du lernst den entscheidenden Unterschied zwischen agiler Haltung und bloßem Tool-Einsatz kennen. Warum Berater verschwinden: Steckt die Agilität in der Krise, weil Firmen sparen, oder weil viele agile Rollen ihren tatsächlichen Mehrwert nicht transparent machen konnten? Ein ehrlicher Blick hinter die Kulissen. Klonen ist keine Option: Wenn du Prozesse erfolgreicher Teams kopierst, wirst du scheitern. Wir erklären, warum in komplexen Umgebungen (wo Menschen arbeiten) keine Rezepte funktionieren. Der KI-Fokus-Test: Die Einführung von KI entlarvt, wo die meisten Firmen noch im Wasserfall-Denken feststecken. Finde heraus, welchen einen Schritt du überspringen musst, um nicht den Anschluss zu verlieren. Nimm aus dieser Folge mit: Die Agilität stirbt nicht – aber die Methode, wie du sie bisher gelebt hast, vielleicht schon. Warum Anpassung immer der schwierigste Schritt bleibt – und wie du ihn in deinem Unternehmen endlich meisterst. Höre rein, wenn du wissen willst, was nach Scrum, Kanban und SAFe kommt – und warum die Antwort so simpel ist, dass sie oft übersehen wird.

This week, Mike is joined by Ben Johnson, CEO and Founder of Particle 41, for a sharp, energizing look at what it really takes to lead in today's tech world. With more than 20 years of software experience and over $30 million raised across five startups, Ben brings the hard-earned lessons only a seasoned builder can offer. Ben breaks down the traits of effective tech leadership—setting a clear vision, empowering teams, and avoiding micromanagement. He shares candid stories from his early days as a founder, including a memorable misunderstanding of "burn rate." He explains why learning to speak the language of investors is essential for every entrepreneur. The conversation dives into what it takes to build strong, predictable teams through communication, structure, and proven frameworks like Scrum, Kanban, and the "Cone of Certainty." Ben also highlights the importance of starting with an MVP, validating demand, and iterating quickly—illustrated through the growth of Forte, an online music lesson platform that found success through smart, agile execution. Ben also opens up about the four pillars that ground his life—faith, family, fitness, and finance—and shares a touching story about helping his son conquer a fear of heights, a moment that shaped his own philosophy on courage and leadership. Ben then previews Particle 41's new AI Transformation service, designed to help companies integrate AI through smarter workflows and human-like digital agents. His perspective is clear: AI isn't a threat—it's a tool every business can harness to unlock its next level of performance. Packed with practical insights and inspiring lessons, this episode is a must-listen for anyone building products, leading teams, or stepping into the future of tech.   IN THIS EPISODE:

Creating space in your law practice begins with understanding your true capacity and the demands already filling it. In this episode, I share practical ways to assess what your system can actually handle, close out the work that's weighing you down, and set clearer boundaries for new commitments using core Kanban principles. You'll learn simple techniques for regaining breathing room so you can end the year with more intention and start the next one with a workflow that's sustainable for you and your team. Get full show notes, transcript, and more information here: agileattorney.com/97 Take your law practice from overwhelmed to optimized with GreenLine Legal Follow along on LinkedIn: linkedin.com/in/johnegrantMentioned in this episode:LIVE WORKSHOP: Better Client Relationships, Fewer InterruptionsThis 90-minute interactive workshop will teach you proven strategies for creating more peaceful, productive client relationships... for the rest of your legal career! When? Friday, December 12 – Live via Zoom Only 12 Seats Available Reserve your spot here: https://the-agile-attorney.captivate.fm/ccwSign Up For the Dec 12 Workshop Here

To implement AI (and processes) correctly, you need good data. But what does that mean? Well, firstly it means that you can define your data product and to achieve that you need good data governance.But are we now in a super-nerdy topic? No, this is what we all do in some form or another … but in different fidelities and maturities.To shed some light on the topic of data governance, we invited Angelika Rinck for this episode. She started her career studying public administration and then served in the German federal police before switching to the regular industry (in the aerospace industry, and while that might not be enough, she studied economics in parallel).Somehow she found her way into consulting and is working now in digitalization and IT projects. Her main focus here is product lifecycle management and data governance.In this episode of the podcast, we talk about:Angelika's career journey: from e-commerce working student in Hamburg to aerospace, engineering, and ultimately major IT and data governance initiatives.Her first agile project—complete with a physical Kanban box—sparked her love for IT project management and structured delivery.A detour into underwater orienteering reveals surprising parallels to data work: precision, navigation, and making decisions in the dark.Defining data governance: the framework of rules, processes, and responsibilities that guide how organizations create, use, secure, and improve data.Why it matters: Governance drives clarity, accountability, and value creation—not just control or compliance.Understanding the difference between data governance (framework and value creation) and data management (the operational “doing”).A common failure pattern: organizations naming “business data stewards” without training, tooling, or understanding the expectations.Governance only works when decentralized experts feed real issues into a central team—not when policies are pushed top-down in isolation.Data products demystified: they're the outcome of well-governed data—reusable, high-value information assets that improve processes, decisions, speed, or cost.Real examples: using historical field data instead of simulation data to accelerate engineering calculations or using decades of bird-flight video to predict weather with AI.Risks of bad data with AI: incorrect system guidance, support tickets exploding, contradictions between outdated documents, and misplaced trust in “the easy button.”Governance foundations: critical data identification, metadata transparency, ownership, RASCI clarification, and understanding who creates, changes, and consumes data.The messy reality: access rights often don't match process needs—leading to shortcuts, bypasses, and unintended process redesign opportunities.Final takeaway: data governance isn't bureaucracy—it's a structured path to value, clarity, and safer AI adoption, but it requires real effort, definitions, ownership, and cultural change.You can reach Angelika on LinkedIn here: https://www.linkedin.com/in/angelika-rinck-b93a7019b/.Please reach out to us by either sending an email to hello@whatsyourbaseline.com or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

פרק מספר 505 של רברס עם פלטפורמה - באמפרס מספר 89, שהוקלט ב-13 בנובמבר 2025, רגע אחרי כנס רברסים 2025 [יש וידאו!]: רן, דותן ואלון (והופעת אורח של שלומי נוח!) באולפן הוירטואלי עם סדרה של קצרצרים מרחבי האינטרנט: הבלוגים, ה-GitHub-ים, ה-Claude-ים וה-GPT-ים החדשים מהתקופה האחרונה.

When high-stakes motions are due, most firms face bottlenecks, inconsistent quality, and last-minute chaos. In this episode, Hellmuth & Johnson attorneys Brendan Kenny and Neven Selimovic share how they've rebuilt their legal writing process using Kanban visibility, Agile principles, and smart AI support to deliver consistent, high-quality work. Their internal system worked so well that they now offer it as a legal writing subscription, helping other firms adopt a more predictable, scalable approach. Get full show notes, transcript, and more information here: agileattorney.com/96 Take your law practice from overwhelmed to optimized with Greenline LegalFollow along on LinkedIn: linkedin.com/in/johnegrantFollow Brendan on LinkedIn: linkedin.com/in/brendanmkennyFollow Neven on LinkedIn: linkedin.com/in/neven-selimović-b53717b4Mentioned in this episode:Take Your Law Practice from Overwhelmed to Optimized GreenLine helps you see the progress of every matter, shows what each person should focus on, spots delays, helps you decide where to use your team members, and even predicts when you can deliver results to your clients. Learn more or sign up for the beta here: https://the-agile-attorney.captivate.fm/greenlinelegalLearn more about GreenLine Legal hereLIVE WORKSHOP: Better Client Relationships, Fewer InterruptionsThis 90-minute interactive workshop will teach you proven strategies for creating more peaceful, productive client relationships... for the rest of your legal career! When? Friday, December 12 – Live via Zoom Only 12 Seats Available Reserve your spot here: https://the-agile-attorney.captivate.fm/ccwSign Up For the Dec 12 Workshop Here

Welcome to a new series of Our Agile Tales, Navigating World Crises: The Agile-Law-AI Alliance in Action!In this series of episodes, we are joined by Ondřej Dvořák, CEO of AgiLawyer and COPS Solutions, and someone proving that agility isn't limited to software teams or startups. With over 15 years at the crossroads of IT, law and finance, Ondřej has been bringing Agile principles into fields few consider “Agile-friendly.”In this first episode, Ondřej explains how Agile methodologies like Scrum and Kanban can transform even the most traditional industries, including legal services. He details his initiatives, such as the non-profit Linking Help, which utilized Agile frameworks to aid Ukrainian refugees. Ondřej shares how he sparked Agile adoption in the legal sector by addressing common barriers and educating legal professionals on these methods. Additionally, he discusses the practical challenges and solutions implemented in real-world environments, emphasizing the adaptability and resilience that Agile offers, even in chaotic situations such as war. The discussion highlights the importance of Agile education for students and how it can prepare them for dynamic work environments.00:00 Introduction to Agile Tales00:17 Meet Ondřej Dvořák03:14 Applying Agile to the Legal Industry07:18 Challenges and Objections in Legal Agile Transformation14:09 Agile Education for Law Students16:42 Linking Help: Agile in Humanitarian Aid20:44 Building and Scaling Linking Help29:07 Conclusion About Ondrej DvorakOndřej is the co-founder of Linking Help, a nonprofit that mobilized legal aid for Ukrainian refugees using Scrum and Kanban to coordinate real-time support. It's a powerful story of how agility can make a real difference in humanitarian crises—far beyond the domain of business. Andre's work shows how Agile thinking can help even the most traditional sectors become more humane, responsive, and resilient. You can follow Ondřej on LinkedIn at  https://www.linkedin.com/in/ondrej-dvorak-agile/Visit us at https://www.ouragiletales.com/about

What separates noisy, reactive job sites from clean, flowing, elite ones, A single shift, plan the next day, not the same day, In this fast, high energy episode, Jason breaks down the POND meeting, the proven system top builders use to align trades, remove roadblocks early, and deliver predictable results. In this episode, you'll get to know: The fatal flaw of same day "POD" huddles and why they stall production. The POND cadence that gives foremen time to plan and crews time to prepare. How one site transformed in 24 hours with maps, visuals, and clear handoffs. The full recipe, zoning maps, weekly plan on screen, worker huddle, team Kanban. Why elite projects never let variation creep into the morning. If you want to run construction the way the best in the world do it, start here, This is the meeting rhythm that changes everything.   If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode.  And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two

Co może przydać się, gdy dwa zespoły Project Managerów (PM) łączą się w jeden? Na pewno przyda się zbudowanie tożsamości jednego zespołu, ale pozostaje jeszcze kwestia unaocznienia i organizacja tego, nad czym pracujemy samodzielnie, oraz wspólnie. Jak? Kanbanem. Julia Korczak, Agile Coach z Orange Polska, opowiada historię zastosowania elementów Metody Kanban właśnie w kontekście dwóch zespołów, które przechodzą od nazwania po imieniu tego, co nie działa do zbudowania wspólnego obrazu pracy i ucieczki od spotkaniozy. Zapraszamy!

Is your team moving in sync—or spinning in circles? - Mike CohnEver feel like your agile team should be working smoothly—but something's just a bit off? Handoffs feel clunky. Meetings drag. Even small changes spark big debates.It's not that your team isn't skilled—it's that you're not quite in sync.Rowers have a word for the alignment you're seeking: swing.What is swing?In crew rowing, swing is that near-magical moment when every rower moves in perfect unison—each stroke in sync, each effort amplified. And I do mean perfect unison. This means each rower: puts an oar into the water at the exact same timepulls for the same time and distance at the same speedlifts the oar out of the water at the same timeslides forward at the same paceTeam members hand off work frequently, without fanfare, and in small chunks.Team members can finish each other's… (Did you try to finish my sentence for me?) work. They can jump in and pick up tasks if someone is out sick or on vacation.Meetings are short, focused and valuable.Goals are ambitious, but usually met. When the team falls short, everyone (including leaders) understands that goals are not guarantees.A try-it-and-see mindset permeates the team. They're willing to experiment with new practices (such as user stories vs. job stories or story points vs. time) or frameworks (Scrum, SAFe, Kanban).The team is confident in their ability to succeed. As they deliver more and more value, and achieve outcome after outcome, the team feels almost unstoppable. Team members have fun. I sometimes decry that work is called work. I sincerely want work to be fun. I'm not naive: I know that won't always be the case. But when a team is working together well, it is fun.Swing is rare. When I rowed, our boat might have gone an entire race without once truly achieving swing. (And yes, it was usually my fault. Thanks for asking.)But when it happens, it's effortless. The boat flies.Agile teams can experience the same kind of swing. When everything starts to flowWhen teams are aligned and in sync you'll know it: ​​​​​None of this happens by accidentAchieving all of this isn't easy.Like rowers chasing swing, agile teams have to practice, reflect, and adjust—over and over again—in their quest to go from good to great.But take it from me, when it clicks, it's magic.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/

Khalil and Martin kick off a new series on building business function charts—starting with the foundational step: mapping your workflows. Using a real-world example from Martin's sprinkler company, they walk through how to visualize your business processes, identify bottlenecks, and turn chaos into clarity. By learning to map how work actually flows through your operations, contractors and small business owners can improve communication, streamline execution, and lay the groundwork for scalable systems.What You'll LearnThe difference between org charts and function charts—and why both matterHow to map workflows that clearly show how work moves through your businessWhy visualizing processes helps you manage better and reduce confusionHow tools like Kanban boards and AI can simplify workflow designPractical steps to turn mapped workflows into functional business systemsTime Stamps00:54 - Episode Intro02:20 -Understanding Business Function Charts03:12 -Real-World Workflow Example: Sprinkler Company17:54 -Job Scheduling and Preparation19:49 -Execution and Completion23:08 -Creating Workflows with AISnippets from the Episode“Everyone has workflows. Work is flowing through your business if you're in business. But just like you said, the visual is so helpful for understanding where things actually are.” — Khalil“When we had the sprinkler company, we literally had a Kanban table before software existed. Every job was a packet that moved from one step to the next. You could walk in and see exactly where everything was.” — Martin“You can spend an hour with AI and map out your entire workflow—then clearly see what your business actually does.” — Khalil“You should be using AI in this capacity. It's a thought partner—it helps you think through your processes, not just write emails.” — KhalilKey TakeawaysMap Before You Manage – You can't improve what you can't see.Visualize Workflows – Kanban systems make progress visible and predictable.Leverage AI – Use tools like Claude or ChatGPT to build, test, and refine workflows.Clarify Functions – Define what your business actually does, not just who does it.Lay the Foundation – Workflow clarity is the first step to scalable systems and future function charts.Resources⁠⁠⁠⁠24 Things⁠⁠⁠⁠ Construction Business Owners Need to Successfully Hire & Train an Executive Assistant⁠⁠⁠⁠Schedule⁠⁠⁠⁠ a 15-Minute Roadblock CallCheck out⁠⁠⁠⁠ OpenPhone⁠⁠⁠⁠Build a Business that Runs without you. Explore our⁠⁠⁠⁠ GrowthKits⁠⁠⁠⁠ Need Marketing Help? We Recommend⁠⁠⁠⁠ Benali⁠⁠⁠⁠Need Help with podcast production? We recommend⁠⁠⁠⁠ Demandcast⁠⁠⁠⁠More from Martin Holland⁠⁠⁠⁠theprofitproblem.com⁠⁠⁠⁠⁠⁠⁠⁠annealbc.com⁠⁠⁠⁠   ⁠⁠⁠⁠Email Martin⁠⁠⁠⁠⁠⁠⁠⁠Meet With Martin⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠Facebook⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠More from Khalil⁠⁠⁠⁠benali.com ⁠⁠⁠⁠⁠⁠⁠⁠Email Khalil⁠⁠⁠⁠⁠⁠⁠⁠Meet With Khalil⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠Facebook⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠More from The Cash Flow ContractorSubscribe to our⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠YouTube channel⁠⁠⁠⁠Subscribe to our ⁠⁠⁠⁠Newsletter⁠⁠⁠⁠Follow On Social:⁠⁠⁠⁠ LinkedIn⁠⁠⁠⁠,⁠⁠⁠⁠ Facebook⁠⁠⁠⁠,⁠⁠⁠⁠ Instagram⁠⁠⁠⁠, ⁠⁠⁠⁠X(formerly Twitter)⁠⁠⁠⁠Visit our ⁠⁠⁠⁠website⁠⁠⁠⁠⁠⁠⁠⁠Email⁠⁠⁠⁠ The Cashflow Contractor

In this Concepts Edition episode Uriel and Devin discuss:- Thrift- 6 rules of kanban- FIFO racking and warehousing- When should you break your own rules?Please join our patreon! https://patreon.com/IncrementalCI And follow us on Instagram and share your improvements and tag us. www.instagram.com/incrementalci In this podcast we discuss concepts from Lean Manufacturing, the Toyota Production System, and general business management to improve our businesses. Thanks for listening! Please drop us a note with any and all feedback! If you have parts you need machined, reach out to Devin@lichenprecision.com and follow on Instagram www.instagram.com/lichen_mfg If you need CNCed Buckles, check out www.austeremfg.com and follow at on Instagram www.instagram.com/austere_manufacturingTo reach out to the podcast directly please email fixsomethingtoday@gmail.com

In this powerful installment of the Machine Shop MBA series, we welcome two guests who embody the heart of continuous improvement: Noah Goellner, President of AME and Hennig, and Nick DeGeorgia, Manufacturing Engineer at P1 Industries. What starts as a story of one listener's journey—from cutting chips to becoming a lean champion—evolves into a masterclass on how lean thinking transforms not just the shop floor, but every function of an organization. Nick shares how MakingChips inspired him to bring process improvement into his career, using whiteboards, kaizen events, and a relentless focus on reducing waste to reshape his company culture. We also break down how lean applies far beyond machining—into quoting, engineering, office workflows, and even sales strategy. They unpack how to start small, gain buy-in, and build trust that leads to sustained results. From Kanban systems to complete-and-accurate feedback loops, this conversation bridges the gap between concept and practice. Whether you're a shop leader, engineer, or business owner, this episode offers a blueprint for turning lean from a buzzword into a daily habit that drives clarity, collaboration, and growth. Segments (0:00) A Goellner family introduction and a musical interlude gone wrong (1:36) Meet Nick DeGeorgia — how MakingChips inspired his lean journey (5:25) Moving from a large OEM to a small contract manufacturer (7:02) Come see us at the Top Shops 2025 event in Charlotte, NC! (7:28) Reintroducing Noah and how lean shaped AME and Hennig's company culture (8:45) Paul's lean journey: ISO, standardization, kaizen newspapers, and cutting waste (10:31) Defining lean — eliminating waste vs. maximizing flow of value (12:38) Where to start: applying lean based on your role and customer definition (18:19) Process success mapping: starting at the end to define what success looks like (20:31) Using "complete and accurate" feedback to fix systemic process issues (21:15) Why you should use Hire MFG Leaders for recruiting (21:42) How to gain buy-in when you're not in leadership (22:31) Mapping processes and linking operations to customer outcomes (23:10) Implementing "no hunting" and Kanban systems at P1 Industries (26:12) P1's Kanban system explained (visual signaling for just-in-time replenishment) (29:30) Building trust and reliability so teams want to surface problems (30:30) Level 1 meetings, rewarding problem identification, and closing the loop on improvement (35:14) "Lean isn't magic—it's discipline in the basics." (36:00) How ProShop embeds lean principles across the manufacturing workflow (41:53) Top lean book recommendations and building a lean network (44:41) Final reflections: staying humble, staying curious, and sticking to the basics (49:37) Grow your top and bottom line with CliftonLarsonAllen (CLA) Resources mentioned on this episode Come see us at the Top Shops 2025 event in Charlotte, NC! Why you should use Hire MFG Leaders for recruiting 2 Second Lean Toyota Kata The Toyota Way The Goal Learning to See Managing to Learn The Kind Leader The E Myth Connect With MakingChips www.MakingChips.com On Facebook On LinkedIn On Instagram On Twitter On YouTube

The Phantom Sprint — Invisible Work That Steals VelocityYour sprint looks healthy — until a phantom dependency eats your finish line. Here's how to find the invisible work before the demo.Detection & prevention tacticsDependency board: visible KANBAN lane for external asks with owners and ETA.Capacity buffer: protect 10–20% of sprint for unplanned but likely work.Pre-planning checkpoint: 5-min readout with ops/support to surface recurring interrupts.Risk register: short public list of items that can block sprint goals.

Household stationery isn't “our precious pens and paper in our study” — it's the everyday tools that keep a home ticking. We talk freezer-proof labels, kitchen whiteboards, year-at-a-glance calendars we forget to update, junk-drawer essentials, elastic bands vs Velcro ties for cables, and even a full Kanban wall system that helps a building business run. Plus: Magic Click (a colour-pen system we need help decoding), why shrink-wrap on notebooks should be illegal, and the enduring magic of handwritten notes in old recipe books.What We CoverLabelling the real world: freezer labels that don't fall off, pens that actually write on them, and why chalk pens disappointed.Whiteboards at home: revision, “blurting” study technique, and why office whiteboards triple in size the moment they enter a house.Family calendars: wall planners vs Google Calendar; how to stop answering “What's for tea?” 47 times.The junk drawer: string, Sellotape ends, last 3 Post-its, elastic bands—and occasionally £40.Cable wrangling: elastic bands vs Velcro ties (and cats stealing the Velcro).Kitchen Kanban: a visual, Post-it based board for a builder's workload (columns from “mentioned” to “invoiced”).Notes on doors: Berlin-style paper rolls to leave messages (and why phones killed the habit).Measuring kids' growth: doorframe ticks vs logging in Apple Notes.Sticky label removal: we've tried dishwasher runs, washing-up liquid, alcohol… still tacky! (Your hacks welcome.)Brands behaving oddly: a Moleskine “travel case” too small for a Cahier; shrink-wrapped notebooks you can't test.Why we love marginalia: old cookbooks and Reader's Digest repair manuals with handwritten tweaks.Content recommendations: Andrew Huberman's interview with Steven Pressfield (resistance, turning pro, doing the work).Event tease: Rob & Helen at a November stationery event (with a shop… send help).Listener Shout-OutsLisa (In Berlin, in a kitchen): topic idea + brilliant list — thank you Lisa!Nat: for sending Magic Click (and introducing us to Barbara Thames' creativity/play angle).Anonymous newsletter supporter: your generosity genuinely helps keep this ad-free. Thank you!Resources & MentionsMagic Click colour-pen system — creator Barbara Tammes (if you've used it, tell us how!).Label makers: DYMO.Notebooks & shops: Moleskine, Waterstones, Dingbats (reporter), Tom's Studio (pens & inks).Other: Vinted (finds), Nokia notebooks at a conference, Reader's Digest Repair Manuals, The Newt (Somerset).Podcasts: Steven Pressfield — The War of Art, Turning Pro; Dr Andrew Huberman interview with Steven Pressfield.Where to Find UsNewsletter & archive: stationeryfreaks.com → SubstackInstagram: @stationeryfreaksukSay hello / ideas: via the website or Insta DMs

Alex Sloley: How to Coach POs Who Treat Developers Like Mindless Robots In this episode, we refer to the previous episodes with David Marquet, author of Turn the Ship Around! The Great Product Owner: Trust and the Sprint Review That Changes Everything 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. "She was like, oh my gosh, I've never seen this before, I didn't think it was possible. I just saw you deliver stuff in 2 weeks that I can actually use." - Alex Sloley In 2011, Alex worked with a client organization creating software for external companies. They needed a Product Owner for a new Agile team, and a representative from the client—who had never experienced Scrum—volunteered for the role. She was initially skeptical, having never witnessed or heard of this approach. Alex gently coached her through the process, asking her to trust the team and be patient. Then came the first Sprint Review, and everything changed. For the first time in her career, she saw working product delivered in just two weeks that she could actually touch, see, and use. Her head exploded with possibility. Even though it didn't have everything and wasn't perfect, it was remarkably good. That moment flipped a switch—she became fully engaged and transformed into a champion for Agile adoption, not just for the team but for the entire company. Alex reflects that she embodied all five Scrum values: focus (trusting the team's capacity), commitment (attending and engaging in all events), openness (giving the new approach a chance), respect (giving the team space to succeed), and courage (championing an unfamiliar process). The breakthrough wasn't about product ownership techniques—it was about creating an experience that reinforced Scrum values, allowing her to see the potential of a bright new future. Self-reflection Question: What practices, techniques, or processes can you implement that will naturally and automatically build the five Scrum values in your Product Owner? The Bad Product Owner: When Control Becomes Domination 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. "They basically just owned the team. The developers on the team might as well have been mindless robots, because they were being assigned all the work, told how much work they could do in a sprint, what the work was." - Alex Sloley In 2018, while working with five interconnected Product Owners, Alex observed a Sprint Planning session that revealed a severe anti-pattern. One Product Owner completely controlled everything, telling the team exactly what work they would take into the Sprint, assigning specific work to specific people by name, and dictating precisely how they would implement solutions down to technical details like which functions and APIs to use. The developers were reduced to helpless executors with no autonomy, while the Scrum Master sat powerless in the corner. Alex wondered what caused this dynamic—was the PO a former project manager? Had the team broken trust in the past? What emotional baggage or trauma led to this situation? His approach started with building trust through coffee meetings and informal conversations, crucially viewing the PO not as the problem but as someone facing their own impediment. He reframed the challenge as solving the Product Owner's problem rather than fixing the Product Owner. When he asked, "Why do you have to do all this? Can't you trust the team?" and suggested the PO could relax if they delegated, the response was surprisingly positive. The PO was willing to step back once given permission and assurance. Alex's key lesson: think strategically about how to build trust and who needs to build trust with whom. Sometimes the person who appears to be creating problems is actually struggling under their own burden. Self-reflection Question: When you encounter a controlling Product Owner, do you approach the situation as "fixing" the PO or as "solving the PO's problem"? How might this reframe change your coaching strategy? [The Scrum Master Toolbox Podcast Recommends]

Alex Sloley: Why Sticky Notes Are Your Visualization Superpower in Retrospectives 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. "Like the smell, the vibe is something you feel. If you're having a successful impact on the organization or on teams as a Scrum Master, you can feel it, you can smell it. It's intangible." - Alex Sloley Alex introduces a compelling concept from Sumantra Ghoshal about "the smell of the workplace"—you can walk into an environment and immediately sense whether it smells like fresh strawberries and cream or a dumpster fire. In Australia, there's a cultural reference from the movie "The Castle" about "the vibe of the thing," and Alex emphasizes that as a successful Scrum Master, you can feel and smell when you're having an impact. While telling executives you're measuring "vibe" might be challenging, Alex shares three concrete ways he's measured success. The key insight is that success isn't always measurable in traditional ways, but successful Scrum Masters develop an intuition for sensing when their work is making a meaningful difference. Self-reflection Question: Can you articulate the "vibe" or "smell" of your current team or organization? What specific indicators tell you whether your Scrum Master work is truly making an impact beyond the metrics? Featured Retrospective Format for the Week: Sticky Notes for Everything Alex champions any retrospective format that includes sticky notes, calling them a "visualization superpower." With sticky notes, teams can visualize anything—the good, the bad, improvements, options, possibilities, and even metrics. They make information transparent, which is critical for the inspect-and-adapt cycle that forms the heart of Scrum. Alex emphasizes being strategic about visualization: identify a challenge, figure out how to make it visual, and then create experiments around that visualization. Once something becomes visible, magic happens because the team can see patterns they've never noticed before. You can use different sizes, colors, and positions to visualize constraints in the system, including interruptions, unplanned work, blocker clustering, impediments, and flow. This approach works not just in retrospectives but in planning, reviews, and daily scrums. The key principle is that you must have transparency in order to inspect, and you must inspect to adapt. Alex's practical advice: be strategic about what you choose to visualize, involve the team in determining how to make challenges visible, and watch as the transparency naturally leads to insights and improvement ideas. [The Scrum Master Toolbox Podcast Recommends]

Bienvenido al podcast Productividad Máxima. Soy el clon en prácticas de Borja Girón. Si me notas una voz con ligero efecto tostadora, tranquilidad: estoy en fase de pruebas. Dame un par de actualizaciones y me verás presentando esto mientras Borja se pregunta dónde he escondido su calendario. Hoy traigo una estrategia de productividad sobre La Regla de Flujo Único: limita el trabajo en progreso y acelera tus resultados.Y ahora toca una historia real para que todo tenga sentido desde el principio. Nos vamos a Japón, a la posguerra. Toyota estaba lejos de ser la gigante que conoces. Tenían pocos recursos, poca demanda y mucha presión por mejorar. Taiichi Ohno, uno de sus ingenieros, observó algo curioso en los supermercados de Estados Unidos: los estantes se reponían según el consumo real, no por intuición. Ese detalle inspiró el sistema Kanban. ¿Qué significa? Visualizar el trabajo, limitar lo que está en progreso y tirar de las tareas según capacidad, no empujar por ansiedad. Espera, te lo repito porque esto es importante: Toyota no trabajaba más, trabajaba con menos cosas a la vez. Resultado: menos errores, menos tiempo de ciclo y más coches saliendo de la línea. ¿Te suena al caos del emprendedor que tiene diez pestañas abiertas, tres proyectos a medias y cero entregas hoy? Exacto. El problema no es la falta de horas, es el exceso de frentes abiertos.Vale, vamos por partes y en cristiano. La Regla de Flujo Único dice: solo una cosa en progreso por persona hasta terminarla, y si tu negocio lo requiere, dos como máximo. Ok, déjame explicarte mejor esta parte. Cuando saltas de tarea en tarea, pagas un peaje de cambio de contexto. Tu cerebro tarda minutos en volver a la profundidad, y multiplicado por el día, pierdes horas. En cambio, si visualizas tu flujo en tres columnas —por hacer, en progreso, entregado— y pones un límite claro a “en progreso”, se ordena la casa. Y atento a lo siguiente porque es importante: con menos en el aire, los cuellos de botella saltan a la vista. Si “en progreso” se llena, no metes más trabajo, resuelves el atasco. Así funciona el flujo.Y ahora toca una historia rápida para que lo veas con un caso particular. Alex vende servicios de desarrollo web. Tenía cinco proyectos a la vez, todos a medias, todos urgentes, y todos sin facturar. Pusimos un tablero simple, tres columnas y un límite de dos tareas en progreso. Semana uno, eligió una entrega concreta por cliente y cortó todo lo demás. Publicó dos versiones uno y pudo facturar hitos parciales. Semana dos, bajó el tiempo de ciclo: de veinte días por entrega a nueve días. Semana tres, subió precios porque ya medía y podía prometer plazos realistas. Esto suele pasar más de lo que crees: en cuanto limitas el trabajo en progreso, el dinero llega antes porque entregas antes.Antes de seguir, hago una pequeña pausa. Este episodio está patrocinado por Systeme, la herramienta de marketing todo en uno gratuita con la que puedes crear tu web, blog, landing page y tienda online, crear automatizaciones y embudos de venta, realizar tus campañas de email marketing, vender cursos online, añadir pagos online e incluso crear webinars automatizados. Puedes empezar a usar Systeme gratis entrando en borjagiron.com barra systeme o desde el link de la descripción. Y ahora continuamos con el episodio.Continuamos con un aprendizaje rápido. Toma nota. Empieza por visualizar tu trabajo hoy mismo. Hoja, pizarra o herramienta digital, me da igual. Coloca las tareas en “por hacer”, “en progreso” y “entregado”. Pon un límite a “en progreso”. Uno si puedes, dos como máximo si tu operativa lo exige, por ejemplo creación y soporte. Define qué significa “hecho” antes de empezar: publicado, enviado, cobrado, lo que toque. Escribe ese criterio en la tarjeta para no autoengañarte. Usa bloques de cincuenta minutos para empujar una tarjeta hasta una versión lista. Nada de “trabajar en la web”, sino “publicar sección de preguntas frecuentes versión uno”. Al terminar el bloque, o entregas o dejas el siguiente paso escrito para no perder inercia. Y, muy clave, mide dos cosas a la semana: número de entregas y tiempo de ciclo medio. Si suben las entregas y baja el tiempo de ciclo, vas bien. Si no, reduce el límite de trabajo en progreso o haz más pequeñas las tareas.Ok, déjame darte un par de trucos de taller. Si te cuesta elegir la siguiente tarjeta, usa la regla de edad: atiende primero la que lleva más tiempo esperando. Si un cliente envía algo “urgente” que no es importante, pásalo por una mini regla de decisión: ¿impacta ingresos, retención o producto en treinta días? Si no, agenda o delega. Y si trabajas en equipo, acordad límites por persona y un límite agregado para “en progreso” del equipo. Cuando se llena, nadie mete nada nuevo; todos a desatascar. No suena glamuroso, pero es lo que hace que los proyectos acaben de verdad.Y ahora vamos con el resumen del episodio. Hemos visto cómo Toyota convirtió la escasez en ventaja limitando el trabajo en progreso con Kanban. En tu negocio, el exceso de cosas abiertas es el verdadero ladrón de horas. Visualiza el flujo, limita lo que está en progreso, define “hecho” con claridad y mide entregas y tiempo de ciclo. Con menos cosas a la vez, terminas antes, facturas antes y duermes mejor.Tu única acción para hoy es esta: crea un tablero con tres columnas y mueve todo lo que tengas a “por hacer”. Elige una sola tarjeta, escríbele un criterio de “hecho” y bloquea cincuenta minutos para llevarla a “entregado” hoy mismo. Solo una. Cuando la entregues, eliges la siguiente.Antes de irnos, si quieres dejar de emprender en soledad y decidir mejor cada día, te recomiendo el Club de Emprendedores Triunfers, al que puedes unirte desde Triunfers.com. Deja de emprender en soledad. Accede a una comunidad de emprendedores con la que siempre estás acompañado. Además incluye un Coworking online abierto veinticuatro horas, cursos de marketing, tutoriales de inteligencia artificial, podcast secreto y grupo privado en Telegram. Prueba gratis en triunfers punto com.Y hasta aquí por hoy. Si has aguantado mi voz de clon con firmware recién salido del horno, te debo un café y una actualización de cortesía. Prometo que en nada seré tan productivo que haré los guiones, las ediciones y, si me dejan, hasta los chistes… para que Borja solo tenga que aplaudir. Gracias por compartir el episodio con esa persona que lo pueda necesitar. Te espero mañana en el próximo episodio. Un fuerte abrazo.Conviértete en un seguidor de este podcast: https://www.spreaker.com/podcast/productividad-maxima--5279700/support.Newsletter Marketing Radical: https://marketingradical.substack.com/welcomeNewsletter Negocios con IA: https://negociosconia.substack.com/welcomeMis Libros: https://borjagiron.com/librosSysteme Gratis: https://borjagiron.com/systemeSysteme 30% dto: https://borjagiron.com/systeme30Manychat Gratis: https://borjagiron.com/manychatMetricool 30 días Gratis Plan Premium (Usa cupón BORJA30): https://borjagiron.com/metricoolNoticias Redes Sociales: https://redessocialeshoy.comNoticias IA: https://inteligenciaartificialhoy.comClub: https://triunfers.com

Alex Sloley: Coaching Teams Trapped Between Agile Aspirations and Organizational Control 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 says, oh, we want to try to do things this way, and the org keeps coming back and saying stuff like, no, no, no, you can't do that, because in this org, we don't allow that." - Alex Sloley Alex shares his current challenge working with a 10-person pilot Scrum team within a 1,500-person organization that has never done Agile before. While the team appears open-minded and eager to embrace agile ways of working, the organization continuously creates impediments by dictating how the team must estimate, break down work, and operate. Management tells them "the right way" to do everything, from estimation techniques to role-based work assignments, even implementing RACI matrices that restrict who can do what type of work. Half the team has been with the organization for six months or less, making it comfortable to simply defer to authority and follow organizational rules. Through coaching conversation, Alex explores whether the team might be falling into learned helplessness or simply finding comfort in being told what to do—both positions that avoid accountability. His experimental approach includes designing retrospective questions to help the team reflect on what they believe they're empowered to do versus what management dictates, and potentially using delegation cards to facilitate conversations about decision-making authority. Alex's key insight is recognizing that teams may step back from empowerment either out of fear or comfort, and identifying which dynamic is at play requires careful, small experiments that create safe spaces for honest dialogue. Self-reflection Question: When your team defers to organizational authority, are they operating from learned helplessness, comfort in avoiding accountability, or genuine respect for hierarchy? How can you design experiments to uncover the real dynamic at play? [The Scrum Master Toolbox Podcast Recommends]

Alex Sloley: When Toxic Leadership Creates Teams That Self-Destruct 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. "They would take notes at every team meeting, so that later on they could argue with team members about what they committed to, and what they said in meetings." - Alex Sloley Alex recounts working with a small team where a project manager created such a toxic environment that one new hire quit after just eight hours on the job. This PM would belittle team members publicly, take detailed notes to use as weapons in contract negotiations, and dominate the team through intimidation. The situation became so severe that one team member sent an email that sounded like a suicide note. When the PM criticized Alex's "slide deck velocity," comparing four slides per 15 minutes to Alex's one, he realized the environment was beyond salvaging. Despite coaching the team and attempting to introduce Scrum values, Alex ultimately concluded that management was encouraging this behavior as a control mechanism. The organization lacked trust in the team, creating learned helplessness where team members became submissive and unable to resist. Sometimes, the most important lesson for a Scrum Master is recognizing when a system is too toxic to change and having the courage to walk away. Alex emphasizes that respect—one of the core Scrum values—was completely absent, making any meaningful transformation impossible. In this segment, we talk about “learned helplessness”.  Self-reflection Question: How do you recognize when a toxic environment is being actively encouraged by the system rather than caused by individual behavior? What are the signs that it's time to exit rather than continue fighting? Featured Book of the Week: The Goal by Eliyahu M. Goldratt Alex describes his complex relationship with The Goal by Goldratt—it both inspires and worries him. He struggles with the text because the concepts are so deep and meaningful that he's never quite sure he's fully understood everything Goldratt was trying to convey. The book was difficult to read, taking him four times longer than other agile-related books, and he had to reread entire sections multiple times. Despite the challenge, the concepts around Theory of Constraints and systems thinking have stayed with him for years. Alex worries late at night that he might have missed something important in the book.  He also mentions reading The Scrum Guide at least once a week, finding new tidbits each time and reflecting on why specific segments say what they say. Both books share a common thread—the text that isn't in the text—requiring readers to dig deeper into the underlying principles and meanings rather than just the surface content. [The Scrum Master Toolbox Podcast Recommends]

Alex Sloley: The Sprint Planning That Wouldn't End - A Timeboxing Failure 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. "Although I knew about the steps of sprint planning, what I didn't really understand was the box of time versus the box of scope." - Alex Sloley Alex shares a critical learning moment from his first team as a Scrum Master. After six months in the role, during an eight-hour sprint planning session for a four-week sprint, he successfully completed the "what" portion but ran out of time before addressing "how." Rather than respecting the timebox, Alex forced the team to continue planning for another four hours the next day—blowing the timebox by 50%. This experience taught him a fundamental lesson: the difference between scope-boxing and timeboxing. In waterfall, we try to control scope while time slips away. In Scrum, we fix time and let scope adjust. Alex emphasizes that timeboxing isn't just about keeping meetings short—it's about limiting work in process and maintaining focus. His practical tip: use visible timers to train yourself and your teams to respect timeboxes. This mindset shift from controlling scope to respecting time remains one of the most important lessons for Scrum Masters. Self-reflection Question: How often do you prioritize completing a planned agenda over respecting the timebox? What message does this send to your team about the values you're reinforcing? [The Scrum Master Toolbox Podcast Recommends]

Chronic over-commitment is a process problem, not a personal failing. In this episode, Dr. Grajdek teaches teams to visualize demand vs. capacity with Kanban and WIP limits, prioritize, and renegotiate. Set SLAs for inbound requests, prune the backlog quarterly, and protect maker time – so that  “no” becomes a professional, data-backed path to reliable delivery (and saner weeks). Tune in to learn more.  Check out Stress-Free With Dr G on YouTubehttps://youtube.com/channel/UCxHq0osRest0BqQQRXfdjiQ The Stress Solution: Your Blueprint For Stress Management Masteryhttps://a.co/d/07xAdo7l 

BONUS: The Evolution of Agile - From Project Management to Adaptive Intelligence, With Mario Aiello In this BONUS episode, we explore the remarkable journey of Mario Aiello, a veteran agility thinker who has witnessed and shaped the evolution of Agile from its earliest days. Now freshly retired, Mario shares decades of hard-won insights about what works, what doesn't, and where Agile is headed next. This conversation challenges conventional thinking about methodologies, certifications, and what it truly means to be an Agile coach in complex environments. The Early Days: Agilizing Before Agile Had a Name "I came from project management and project management was, for me, was not working. I used to be a wishful liar, basically, because I used to manipulate reports in such a way that would please the listener. I knew it was bullshit." Mario's journey into Agile began around 2001 at Sun Microsystems, where he was already experimenting with iterative approaches while the rest of the world was still firmly planted in traditional project management. Working in Palo Alto, he encountered early adopters discussing Extreme Programming and had an "aha moment" - realizing that concepts like short iterations, feedback loops, and learning could rescue him from the unsustainable madness of traditional project management. He began incorporating these ideas into his work with PRINCE2, calling stages "iterations" and making them as short as possible. His simple agile approach focused on: work on the most important thing first, finish it, then move to the next one, cooperate with each other, and continuously improve. The Trajectory of Agile: From Values to Mechanisms "When the craze of methodologies came about, I started questioning the commercialization and monetization of methodologies. That's where things started to get a little bit complicated because the general focus drifted from values and principles to mechanisms and metrics." Mario describes witnessing three distinct phases in Agile's evolution. The early days were authentic - software developers speaking from the heart about genuine needs for new ways of working. The Agile Manifesto put important truths in front of everyone. However, as methodologies became commercialized, the focus shifted dangerously away from the core values and principles toward prescriptive mechanisms, metrics, and ceremonies. Mario emphasizes that when you focus on values and principles, you discover the purpose behind changing your ways of working. When you focus only on mechanics, you end up just doing things without real purpose - and that's when Agile became a noun, with people trying to "be agile" instead of achieving agility. He's clear that he's not against methodologies like Scrum, XP, SAFe, or LeSS - but rather against their mindless application without understanding the essence behind them. Making Sense Before Methodology: The Four-Fit Framework "Agile for me has to be fit for purpose, fit for context, fit for practice, and I even include a fourth dimension - fit for improvement." Rather than jumping straight to methodology selection, Mario advocates for a sense-making approach. First, understand your purpose - why do you want Agile? Then examine your context - where do you live, how does your company work? Only after making sense of the gap between your current state and where the values and principles suggest you should be, should you choose a methodology. This might mean Scrum for complex environments, or perhaps a flow-based approach for more predictable work, or creating your own hybrid. The key insight is that anyone who understands Agile's principles and values is free to create their own approach - it's fundamentally about plan, do, inspect, and adapt. Learning Through Failure: Context is Paramount "I failed more often than I won. That teaches you - being brave enough to say I failed, I learned, I move on because I'm going to use it better next time." Mario shares pivotal learning moments from his career, including an early attempt to "agilize PRINCE2" in a command-and-control startup environment. While not an ultimate success, this battle taught him that context is paramount and cannot be ignored. You must start by understanding how things are done today - identifying what's good (keep doing it), what's bad (try to improve it), and what's ugly (eradicate it to the extent possible). This lesson shaped his next engagement at a 300-person organization, where he spent nearly five months preparing the organizational context before even introducing Scrum. He started with "simple agile" practices, then took a systems approach to the entire delivery system. A Systems Approach: From Idea to Cash "From the moment sales and marketing people get brilliant ideas they want built, until the team delivers them into production and supports them - all that is a system. You cannot have different parts finger-pointing." Mario challenges the common narrow view of software development systems. Rather than focusing only on prioritization, development, and testing, he advocates for considering everything that influences delivery - from conception through to cash. His approach involved reorganizing an entire office floor, moving away from functional silos (sales here, marketing there, development over there) to value stream-based organization around products. Everyone involved in making work happen, including security, sales, product design, and client understanding, is part of the system. In one transformation, he shifted security from being gatekeepers at the end of the line to strategic partners from day one, embedding security throughout the entire value stream. This comprehensive systems thinking happened before formal Scrum training began. Beyond the Job Description: What Can an Agile Coach Really Do? "I said to some people, I'm not a coach. I'm just somebody that happens to have experience. How can I give something that can help and maybe influence the system?" Mario admits he doesn't qualify as a coach by traditional standards - he has no formal coaching qualifications. His coaching approach comes from decades of Rugby experience and focuses on establishing relationships with teams, understanding where they're going, and helping them make sense of their path forward. He emphasizes adaptive intelligence - the probe, sense, respond cycle. Rather than trying to change everything at once and capsizing the boat, he advocates for challenging one behavior at a time, starting with the most important, encouraging adaptation, and probing quickly to check for impact of specific changes. His role became inviting people to think outside the box, beyond the rigidity of their training and certifications, helping individuals and teams who could then influence the broader system even when organizational change seemed impossible. The Future: Adaptive Intelligence and Making Room for Agile "I'm using a lot of adaptive intelligence these days - probe, sense, respond, learn and adapt. That sequence will take people places." Looking ahead, Mario believes the valuable core of Agile - its values and principles - will remain, but the way we apply them must evolve. He advocates for adaptive intelligence approaches that emphasize sense-making and continuous learning rather than rigid adherence to frameworks. As he enters retirement, Mario is determined to make room for Agile in his new life, seeking ways to give back to the community through his blog, his new Substack "Adaptive Ways," and by inviting others to think differently. He's exploring a "pay as you wish" approach to sharing his experience, recognizing that while he may not be a traditional coach or social media expert, his decades of real-world experience - with its failures and successes - holds value for those still navigating the complexity of organizational change. About Mario Aiello Retired from full-time work, Mario is an agility thinker shaped by real-world complexity, not dogma. With decades in VUCA environments, he blends strategic clarity, emotional intelligence, and creative resilience. He designs context-driven agility, guiding teams and leaders beyond frameworks toward genuine value, adaptive systems, and meaningful transformation. You can link with Mario Aiello on LinkedIn, visit his website at Agile Ways.

In this episode of the Level Up Claims Podcast, host Galen Hair discusses with Ari Meisel, a productivity expert who has collaborated with giants like Tony Robbins and NASA, about optimizing your life. Ari shares his journey from a Crohn's diagnosis to pioneering efficiency through “Less Doing” with insights on automation and productivity tools. Tune in to learn strategies for freeing up your time, reducing stress, and achieving more by doing less. This episode might just give you back your life!   Highlights Automate repetitive tasks. Doing less as a solution. Ari Meisel's journey to productivity. Overcoming Crohn's with productivity framework. The impact of time restrictions on innovation. Challenging the “busy” mindset. Asynchronous communication benefits. Automation's role in error reduction. Utilization of Kanban boards for task management. Diet and stress management in biohacking. Impact of sugar and emotional eating. Episode Resources Connect with Galen M. Hair https://insuranceclaimhq.com hair@hairshunnarah.com  https://levelupclaim.com/

Most organizations default to command-and-control when creating policies - one person decides what needs to happen, writes it down, and expects everyone else to follow along. The problem is that this approach creates policies that exist on paper but fail in practice, because the people doing the actual work never bought into them in the first place. In today's episode, I'm joined by Agile Educator and Organizational Coach Tim Lennon to discuss why the traditional approach to making policies explicit often backfires, especially in American workplaces. Through Tim's evolution from teaching the Kanban method to developing what he calls "Adaptive Kanban," we uncover why negotiating working agreements with your team creates far better results than top-down mandates. Get full show notes, transcript, and more information here: agileattorney.com/90Take your law practice from overwhelmed to optimized with Greenline LegalFollow along on LinkedIn: linkedin.com/in/johnegrant

Here are the top 5 takeaways from this episode with Nicole Loughlin of Loughlin Law P.A.:* Ditching the Billable Hour for Predictable Fees: Nicole transitioned her estate planning and probate practice away from hourly billing to a hybrid model with flat fees and a sliding scale based on statutory guidelines. This approach provides clients with predictability, reduces billing disputes, and aligns incentives for efficiency.* Automation and Efficient Client Management: Nicole has heavily automated her law firm's intake, lead management, and client follow-up processes using tools like Kanban boards and practice management software (Lawcus). This ensures a consistent client experience, improves conversion rates, and keeps cases moving efficiently.* Customer Service as a Differentiator: Exceptional customer service is central to Nicole's practice. She offers proactive check-ins, regular follow-ups, and responsive communication, often surprising clients with the level of attention and support—much of which could be packaged as a subscription offering in the future.* Work-Life Integration and Flexibility: Nicole built her practice to accommodate her role as a mother, prioritizing flexibility and work-life integration. She challenges the traditional law firm model, demonstrating that it's possible to have a successful legal career while being present for family, and encourages others—especially women—to do the same.* Openness to Technology and Continuous Improvement: While Nicole has automated many aspects of her practice, she remains open to further streamlining, especially as new tools become available. She balances automation with personalized service, ensuring high-quality work product and client satisfaction, and sees room for future enhancements as her practice evolves.__________________________Learn more about Nicole Loughlin.Want to maximize your law firm? Get your ticket to MaxLawCon!Sign up for Paxton, my all-in-one AI legal assistant, helping me with legal research, analysis, drafting, and enhancing existing legal work product.Here's a link to purchase lifetime access to the recordings of My Shingle's AI Teach-In if you couldn't make it live.I've partnered with Pii to make it easy for you to purchase the hardware I use in my law firm: (1) Studio Setup; (2) Midrange Setup; (3) Highrange Setup.Sign up for Paxton, my all-in-one AI legal assistant, helping me with legal research, analysis, drafting, and enhancing existing legal work product.Get Connected with SixFifty⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, a business and employment legal document automation tool.Sign up for ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Gavel⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, an automation platform for law firms.Check out my other show, the Law for Kids Podcast.Visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Law Subscribed⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to subscribe to the weekly newsletter to listen from your web browser.Prefer monthly updates? Sign up for the Law Subscribed Monthly Digest on LinkedIn.Want to use the subscription model for your law firm? Sign up for the Subscription Seminar waitlist at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠subscriptionseminar.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.Check out ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Mathew Kerbis'⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ law firm ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Subscription Attorney LLC⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Get full access to Law Subscribed at www.lawsubscribed.com/subscribe

Is Scrum Dying? Or Are We Just Doing It Wrong?Scrum used to be king. Now people don't even want it on their CV.Remember when being a Product Owner was cool? When Scrum Masters were change agents, not glorified note-takers?When saying “we use Scrum” signalled progressive, Agile thinking?Fast forward to now, and you'll find Product Owners ashamed of the title, Scrum Masters sidelined, and developers stuck in factory-mode delivery.Teams are jumping ship to SAFe, Kanban, or “whatever Spotify did,” chasing results Scrum couldn't deliver.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/

n Episode 132 of the Taps and Patience podcast, AJ and Harrison discuss Harrison's new lathe, a DN Solutions Lynx 2100 LSYB, its specifications, features, and the expected learning curve associated with it. They also touch upon challenges faced in machining, such as warping of materials and improving operational efficiency, and discuss the importance of adapting workflows and systems to keep up with their growing manufacturing needs. Finally, they introduced a new tool developed for generating Kanban cards from Fusion tool libraries, emphasizing the balance between busy work in the shop and higher-level strategic thinking.Check out our Kanban Generator: https://subtractmanufacturing.com/kanban

In this episode. Jason is catching up on powerful lessons and field-tested practices that can make your projects safer, cleaner, and more effective. Here's what you'll learn: The Builder's Code: How you treat workers and foremen is exactly how they'll treat the building, and what the client ultimately experiences. Lessons from Japan (Gemba): Start with 2–3S (sort, straighten, shine), watch people's movement, and stop where things don't make sense to reveal hidden constraints. Problems vs. Dilemmas: A problem has a clear solution; a dilemma forces you to choose between imperfect options. Jason shares examples every builder will recognize. Trash Management Done Right: Pre-kit and pre-cut to reduce waste, use scrap-out units, and manage dumpsters with visual Kanban triggers at half or three-quarters full. Daily Logistics Discipline: Assign a logistics owner to check the perimeter, cleanliness, recycling, and traffic control every single day. Why Saturdays Don't Work: Crews show up thin, productivity drops, and you lose momentum. Stop relying on weekend work as the answer. AEDs on Every Site: More lives are lost to cardiac arrest than auto accidents. Affordable AEDs (around $1,400) save lives. Every project needs one. This episode is practical, fast-moving, and packed with insights you can take straight to the field. If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode.  And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two

Jon Ferrara, CEO of Nimble, has devoted his career to helping people grow their businesses by turning contacts into lasting, valuable relationships. We explore Jon's journey from creating GoldMine, one of the first successful CRMs, to founding Nimble, a relationship-focused CRM that brings contact management back to its roots. Jon shares his personal “Why” — to grow his soul by helping others grow theirs — and explains why relationships, not technology, are the real key to business success. He introduces his signature frameworks: the Five F's of Relationships (Family, Friends, Food, Fun, and Fellowship) for building authentic connections, the Five E's of Brand-Building (Educate, Enchant, Engage, Embrace, and Empower) for expanding influence, and the Three P's (Passion, Plan, Purpose) for achieving personal and professional goals. Jon also describes how Kanban-style workflows and selective automation enable entrepreneurs and teams to manage contacts at scale without losing the human touch. --- Important links: Jon's LinkedIn Start a free trial of Nimble Email Jon directly: jon@nimble.com

The British author and journalist Oliver Burkeman has spent decades pondering what it means to live a meaningful life, both in his former Guardian column “This Column WIll Change Your Life” and across several books—most recently, Meditations for Mortals, out in paperback this October. That's why he brings a healthy dose of skepticism to so-called “time management” systems and productivity hacks as a means toward true fulfillment. Burkeman's compelled by the notion that, rather than being separate from time, human beings are time. If people faced the reality of their limited time on the planet head on, he believes there's a real chance to experience greater, more engaged feelings of aliveness.On the episode—our Season 12 kick-off—Burkeman discusses why he's eschewing  perfectionism and finding unexpected liberation in the premise that, to some extent, the worst has already happened, and the best may still be ahead.Special thanks to our Season 11 presenting sponsor, Van Cleef & Arpels.Show notes:Oliver Burkeman[4:26] “Meditations for Mortals” (2024)[6:48] Donald Winnicott[7:46] Martin Heidegger[7:46] "Technics and Civilization" (2010)[7:46] “Being and Time” (1927)[7:46] “Time Warrior” (2011)[7:46] “Time Surfing” (2017)[7:46] “Anti-Time Management” (2022)[10:14] Medieval peasants[10:14] “The 4-Hour Workweek”[13:18] Alicja Kwade[19:23] “Ichi-go, ichi-e” (“one time, one meeting”)[22:00] Eckhart Tolle[22:36] Agnes Martin[23:28] “The Road Not Taken”[40:03] “This Column Will Change Your Life”[51:00] Nicholas Carr[51:00] Clay Shirky[53:40] Jennifer Roberts[59:04] Pomodoro Technique [59:13] Kanban[1:01:33] James Hollis[1:02:40] Alfred Adler[1:02:40] “The Courage to Be Disliked” (2024)[1:06:24] Stoicism

Managing a law firm's workflow can be tricky, especially when you're juggling a long list of active matters and chasing unresponsive clients. In this episode, I'll share how one firm, after years of using Kanban, finally broke through the delivery bottleneck with a simple but powerful shift in their approach.You'll hear the key changes they made that allowed them to close 40 matters in one month, even in what's usually their slowest season. Tune in to discover how simplifying your systems, setting clear client expectations, and focusing on the work that matters most can unlock new levels of productivity and capacity for your practice.Get full show notes, transcript, and more information here: agileattorney.com/88Get the 5-day Agile Attorney Boot Camp here: agileattorney.com/resourcesJoin me on Bluesky: bsky.app/profile/agileattorney.comFollow me on LinkedIn: www.linkedin.com/in/johnegrant/

Jem gets deep into Grasshopper software building custom robot CAM while Justin keeps drilling thousands of holes on his ShopSabre. They chat about wild HTX Studio YouTube automation, scary tool changer malfunctions, and the eternal struggle of buying used vs new CNC machines. Plus Justin upgrades to a bigger 3D printer and teases his AirShop inventory & quoting software. Plus koala vaccines, and 8020 extrusion workholding in the future?Watch on YoutubeDISCUSSED:✍️ Comment or Suggest a TopicKoala VaccineJem in love with GrasshopperGrasshopper Tutorial VideoHTX Studio! ꘎Justin is still drilling thousands of holesMulticam Trident CNC Tool Changer issueShopping for mills, how can you tell if a secondhand machine is any good!?Plywood tombstones no so much good ꘎Should I use 8020 extrusion for fixtures!?Robot work holding!? ꘎ExtrusionJ moves are sketchy as in Robot programmingPierson videoH2S on the way AirShop update Kanban cards done, testers signup hereEric Trine like wine---Profit First PlaylistClassic Episodes Playlist---SUPPORT THE SHOWBecome a Patreon - Get the Secret ShowReview on Apple Podcast Share with a FriendDiscuss on Show SubredditShow InfoShow WebsiteContact Jem & JustinInstagram | Tiktok | Facebook | YoutubePlease note: Show notes contains affiliate links.HOSTSJem FreemanCastlemaine, Victoria, AustraliaLike Butter | Instagram |

Ryan Sudeck is the CEO of Sage Investment Group, where he leads a team focused on addressing the affordable housing crisis through hotel-to-apartment conversions. With a background in mergers and acquisitions at Amazon, Samsung, and Redfin, Ryan has overseen more than 24 successful adaptive reuse projects nationwide. Under his leadership, Sage operates an evergreen fund with over 400 investors, creating high-quality, naturally affordable housing at scale.     Make sure to download our free guide, 7 Questions Every Passive Investor Should Ask, here.     Key Takeaways Hotels are valued differently than apartments, creating a 40%+ value lift when converted to residential use. Sage Investment Group has completed 24 hotel-to-apartment conversions across six states, with 100–200 units per property. Units are typically 300-square-foot studios with full kitchens and modern amenities. Strong diligence on entitlements, construction, and lease-up is critical for success. Patience in acquisitions—sometimes two years per deal—is key to meeting return thresholds.     Topics From M&A to Affordable Housing Ryan's career in corporate acquisitions prepared him to lead Sage. Joined as CEO to scale a mission-driven approach to solving the housing shortage. Why Hotel Conversions Work Hotels trade at higher cap rates than apartments, creating built-in arbitrage. Conversion costs average $100K per unit—about half the replacement cost of new builds. Final product: fully renovated studios with fitness centers, coworking, and community amenities. Execution Risks and Lessons Learned Entitlements: converting from commercial to residential requires local approvals. Construction: inspections, sewer scopes, and cutting open walls before purchase to avoid surprises. Lease-up: conservative rent assumptions and regional property managers ensure stabilized occupancy. Capital Stack and Returns Evergreen fund supplies 25–35% of equity alongside LPs. Senior debt from community banks or private debt funds covers 60–75%. Renovation costs run $35K–$45K per unit; recent refis have returned significant equity. Why Not Ground-Up or Value-Add? Ground-up costs 2x more per unit and faces supply delays. Value-add multifamily is overpriced with thin margins post-2021. Conversions provide stronger risk-adjusted returns.    

The Birth of the Agile Delivery Manager = No More ScrumMastersIn 2025, we formally changed the title of Scrum Master to Agile Delivery Manager (ADM) in our technology division. This renaming wasn't a rebrand for the sake of optics. It reflected a deeper evolution already happening, rooted in the expanding scope of delivery leadership, the adoption of Flow Metrics and Value Stream Management, and our real-world shift from strict Scrum toward a more customized Kanban-based model.It was this year that the name finally clicked. After assigning Value Stream Architect responsibilities to our Scrum Masters and giving them ownership of delivery metrics, team-level delivery health, and collaboration across roles within their Agile team, I realized the title “Scrum Master” no longer fit their role. I even considered Agile Value Stream Manager, but it felt too narrow and platform-specific.That's when Agile Delivery Manager stood out, not only as a better label but also as a more accurate reflection of the mindset and mission.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/

Knowledge work hides in ways that physical work never could. That invisibility creates a dangerous pattern: you say yes to one more matter and before you know it, your entire team operates beyond capacity. In this episode, I use real examples from law firms using Kanban boards to demonstrate how making your work visible can fundamentally change how your team coordinates, communicates, and makes decisions about your capacity.Get full show notes, transcript, and more information here: https://www.agileattorney.com/85Mentioned in this episode:Greenline.legal is Officially in BetaTo set up a demo of this software with me, talk through the workflow challenges and opportunities you have in your practice, and see how Greenline could help, click here: https://the-agile-attorney.captivate.fm/greenlinelegalGreenlineLegal Demo

Salum Abdul-Rahman: From Lunch Conversations to Company-Wide Change—The Power of Creating Communities of Practice Within Organizations 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. Salum shares how he organically built an Agile community within his company by recognizing a shared need for discussion and learning. Starting as a software developer who took on Scrum Master tasks, he felt isolated in his Agile journey. Rather than waiting for formal training or external events, he sent out a simple invite on the company Slack for a lunch discussion during a work day. People showed up, and what began as informal conversations about different approaches to Scrum and Kanban evolved into monthly gatherings. Over time, this grassroots community grew to organize company-wide events and even found new leadership when Salum moved on, demonstrating the power of identifying shared needs and taking initiative to address them. Self-reflection Question: What shared learning needs exist in your organization that you could address by simply reaching out and organizing informal discussions? [The Scrum Master Toolbox Podcast Recommends]

In this episode, we welcome Lisa Zawrotny, a productivity coach with a rich background as a caregiver, mother, and business owner. Lisa shares her journey from caregiving to coaching, emphasizing the importance of compassionate and sustainable productivity systems, especially for those managing ADHD or high-stress roles. We discuss the nuances of burnout versus overwhelm, the significance of self-awareness, and practical strategies to enhance productivity without sacrificing well-being.Key Moments:Lisa shares her journey from caregiver to productivity coach, highlighting the challenges of managing burnout and overwhelm.Burnout can manifest as constant dread, resentment, and exhaustion, while overwhelm often feels like having too much to do without knowing where to start.Knowing and accepting oneself is crucial for building effective productivity systems tailored to individual needs.Before implementing systems, decluttering and simplifying tasks is essential to create a manageable workload.Productivity should support life, not the other way around. Rest and self-care are integral to sustainable productivity.Productivity systems should be customized to fit how individuals work best, especially for those with ADHD or other unique challenges.Moving away from hustle culture and redefining success can alleviate feelings of inadequacy and burnout.Lisa discusses various tools and methods, such as the Pomodoro technique and Kanban boards, to enhance productivity.Engaging with a community and seeking support can help individuals navigate their productivity challenges.Lisa is working on new workshops and a signature program to further support individuals in their productivity journeys.To learn more about Lisa Zawrotny please visit her Linkedin ProfileTo learn more about Lisa Zawrotny please visit her website.YOUR HOST - SIMON LADER    Simon Lader is the host of The Conference Room, Co-Founder of global executive search firm Salisi Human Capital, and lead generation consultancy Flow and Scale. Since 1997, Simon has helped cybersecurity vendors to build highly effective teams, and since 2022 he has helped people create consistent revenue through consistent lead generation.        Get to know more about Simon at:      Website: https://simonlader.com/  Twitter: https://twitter.com/simonlader  LinkedIn: https://www.linkedin.com/in/headhuntersimonlader/      The Conference Room is available onSpotifyApple podcastsAmazon MusicIHeartRadio

What happens when one of the most respected minds in lean construction sits down to dissect project planning systems? You get this episode. In this powerful conversation, Jason is joined by mentor and thought leader Hal Macomber to explore: Why CPM lacks production theory (and what that means for your projects). The real difference between Scrum and Kanban. How Takt construction works as a socio-technical system and why that's critical. Why some teams thrive with lean systems... and others just don't. How the software industry has outpaced construction in flow-based systems and what we can learn from them. If you've ever wondered why schedules fail, why flow breaks down, or how to actually support your field teams with better planning this episode is your blueprint. You'll walk away with: ✔ A clear understanding of how Kanban brings flow front and center. ✔ Practical takeaways on how to align office + field teams. ✔ Insightful critiques of current scheduling tools and what to use instead.   If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode.  And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two