Podcasts about Kanban

In this episode, Jason explores how to apply Kanban at the crew level within construction projects. He explains how a Kanban or Scrum board can track work from backlog, to in-progress, to done, ensuring clarity and alignment across the office and field. What you'll learn in this episode: How Kanban and Scrum boards function in construction project delivery. Using boards to align project managers, engineers, and field crews. How to implement backlog, in-progress, and done columns for clarity. The benefits of crew-level Kanban for sequencing and pacing tasks. How real-time adjustments keep office and field work in sync. Are your crews seeing the work in real time and flowing efficiently or is your process creating confusion and wasted effort?   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

One of the biggest problems of vibe coding? Securely keeping the project up to date and sharing it with your team to make it actually useful. And there's a new solution that does just that, Codex Sites. With a few simple prompts, you can turn vibe coded throwaway apps into working pieces of software that your team can share. We put AI to work on Wednesday and show you how to get the most out of Codex Sites. Codex Sites: The Lovable and Replit Killer? A hands-on Guide to Codex Sites -- An Everyday AI Chat with Jordan WilsonNewsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageToday's Episode on LinkedIn: Thoughts on this? Join the convo on LinkedIn and connect with other AI leaders.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:Codex Sites vs Static File SharingLive Dashboards and Automated WorkflowsBuilding Internal Apps With Codex SitesReal-Time Data Integration in CodexAgent Layer and Role-Based Access ControlCodex Sites vs Replit, Lovable, BoltDynamic Business Insights and CollaborationCodex Sites Secure Team Sharing LimitationsAutomations and Custom Skills in CodexFuture of AI Native Business ToolsTimestamps:00:00 The future of work automation03:43 Free daily newsletter highlights08:29 Managing audience momentum dashboard12:04 Pulling stats and data access14:48 Creating dynamic web tools16:18 Editing video collaboration challenges21:09 Comparing coding platforms like Replit25:47 Future of Business Analytics Tools27:11 Introducing the Start Here series32:35 Updating old content ideas34:53 Streamlining team efficiency with AI37:02 Episode use cases overviewKeywords: Codex sites, OpenAI, AI dashboards, live software, file sharing, business automation, dynamic data, ChatGPT business, agentic system, Chrome integration, MCP servers, skills, plugins, Copilot Scout, internal dashboards, data analysis, role based access control, data governance, enterprise AI tools, site hosting, live app builder, prompt driven apps, automations, Replit alternative, Lovable competitor, full stack app builder, dynamic business context, annotation feature, nontechnical teams, BI dashboards, Kanban tracker, evergreen content, live indicators, audience momentum dashboard, sub agent, responsive design, visual design, parallax feature, actionable insights, version control, dynamic deliverables, artifact, demo over memo, knowledge work, IT security, internal URL sharing, AI native workflow, internal business tools, real time updates, start here seriesSend Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Start Here ▶️Not sure where to start when it comes to AI? Start with our Start Here Series. You can listen to the first drop -- Episode 691 -- or get free access to our Inner Cricle community and all episodes: StartHereSeries.com Also, here's a link to the entire series on a Spotify playlist. 

Chris Lucian and Austin Chadwick discuss all things #agile and product development from a #MobProgramming perspective. What if you could decompose every agile method down to its essential building blocks and recombine them for your own specific context? In this episode, Chris and Austin are joined by Aria Omidvar to explore the HEXI method — a framework-agnostic approach to understanding and applying agile, lean, and software craftsmanship practices through physical hexagon objects and collective sense-making. Aria shares his journey from software craftsmanship and clean code, through Scrum and XP, to discovering Dave Snowden's HEXI method and building his own independent "Hexiverse" — a modular knowledge map that spans Software Teaming, Extreme Programming, Kanban, Modern Synthesis, the Agile Manifesto, and more. He unpacks how breaking methods into reusable hexagonal pieces allows teams (and individuals) to see the connections between ideas, surface what is missing, and navigate the overwhelming landscape of agile methods without falling into method wars. We dig into: What the HEXI method is and how Dave Snowden and Nigel Thurlow introduced it via Scrum.org How Aria independently adapted HEXI to create a Hexiverse for software teaming and mob programming Why decomposing methods into building blocks enables recombination for any specific context The spatial design choices behind the Hexiverse — and why dotted hexagons signal a concept shared across sets How Alistair Cockburn validated the Agile Manifesto hexiset (and why that meant the world to Aria) The learning journey metaphor of islands growing large enough to connect — and how the Hexiverse accelerates that Why "nice" doesn't cut it in high-collaboration environments — and how kindness, consideration, and respect offer a deeper model The "turn up the good" retrospective format and why it flips the traditional improvement lens How the Hexiverse serves both as a personal learning quest and a potential onboarding tool for teams new to agile methods Aria's call to action: check the original HEXI sources, play with the physical kits, and consider building your own Hexiverse Scaling Complex Systems by Building on Agile Frameworks with Dave Snowden and Nigel Thurlow: https://youtu.be/AEf1BCffimA Aria's Hexiverse on Miro: https://miro.com/app/board/uXjVKv84GGU= The Hitchhiker's Guide to Hexiverse on Medium: https://medium.com/@omidvar.aria/list/the-hitchhikers-guide-to-the-independent-hexiverse-fe509a7c46f8 The Hitchhiker's Guide to Hexiverse on LeanPub: https://leanpub.com/HG2H

Agilität ist längst Realität in vielen Organisationen. Scrum, Kanban, Dailys, Retrospektiven – die Methoden sind bekannt. Und trotzdem beobachten wir in der Praxis immer wieder: Teams arbeiten „agil", aber echtes Lernen findet kaum statt. Woran liegt das? In unserer neuen Podcastfolge sprechen wir mit Imola über einen Faktor, der in vielen Transformationen unterschätzt wird: psychologische Sicherheit. Denn gute Stimmung im Team bedeutet noch lange nicht, dass Menschen auch Widerspruch äußern, Risiken ansprechen oder Fehler früh sichtbar machen. Genau das wäre aber die Grundlage dafür, dass Teams wirklich lernen und sich weiterentwickeln können. In der Folge geht es unter anderem um diese Fragen: • Woran erkenne ich echte psychologische Sicherheit – jenseits von Harmonie? • Warum greifen agile Methoden ohne die passende Haltung oft zu kurz? • Welche Rolle können Coaches in agilen Transformationsprozessen übernehmen? • Und welche Kompetenzen brauchen Coaches, um in diesen Kontexten wirksam zu sein? Wenn du mit Teams arbeitest, Transformation begleitest oder verstehen möchtest, wie Coaching in komplexen Organisationen wirkt, ist diese Folge für dich.

Law firms are constantly being introduced to new tools, frameworks, and operational philosophies that promise better efficiency and better results. But the challenge is not simply adopting a popular methodology; it's understanding which approaches actually fit the type of work your team is doing and the problems you're trying to solve within your law firm operations.In this episode, I sit down with business consultant and Agile practitioner Robin Sims-Allen to explore what law firms can learn from other heavily regulated industries about process improvement, project management, and organizational change. We discuss the strengths and limitations of frameworks like Scrum, SAFe, Kanban, and Waterfall, and why choosing the right tool depends on the nature of the work, the structure of the team, and the realities of the environment you're operating in.Get full show notes, transcript, and more information here: agileattorney.com/121Take your law practice from overwhelmed to optimized with GreenLine LegalFollow along on LinkedIn: linkedin.com/in/johnegrantFollow Robin on LinkedIn: linkedin.com/in/robinsimsallen

Roland and J-M go solo to pull back the curtain on something that's been years in the making: BPM OS, a purpose-built, local-first tool stack designed to help small, talented process and architecture teams stand up a real BPM practice — without the vendor dependency, IT overhead, or 12-month procurement nightmare.In this episode of the podcast we talk about: Most BPM programs fail not because of bad content, but because organizations treat it as a pure IT exercise — buy a platform, check the box, and wonder why nothing sticks.The three pillars every BPM capability needs are content, governance, and adoption — yet most organizations only address the first one.Knowledge rented from consultants or SaaS vendors disappears the moment you stop paying; BPM OS is built on the principle that you own it outright, forever.BPM OS targets three groups: small internal teams doing more with less, consulting organizations that want baked-in methodology for client delivery, and vendors looking to bundle a white-labeled practice layer with their platforms.Groundwork is the brainstorming and planning app — dump ideas onto a canvas, sort them into zones, and shift into structured planning mode with priorities and rough timelines.Playbook is a lightweight wiki for capturing structured knowledge, course profiles, stakeholder analyses, and methodology documentation — with templates so you never start from a blank page.Atlas generates visual subway maps of your learning curriculum or capability landscape, complete with time-sensitive station states, deprecation indicators, and links back to Playbook pages.Outline lets you define the detailed content structure of a course or deliverable in a hierarchical, mind-map-style view — moving from “What do we need to teach?” to "Exactly what are the chapters and items?”Course Flow is a Kanban-based project management tool for developing and iterating on courses, complete with a built-in feedback form, an inbox for triage, and a status dashboard across all active projects.Cadence is a personal (and optionally team) task planner organized by day and category — with recurring daily items, carry-forward of incomplete tasks, and a simple velocity metric to spot overload before it becomes a crisis.The entire stack runs on Node.js, saves files as Markdown and JSON (no database required), plays nicely with Google Drive or OneDrive for backup, and optionally connects to GitHub or GitLab for full version history.Apps interoperate through lightweight linking and import/export — cards from Groundwork flow into Atlas, tasks from CourseFlow export into Cadence, and every Playbook page carries a permanent link that works anywhere in the stack.Find out more and download your free personal copy of Cadence at whatsyourbaseline.com/bpm-os—and check the episode show notes for a PDF overview of all six apps.Reach out by emailing ⁠hello@whatsyourbaseline.com⁠ or subscribe to our newsletter and articles on Substack at whatsyourbaseline.substack.com.

