liberating structures Archives - Scrum Master Toolbox Podcast

Danil Chernyshev: Success Is Synergy—When the Team and the Product Both Win

“Success is when team members say thank you, and praise others for delivering a successful product.” – Danil Chernyshev

For Danil, success as a Scrum Master is never one thing—it’s a combination. It’s the moment team members thank each other and credit the whole group for a product that actually landed with customers.

As he reminds us, Scrum Masters, Product Owners, and developers are all there for the same reason: to deliver a product and solve real problems for the end user. A healthy team that has fun together but ships nothing has only spent time and money. A team that delivers but burns everyone out, until no one wants to see each other again, isn’t a success either.

Real success is the synergy of both: a productive team, happy customers and stakeholders, and people who still have the energy to keep going. Danil also turns the lens inward—success means understanding where you are in your own journey.

And it grows from action: when teams get stuck overthinking, he guides them back to what’s inside their control, helps them find the smallest valuable step, and gets them experimenting. Start where you are, do what you can, then learn from it.

Self-reflection Question: Are you optimizing for a happy team, a delivered product, or the synergy of both—and how would you know the difference?

Featured Retrospective Format for the Week: Lean Coffee (paired with 1-2-4-All and 5 Whys)

Danil doesn’t lock himself into a single retrospective format—he chooses based on the sprint, guided by “common sense in Scrum.” His default is to keep a running list of topics gathered throughout the sprint, then open the retrospective with a Lean Coffee session to democratically decide what to discuss.

From there, a light topic gets a quick Lean Coffee conversation, while a deeper one moves into 1-2-4-All from Liberating Structures or a 5 Whys. The non-negotiable for Danil: every retrospective must end with actionable action items. A retro that produces only conversation and no change, he says, was a waste of time—maybe fun, but still a missed opportunity to reflect, learn, and adapt.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Danil Chernyshev

Danil is a results-driven Scrum Master and Delivery Manager passionate about optimizing SDLC processes and unlocking development teams’ potential. With a keen interest in AI, he empowers organizations to innovate and excel, bridging agile practices with cutting-edge technology for impactful results.

You can link with Danil Chernyshev on LinkedIn.

Mirco Gerling: The Silence Test — How to Know Your Team Doesn’t Need You Anymore

“Don’t talk too much. And only talk if it’s necessary.” – Mirco Gerling

For Mirco, success as a Scrum Master starts with a simple rule he had to fight for: don’t try to be someone else. Early in his career, when people kept saying “Mirco, you decide, you’re the Scrum Master,” he had to do the hard work of pushing back — “no, we decide together.” That instinct shapes his whole definition of success. Be authentic. Wait before you speak. Ask before you instruct. And when a discussion stalls, sit with the silence — because in most cases, someone in the team has a better idea than you do. The cleanest test of whether a team is truly self-managing? Step back.

When Mirco took two months of parental leave, his team kept running every Scrum event without him. That’s the signal. If you stop sending the sprint review invite, stop preparing the retrospective, stop nudging — and the team picks it up because they own it — your work is showing.

Self-reflection Question: What’s one thing you currently do for your team that you suspect they would do themselves if you simply stopped doing it?

Featured Retrospective Format for the Week: 1-2-4-All from Liberating Structures

Mirco’s universal tool is Liberating Structures, and within that toolbox, 1-2-4-All is his go-to. The pitch: “involve everybody, especially in large groups. And there’s nearly no preparation needed.” His proof point — facilitating a retrospective for 60 people at the Agile by Nature bar camp in just 20 minutes. The format scales from a team of five to a room of sixty without changing its shape: one minute alone, two minutes in pairs, four minutes in small groups, then a share-back with the whole group. During a 30°C COVID summer in Hamburg, Mirco even ran retros walking outdoors with his team — station to station, down to the lake for ice cream, then back. “It was a very good and constructive retrospective.” The lesson: the right structure makes you portable.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Mirco Gerling

Mirco is an experienced Scrum Master in the public sector. With a strong IT background, he has spent 25 years developing software and driving agile transformations. Passionate about innovation and teamwork, Mirco brings expertise and dedication to every project.

You can link with Mirco Gerling on LinkedIn.

Gunnar Fischer: Healthy Flow of Value in a Healthy Work Environment—The Ecosystem Definition of Success

“A successful Scrum Master is healthy flow of value in a healthy work environment.” – Gunnar Fischer

Gunnar’s definition of success comes in one phrase that hides a lot of work: healthy flow of value in a healthy work environment.

The work environment, he says, is an ecosystem—it doesn’t have tigers, but it has plenty of layers and forces that can throw the balance off. You start at the team: are we reaching our goals most of the time? (If always, you might be playing too safe.) Then you move outward to the customer: who are we doing this work for, and are they succeeding?

Then to the company: what’s good for the customer might still be bad for the financials. And finally back to the individual: a team can be hitting its goals, the customer can be happy, the company can be making money, and a person on the team can still be quietly under-challenged and ready to leave.

Gunnar measures the flow side with the four Kanban guide metrics—cycle time, throughput, work item age, and work in progress—but he keeps reminding himself that finishing isn’t the same as getting feedback.

