Most teams start big initiatives with a slice that’s too big, too obvious, or too fuzzy to deliver anything useful. Feature Mining gives you a simple, reliable way to find the smart first slice of a big complex idea. It helps you uncover the real sources of complexity, align stakeholders early, and design first steps that create value, reduce risk, and generate real learning.

In this episode, Peter Green and Richard Lawrence explain how Feature Mining works, where it came from, and why it’s so effective in complex environments. You’ll hear a real retail example, the step-by-step process, and the core benefits teams see when they use this approach well.

You can learn Feature Mining in depth as part of our 80/20 Product Backlog Refinement online course, or join us live in our CSPO, A-CSPO, or CAPED workshops, where Feature Mining is a core practice for shaping big initiatives.

Episode page: https://www.humanizingwork.com/feature-mining-overview-finding-the-first-slice-in-complexity
Share a challenge or episode idea: mailbag@humanizingwork.com
Connect on LinkedIn: https://www.linkedin.com/company/humanizingwork

Most agile practices have become widely adopted—but cross-functional team structures remain the exception. Despite clear benefits like faster learning, shorter time to market, and simpler coordination, many teams still depend on others to get work done.

In this episode, Peter Green and Richard Lawrence share three practical strategies to reduce the pain of cross-team dependencies and make work flow better right where you are. You’ll learn how to spot where complexity really lives, use the CAPED model to collaborate across teams, define clear interfaces, and make the flow of value visible to build a case for change.

Full episode page, transcript, and resources:
https://www.humanizingwork.com/reduce-the-pain-of-cross-team-dependencies/

An overgrown backlog is not a promise—it’s a drag on focus and trust. Peter and Richard explain how to release the weight of GTD-style open commitments, use a Kondo-inspired “thank it and let it go,” and sort work into Active / Archive / Someday-Maybe. When needed, declare Backlog Bankruptcy and rebuild from the top, aligned to purpose. Less noise. More signal. Real momentum.

Check out the episode page for links, a transcript, and other resources: https://www.humanizingwork.com/life-changing-focus-clean-backlog/

If your calendar is full of “quick requests” and constant context switching, you’re not alone.
In this episode, Peter Green and Richard Lawrence explore why saying no at work is so hard—and how to do it well.

They share five practical, research-backed ways to protect focus and maintain trust:

1. Purpose – Use a clear team purpose as your filter for incoming requests.

2. Goals – Anchor decisions to aligned commitments, not personal priorities.

3. Flow – Protect attention and energy to finish meaningful work.

4. Decision Rights – Clarify who decides what, so refusals aren’t personal.

5. Stewardship – Reframe “no” as an act of service to your commitments.

Along the way, they reference organizational psychology research on attention residue, goal-setting, role clarity, and empowered refusal—and share practical ways to translate those findings into daily team habits.

Listen to learn how to stop reacting, focus on what matters, and say no gracefully.

Full transcript and links:
https://www.humanizingwork.com/research-backed-ways-to-say-no-without-being-a-jerk/

We just passed 200 episodes of The Humanizing Work Show!

To celebrate, we’re bringing back one of our most practical episodes—Two Key Moves for Better Sprint Retrospectives.

If your retros have become stale, repetitive, or ineffective, this conversation will help you turn them into one of the most valuable meetings you run.

Richard Lawrence and Peter Green share two facilitation practices that transform retros from a “check-the-box” routine into a continuous learning engine:

• Using the Focused Conversation (ORID) structure to move from scattered opinions to shared insight

• Treating each sprint as an experiment so improvement feels safe, steady, and sustainable

You’ll learn why “Stop/Start/Continue” hits a ceiling, how to collect shared data that fuels meaningful reflection, and why the phrase “let’s just try it for one sprint” can change everything.

Part of our 200-Episode Celebration—revisiting foundational ideas that make work more fit for humans, and humans more capable of doing great work.

Agile expert Richard Lawrence breaks down the differences between Scrum and Kanban, two of the most widely used approaches for managing work. He explains how each method works, where each one excels, and how you can decide which is best for your team or project.

You’ll learn the core distinction between Scrum’s time boxes and Kanban’s work-in-progress (WIP) limits, when to use Scrum, when to use Kanban, and why the answer is sometimes “both.”

Richard shares practical ways to combine elements of Scrum and Kanban to solve real-world problems, along with the most common pitfalls teams encounter when switching between these approaches—and how to avoid them.

Whether you’re new to agile methods or looking to refine your team’s process, this episode will give you a clear, practical framework for making better decisions about how you work.

Show notes, links, and transcript: https://www.humanizingwork.com/scrum-vs-kanban-getting-the-most-of-both-episode

When leaders ask for more data, dashboards, and reports, it’s often a signal of low trust. The trouble is, giving them more data doesn’t build it. So what do you do instead?

In this episode of the Humanizing Work Show, we unpack why reporting fails to create trust and what actually does. You’ll hear Rachel Botsman’s four traits of trust, how to connect with stakeholder needs, and three steps you can use to escape the status report trap.

Show notes, links, and transcript: https://www.humanizingwork.com/metrics-trust-and-escaping-the-status-report-trap/

Leaders may know the value of early learning, but teams may have built up resistance tackling the hardest, most uncertain work first. Instead, they chase quick wins that feel safe but create nasty surprises later. In this episode of the Humanizing Work Show, Richard Lawrence and Peter Green share how CAPED helps leaders make it safe for teams to go complexity first.

You’ll hear why quick wins are such an alluring trap, what causes team hesitation, and how leaders can use culture signals and skill-building to change the pattern. From Microsoft’s Tay chatbot story to practical tools like complexity mapping, feature mining, and reference class forecasting, this episode shows how to turn complexity first into the obvious, motivating choice.

Show notes, links, and transcript for this episode: https://www.humanizingwork.com/quick-wins-trap-core-complexity/