Todos los enlaces a los recursos los encontrarás aquí: https://open.substack.com/pub/webreactiva/p/multiplicate-con-la-ia-contado-porEn este episodio con Robert Menetray aprenderás a:

Christian Thordal: Structure Creates Freedom, How an Agile Coach Measures Success by Becoming Less Needed 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 less I shine and the more the team shines, the better I perform." - Christian Thordal   Christian shares how his definition of success has fundamentally shifted over the years. Early in his career, the question was "How can I shine?" Today, it is the opposite — success means becoming invisible. For Christian, a high-performing Scrum Master builds teams that no longer depend on them, much like raising a child to become a functional adult by eighteen. They can always call dad for coaching or to borrow money, but they can stand on their own. He illustrates this with a team he moved from what he calls "cowboy loose Kanban" to an adapted Scrum framework. The structure gave the team freedom: he can now miss dailies and planning sessions, and the team still produces a solid plan, sprint backlog, and sprint goal. He drops by to give pointers and encourage good behaviors. Christian also highlights the importance of the Scrum Master and Product Owner partnership — "the mom and dad of the team" — and how building predictability and flow matters more than heroics. A key tactical insight: he created a one-pager roadmap for his domain leader showing issues, plans, milestones, and metrics. This simple artifact gave leadership the comfort that things were under control, buying Christian the autonomy to do his best work. This proved critical when his team was decimated by departures in late 2025 — he hired new people, stabilized the group, and got them delivering again.   Self-reflection Question: What would it look like if your team could run a full sprint cycle without you present — and what is stopping that from happening today? Featured Retrospective Format for the Week: The Four-Box Retrospective Christian shares a retrospective format he calls the Four-Box Retrospective — a structured, pragmatic approach that resonates especially well with engineer-minded teams. The session begins with a team check-in to get the vibe in the room. Next, the team reviews last week's agreements: who was accountable, and are those items still alive or handled? Anything still alive moves forward automatically, ensuring nothing falls through the cracks. Then comes the core mechanic: topic creation divided into four boxes — Tech (tools and tech stacks), Team (issues within the team), Outside (external dependencies and blockers), and Parking Lot (everything else). Presenters explain their topics briefly to give context, and the group uses dot voting to surface the most pressing issues. Discussion follows, with clear accountability assignments and action items written down. The pre-grouping into four boxes saves significant time by giving topics a natural home before discussion begins. Named owners for every action item create real progress between retrospectives. Christian values this format because it is grounded in actual operational problems — people can see the direct application of every conversation, which keeps engagement high and outcomes tangible.   [The Scrum Master Toolbox Podcast Recommends]

Learn more and apply for the November 2026 cohort of my Japan Leadership Experience: https://kbjanderson.com/japantrip/Lean has always been about people. We just kept reaching for the tools, without understanding the human purpose behind them.In part two of my three-part conversation with John Shook, we go behind the scenes of Toyota's culture and leadership — sharing stories of the system-building leaders who actually made it what it is, and exploring what it really means to lead people-centered change.John shares behind-the-scenes reflections from his time inside Toyota that you might not have heard before. Drawing on his direct experience in the company and our shared experiences living and working in Japan and globally, we explore a critical feature that is often missed: lean has always been a socio-technical system. The tools only work when we understand the deeper human purpose behind them.In this episode, we talk about the people who actually built Toyota's culture, what John learned from his two very different bosses — including Isao Yoshino, the subject of my book “Learning to Lead, Leading to Learn” — and what happens when we lose sight of the human purpose inside the tools we practice every day.In the previous episode, John offered a powerful reframe on lean's impact — and what question we should really be asking as change leaders. If you haven't listened to episode 74 yet, hit pause and start there first — then come back to this one to pick up where we left off.You'll Learn:Inside stories of how Toyota's culture was built and the system builders behind itWhat John learned from his very different bosses inside Toyota and how their styles shaped his own leadershipWhether you are a lean “mechanic” or “social worker” and what your answer reveals about your leadershipWhy every lean tool is already socio-technical — kanban, standardized work, A3, andon — and what we lost when we introduced them as primarily technicalThe concept of motainai — waste as a moral failure, not just a technical one — and why this matters for how you leadABOUT MY GUEST:John Shook spent eleven years with Toyota in Japan and the U.S., where he helped transfer the Toyota Production System globally. He later served as President of the Lean Enterprise Institute and Chairman of the Lean Global Network.John is the co-author of the award-winning books Learning to See and Managing to Learn, and wrote the foreword to my book Learning to Lead, Leading to Learn. As an industrial anthropologist, he brings a perspective that connects culture, systems, and practice to bridge deep thinking with real-world application.IMPORTANT LINKS:Full episode show notes: ChainOfLearning.com/75Connect with John Shook: lean.org/about-lei/senior-advisors-staff/john-shook/ Follow me on LinkedIn: linkedin.com/in/kbjanderson Subscribe to my newsletter: kbjanderson.com/newsletterCheck out my website for resources and working together: KBJAnderson.comJoin us on the Japan Leadership Experience: KBJAnderson.com/japantrip Purchase a copy of, “Learning to Lead, Leading to Learn,”: kbjanderson.com/learning-to-lead TIMESTAMPS FOR THIS EPISODE:03:04 Why changing culture is harder than copying systems04:05 John's question that still drives him: Why Toyota?05:10 How John found his way into Toyota and NUMMI06:15 Why Toyota endured while other Japanese companies faded07:10 Short-term leaders vs. long-term system builders08:15 The crisis that shaped Toyota's future direction10:05 John's experience learning from very different Toyota leaders11:15 Why conflicting feedback accelerated John's learning12:10 Bringing your own thinking into the A3 process13:15 Different cultures inside Toyota and how they shaped leadership14:10 Mr. Cho's powerful way of teaching through stories16:10 Katie's lion story and breaking the telling habit17:15 Adapting your leadership approach to the situation19:15 Reading both the technical and social sides of change20:20 TPS as a way to expose weaknesses and accelerate growth21:45 Are you a lean mechanic or a lean social worker?22:50 Identifying your leadership bias and growth edge24:05 Why process improvement and OD teams should work together27:10 Scientific thinking, humanism, and ethics in Toyota leadership28:55 Eliminating waste as more than a technical exercise30:05 Mottainai and the deeper meaning of waste32:25 Why lean tools were always socio-technical33:40 Kanban, standardized work, and the human side of lean35:10 The A3 as more than a problem-solving tool37:35 The most common failure mode in lean transformations38:30 When lean becomes the goal instead of the means39:30 Why lean isn't just for executives40:35 Improving work at every level of the organization41:40 Why empowerment without support falls apart42:20 The Andon system as a model for real support43:45 Where do you need to grow: technical or human? Learn more and apply for the November 2026 cohort of my Japan Leadership Experience: https://kbjanderson.com/japantrip/

Kanban-Methode im Krisenstab.

Christian Thordal: How "Fake Kanban" Fooled the Metrics, And What This Agile Coach Did to Fix It 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 was like birds in a nest waiting to get fed — completely dependent on the PO for every piece of work." - Christian Thordal   Christian tells us about a team that always appeared busy but was hiding serious dysfunction behind a single healthy metric. When he rated the system across his domain, he found the team scored low in process maturity, effectiveness, and learning — yet their cycle time looked good. The team claimed to practice Kanban, but in reality it meant "we can do whatever we want." Daily standups had become social check-ins. The backlog held over 100 items to do and 50+ in progress, most of them just headlines with no descriptions. Real work assignments happened through 30-minute Slack huddles between the PO and individual developers — pure push, no prioritization. Despite having OKRs, the team could only plan a week ahead. Christian's fix was radical: he restarted the backlog entirely, cutting 150 items down to roughly 30, established WIP limits to create a pull-based system, and brought the team into the process as active participants rather than passive recipients.   In this segment, we refer to Kanban and OKRs.   Self-reflection Question: When was the last time you looked beyond a single "green" metric to understand what was really happening in your team's workflow? Featured Book of the Week: Turn the Ship Around by David Marquet Christian recommends Turn the Ship Around by David Marquet, a former U.S. Navy submarine commander who transformed his crew's performance by replacing permission-seeking with intent-based leadership. Instead of waiting for orders, crew members were expected to say "I intend to..." — transferring ownership and making people accountable for their decisions. Christian says this deeply resonated with his own military background in the Danish Army, where leadership operated on similar principles. The book's core message — stop creating dependency and start building leaders at every level — connects directly to the team story in this episode, where passive dependency on the PO was the root of the dysfunction. You can also listen to previous episodes with David Marquet and explore more on intent-based leadership.   [The Scrum Master Toolbox Podcast Recommends]

