Many teams depend on others to get work done, slowing down feedback, learning, and flow. This episode shares three ways to reduce the pain of cross-team dependencies—even if you can’t change the org structure. Read More
A Product Backlog should provide focus and transparency, but most are overcrowded collections of items, where stakeholder's dreams go to die. Learn how to release the weight of old commitments, sort work into Active / Archive / Someday-Maybe, and when to declare Backlog Bankruptcy so every item earns its place. Read More
Five practical, research-backed ways to say no without being a jerk. Use purpose and goals as filters, protect flow, clarify decision rights, and practice stewardship language that keeps trust high while guarding capacity. Read More
To celebrate 200 episodes of The Humanizing Work Show, we’re revisiting one of our most practical and popular episodes: two facilitation moves that turn retrospectives from repetitive to transformative. Learn how ORID and a simple experiment mindset can reignite learning and improvement in every sprint. Read More
What's the big difference between Scrum and Kanban? When is each the best fit for a team's work? We share our experience on how to choose among them, along with four different ways to combine them effectively. Read More
When leaders ask for more data and reports, it’s often a signal of low trust. The problem is, more data doesn’t build it. In this episode, we show what actually earns trust and how your team can escape the status report trap. Read More
CAPED teaches leaders to go complexity first, but teams often resist. Richard and Peter explain the quick win trap and show how to make early learning safe and motivating. Read More
Most presentations to leaders don’t lead to real decisions. In this episode, we share a proven approach to preparing, structuring, and following up on presentations so leaders say yes. Learn how to use the “Therefore / But” pattern and other practical tools to turn presentations into results. Read More
Vibe coding prototypes can feel magical. With just a few prompts, you’ve got a working app. But as Peter’s experiment vibe coding an app shows, the biggest risk isn’t the code itself — it’s skipping the critical work of testing assumptions and validating whether the product actually solves a problem. Read More
Story points are everywhere in agile teams, but most groups use them in ways that create waste and frustration. In this episode, Peter and Richard explain how story points should work as a form of Reference Class Forecasting, why so many teams get them wrong, and the simple shift that makes estimation accurate and useful again. Read More
