KatAnu Connect Podcast

Earlier this year the PMI and Agile Alliance introduced the Manifesto for Enterprise Agility.  Then came the harder question: why do organizations with great strategies still struggle to execute them?  Their answer is a report called Closing the Change Readiness Gap, and in this episode Kate Megaw, Anu Smalley and Ryan Smith dig into what it found.  Executives are confident their purpose is clear, yet the single biggest problem they named was the disconnect between planning and execution.  The report points to four obstacles: signal loss, where the why gets stripped out on the way down; decision rights that sit too far from the work; a structural trap where friction hardens into process; and a lack of psychological safety to name any of it.  The trio unpack why these are not four separate problems but one connected system, why the frozen middle is really a shock absorber, and why you cannot bolt AI or a framework onto a broken structure and expect flow. 

This year's Agile 2026 theme was “shaping the future with agility,” and that is exactly where Kate Megaw and Anu Smalley found the industry: mid-shift, still deciding what comes next. Back from the conference, they sit down with Ryan Smith for an honest field report. The partnership between PMI and the Agile Alliance has solidified, so the room was no longer split into project managers on one side and Scrum Masters on the other.  AI, meanwhile, has stopped being the shiny new thing bolted onto every session title and settled into the operating system of how we work, though “don't forget the human” is still treated as a footnote.  Kate and Anu wrestle with an industry in flux where no one has put a finger on what is broken yet, the Scrum Master role morphing into a dozen job titles, and Anu's growing conviction that the psychology of AI is the work that matters.  The phrase that stuck with Kate from one of the sessions says it all: we are in the age of perpetual transformation.

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.

There is “Big A” Agility, the frameworks like Scrum, Kanban, and SAFe, and there is “little a” agility, the plain human ability to change direction when the world shifts under your feet. Kate Megaw and Ryan Smith make the case that the second one matters most, and that it belongs in every company's core values, not just its delivery teams. Recorded ahead of Agile 2026 in Washington DC, whose theme is “Shaping the Future with Agility”, the conversation moves from VUCA to Bill George's VUCA 2.0, which answers volatility with vision, uncertainty with understanding, complexity with courage, and ambiguity with adaptability, to the most expensive words in business: “we have always done it this way”. Kate and Ryan dig into experimentation and the experiment log, why psychological safety is the ground everything grows from, the shift from a fixed mindset to a growth mindset, and why the five year plan and the pretty Gantt chart no longer survive contact with reality. The takeaway is simple. Shaping the future with agility is not about predicting what comes next. It is about building leaders, teams, and organizations that can thrive no matter what does.

Communication used to be filed away as a soft skill.  Kate Megaw and Ryan Smith make the case that it has become central to everything we do.  In a VUCA environment that is volatile, uncertain, complex, and ambiguous, communication is the anchor that keeps teams steady, and a recent Wiley survey found that 64 percent of people call it the single most important leadership skill.

Kate and Ryan dig into why communicating well is harder than ever across hybrid, remote, and distributed teams.  They unpack the Mehrabian 7-38-55 rule and why a quick Slack can cost you most of your message, the rule of seven and how to repeat yourself without becoming noise, and the over-communication trap that trains people to tune you out.  You will walk away with practical habits for choosing channels, building two-way dialogue, and turning communication into part of your team's working agreement.  When things are stable, a team can survive weak communication.  Nothing is stable right now, so 

Kate and Ryan come at agility from opposite ends of the org chart. Kate arrived through training, operations, and project management on the leadership side. Ryan started as a front-end developer who built a Kanban board before he knew it had a name.  In this episode they trace Ryan's path from coder to Scrum Master, and dig into the questions every agile practitioner eventually asks.  Does a Scrum Master need to be technical?  What does the role really protect?  Why do so many transformations stall without a dedicated Scrum Master?

Ryan makes the case that Scrum is agnostic to the work itself, that the Scrum Master creates the air the team breathes, and that the most important job is enforcing the pact between the team and the business so developers can do their best work without interruption.  He closes with practical advice for anyone growing into the role: go back to the Scrum Guide, get certified, and strip away the barnacles you have collected from role to role.

“We have twelve scrum masters. Why is nothing working?” If you have ever asked some version of that question, this episode is for you.

Kate Megaw, Anu Smalley and Ryan Smith dig into the challenge they hear in almost every class they teach, a real lack of role clarity. Companies send a strong project manager to a two day course, hand them a new title, and then wonder why nothing changes. The honest answer is that nobody ever defined what the role is actually accountable for. This episode unpacks the difference between roles and accountabilities, why a scrum master is not optional, and how to define seats around outcomes instead of titles. Along the way Kate and Anu have a friendly fight over RACI, whether it hardens into swim lanes or serves as a living guiding light, and what responsible really means at a startup versus a large enterprise.

What we cover:

• “We have twelve scrum masters, why is nothing working?”
• Roles vs. accountabilities, and why the org chart lies
• The RACI debate: swim lanes vs. guiding light
• The kitchen sink job description with 45 impossible duties
• Start with outcomes, not titles, and revisit at every kickoff

Everything is a fire. Everything is priority number one.  And by tomorrow, the number one priority has changed again. Sound familiar?

In this episode, Kate Megaw, Anu Smalley, and Ryan Smith dig into the challenge they hear at almost every client and leadership class: a real lack of prioritization.  Not just inside the sprint, but across the whole organization, where teams get handed a brand new top priority every single day.

When everything is important, nothing is important.  Constant reprioritizing whipsaws teams, burns people out, and leaves a trail of half-finished work and rising tech debt.  Jerry Weinberg's research found you can lose 20 to 40 percent of productivity every single time you switch context, so three projects can leave you down 60 to 80 percent.

In this episode, we discuss:

• Why a lack of prioritization is really a sign that your stakeholders are not aligned
• The real cost: burnout, rework, tech debt, lost innovation, and the context-switching tax
• Why this is a leadership problem, not a team problem, and why the team always gets blamed
• Using the sprint to hold the line and protect work the team has committed to
• Emergent requests as a better signal than velocity for how often the team gets interrupted
• MoSCoW for sorting the must-haves from the nice-to-haves
• The 20/20 approach from Innovation Games for a truly ordered backlog
• The impact-effort matrix for spotting quick wins and killing low-value work
• Buy-a-feature with stakeholders and a limited budget
• The wins on the board debate: put easy wins up first, or dig into why the big thing is big

Every time someone says yes, it consumes time, money, and attention.  Prioritization is the discipline of protecting all three.

Referenced in this episode: Jerry Weinberg's research on the cost of context switching, the 20/20 prioritization method from Innovation Games, the MoSCoW method, and the Eisenhower impact-effort matrix.