In this episode, Jason dives into a powerful logistics concept that can completely change how construction teams organize work in the field. He explains the "five-and-five" principle: can workers access everything they need within five steps and five seconds? along with the idea that all visual information and standard work should be understandable from ten feet away. Drawing from lean manufacturing, military logistics, and real-world construction examples, Jason explains why logistics is one of the most overlooked but critical systems in construction. From strike zones and kitted carts to de-trashing stations, Kanban replenishment, and visual controls, the goal is to eliminate wasted motion, reduce confusion, and allow crews to focus entirely on installation instead of scrambling for materials or information. What you'll learn in this episode: What the "five-and-five" principle means in construction logistics. Why all tools and materials should be accessible within five steps and five seconds. How visual systems should be readable from ten feet away. Why logistics not firefighting is the key to production flow. How strike zones, carts, shadow boards, and Kanban systems improve efficiency. Why the field is for installing work not figuring things out. Are your crews spending their time installing or searching, walking, and scrambling for what they need? 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

Blakely Graham co-founded TaskRay, a project management and customer onboarding platform built inside the Salesforce ecosystem. After years working with Salesforce implementations and operations teams, she and co-founder Eric Wu saw a major gap between closing deals and successfully onboarding customers. They bootstrapped the company from a simple Kanban-style workflow app into a growing SaaS business serving increasingly complex enterprise implementations. TaskRay started with self-serve AppExchange purchases and evolved into enterprise software with six-figure contracts, serving companies with sophisticated onboarding and delivery needs. The company stayed profitable from the beginning, grew to roughly 40 employees, and eventually reached nearly $10M ARR. A major turning point came when the team repositioned around "customer onboarding" instead of generic project management, dramatically improving focus, retention, and enterprise growth. Blakely also shares the difficult founder realities rarely discussed openly: co-founder conflict, burnout, loneliness, identity shifts, and the emotional weight of leading a growing company for more than a decade. After stepping away following the 2021 sale of TaskRay to a search fund-backed buyer, she focused on recovery, advisory work, and co-hosting the Not All Business podcast to help founders and leaders feel less isolated during difficult growth stages. Key Takeaways Focus to Grow Faster — TaskRay discovered its strongest positioning by focusing narrowly on post-sale onboarding instead of generic project management. Bootstrap Discipline — The company stayed profitable from day one by growing carefully, shipping quickly, and avoiding unnecessary complexity early. Founder Burnout — Burnout showed up as physical exhaustion, emotional numbness, and losing the energy to inspire teams or create new ideas. Co-Founder Conflict — Long-term founder relationships can fracture under pressure, but respect and self-awareness can rebuild trust over time. Invest In Yourself — Peer groups, coaching, therapy, and personal health practices are essential leadership tools, not optional luxuries. Quote from Blakely Graham, Co-founder of TaskRay "This is probably the most important thing I learned as a CEO, and, I swear founders can't hear it. They just can't hear it. "You have to invest in yourself. The word "self care" drives me crazy because that's what people told me for 10 years. Self care. What are you doing for self care? I'm like, I don't know. Leave me alone. I don't have time, any down time.  "Well, of course sitting on the other side of burning out and selling my company, founders just have to invest in themselves in the journey. It can be a peer group, it can be a coach. can be therapy. Heck for me, it's nature walks and going to the gym. Just do it because people don't want you to burn out. They want your leadership, so you have to invest in yourself and don't feel guilty about it. There, I said it." Links Blakely Graham on LinkedIn TaskRay on LinkedIn TaskRay website Plexus Capital website Podcast Sponsor – LaunchBay LaunchBay helps B2B software companies automate client onboarding and implementation so customers activate faster and everyone stays aligned. If your onboarding includes data collection, setup steps, approvals, training, or any level of customization, LaunchBay replaces the messy mix of emails, spreadsheets, and meetings with a clear, all-in-one onboarding system. Teams use LaunchBay to onboard clients faster, stay on top of follow-ups automatically, and deliver a smoother experience, without hiring more people or adding more tools. Visit launchbay.com/practical and get 25% off your first 3 months on any LaunchBay plan. The Practical Founders Podcast Tune into the Practical Founders Podcast for weekly in-depth interviews with founders who have built valuable software companies without big funding. Subscribe to the Practical Founders Podcast using your favorite podcast app or view on our YouTube channel. Get the weekly Practical Founders newsletter and podcast updates at practicalfounders.com. Practical Founders CEO Peer Groups Be part of a committed and confidential group of practical founders creating valuable software companies without big VC funding.  A Practical Founders Peer Group is a committed and confidential group of founders/CEOs who want to help you succeed on your terms. Each Practical Founders Peer Group is personally curated and moderated by Greg Head.

These episodes of #thePOZcast, live from Transform 2026 in Las Vegas, are proudly brought to you by our friends at PIN. AI recruiting tools that automate candidate sourcing, screening, and scheduling across 850M+ profiles. Built for recruiters, agencies, and hiring teams. Learn more and check out a demo:  https://www.pin.com/book-a-demo?via=adam-posner Thanks for listening, and please follow us on Insta @NHPTalent and www.youtube.com/thePOZcast For all episodes, please check out www.thePOZcast.com TAKEAWAYS:  1. Same Tools, Same Results — You Have to Rebuild the Engine The insight at the heart of Pin: giving AI the same Boolean search infrastructure that human recruiters use produces the same mediocre results, just faster. The only way to get genuinely better outcomes is to rebuild the search engine itself so that AI can operate on a fundamentally different foundation. That's what Pin did — and why the results look different. 2. The Best Candidate Should Be First, Not on Page Seven The clearest signal that a recruiting search tool is working: the most qualified candidate for a role appears at the top of results, not buried deep in a list that requires manual excavation. For recruiters who've spent years digging through pages of search results, seeing the right person in slot one is a genuinely disorienting experience — in the best way. 3. Natural Language Filtering Closes the Gap Between Search and Judgment Standard filtering tools handle objective criteria — location, tenure, title. Pin's natural language feature handles the subjective judgment calls that used to require hours of resume scanning: the specific details that determine whether a candidate is actually worth a call. Resolving those questions in two questions or fewer is a meaningful time return for high-volume recruiters. 4. Pattern Recognition Learns Even Without Feedback — But Feedback Makes It Faster Pin's algorithm doesn't require explicit feedback to improve — it reads behavioral patterns in what recruiters accept and reject and adjusts accordingly. But providing reasons for rejections accelerates the learning dramatically. The system is watching, learning, and tuning, whether or not you tell it why. 5. The Curveball Candidate Is a Feature, Not a Bug Periodically surfacing a candidate who sits just outside the current search parameters isn't an error — it's deliberate calibration. When a recruiter declines that candidate, Pin learns where the line actually lies, resulting in increasingly precise results over time. The tool is always running a low-stakes experiment to get better. 6. A Visual Pipeline Changes How You Manage a Search Pin's upcoming Kanban board — drag-and-drop stages from interested through offer made — addresses one of the most persistent frustrations in recruiting: knowing at a glance where every candidate stands without digging through notes or spreadsheets. Pipeline visibility is a workflow problem as much as a sourcing one. 7. MCP + Claude Desktop = Autonomous Sourcing The MCP Server integration is the most forward-looking announcement in this episode: the ability for Claude Desktop to run Pin autonomously, without manual recruiter input, using Claude's broad knowledge base to execute searches and surface candidates. For business development and high-volume sourcing, this is autopilot for the top of the funnel. 8. The Second Company Is Easier Because the Team Already Knows How to Build Together Steven's team story is a blueprint for founder-led companies: seven people from his first venture joined him at Pin, bringing a shared language, shared trust, and a shared understanding of what works and what doesn't. The result is what Steven calls "life on easy mode" — not because the work is easier, but because the team already knows how to do it together. 9. Always Give Feedback to Your AI Tools Every rejection is a data point. Every accept is a signal. The recruiters getting the best results from AI-powered search tools are the ones who treat the interface as a two-way conversation — providing context, reasons, and reactions that train the system toward increasingly precise output. Passive use gets passive results.   CHAPTERS: 00:00 – Day 9: The Return of Steven Lu Adam, on day 9 of 10 at Transform, welcomes back Steven Lu — a returning guest and the founder of Pin, the recruiting AI tool Adam uses every day. 02:00 – Why Giving AI Boolean Tools Gets You Boolean Results The core problem Pin was built to solve: if you give AI the same search tools as a human recruiter, you get the same results. Pin rebuilt the search engine itself so AI could actually deliver better outcomes. 04:30 – The Aha Moment: Best Candidate, Slot Number One What clients experience when they switch to Pin: the best candidate for the role appears first — not buried on page seven. 06:30 – Natural Language Questions That Answer the Hard Stuff How Pin's natural language feature goes beyond standard filters — answering the nuanced, make-or-break questions about a candidate in two questions or less. 09:00 – Pattern Recognition: Learning From Every Rejection Pin's behind-the-scenes intelligence: even without explicit feedback, the platform picks up on recruiter behavior patterns and adjusts results automatically. 12:00 – The Curveball Candidates Why Pin intentionally surfaces occasional outlier candidates — to test parameters, refine the algorithm, and deliver increasingly precise results over time. 14:30 – Alpha Drop: The Kanban Pipeline Board Feature 1 in development: a visual Kanban board for tracking candidates through the hiring pipeline with full drag-and-drop functionality. 17:00 – Alpha Drop: MCP Server + Claude Desktop Integration The bigger announcement: Pin is building an MCP Server integration that allows Claude Desktop to run Pin autonomously — putting AI-powered sourcing on autopilot. 20:00 – The Team Behind Pin: Seven People Who Followed Him Seven employees from Steven's first company joined him for Pin — and that shared experience is what makes the second company feel like "life on easy mode." 22:30 – Real Results: Fees Collected, Offers Made The feedback that hits hardest: fee emails arriving up to 20 a day, and Adam's live proof point — three Pin-sourced candidates getting offers by end of the week. 24:30 – Where to Find Pin A direct listener recommendation: try pin.com, mention Adam and Steven, and see what a rebuilt search engine actually delivers.  