Did the customer use what we built? He’s been demotivated more than once by seeing a “very important” piece of work go untouched after delivery. And then there’s the social side: the level of healthy, constructive disagreement, and reading the room when colleagues from a culture that doesn’t say “no” go silent.

In this episode, we refer to Kanban flow metrics (cycle time, throughput, work item age, WIP) and the importance of treating the backlog as options, not promises.

Self-reflection Question: When was the last time you measured not whether the team finished something, but whether the customer actually used it?

Featured Retrospective Format for the Week: What, So What, Now What?

Gunnar’s favorite retrospective format is What, So What, Now What?, one of the Liberating Structures (and free to read up on online). He used it after a tense production deployment that succeeded but left the team rattled. Instead of jumping to “we need to do exactly this,” he forced the team to split their thinking: what are the facts we can describe, so what is our interpretation of those facts, and now what are the possible options going forward.

Sounds simple. But the brain hates incomplete pictures—it auto-completes them with speculation. That instinct kept our ancestors alive when they couldn’t see the full tiger behind the bushes; it ruins our reasoning at work.

By making the team distinguish hard between fact and interpretation, the format produced three concrete ideas. Within three months, the team had implemented all three, and things improved.

Gunnar’s broader takeaway about retrospectives: don’t run them right after the event (“get a coffee, step away from your desk for fifteen minutes”), don’t wait two months either, and—above all—“people need to look like winners when they’re going into a difficult retrospective.” Then honor their time by following up. If nobody else does the follow-up, the Scrum Master has to be the reminder.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Gunnar Fischer

Gunnar is the leader of the Chocolate Guild. Agile practitioner with a software developer background and a strong interest in people, intercultural contacts and the bigger picture. Gunnar’s purpose is to teach and to learn, to grow as a person and to support others who want the same.

You can link with Gunnar Fischer on LinkedIn.

You can also read Gunnar’s writing on his blog, Leader of the Chocolate Guild.

Aimé Flemm: When The Team Tells You You’re Doing Too Much — That’s The Success Signal

“It’s when you know you’re on the right track — when the teams start complaining that you’re doing too much.” – Aimé Flemm

Aimé got the feedback nobody wants to hear: “You’re being too much in the front of the group.” His first reaction was to take it personally. Then he saw it for what it was — the success signal. The team was telling him: let us do it. After months of helping them build self-managing capability, they hit a tipping point. They wanted the floor. He stepped back, started “actively doing nothing,” sat down and crossed his arms.

When they brought a problem, he asked: “What are you going to do about this? Have you tried that already?” But Aimé pushed back on himself in this conversation, and accepted the reframe: the Scrum Master isn’t less needed at the tipping point — they’re needed differently.

The shift is from teaching and facilitating ceremonies to nudging with questions, helping the team reach out when they’re stuck, surfacing issues with the PO and outside stakeholders. The focus shifts when you reach success. Don’t take “you’re doing too much” as offense — take it as your cue to change levels.

Self-reflection Question: When the team last pushed back on something you were doing, did you take it as feedback to defend — or as a signal that they’re ready to take more ownership?

Featured Retrospective Format for the Week: Retromat + Liberating Structures

Aimé’s favorite retro? “If I don’t have to do it myself.” Once teams reach the tipping point, he uses a pull system — they run their own retros, he checks in a few days later. But when he does facilitate, he layers two tools. First, Retromat — not just for the techniques, but for the flow: check-in, gather data, generate insights, decide what to do, checkout.

Second, Liberating Structures on top of that flow. His favorite is Impromptu Networking — small groups answer a question, then re-form in different groups. “It’s like a beehive. There’s so much energy. It’s bubbling.” He’s used it cross-org, his team and the client team in the same room. And his strong recommendation: do retrospectives on-site whenever you can.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Aimé Flemm

Aimé Flemm joins us from the Netherlands. Our guest is an organizational design coach who starts where most agile transformations stop. He works at the structural level: redesigning the incentives, reporting lines, and systems that either enable or quietly kill agility. His belief: you can’t coach your way out of a broken org design.

You can link with Aimé Flemm on LinkedIn.

Hassan Butt: Leading Change with Radical Candor, Building Organizational Openness

Hassan shares his experience leading a change initiative through Radical Candor workshops. He noticed that people in the organization were hesitant to share ideas with leadership. By using the Radical Candor framework, Hassan encouraged openness and honest feedback. He shares practical tips, such as role-playing, embedding accountability, and using structured formats like Liberating Structures, to create a safe space for feedback and collaboration. Hassan emphasizes the importance of follow-ups and self-accountability to ensure lasting change.

Self-reflection Question: How can you foster a culture of Radical Candor in your organization?

The Scrum Master Toolbox Podcast Recommends…

🔥 In the ruthless world of fintech, success isn’t just about innovation—it’s about coaching! 🔥

Angela thought she was just there to coach a team. But now, she’s caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn’t just about the product—it’s about the people.

🚨 Will Angela’s coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

Buy Now on Amazon

The Scrum Master Toolbox Podcast Recommends…

About Hassan Butt
Hassan builds high-performing teams and unlocks their full potential in his current role as a Scrum Master for a UK FTSE100 Telco. He also serves as an Agile Coach and mentor, supporting others in their professional growth. Hassan is well-known on LinkedIn for sharing valuable content and insights with the Agile community.

You can link with Hassan Butt on LinkedIn.