You schedule the meeting, you ask for input, and the room goes quiet. Then the real conversation happens in the hallway afterward. Kate Megaw and Ryan Smith dig into why people stay silent, and what facilitators can actually do about it. Silence is rarely about a disengaged team. It is fear of looking foolish, internal processors who need time to think, a leader who anchors the room before anyone speaks, and big talkers who cannot sit with a pause. Remote meetings can quietly make all of it worse.

The cost is real. Silence erodes trust, hides risks that surface mid sprint when it is too late, shrinks innovation, and hands the decision to the loudest voice in the room. Kate and Ryan share the practical moves they use to turn it around, from waiting out the silence and asking sharper questions, to silent writing, round robins, breakout pairs, stacking, and priming the pump before the meeting even starts. The throughline is simple. Facilitation is not just a soft skill, it is a design tool. Good meetings are designed, not winged, because as our friend Anu likes to say, “winging it is not a plan”!

The Scrum Master role has quietly evolved, and the industry has not caught up. Kate Megaw and Ryan Smith unpack how the role calcified into a person who runs the events and works through a checklist, when the real job was always to be a change agent and an organizational catalyst. Look at the job market and you see the shift already happening. Scrum Master, Project Manager, Technical Project Manager, Delivery Manager, and Program Manager are being used interchangeably, because the title never fit cleanly on an org chart and the Scrum Guide 2020 move from roles to accountabilities went largely unnoticed.

Kate and Ryan wrestle with a hard question. If the title confuses more than it clarifies, is it time to let it go? The word master implies telling rather than facilitating, and the name says nothing about what the person actually delivers. They also push back on the idea that agility is dying, making the case that it is becoming the DNA of healthy organizations instead. The takeaway is simple and a little uncomfortable. Stop defending the label and start demonstrating the impact a person in this role can have.

Velocity feels like proof. Fifty story points done, a bigger number than last sprint, a box checked. But velocity measures how busy a team is, not whether anything valuable reached the customer. Kate Megaw and Ryan Smith take apart the metric everyone loves to report and rebuild the case for measuring what matters. Velocity, they argue, was never a metric at all. It is an internal planning tool, Mike Cohn's “yesterday's weather”, useful for forecasting and useless for judging. From there the conversation turns to the measures that actually signal agility: outcome over output, flow metrics like lead time, work in progress limits, emergent work per sprint, flow efficiency, and the strategic questions executives really care about, such as whether the business moved forward. Along the way Ryan shares the MVP that 300 people found on their own, and Kate lands the question that cuts through it all: if your velocity doubled tomorrow, would your customers even notice? Velocity is vanity. Outcomes are reality. Agility lives in the flow.