Episode Summary In Part Two of this Brand Retro "Lost Episode," Mike Brevik continues his conversation with Chris Bolton of Murmur Creative, diving deeper into the evolving relationship between branding, technology, and client expectations. The discussion tackles the growing hype around artificial intelligence and how it is reshaping perceptions of creativity, marketing value, and agency work. Mike and Chris break down why AI should be viewed as a tool rather than a replacement for human insight and why context, experience, and problem-solving still define great branding. They also explore how agencies can build stronger client relationships through transparency, retainers, and deeper collaboration. Ultimately, the conversation reinforces a core truth: while technology changes, the power of branding remains one of the most important drivers of business growth. Links & Resources murmurcreative.com Home - BRAND RETRO PODCAST Keywords branding strategy marketing agency AI in marketing client relationships creative agencies brand perception retainers transparency business growth digital marketing SEO branding value marketing misconceptions agency model  Highlights 00:00–01:00 – The challenge of defining "marketing" and its evolving meaning 01:00–02:00 – Why agencies start with a trust deficit (1 good experience vs 10 bad ones) 02:00–03:00 – The Fiverr effect and commoditization of creative work 03:00–04:00 – Transparency as a tool to communicate value to clients 04:00–05:00 – The limits of hourly billing and the importance of perceived value 05:00–06:00 – "Home run hitter" analogy: why top-tier creative commands higher rates 06:00–07:00 – The subjectivity problem in design and branding 07:00–08:00 – 2024 market uncertainty and shifting client expectations 08:00–09:00 – Branding as the core driver of exponential business growth 09:00–10:00 – Branding vs tactics: why ads alone won't scale a business 10:00–11:00 – Branding is not surface-level—it's relationships and perception 11:00–12:00 – How consumers are unconsciously influenced by branding 12:00–13:00 – The shift from project-based work to long-term client relationships 13:00–14:30 – Retainers, transparency, and structured workflows (Kanban approach) 14:30–16:00 – Agencies as extensions of internal teams (augmentation model)

Something flipped this year. Chatbots were a toy. Useful sometimes, but a toy. Agents are not. Agents take actions, hold credentials, write code, move Kanban cards, and run on cron schedules. The window between "this is interesting" and "this is existential" has closed faster than cloud, faster than Kubernetes, faster than any prior shift. Viktor's read is blunt. One person can now build a bigger business than most mid-size companies have ever managed. That is not hyperbole -- that is a description of what is already happening with a handful of solo-built projects shipping in weeks what used to take a hundred-person org years. The thesis: panic. Not because the sky is falling, but because larger companies cannot turn around overnight, and the gap between the people who get this and the people who are still scheduling meetings about scheduling meetings is widening every week. The conversation walks through what each big provider is actually doing. AWS is not pretending to compete on models -- they want the inference revenue. Microsoft is lost in Copilot button-stuffing. Google is quietly winning on three layers at once: TPUs, models, and inference infrastructure. Anthropic is on the path to becoming the next defining IPO, while OpenAI looks like a place to take money out of, not put more in. The Linux Foundation's new Agentic AI foundation got Anthropic's MCP, Block's Goose, and OpenAI's AGENTS.md spec. Viktor's reaction: those are heavy hitters donating not very much. Then it gets practical. Vendor-provided agents are like hiring a genius engineer who knows nothing about your company. Public skills are mostly nonsense -- if it is in public training data, the model already knows it; what is missing is everything specific to you, which is exactly what no public skill can provide. OWASP just published an Agentic AI Top 10 and most of it is least-privilege rebranded for agents. The cost story is also not what the marketing says: a 00 monthly subscription will not last a day for anyone working full-time with agents. There is a true story in here about a leaked token that turned a 00 monthly spend into 5,000 in two days. The hardest part of the episode is the part nobody likes hearing. If your output stays the same in 2026, you are in trouble. If you multiply your output, you are fine. Companies have always wanted to do more than they could afford to do. Now they can. The middle is where careers used to live. The middle is where the cuts are going.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Is the State of Agile Report a clear-eyed snapshot of the industry - or a sales brochure? In this episode of Arguing Agile, hosts Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel are joined by returning guest Ed Martin to dissect the 18th State of Agile Report from Digital.ai. Applying the economic theory of the 'Market for Lemons,' where asymmetric information leads to market failure, we discuss the survey results and 'pontificate' on the state of the agile industry.Join us by watching or listening as we discuss:Why 41% of organizations increased agile investment while only 13% claim it is deeply embeddedIf the Rise of Hybrid and Homegrown Agile is an indicator of a return to 'cowboy coding'Analyzing the report's contradictory finding that 63% of companies struggle with quality while 68% claim high-quality deliveryThe critical issue of leaders demanding ROI from systems they do not understand or actively guideWe don't just discuss the report, but we also brainstorm and share actionable advice for agilists and tech workers on how to navigate a landscape of conflicting data and pressure to prove value.#Agile #ProductManagement #LeadershipThe Market for Lemons by George Akerlof, The 18th State of Agile Report by Digital.ai, Inspired by Marty Cagan, The Wright Brothers vs. Samuel Langley history, J.J. SutherlandLINKSWatch it on YouTube!YouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Watch the YouTube version of this episode HEREMost PI firms obsess over “more leads” and ignore the single number that quietly runs their entire business: average fee per case. In this crossover episode, Chris Dreyer (Personal Injury Mastermind, Rankings.io) sits down with Tyson Mutrux (Mutrux Firm Injury Lawyers, Maximum Lawyer) to unpack how he nearly tripled his average fee by mastering bad faith, redesigning the client journey, and installing a Cares Team that doubles as a 5‑star review engine.Tyson breaks down how he went from roughly 7.4k to about 24k per case without relying on lottery-ticket verdicts, and why most high-volume PI firms leave policy‑plus settlements on the table because they simply don't understand bad faith. You'll hear his simple explanation of bad faith, how he pits the insured against the insurer ethically, and why that unlocks settlements over limits for clients while funding a serious marketing war chest.Then, Tyson flips the conversation from numbers to people. He walks through his “Complete Injury Law” mindset: mapping every stage of the client's journey from the crash scene to case resolution, solving transportation, medical access, and life disruption so injured clients don't lose jobs or miss care. That deep empathy led to building a dedicated Cares Team that shadows cases from start to finish, checks in on real life (kids, ballgames, surgeries), and protects high-value files over months or years of litigation.Finally, Tyson reveals the psychological script his team uses to turn that client experience into an unstoppable Google review engine. Instead of awkwardly begging for firm reviews, they position the review as a “gift” to a specific team member, then remove all friction with direct links and clear prompts. Chris calls it one of the best review strategies he's ever heard, and together they connect the loop: bad faith drives higher fees, operations protect those fees, and reviews convert that excellence into a durable marketing moat.If you're a law firm owner who wants to build a business, not just a job, this episode is a masterclass in aligning litigation strategy, operations, and marketing around one goal: bigger fees and happier clients.Timestamps00:00 – Cold open: why your average fee matters more than more leads02:00 – Tyson's North Star: average fee vs. CAC:LTV06:30 – The 80/20 shift to bad faith (and why most PI lawyers miss it)11:15 – Bad faith in plain English (how to go over policy)15:00 – Spending 8k to make 24k: the math of a PI marketing war chest19:30 – “Complete Injury Law”: fixing the whole problem, not just the file24:30 – Inside the Cares Team: empathy as an operational system28:30 – Mapping the client journey with a giant Kanban board32:00 – The review “gift” script that Chris calls ‘the best advice I've heard'36:00 – Closing the loop: from bad faith to marketing moatResources:Join the Guild MembershipSubscribe to the Maximum Lawyer Youtube ChannelFollow us on InstagramJoin the Facebook GroupFollow the Facebook PageFollow us on LinkedIn Resources:Join the Guild MembershipSubscribe to the Maximum Lawyer Youtube ChannelFollow us on InstagramJoin the Facebook GroupFollow the Facebook PageFollow us on LinkedIn

In episode 26, guest host Gregory Paolini, founder of Gregory Paolini Design and board member of the Cabinet Makers Association (CMA), sits down with Gary Balcom, president of Atlanta Cabinet Shop Inc. in Buford, Georgia, to explore his journey from hobbyist to industry leader. Balcom reflects on learning woodworking as a teenager in Western New York, inspired by his father and PBS icons like Norm Abram and Roy Underhill, and how an early silhouette business sparked his entrepreneurial mindset. He traces his path from Niagara Falls to a high-end conference table shop in Vermont, and eventually to Georgia, where he now leads a commercial millwork operation focused on panel processing for spaces like medical and dental offices. The conversation dives into the balance between high-tech manufacturing and traditional craftsmanship, with Balcom leveraging CNC-driven equipment at scale while maintaining a personal passion for hand-tool woodworking. He also shares how lean principles and Kanban systems support continuous improvement in a high-volume, data-driven environment, and why hiring for attitude, attention to detail, and aptitude often outweighs prior experience. They also highlight the value of the Cabinet Makers Association as a trusted network for collaboration, learning, and problem-solving within the industry.   PRO Cabinet Maker is produced by Association Briefings.

Most organizations think they have a capacity problem. They usually don't.What they have is a work-in-progress problem. And those two things call for very different solutions.In this episode, Peter Maddison and Dave Sharrock dig into one of the most persistent headaches in organizational management: capacity tracking. Why does the instinct to measure utilization backfire? Why does loading people up to 100% actually slow things down? And what should leaders be asking instead?The conversation covers the real cost of context switching, why that "nearly done" project is probably further away than it looks, and how AI is making all of this more urgent, not easier.Three things to take away from this episode:100% utilization is not a goal. It's a warning sign. The right question isn't "how much capacity do we have?" It's "how much work in progress can we actually sustain?AI accelerates your breaking points.If this conversation resonated, there's more where it came from. Peter Maddison and Dave Sharrock explore these kinds of organizational challenges every week on Definitely Maybe Agile - the podcast that gets into the real complexity of modern ways of working, without the buzzwords.Listen wherever you get your podcasts, or visit definitelymaybeagile.com to catch up on past episodes and reach out with your own questions.

#347: Andrei Kvapil has been around Kubernetes since the early days. Contributor to Cilium, Kubevirt, and a handful of other projects you probably use without realizing it. He is also the maintainer of Cozystack, a CNCF sandbox project, and the CEO of Aenix, the company behind it. The thesis: Kubernetes should be boring. Not exciting, not cutting-edge, not the thing everyone argues about. Boring like the Linux kernel is boring. Something that sits underneath everything and nobody needs to think about. Viktor takes it one step further and says it should be invisible -- developers should never need to know Kubernetes exists, any more than they need to know what kernel their laptop is running. Cozystack is Andrei's answer to a specific problem. ISPs, banks, finops shops, anyone in Europe who cannot or will not put their data in AWS -- they all want to offer managed databases, managed Kubernetes, object storage, the whole stack. Building that from scratch is hard. Running OpenStack requires a dedicated team that does nothing but tune networking. Cozystack bundles the pieces (Kubevirt, CloudNative Postgres, Cilium, etc) into one product with an aggregation API layer on top of Kubernetes itself. Helm becomes the extension language. The platform becomes a product. Then the conversation takes a turn. Andrei is the CEO of a bootstrapped company and he says flatly that without AI the company would not exist. Claude Code is moving Kanban cards. Clients send files generated by their AI agent and Aenix feeds those files to their AI agent to generate the response. Andrei's only wish is for this middle step -- him -- to stop existing. Let the agents talk to each other and call him when something actually matters. There is a hiring question in here too. If the next generation of engineers starts their career with AI on the first commit, do they ever build the mental model that lets them guide the agent when it goes wrong? Andrei thinks you still need deep understanding for anything serious. Viktor agrees. Speed versus quality is still a choice, and juniors who skip the "write it three times until it stops being garbage" phase are going to feel that gap eventually.   Andrei's contact information: LinkedIn: https://www.linkedin.com/in/kvaps/   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Most productivity advice doesn't work for ADHD—but this does. In this episode of Rebel Mama Pod, host Sarah Castañeda sits down with Dani Donovan to break down what actually works when it comes to ADHD productivity. Instead of forcing yourself into rigid systems, Dani shares her toolbox approach—a flexible, realistic way to get things done without burnout, shame, or relying on last-minute panic. If you've struggled with consistency, procrastination, or overwhelm, this episode will give you tools you can actually use.    

In this premier episode of Systems of Imperfection, Olivia Vick shares insights on emotional intelligence, self-discovery, regulation, and practical tools like personal Kanban to enhance personal and professional growth. Discover how neurodiversity, acceptance, and intentional habits can transform your approach to work and life. Takeaways - Self-awareness accelerates understanding of personal systems. - Acceptance reduces suffering and enhances resilience. - Personal Kanban helps visualize and limit work in progress. - Neurodiversity, like ADHD, can be a superpower with the right strategies. Chapters 00:00 Introduction to the Podcast and Its Philosophy 4:47 Understanding Emotional Intelligence and Self-Regulation 7:39 Navigating ADHD: Insights and Coping Mechanisms 10:47The Power of Self-Awareness and Regulation Techniques 13:27 Exploring Personal Kanban as a Tool for Productivity 16:53 Joy in Tasks: Balancing Urgency and Enjoyment 22:40The Importance of Mindset in Time Management 26:01 The Importance of Self-Care and Balance 27:18 Integrating Joy into Daily Routines 29:43 Understanding Energy Regulation and Emotional Awareness 30:48The Role of Self-Awareness in Personal Growth 33:57 Untethering: The Path to Authenticity 40:53 Taking Agency in Life Decisions 45:47 Outro.mp4 Subscribe to Systems of Imperfection https://systemsofimperfection.riverside.com/ Subscribe to Surfing Chaos https://surfingchaosaudionewsletter.riverside.com/ Links to Resources - Daniel Goleman - Emotional Intelligence - https://www.amazon.com/Emotional-Intelligence-Why-It-Matters/dp/055338371X - Jim Benson - Personal Kanban - https://www.amazon.com/Personal-Kanban-Visualize-Work-Manage/dp/1938289694 - Insight Timer App - https://insighttimer.com/ -The Untethered Soul by Michael A. Singer - https://www.amazon.com/Untethered-Soul-Journey-Breakfree-Yourself/dp/1572245379 Contacting Olivia - LinkedIn - https://www.linkedin.com/in/oliviavick/ - Twitter - https://twitter.com/OliviaVick Contacting Stuart  - linktr.ee/stuartliveart

 Contacting Dave  - linktr.ee/mrsungo THE BOOK No One Is Coming to Save You: The Power-Ups you need to surf the chaos
 - Amazon: tinyurl.com/yv7chp54
 - Leanpub: leanpub.com/surfthechaos

Bhavin Shukla: Why Scrum Master Success Means Confronting the Ugly Truth With Data Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Success is not always good vibes, good environment for us as Scrum Masters. For me, it's about confronting the reality, the ugly truth, which takes the team to tougher conversations, more constructive challenges." - Bhavin Shukla   Bhavin shares a pivotal moment in his career that redefined what success means for a Scrum Master. He was working with a fantastic team — great culture, people who believed in quality, knowledge sharing, strong bonds. But sprint goals weren't being met, and stakeholders were constantly chasing the Product Owner and Scrum Master for answers. Bhavin got his hands dirty with the data: lack of clarity on work, context switching, patterns emerging. When he presented the data to the team, he was met with silence — a confronting kind of silence. The team was essentially saying, "We were happy. Why would you do this to us?" Bhavin's response was direct: going for coffees and laughing together isn't the whole job. If he wasn't showing them reality, he couldn't look at himself in the mirror. The team eventually used that data to raise their own voice, pointing out systemic issues with external vendors and organizational constraints. The data gave them a platform to speak truth — not as blame, but as discovery.   Self-reflection Question: What conversations did you avoid this week that could have unlocked progress for your team? Are you bringing data to those conversations, or relying on vibes? Featured Retrospective Format for the Week: Newspaper Headline Retrospective Bhavin shares an unconventional use of the newspaper headline technique — typically used for roadmaps and vision — as a retrospective format. The idea is simple but powerful: ask the team to write the newspaper headline they want to see about themselves. What would the story say when they succeed? By authoring their own headline, the team takes ownership of the narrative — they define what success looks like, what must go right, and what risks could derail them. "Putting them in that newspaper headline, they authored the story. They own the accountability to make it successful," Bhavin explains. He also shares a second technique for Kanban teams under pressure: a rolling two-column whiteboard — "Frustration of the Day" and "Success of the Day" — with no meetings required, just real-time data capture that becomes a continuous retrospective, reviewed every 2-3 weeks.   [The Scrum Master Toolbox Podcast Recommends]

In this episode of the Build America Podcast , host Scott Jennings provides an unfiltered look at Smartsheet. Describing it as "Excel, but not Excel" , Scott explains why this cloud based platform is a "Contractor's Dream" for managing critical project data like submittals, RFIs, and change orders.Drawing from his experience as a heavy civil construction company owner , Scott explores how Smartsheet turns raw data into live dashboards and offers a level of customization that industry specific software often lacks. Whether you are in the office or the field, this episode highlights how to move away from reactive "firefighting" and maintain a professional overview of your project's health.Beyond the Spreadsheet: Learn about versatile data visualizations including Gantt charts, calendars, and Kanban style Card views.Extreme Customization: How the platform stays flexible enough to fit specific internal processes in construction, manufacturing, or even pharmaceuticals.Live Dashboarding: How sheets feed directly into visual dashboards to provide managers with immediate project metrics.Mobile Functionality: Using phone based "Forms" to log site deficiencies and photos that instantly populate the main grid.Cost and Licensing: Scott shares his experience with the price point, reporting a cost of approximately $450 per license per year.Submittal and RFI Logs: Track every stage of a request and identify exactly whose "ball" is in which court.Deficiency Tracking: Log issues line by line, attach photos directly to the row, and set automated alerts for subcontractors.Document Management: Keep project letters, pictures, and change orders organized and easy to find by attaching them to specific data rows.Team Coordination: Use collaborative calendars to manage office vacations and project milestones in real time.Website: https://sjcivil.com/ LinkedIn: www.linkedin.com/in/scott-jennings-p-e-1435103 Email: sj@sjcivil.com Blog: https://sjcivil.com/blog/ Ted Determite Children's Book Series: Available on Amazon.If you found this episode informative, please rate and review the show to help more construction and engineering professionals discover these insights. Subscribe to the Build America Podcast on your favorite platform to stay connected.#Smartsheet #ConstructionManagement #ProjectTracking #WorkflowAutomation #CloudCollaboration #SaaS #BusinessEfficiency #Dashboarding #ConstructionTech #BuildAmerica

Bhavin Shukla: The Hidden Cost of Always Saying Yes — How a Helpful Scrum Team Nearly Self-Destructed Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "It was sort of making me feel as a Scrum Master, like it's a slow self-destruction mode they are in. Good intentions, but it wasn't helping them, and that's something that they were not able to notice." - Bhavin Shukla   Bhavin tells the story of a banking team that looked like every Scrum Master's dream on day one — humming, cracking jokes, in the zone. But underneath the positive energy, the data told a different story. Sprint commitments kept overflowing, tech debt was rising, P1 and P2 production issues were climbing, and decision latency was immense. The root cause? This team of genuinely helpful people couldn't say no. They wanted to help everyone who came to them, and that desire was slowly drowning them. No one was giving them feedback about the consequences — missed sprint goals were met with "that's okay, we'll do it next sprint." Bhavin introduced two simple tools: an anonymous happiness meter on the wall (rate 1-5, leave a note if below 3) and a gratitude wall. The data revealed the truth — the team was burning out, handling weekend incidents with no escalation path. Armed with this data, Bhavin coached the team on negotiation techniques: you don't have to be rude to say no, you can negotiate the yes, you can negotiate the no.   In this segment, we talk about the importance of collecting regular data to surface hidden patterns, and the anti-pattern of teams operating without feedback on the consequences of their decisions.   Self-reflection Question: Is your team's positive energy masking underlying problems? What data would help you discover whether good vibes are hiding unsustainable patterns? Featured Book of the Week: Make Work Visible by Dominica DeGrandis Bhavin recommends Make Work Visible by Dominica DeGrandis because it goes beyond values and principles to put them into practice in a grounded, system-focused way. "One clear message I get from that book is it's not the people who are the problem, it's the system that we need to work on to improve ways of working," Bhavin shares. The book introduces concepts like the five thieves of time, visualizing work, dependencies, and bottlenecks — connecting lean thinking, Kanban principles, and behavioral patterns into a practical guide for any Scrum Master looking to understand the systems their teams operate in.   [The Scrum Master Toolbox Podcast Recommends]

Are you building a practice designed to last, or one that only works as long as you can keep up with the pace? It is easy to focus on immediate demands, chasing efficiency or output, without stepping back to consider whether your systems, your reputation, and your way of working are actually sustainable over time. In this episode, I talk with Jordan Couch, an attorney and innovator at Palace Law, about what it really looks like to take a long view of your legal practice. We explore how tools like Kanban can help make work visible and manageable, but also how credibility, consistency, and service shape the foundation of a practice that endures. This conversation goes beyond workflow and into how you think about your role, your clients, and the kind of practice you are building. Get full show notes, transcript, and more information here: agileattorney.com/113 Take your law practice from overwhelmed to optimized with GreenLine Legal Follow along on LinkedIn: linkedin.com/in/johnegrantConnect with Jordan Couch on LinkedIn: linkedin.com/in/jordanlcouch

Jay and Andrew begin with a deceptively simple question: what actually makes a company “lean”? Starting with a quote from Shigeo Shingo, they challenge the common misconception that lean is just Kanban, and explore the deeper reality that lean is less about specific tools and more about principles, tradeoffs, and context.From there, Andrew shares a deep dive into labor tracking and ERP data, uncovering how much work was happening that never made it into cost calculations, and why “door-to-door” time matters more than overly segmented tracking. Jay pushes back with the tension every shop feels: data is only valuable if it leads to action, and too much friction in systems can break team buy-in entirely.The episode then shifts into Andrew's current challenge: producing tight-tolerance parts that his team can't fully verify in-house. They take a candid look at outsourcing vs. vertical integration, the true cost of CMM capability, and the uncomfortable position of shipping parts you can't independently validate. Jay talks about why he bought a CMM earlier than expected, what he regrets, and how fast feedback loops can change everything.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/422Fabrice Bernhard - Co-Author of “The Lean Tech Manifesto” & Co-Founder & CTO at TheodoSteve Pereira - C o-Author of “Flow Engineering” & Principal Consultant at Visible Flow ConsultingRESOURCESFabricehttps://bsky.app/profile/fab-ber.bsky.socialhttps://x.com/fabricebhttps://github.com/fabricebhttps://www.linkedin.com/in/fabricebernhardStevehttps://x.com/steveelsewherehttps://github.com/stevepereirahttps://www.linkedin.com/in/devopstohttps://stevepereira.caLinkshttps://hbr.org/1986/01/the-new-new-product-development-gameDESCRIPTIONFabrice Bernhard, co-founder of Theodo and co-author of "The Lean Tech Manifesto", shares his journey from agile practitioner to lean thinking advocate. The discussion explores how lean principles can scale agile practices beyond small teams, the misconceptions around both methodologies, and the emergence of tech-enabled networks of teams as a new organizational model.Fabrice emphasizes that both lean and agile are fundamentally about people, not processes, and shares practical lessons from scaling his consultancy to 700 people while maintaining agility through lean principles.RECOMMENDED BOOKSFabrice Bernhard & Benoît Charles-Lavauzelle • The Lean Tech Manifesto • https://amzn.to/3Z4EbU6Steve Pereira & Andrew Davis • Flow Engineering • https://amzn.to/3GY3u44General Stanley McChrystal, Collins, Silverman & Fussell • Team of Teams • https://amzn.to/4bUzhQYMatthew Skelton & Manuel Pais • Team Topologies • https://amzn.to/4a2gh0iBill Frasure, Bruce Eckel, James Ward • Effect Oriented Programming • https://amzn.to/4sO6wLVSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCcBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

What if the smallest things in your life are actually themost powerful?In this episode, Michelle reflects on the launch of her newbook, 50 Questions Coaches Ask to Be a More Impactful Coach, and what it represents. While speaking at the Michigan AEYC conference and celebrating 25 years of involvement, she pauses to consider a deeper truth: big outcomesalmost always begin with small, quiet questions.For Michelle, questions are more powerful than opinions,ideas, or even answers. The quality of your life and leadership is shaped by the quality of the questions you ask yourself and others. What are you asking? What are you looking for? What are you cultivating?She explores how unplanned moments of rest, reflection, andpresence often generate the most transformational insights. Drawing from leadership tools like the Eisenhower Matrix and the Kanban method, she challenges the assumption that constant activity equals productivity. Sometimes the most “unproductive” moments become the birthplace of your greatest impact.Whether you are coaching, leading, parenting, or buildingsomething meaningful, this episode invites you to examine how you treat the small things in your life. Because what looks small today may become everything tomorrow.Michelle@GrowBy1.comGrowBy1.com/CoachingAcademyGrowBy1.com/CEU

Jem's rocking top-tier muffs that isolate a screaming spindle while the guys talk one-click Kanban card glory. They discuss the magic of good- documentation, fighting AI amnesia with markdown, and the logistics of shipping PS2 kits to the States. From bike-ride domain buys to handling trade apathy, it's a heavy look at refining the systems that keep a modern shop running.Watch on YoutubeDISCUSSED:✍️ Comment or Suggest a TopicCommunication in the trades, what the actual fuck? ꘎Are you driving Cursor remotely? ꘎Dylan got good muff recommendation ꘎Gemini Lead Interview Youtube @Justin Brouillette HA Dashboard for Bambuinput.buttonAirShop upatesNew Docs site

Libsyn Description: In this episode, Jason tackles a modern construction epidemic: email overload. For the sender, it feels productive. You fire it off, get a dopamine hit, and move on. But for the receiver especially project managers and project engineers it becomes an endless queue of stress, batching, and overwhelm. Jason explains why email as a primary internal communication tool slows projects down, increases stress, and hides capacity issues. He challenges leaders to rethink how they delegate and to use better systems like Scrum, Kanban boards, and task management platforms to create flow instead of chaos. What you'll learn in this episode: Why email multiplies communication time by 4x. How batching and queueing create hidden work-in-progress. Why email culture overwhelms PMs and PEs. The leadership responsibility behind delegation overloa. Better alternatives for managing internal work and communication. If your team is drowning in inboxes… Is it because of workload or because of how you're assigning it? 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

Read the blog postTL;DR: Toyota's real competitive advantage is not its tools -- it is mutual trust and mutual respect. Leaders are responsible for cultivating both. When trust is present, employees speak up, problems surface early, and continuous improvement accelerates. Without it, Lean becomes mechanical and unsustainable.When executives discuss Toyota, the conversation often centers on tools.Kanban. Andon. Standardized work. A3 thinking.Those matter. But Toyota's sustained performance does not come from tools alone. It comes from the leadership philosophy that makes those tools work.At the center of that philosophy is mutual trust and mutual respect.Not as cultural decoration.As operational necessity.Toyota is explicit: improvement depends on people surfacing problems quickly. That only happens when trust flows in both directions.Toyota's own guiding principles website says they:"Foster a corporate culture that enhances both individual creativity and the value of teamwork, while honoring mutual trust and respect between labor and management."Leaders must trust employees to act responsibly.Employees must trust leaders to respond constructively.Without that reciprocity, performance deteriorates.

Louis Knight-Webb is the co-founder of Vibe Kanban, an open-source tool for orchestrating AI coding agents. After years of building for enterprise legacy code, Louis pivoted and saw his new project explode to over 20,000 GitHub stars in just a few months. We talk about the "startup university" of the last five years, why he walked away from 6-figure enterprise deals to find true founder-market fit, and why he thinks most people are wrong about AI-generated pull requests.This episode is brought to you by WorkOS. If you're thinking about selling to enterprise customers, WorkOS can help you add enterprise features like Single Sign On and audit logs.Links:   •  Vibe Kanban   •  Louis' Linkedin

Prabhleen Kaur: The Art of Coaching Product Owners on What vs. How Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Master of Stakeholder Relationships and the Power of No "The best PO is the person who has the superpower of saying no, and they can deal with the stakeholders with the same prowess." - Prabhleen Kaur   Prabhleen describes working with a Product Owner who managed multiple stakeholders—not just a handful, but a significant number with competing priorities. What made him exceptional was his deep understanding of each stakeholder's pulse and motivations. He knew when to push back and how to frame the "no" in a way that stakeholders could accept. This wasn't random resistance—it came from thorough preparation manifested in clear roadmaps that made most incoming work predictable for the team.  His user stories stood out for their richness in context: beyond the business requirements, they included information about who would be impacted, which proved invaluable for a team dealing with multiple interconnected systems.  He leveraged JIRA's priority field effectively, ensuring the moment anyone opened the board, they could immediately understand what mattered most. Prabhleen emphasizes that this PO understood his role as the "what" while respecting the team as the "how." By maintaining strong stakeholder relationships built on mutual understanding, he created space for the team to prepare, plan, and deliver without constant firefighting.   Self-reflection Question: Does your Product Owner have the preparation and stakeholder relationships needed to confidently say "no" when priorities compete, or does every request become an emergency? The Bad Product Owner: Technical Experts Who Manage the Sprint Backlog "The PO is the what, and the team is the how. When POs start directing the team about how to do things, the sprint goal gets compromised." - Prabhleen Kaur   Prabhleen addresses a common anti-pattern she's observed repeatedly: Product Owners with technical backgrounds who cross the line from "what" into "how." When POs come from developer or technical roles, their expertise can become a liability if they start prescribing solutions rather than defining problems.  They direct the team on implementation approaches, suggest specific technical solutions in user stories, and effectively manage the sprint backlog instead of focusing on the product backlog. The consequences are predictable: stories keep getting added or removed mid-sprint, the sprint goal becomes meaningless, and the team ends up delivering nothing because focus is constantly shifting.  Prabhleen's solution starts in backlog refinement, where she ensures conversations about technical approaches happen openly with the whole team during estimation. When a PO suggests a specific implementation, she facilitates discussion about alternatives, allowing the team to voice their perspective.  The key insight: everyone comes from a good place—the PO suggests solutions because they believe they're helping. The Scrum Master's role is to create space for the team to own the "how" while helping the PO see the value in stepping back.   Self-reflection Question: When your Product Owner has technical expertise, how do you help them contribute their knowledge without directing the team's implementation choices?   [The Scrum Master Toolbox Podcast Recommends]

Prabhleen Kaur: When Team Members Raise Concerns with Clarity, Not Anger 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 idea of success as a Scrum Master is when you look around, you see motivated people, and when something goes wrong, they come to you not in anger, but with concern." - Prabhleen Kaur   Prabhleen offers a refreshing perspective on measuring success as a Scrum Master that goes beyond velocity charts and feature counts. She shares a pivotal moment when her team was in production, delivering relentlessly with barely any time to breathe. A team member approached her—not with frustration or blame—but with thoughtful concern: "This is not going to work out." He sat down with Prabhleen and the Product Owner, explaining that as the middle layer in an API creation team, delays from upstream were creating a cascading problem.  What struck Prabhleen wasn't just the identification of the issue, but how he approached it: with options to discuss, not demands to make. This moment crystallized her definition of success. When team members feel safe enough to voice concerns early, when they come with ideas rather than accusations, when they see themselves as part of the solution rather than victims of circumstances—that's when a Scrum Master has truly succeeded.  Prabhleen reminds us that while stakeholders may focus on features delivered, Scrum Masters should watch how well the team responds to change. That adaptability, rooted in psychological safety and mutual trust, is the true measure of a team's maturity.   Self-reflection Question: When problems emerge in your team, do people approach you with defensive anger or constructive concern? What does that tell you about the psychological safety you've helped create? Featured Retrospective Format for the Week: Keep-Stop-Happy-Gratitude Prabhleen shares her favorite retrospective format, born from necessity when she joined an established team with dismal participation in their standard three-column retrospectives. She transformed it into a four-column approach: (1) What should we keep doing, (2) What should we stop doing, (3) One thing that will make you happy, and (4) Gratitude for the team. The third column—asking what would make team members happy—opened unexpected doors. Suggestions ranged from team outings to skipping Friday stand-ups, giving Prabhleen real-time insights into team needs without waiting for formal working agreement sessions. The gratitude column proved even more powerful. "Appreciation brings a space where trust is automatically built. When every 15 days you're sitting with the team making a point to say thank you to each other for all the work you've done, everybody feels mutually respected," Prabhleen explains. This ties directly to the trust-building discussed in Tuesday's episode—using retrospectives not just to improve processes, but to strengthen the human connections that make teams resilient.   [The Scrum Master Toolbox Podcast Recommends]

You can develop a working Mac app in minutes.

Prabhleen Kaur: How AI Is Changing the Way Agile Teams Deliver Value 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.   "AI's output is not the final output—it's always the two eyes we have that will get us the best results." - Prabhleen Kaur   Prabhleen brings a timely challenge to the coaching conversation: the impact of AI on teams and how Scrum Masters should navigate this transformation. She frames it as both a challenge and an opportunity—teams are now capable of delivering faster than consumers can absorb, fundamentally changing expectations and dynamics.  Prabhleen has observed her teams evolve from uncertainty about AI to confidently leveraging it for practical benefits. Developers use AI for writing and understanding code, particularly helpful for onboarding new team members who need to comprehend existing codebases quickly. QA professionals find AI invaluable for generating test cases based on story and epic context already captured in JIRA.  The next frontier? Agentic AI, where AI systems communicate with each other to produce better outputs. But Prabhleen offers an important caution: AI is learning from many conversations, not all of which are reliable. The human element—critical thinking and verification—remains essential.  For Scrum Masters, this means facilitating conversations about how teams want to experiment with AI, exploring edge cases in testing that AI can help identify, and helping teams navigate the evolving landscape of possibilities while maintaining quality and judgment.   Self-reflection Question: How are you helping your team explore AI as a tool for improvement while ensuring they maintain critical thinking about the outputs AI produces?   [The Scrum Master Toolbox Podcast Recommends]

Prabhleen Kaur: When Lack of Trust Turns Teams Into Isolated Individuals 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.   "Teams self-destruct despite best efforts when they lack trust." - Prabhleen Kaur   Prabhleen observed a troubling pattern while shadowing a team: stand-ups had become a register activity where people reported individual status without any connection to the sprint goal. There was no "we" in the conversation—only "I."  The team had experienced a missed deadline due to a PR conflict that wasn't merged in time, but instead of addressing it openly, everyone focused on fixing the immediate problem while avoiding the deeper conversation. The discomfort was never voiced, and resentment accumulated silently.  Prabhleen explains that team destruction is never about one action—it's about the accumulation of unspoken concerns that eventually explode at the worst possible moment. To rebuild trust, she recommends starting with peer reviews that encourage natural collaboration and conversation.  Scrum Masters must be vocal about challenges in front of the entire team, modeling the openness they want to see. For teams that have completely withdrawn, anonymous feedback and scheduled one-on-ones can create safe spaces for honest communication. The key insight? Trust is rebuilt when people realize they will be heard and understood, not judged.   In this segment, we talk about how trust is the foundation of effective teams and how its absence leads to working in silos.   Self-reflection Question: When your team experiences a failure or missed deadline, do you create space for open conversation about what happened, or does everyone quietly move on while resentment builds? Featured Book of the Week: Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland Prabhleen recommends Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland as a foundational read for understanding the spirit behind the framework. "When I actually read the book and understood the nuances of rugby and how the team should be, everything started making sense. I grew beyond the Scrum guide, beyond following rules—it's about how the team operates around you as a collective," she explains. Prabhleen also highly recommends Turn the Ship Around by David Marquet, summarizing its core message as "leaders lead leaders." Both books shaped her understanding that frameworks exist to enable collaboration, not to create compliance. Check out the David Marquet episodes on the Scrum Master Toolbox Podcast for more insights on intent-based leadership.   [The Scrum Master Toolbox Podcast Recommends]

Prabhleen Kaur: Letting Teams Own Their Process Through Working Agreements Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "It's about coaching the team, not teaching them." - Prabhleen Kaur   Prabhleen shares a powerful lesson about the dangers of being too directive with a forming team. When she joined a new team, her enthusiasm and experience led her to immediately introduce best practices, believing she was setting the team up for success. Instead, the team felt burdened by rules they didn't understand the purpose of. The process became about following instructions rather than solving problems together.  It wasn't until her one-on-one conversations with team members that Prabhleen realized the disconnect. She discovered that the team viewed the practices as mandates rather than tools for their benefit. The turning point came when she brought this observation to the retrospective, and together they unlearned what had been imposed.  Now, when Prabhleen joins a new team, she takes a different approach. She first seeks to understand how the team has been functioning, then presents situations as problems to be solved collectively. By asking "How do you want to take this up?" instead of prescribing solutions, she invites team ownership. This shift from teaching to coaching means the team creates their own working agreements, their own definitions of ready and done, and their own communication norms. When people voice solutions themselves, they follow through because they own the outcome.   In this episode, we refer to working agreements and their importance in team formation.   Self-reflection Question: When you join a new team, do you first seek to understand their current ways of working, or do you immediately start suggesting improvements based on your past experience?   [The Scrum Master Toolbox Podcast Recommends]

Wait.... AI can do THAT now?

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

Starting a company with a blank slate sounds like a dream—but it's also a trap. In this mini episode, Rodney and Sam respond to a listener question about how to design an organizational operating system from scratch, without inheriting all the baggage of traditional management. They argue for resisting the urge to over-design early, letting real tension (not theory) drive structure, and focusing on a few foundational practices that scale. From operating rhythms and Kanban boards to experimentation and “sky sensing,” this episode breaks down what's actually worth putting in place early—and what's better left until it hurts. Mentioned references: "op rhythm": BNW Ep. 118 "strategy": AWWTR Ep. 2 "experimentation": AWWTR Ep. 38 "retrospectives": BNW Ep. 10 with Jordan Husney Kanban board The Ready's Experiment Proposal Template "The Sky" from Depthfinding Mia Wise Schedule a Sky Session with us! Got a work question like this one you'd like us to answer? Email us at podcast@theready.com -------------------------------- Ready to change your organization? ⁠⁠⁠⁠Let's talk!⁠⁠⁠⁠ Get our newsletter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Sign up here⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Follow us: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ -------------------------------- Sound engineering and design by Taylor Marvin of ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Coupe Studios⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.

Send us a textIn this solo episode of Mentoring Matters, Dr. Stephanie Hansen shares how she approaches the start of a new semester with plans that actually survive reality. Instead of chasing perfection, she focuses on building sustainable systems: protecting time for deep thinking work, stress-testing your calendar, and breaking big goals into small, repeatable processes.She also tackles common faculty pain points, from mentoring high-achieving grad students who struggle with perfectionism to setting realistic thesis and dissertation timelines before panic season hits. Along the way, she shares practical tools she uses to keep projects moving when the semester gets chaotic, including a Kanban approach and structured accountability.Finally, she talks attention and technology: reducing social media and phone distraction, and helping students become AI-capable without cognitively offloading their education. The goal isn't flawless performance — it's growth, resilience, and progress you can sustain.If you are interested in having Steph or Mary do a workshop on graduate mentoring at your institution please reach out to Steph at slhansen@iastate.eduFor actionable tips and strategies for mentoring please check out The Graduate Mentor's Trail Map available in paperback and ebook now! If you are enjoying this podcast please leave a rating or review, and join us over on Twitter to let us know what topics you'd like to hear more about.

What happens when good intentions collide with finite capacity? In many law practices, it shows up as overload, missed deadlines, and promises that quietly slip through the cracks.In this episode, I'm introducing the idea of a promise-keeping machine and explaining why making work visible is the first and most important step toward building one. You'll learn how simple visual systems like Kanban help lawyers see their true commitments, protect capacity, and make more credible promises to clients, colleagues, and themselves.Get full show notes, transcript, and more information here: agileattorney.com/102Take your law practice from overwhelmed to optimized with GreenLine LegalFollow along on LinkedIn: linkedin.com/in/johnegrant

We got Ryan Carson on the pod to break down the “Ralph Wiggum” Agent and why it's suddenly everywhere. He walks me through a simple workflow that lets an autonomous agent build a full product feature while I sleep: start with a PRD, convert it into small user stories with tight acceptance criteria, then run a looped script that ships work in clean iterations. The big idea is you're not “vibe coding” one giant prompt—you're giving the agent testable, bite-sized tickets and letting it execute like an engineering team. By the end, Ryan shows how this becomes repeatable (and safer) with a memory layer—agents.md for long-term notes and progress.txt for iteration-to-iteration context. Timestamps 00:00 – Intro 02:44 – What is the Ralph Wiggum AI Agent 03:40 – Step 1: PRD Generator 06:11 – Step 2: Convert PRD to Json 09:47 – Step 3: Run Ralph 12:05 – Step 4: Ralph Picks a Task 13:14 – Step 5: Ralph Implements Task 14:49 – Tokens + Cost: What It Actually Spends 15:45 – Guardrails: Small Stories + Clear Criteria Keep It Sane 16:19 – Step 6: Ralph commits the change 16:38 – Step 7: Ralph Updates PRD json file 16:55 – Step 8: Ralph Logs to Progress txt 20:08 – Step 9: Ralph Picks another Task 20:48 – Step 10: Ralph Finishes Tasks 21:18 – Example of how Ryan uses Ralph 24:08 – How To Start Today (Ralph Repo) and Tips Links Mentioned: Ralph Wiggum Agent: https://startup-ideas-pod.link/Ralph-agent  AI Agent Skills: https://startup-ideas-pod.link/amp-skills  AMP: https://startup-ideas-pod.link/amp-code  Ryan's Ralph Step-by-Step Guide: https://startup-ideas-pod.link/Ryans-Ralph-Guide Key Points I can't expect “sleep-shipping” unless I translate the feature into small, testable user stories with clear acceptance criteria. Ralph works like a Kanban loop: pull one story, implement, commit, mark pass/fail, then grab the next. The real leverage is the reset: each iteration starts fresh with a clean context window, instead of one giant, messy thread. agents.md becomes long-term memory across the repo; progress.txt is short-term memory across iterations. The bottleneck isn't “coding”—it's the upfront spec quality: PRD clarity, atomic stories, and verifiable criteria. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND RYAN ON SOCIAL: X/Twitter: https://x.com/ryancarson Amp: https://ampcode.com

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 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!

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