Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: Guardrails Over Processes—How to Scale Teams Without Killing Creativity What actually slows down tech teams—lack of talent, or lack of ownership? In this episode, Prashanth Tondapu shares lessons from leading through global-scale failures, scaling from a small team to a 100-person company, and discovering why guardrails beat rigid processes when it comes to building teams that own outcomes and execute with discipline. Diffusion of Accountability: When Everyone Is Responsible, Nobody Is "Crisis is not the problem. Crisis is the one that uncovers the problem that has always existed."   Early in his career, Prashanth witnessed a large-scale failure at a major technology company—not because the team lacked talent, but because accountability had become diffused. When too many people are responsible for something, it translates to nobody being responsible. The team was brilliant individually, but there was no clear demarcation of who owned what outcome. On good days, everything worked. But when things went wrong, there was no single person who could no longer delegate accountability to someone else. In this segment, we also refer to the concept from Extreme Ownership by Jocko Willink. Prashant argues for: outcome can only come with 100% emotional commitment to a particular problem, and when five people share that commitment, each carries only 20%. That's where breakdowns happen. The Leadership Design Problem: From Computers to People "I was a developer who imagined that humans are also going to be as predictable as computers. Until 6 or 7 people, it works well because you can be everywhere. But as soon as we increased above 7, I was not able to be everywhere."   Prashanth's journey as a founder mirrors what many tech leaders experience at scale. Starting Innostax at 27 as a developer with no management experience, he initially treated people like predictable systems. Below seven people, it worked—he could be the hero founder, the catch-all. But beyond that threshold, he had to learn delegation, which meant learning to trust. First came the people-dependent phase, then the process-oriented phase with SOPs (Standard Operating Procedures) for everything—even how APIs should look. The SOPs made the team fast at execution, but their clients noticed something troubling: "Your guys do not even ask any questions." The rigid processes had suppressed the very creativity and critical thinking they needed. That feedback became the catalyst for the next evolution: becoming a people-first company. Guardrails vs. Processes: Freeing Creativity Within Structure "If something goes wrong, our guardrail is: we will just ask you one question—what was your intent behind doing this?"   Prashanth draws a sharp distinction between processes and guardrails. Processes tell you exactly what to do and how to do it—they create predictable execution but kill creativity. Guardrails define the boundaries within which people have freedom to be creative and solve problems their own way. At Innostax, guardrails take practical forms:   Time-on-task guardrails: If a task takes longer than expected, ask for help—don't rabbit-hole into it for three days Don't be a hero: When friction appears with a client or a problem, escalate early rather than trying to solve everything alone The intent review: When something goes wrong, instead of punishment, they ask three questions—was the intent right, was the approach right, and what was the outcome? If intent and approach were right but it still failed, that's the company's problem, not the individual's   This framework creates psychological safety while maintaining accountability. People know they won't be penalized for honest mistakes made with good intent, which means they surface problems early rather than hiding them. Vision Elements and the People-First Company "The outcome is not just what is expected, but outcome also consists of what is not expected. People come out in so many creative, great ways that they end up surprising you."   The shift to a people-first company meant replacing rigid SOPs with what Prashanth calls "vision elements"—broader directional guidance like "we are working for the client, we need to give the best for the client in the resources that we have." This gives teams a larger sandbox to work in while guardrails prevent them from going too far off course.  The daily rhythm includes team leads reviewing work summaries—not to micromanage, but to catch misalignment early and offer support. Prashanth emphasizes that guardrails must be created with emotional intelligence and detachment. If you create guardrails assuming you're also part of the problem, they'll be biased and ineffective. That's why he considers emotional intelligence the prerequisite skill for any leader designing team structures. The Books That Changed Everything "Whenever I was reading through the fixed mindset guy, it was like it was describing me. And that actually changed everything."   Prashanth recommends two foundational books for leaders building ownership-driven teams. First, Mindset by Carol Dweck—a book that cracked his own fixed mindset as a confident developer who thought he knew everything. Reading about the fixed mindset felt like reading his own biography, and that uncomfortable recognition opened him to listening more, seeking exposure to experts, and believing there were perspectives he hadn't encountered yet. Second, Emotional Intelligence by Daniel Goleman—because without mastering emotional intelligence, everything you hear feels personal, clouding your judgment and making you too close to the problem to design effective solutions for your team.   Self-reflection Question: Are you building guardrails that give your team freedom to be creative within clear boundaries, or are you still writing processes that tell people exactly what to do—and in the process, suppressing the very thinking you hired them for?   About Prashanth Tondapu Prashanth Tondapu is Founder and CEO of Innostax and a veteran technology leader. He's led teams through high-stakes global incidents at McAfee and scaled disciplined delivery organizations worldwide. His work focuses on ownership, accountability, and designing teams for predictable, sustainable execution as complexity grows.   You can link with Prashanth Tondapu on LinkedIn.

BONUS: Why the Spotify Model Didn't Work (Even at Spotify) Imagine a company that spends a year building an iPad app—and on launch day the product owner says: "Now it'll be interesting to see IF anyone uses it." In this episode, Marcus Hammarberg and Tore Fjaertoft share why organizations keep installing frameworks like software, why it still doesn't work, and what they've learned from places like Spotify about treating your way of working as a product in itself. When Copying Without Adopting Becomes the Norm "It becomes more about following whatever this framework tells you to do, rather than to understand what the problem you're trying to solve is all about."   Marcus and Tore met at a consultancy in Malmö and within 15 minutes realized they shared the same frustrations—despite coming from opposite directions. Marcus comes from the ground up as a software developer and coach, while Tore works top-down with leadership teams on product organization design. Both had worked at Spotify and both had seen organizations copy famous frameworks and models without adopting the underlying mindset. The telltale sign, as Tore describes it, is when people focus on compliance rather than being pragmatic—following the manual without questioning whether the way they're working is actually serving the organization. As Marcus frames it through Cynefin, product development lives in a domain where best practices don't even exist—only emergent practices that you discover by trying things out. Treat Your Process Like a Product "The easiest way for us to explain things has been: take the mindset you use for your product, and then use that same mindset when you're approaching how you set things up and how you work internally."   The core idea Marcus and Tore keep returning to is deceptively simple: see the way you operate as a product in and of itself. Just as a digital product is never finished—you ship it, observe how customers use it, and evolve accordingly—your operating model should follow the same cycle. Tore explains that the "customers" of your process are your employees: they need less friction, more empowerment, and the ability to spend more time on work that actually moves the needle for users. Marcus connects this to the lean concept of True North—a shared direction that everyone understands, so that every experiment and process change moves the organization closer to what matters. He contrasts this with the three Agile transformations he participated in that all had the same misguided tagline: "get more out of our development organization." As Marcus points out, even the AI DORA report shows developers feeling more productive individually—but is individual productivity really the goal? The Factory Floor Story: Empowerment Needs Alignment "Everyone down here knows that anything we do needs to be the best in the world, in every step."   Marcus shares a powerful story from a Swedish lorry factory where workers changed their workstation instructions several times a day—written on a whiteboard with a pen, not locked in a manual. When asked how they got everyone to engage in continuous improvement, the factory managers didn't understand the question. Every worker on the floor knew they were building the most expensive lorry in the world, and they wanted it to stay the best. That shared purpose drove improvement without mandates.  But Marcus is quick to add the counterbalance: empowerment without alignment leads to local optimization. The factory combined local metrics with overarching flow metrics, so everyone could see how their station fit into the whole chain. Marcus and Tore distill this into three interconnected principles: empowerment to enable people to change how they work, alignment to steer toward shared outcomes, and collaboration to prevent teams from optimizing in isolation. From Static Frameworks to Dynamic Ways of Working "We realized that Spotify didn't use the Spotify model. They moved on, because they see the way they work as a continuously evolving approach."   Tore reveals one of the most striking lessons from their Spotify experience: the company that accidentally created "the Spotify model" had already moved beyond it by the time the rest of the world started copying it. The reason? Spotify treated its way of working as something that continuously evolves—not a static blueprint to install and follow. Marcus adds a practical example from Spotify: on your first day, you got access to the company's key metrics. Everyone knew the True North—at the time, increasing monthly active users—and every process change, every experiment, every team decision was oriented toward that outcome. The contrast with organizations that "install" a framework and then wonder why it doesn't work couldn't be sharper. As Marcus puts it: "We tried process X, it didn't work. We tried process Y, the opposite, and that didn't work either. Why doesn't the process work?" The answer is that the "how" must emerge over time, guided by a clear "why." Always Know Why You're Doing What You're Doing "I don't want anyone to work on anything if you don't know why."   Tore shares a policy from a product management colleague at Spotify: every single day, everyone on his team should be able to articulate not just what they're working on, but why—and the "why" could not be "because person XYZ told me to." It had to connect to the company's purpose and users. Marcus takes this even further, recounting how he once stopped productivity at an entire company by telling developers: don't work on anything unless you know why. Nobody could continue. The uncomfortable silence that followed became a powerful catalyst for change. With an 80% failure rate for product experiments being the industry standard, packaging that risk into year-long projects is a recipe for the iPad app scenario they opened with. The alternative is to build the organizational muscle for rapid experimentation—cheap hypotheses, fast feedback, and the humility to let outcomes guide the way forward.   Self-reflection Question: When was the last time you asked your team—or yourself—"why are we doing this?" and got an answer that connected to a real business or user outcome rather than "because the framework says so"?   About Marcus Hammarberg and Tore Fjaertoft Marcus Hammarberg is a product and software coach and consultant who has seen product organizations from the inside and from the trenches. He works at Humane, part of the ADRA consulting collective, and has experience from Spotify, Tradera, and multiple Agile transformations across banks and insurance companies.   Tore Fjaertoft is a product organization advisor who works with leadership teams on how product thinking actually scales in large, complex companies. He works at Above, also part of the ADRA consulting collective, and has experience from Spotify and Volvo Cars.   You can link with Marcus Hammarberg on LinkedIn and Tore Fjaertoft on LinkedIn.

BONUS: Why the Human Architect Still Matters—AI-Assisted Coding for Production-Grade Software How do you build mission-critical software with AI without losing control of the architecture? In this episode, Ran Aroussi returns to share his hands-on approach to AI-assisted coding, revealing why he never lets the AI be the architect, how he uses a mental model file to preserve institutional knowledge across sessions, and why the IDE as we know it may be on its way out. Vibe Coding vs AI-Assisted Coding: The Difference Shows Up When Things Break "The main difference really shows up later in the life cycle of the software. If something breaks, the vibe coder usually won't know where the problem comes from. And the AI-assisted coder will."   Ran sees vibe coding as something primarily for people who aren't experienced programmers, going to a platform like Lovable and asking for a website without understanding the underlying components. AI-assisted coding, on the other hand, exists on a spectrum, but at every level, you understand what's going on in the code. You are the architect, you were there for the planning, you decided on the components and the data flow. The critical distinction isn't how the code gets written—it's whether you can diagnose and fix problems when they inevitably arise in production. The Human Must Own the Architecture "I'm heavily involved in the... not just involved, I'm the ultimate authority on everything regarding architecture and what I want the software to do. I spend a lot of time planning, breaking down into logical milestones."   Ran's workflow starts long before any code is written. He creates detailed PRDs (Product Requirements Documents) at multiple levels of granularity—first a high-level PRD to clarify his vision, then a more detailed version. From there, he breaks work into phases, ensuring building blocks are in place before expanding to features. Each phase gets its own smaller PRD and implementation plan, which the AI agent follows. For mission-critical code, Ran sits beside the AI and monitors it like a hawk. For lower-risk work like UI tweaks, he gives the agent more autonomy. The key insight: the human remains the lead architect and technical lead, with the AI acting as the implementer. The Alignment Check and Multi-Model Code Review "I'm asking it, what is the confidence level you have that we are 100% aligned with the goals and the implementation plan. Usually, it will respond with an apologetic, oh, we're only 58%."   Once the AI has followed the implementation plan, Ran uses a clever technique: he asks the model to self-assess its alignment with the original goals. When it inevitably reports less than 100%, he asks it to keep iterating until alignment is achieved. After that, he switches to a different model for a fresh code review. His preferred workflow uses Opus for iterative development—because it keeps you in the loop of what it's doing—and then switches to Codex for a scrutinous code review. The feedback from Codex gets fed back to Opus for corrections. Finally, there's a code optimization phase to minimize redundancy and resource usage. The Mental Model File: Preserving Knowledge Across Sessions "I'm asking the AI to keep a file that's literally called mentalmodel.md that has everything related to the software—why decisions were made, if there's a non-obvious solution, why this solution was chosen."   One of Ran's most practical innovations is the mentalmodel.md file. Instead of the AI blindly scanning the entire codebase when debugging or adding features, it can consult this file to understand the software's architecture, design decisions, and a knowledge graph of how components relate. The file is maintained automatically using hooks—every pre-commit, the agent updates the mental model with new learnings. This means the next AI session starts with institutional knowledge rather than from scratch. Ran also forces the use of inline comments and doc strings that reference the implementation plan, so both human reviewers and future AI agents can verify not just what the code does, but what it was supposed to do. Anti-Patterns: Less Is More with MCPs and Plan Mode "Context is the most precious resource that we have as AI users."   Ran takes a minimalist approach that might surprise many developers:   Only one MCP: He uses only Context7, instructing the AI to use CLI tools for everything else (Stripe, GitHub, etc.) to preserve context window space No plan mode: He finds built-in plan mode limiting, designed more for vibe coding. Instead, he starts conversations with "I want to discuss this idea—do not start coding until we have everything planned out" Never outsource architecture: For production-grade, mission-critical software, he maintains the full mental model himself, refusing to let the AI make architectural decisions The Death of the IDE and What Comes Next "I think that we're probably going to see the death of the IDE."   Ran predicts the traditional IDE is becoming obsolete. He still uses one, but purely as a file viewer—and for that, you don't need a full-fledged IDE. He points to tools like Conductor and Intent by Augment Code as examples of what the future looks like: chat panes, work trees, file viewers, terminals, and integrated browsers replacing the traditional code editor. He also highlights Factory's Droids as his favorite AI coding agent, noting its superior context management compared to other tools. Looking further ahead, Ran believes larger context windows (potentially 5 million tokens) will solve many current challenges, making much of the context management workaround unnecessary.   About Ran Aroussi Ran Aroussi is the founder of MUXI, an open framework for production-ready AI agents, co-creator of yfinance, and author of the book Production-Grade Agentic AI: From brittle workflows to deployable autonomous systems. Ran has lived at the intersection of open source, finance, and AI systems that actually have to work under pressure—not demos, not prototypes, but real production environments.   You can connect with Ran Aroussi on X/Twitter, and link with Ran Aroussi on LinkedIn.

Junaid Shaikh: Product Owner Anti-Patterns, From Team Owner to Product Owner, And The PO Who Got It Right Junaid opens with a line that cuts straight to the most common PO anti-pattern: "You are the product owner, not the team owner." When he sees a PO slipping into command-and-control mode, he asks them one question: "What is your role?" They say "Product Owner." He says: "Exactly. You own the product, not the team. If you were meant to own the team, we'd call you a project manager." The worst case he witnessed: a PO who was so possessive of "his" team that he required approval on everything — processes, tools, even holiday requests. In sprint planning, he would assign stories to individual team members ("Mr. X, you take this one"). He'd estimate the work himself, and when developers pushed back, he'd override them: "I was a developer, I know how long this takes." For approaching PO anti-patterns, Junaid has a deliberate style: he doesn't confront upfront. He observes, takes notes, and starts by solving a smaller impediment to demonstrate he's there to help. Once trust is built, he brings in coaching tools — first teaching the basics ("this is what the PO role is in Scrum"), then gradually coaching on specific anti-patterns observed in practice. He targets 10-15% improvement at a time. Six months later, you've already achieved 30-40% improvement. The best PO Junaid has worked with had four qualities: clear, concise communication; an open mindset willing to be coached; courage to say "no" when needed; and the discipline to define the "what" and leave the "how" to the team. This PO started with five sources of truth — Excel tabs, whiteboards, JIRA, and other tools. When Junaid pointed out that five sources of truth is the opposite of transparency (one of Scrum's three pillars), the PO asked for help. Junaid's response: "I can't do the push-ups for you." Together, they consolidated everything into one tool. The team was happier, and the PO managed the backlog much better. The key lesson: great product owners trust their team, communicate clearly, prioritize ruthlessly, and have the courage to say no. And they don't try to own the team. You can link with Junaid Shaikh on LinkedIn. [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 Junaid Shaikh Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.

Junaid Shaikh: How Scrum Masters Can Measure Their Own Impact, Practical Self-Assessment Metrics Junaid's favorite retrospective format? The vanilla: what went well, what could have gone better, what to do better next. He's tried many formats — the Three L's (liked, learned, lacked), the Three Little Pigs, the sailboat — but the core principle is always the same. His practical advice: stick with a consistent format so the team gets better at the process itself rather than constantly adjusting to new concepts. One addition he insists on for any format: an appreciation component. In the rush to analyze processes and outcomes, teams often skip acknowledging how another team member, PO, or Scrum Master helped during the sprint. That appreciation builds trust, respect, and openness that feeds into subsequent sprints. On defining success as a Scrum Master, Junaid starts with a Peter Drucker quote: "You cannot improve something you cannot measure." He proposes several practical self-assessment metrics: First, the Agile Team Maturity Index — a spider graph that shows where the team stands across multiple criteria, making gaps visible and actionable. Second, track retrospective action items. Create tiger teams for specific issues, run small iterative experiments, and measure in the next retrospective whether the trend is improving. Third, watch for shared sprint goals. Junaid once saw a team with nine sprint goals for a two-week sprint — those weren't goals, they were individual tasks. A real sprint goal should be something multiple team members work together to achieve. Fourth, self-organizing teams. If the team falls apart when the Scrum Master is absent for a sprint, there's a problem. Coach teams to self-organize, and their ability to function independently becomes a success metric. Fifth, communication patterns. Too many emails flying around can signal hidden conflicts or trust barriers. If communication happens through the right channels — dailies, direct interactions — you're likely in good shape. Sixth, Scrum event health. If events get canceled too frequently, the team may be reverting to traditional ways of working. [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 Junaid Shaikh Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.

Junaid Shaikh: Managing Uncertainty As A Scrum Master, How Scrum's Rhythm Creates Stability In Unstable Times For this week's coaching conversation, Junaid brings a challenge that resonates well beyond any single team: dealing with uncertainty. He references the World Uncertainty Index report from February 2026, which showed the highest levels of global uncertainty ever recorded — surpassing both the COVID pandemic and the 2008 financial crisis. This uncertainty doesn't stay at the geopolitical level. It seeps into teams. People show up stressed, unsure about what the next month or three months will bring. As Scrum Masters, we need to be cognizant of where our team members are coming from. Vasco adds an important layer: uncertainty operates at multiple levels within organizations. A colleague you depend on might be out sick for two weeks. A supplier might not deliver on time. Every dependency is a source of uncertainty. The question becomes: what in our processes is designed to accept and adapt to that uncertainty? Junaid's answer is powerful in its simplicity: Scrum's rhythm. The sprint, the planning, the daily, the retrospective — these events at a defined cadence create internal predictability. "When you have a rhythm, when you have a known sequence of events in front of you, that takes away a lot of uncertainty." Vasco builds on this: Scrum creates a boundary — the sprint — that accepts uncertainty outside while reducing it inside. Internal versus external predictability. Inside the sprint, the team can fail in small ways without exposing every failure to the outside. Compare that with traditional project planning, where every task on the critical path has external visibility and impact. For practical tools, Junaid shares how he used the Eisenhower matrix with a team to convert uncertainty into actionable priorities. They listed all activities from recent sprints, plotted them on the matrix, and found they could delegate or deprioritize 20-25% of their work. That freed them to focus with certainty on the remaining 75%. Combined with timeboxing as an uncertainty management mechanism, teams can create pockets of predictability even in turbulent times. [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 Junaid Shaikh Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.

Junaid Shaikh: Why Teams Go Through The Motions of Agile Without Being Agile, And What To Do About It Junaid's book recommendation is The Culture Map by Erin Meyer. As a Scrum Master working at companies like Ericsson and ABB — organizations that are a "United Nations" of cultures — understanding cultural tendencies has been essential. But Junaid goes further: you can customize the Culture Map framework even within a team of people from the same country, using the parameters to map different personalities. It's about how you use the tool, not just where people come from. He also recommends Scrum Mastery: From Good to Great Servant Leadership by Geoff Watts for practical advice on the servant leadership role, and regularly visits Scrum Alliance and Scrum.org for real-world insights from the community. On the topic of teams that self-destruct, Junaid paints a picture that many listeners will recognize. He picked up a team's retrospective history and cumulative flow diagrams and found problems at every level: managers who declared "from tomorrow we're going agile" without understanding what that meant, then started comparing velocity across teams. Product owners who took PO training but reverted to command-and-control project management. A previous Scrum Master doing what Junaid calls "zombie Scrum" — implementing the framework mechanically without understanding its purpose. The pattern underneath it all: people enveloping their traditional mindset under an agile umbrella. The ceremonies happen, the daily standups run, but nobody is questioning why they're doing any of it. As Vasco observes, this zombie pattern isn't limited to Scrum — it happens with code reviews, architecture reviews, any process that gets adopted without critical thinking about its purpose. Junaid's insight: if you don't understand the basics with the right mindset, every event feels like overhead. Teams complain about "too many meetings" because they're running agile ceremonies on top of their old informal processes. "If you don't get out of your previous shell, you cannot get into a new shell." [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 Junaid Shaikh Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.

Junaid Shaikh: The Eager Scrum Master Trap, Why Proposing Solutions Too Early Can Backfire In this episode, Junaid shares a story from his early days as a Scrum Master when enthusiasm got ahead of experience. Fresh from a CSM certification and full of ideas, he walked into teams and started proposing solutions — "No, this is not how you should do it." It felt obvious. It wasn't. The wake-up call came when he proposed working agreements to a team that had been collaborating well for two years. The pushback was immediate: "Why do we need this?" He realized he was bringing a tool he'd seen elsewhere without first understanding whether the team actually had the problem that tool was meant to solve. This led to a key shift in his approach: stop assuming. Instead of going in with answers, Junaid started creating small tiger teams with the affected people, facilitating sessions where they owned the solution. The result? Much higher acceptance and genuine continuous improvement. These days, Junaid tests his ideas before bringing them to the full team. He connects with individual team members first — his "closer allies" — to validate whether his analysis matches reality. Only when a few people confirm "yes, this is a real problem" does he bring the proposal to the group. As Vasco puts it: not all tools are appropriate at all times for all people. The same working agreements that were wrong for one team at one moment might be exactly right for a different team, or the same team at a different moment. [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 Junaid Shaikh Junaid Shaikh is an energetic Agile Coach with a natural flair for Agile and Scrum, shaped by recent experiences at software giants like Ericsson and hardware leaders ABB. In his work, he champions collaboration, curiosity, and continuous improvement. Beyond coaching, he brings the same passion to cricket, table tennis, carrom, and his newest sporting obsession — padel. You can link with Junaid Shaikh on LinkedIn.

In this CTO Series episode, Daniel Harcek shares how leading engineering teams across radically different scales — from a 7-person fintech startup to a 2,000-person cybersecurity company — taught him that leadership isn't one-size-fits-all. We explore how he builds AI-first organizations, drives agile transformations, and why he believes every person in a company should think like a tech person. What Works at 10 People Breaks at 100 "Leadership is contextual, not absolute. What works with 10 people breaks at 50, at 100." Daniel's career spans from building a 30-person team for a German startup out of Žilina, Slovakia, to leading 70 engineers at Avast's mobile division within a 2,000-person organization, and now running a 7-person team at WageNow. Each scale demanded a fundamentally different approach. At smaller scales, you strip away operational overhead and push ownership directly to the people. At larger scales, you need guardrails, dedicated roles, and structured processes that the smaller team would find suffocating. The lesson: don't carry your playbook from one context to another — rebuild it for the reality you're in. End-to-End Ownership Replaces Specialized Roles "Each engineer owns quality for the task he delivers. And he owns the fact that it comes to production." At WageNow, Daniel runs without dedicated QA people — in a fintech company where quality can't be compromised. Instead, each developer owns quality end-to-end, from code to production. This isn't recklessness; it's intentional design. When teams are small, you set up the system so that it's safe to break things, then trust people with hard tasks. The result: people grow faster, move faster, and care more about what they ship. In larger organizations, you might need specialized DevOps, QA, and platform roles — but the principle of ownership stays the same. The Buddy System and Scaling Without Losing Alignment "The buddy system is one of the easiest things you can do. One buddy for a newcomer for the first 1, 3, 6 months — they often become friends." When scaling fast, Daniel focuses on three things: strong on-boarding guides, well-maintained documentation (now much easier with AI), and a buddy system that pairs every newcomer with a dedicated colleague. The buddy system works because it scales the human side of on-boarding — a tech lead or manager can do one-on-ones, but that's formal, and new people might be scared to speak up. The buddy creates a safe channel for questions, concerns, and cultural integration. Beyond people, scaling also means investing in automation and observability so that as you grow with customers, you grow with failures too — and your incident reporting doesn't burn out the team. Building an AI-First Organization "Every person uses AI. Every person has the capability to use AI. The company builds a second brain so AI can build on top of that." At WageNow, Daniel has implemented what he calls an AI-first organization, inspired by Spotify and other companies pioneering this approach. The concept is simple: before doing any task, ask whether AI can help you deliver the output faster or better. This applies across the entire company — not just engineering. Daniel looks for people in HR, accounting, and UX who understand automation tools like n8n or Make.com alongside AI. The key ingredients: Curate the data: Build a company "second brain" with clean, structured context for AI tools to work with Train the muscle: AI ability is like a muscle — people must use it daily because these skills didn't exist 2-3 years ago Share what works: Exponential AI adoption happened at WageNow once people started sharing their successes and failures with AI tools Respect the guardrails: Data privacy and regulation compliance remain non-negotiable The hidden productivity gains, Daniel argues, lie not in engineering (which gets all the attention) but in operations, accounting, HR, and every other area of the business. Selling Transformation: Financial Arguments for Leaders, Ownership for Teams "For the leaders, it's the financial thing and the cultural thing. For the people doing the work, it's personal development — having more control, having more ownership." At Ringier Axel Springer, Daniel proposed and led a company-wide agile transformation — a 1-2 year effort that required convincing the CEO, product teams, marketing, and sales to change how they operate. His approach: build a dual argument. For leadership, frame the change in financial and cultural terms — more revenue with the same people, better visibility into how work translates to business outcomes. For the people doing the work, emphasize personal growth, increased ownership, and transparency. The transformation breaks silos between engineering and product, creating a shared backlog agreed with all stakeholders. Daniel looks for people with high agency — those who can reinvent and change themselves from the inside, not just wait for a change agent from the outside. Balancing Experimentation with Operational Excellence "The SRE books helped me understand quality as a feature — because quality is basically how reliable you are for your customers." When asked about the books that most influenced his approach as a CTO, Daniel points to the Site Reliability Engineering series from Google — three books that frame quality as reliability, a feature your customers experience directly. Alongside those, he recommends The Lean Startup by Eric Ries, because he believes all tech people should have a sense of business and customer understanding. Together, these books guide how to balance rapid experimentation with operational excellence as the organization scales. About Daniel Harcek Daniel is a technology executive with a proven record scaling engineering organizations across fintech, cybersecurity, and digital media. Builds AI-first teams, operating models, and delivery cultures aligned with product strategy. Led platforms serving 30M MAU, deployed fintech capital pilots, transformed agile delivery at internet scale, and mentors global tech communities and ecosystems worldwide actively. You can link with Daniel Harcek on LinkedIn.

Nigel Baker: Accountability Requires Ability—Why Powerless Product Owners Are Sacrificial Lambs Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   In this episode, we refer to the importance of product ownership and empowerment in Scrum teams. The Great Product Owner: The Empirical PO Who Navigated Like a Slalom Skier "He had an idea of the outcomes he had to achieve, and the solution itself—though he had strong beliefs about it—he was incredibly open-minded to feedback from the engineering teams. Most of the innovation came from his engineering teams." - Nigel Baker   The best Product Owner Nigel ever worked with operated with a startup mentality, even within a larger organization. This PO had a clear vision—not for a specific end solution, but for an end state of the world. He ran experiments, learned continuously, and had a remarkable ability to pivot smoothly during development.  Nigel compares him to a slalom skier: smoothly navigating from post to post, making it look natural rather than effortless. What made him extraordinary was his openness to feedback from engineering teams—most of the product's innovation actually came from the engineers suggesting possibilities, and this PO would absorb those ideas and weave them into the direction.  The engineering teams felt secure because they trusted his judgment. He didn't tell people to trust him—he demonstrated trustworthiness through consistent behavior. It was genuine servant leadership: not making a fuss about being in charge, but leading by showing new, cool, interesting behaviors that allowed everyone to follow naturally.   Self-reflection Question: Does your Product Owner have a vision for the end state of the world they're trying to create, or are they locked into a specific solution? The Bad Product Owner: The Powerless PO Who Can't Say Yes or No "Accountability requires ability. If they want you to take responsibility for this work, you have to have the ability to see that through. Without that, you're a sacrificial lamb." - Nigel Baker   Nigel has seen many PO anti-patterns, but the most damaging one is the powerless Product Owner—someone with all the skills of a business analyst but none of the authority to say yes or no. Commitments get made outside the team, direction can't be changed within sprints, and the whole experience gets crushed.  Early in his career, POs were powerful but IT-ignorant business people—dangerous, but at least they had authority. Today's anti-pattern is far worse: people playing the PO role without the O—the ownership. Nigel's approach is direct: he uses the phrase "accountability requires ability" to help the PO understand their position, then traces up the organizational line to find the person who actually holds real power.  He reveals to that person that they are, in fact, the Product Owner—and 9 times out of 10, they immediately delegate the authority officially to someone, which is exactly what was needed. That official delegation transforms a sacrificial lamb into a genuine Product Owner with the power to steer.   Self-reflection Question: Does your Product Owner have genuine authority to make decisions, or are they a sacrificial lamb accountable for outcomes they can't control?   [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 Nigel Baker   Nigel Baker is a seasoned agile coach with a keen intellect, warm creativity, and thoughtful humour. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform. Outside work, he loves bold ideas, good conversation and a life well lived.   You can link with Nigel Baker on LinkedIn. You can also find Nigel at AgileBear.com.

Nigel Baker: Why Scrum Masters Should Be Measured on Outcomes, Impacts, and Team Happiness Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "No customer's going to come to you and say, do you know why I bought your product? Your remarkable compliance with your internal development process. What they're interested in is outcomes and impacts." - Nigel Baker   Nigel challenges the traditional ways of measuring Scrum Master success. He points to tools like the Nokia test—which, he jokes, was neither a test nor invented by Nokia—as examples of process fidelity assessments that miss the point entirely. Compliance with a process tells you nothing about whether customers are satisfied or whether the team is delivering value. Instead, Nigel argues for measuring Scrum Masters on outcomes and impacts: customer satisfaction, revenue generation, and efficiencies—the same things a Product Owner gets judged on.  But he adds a crucial dimension that POs often overlook: team happiness. Not as an end goal, but as a leading indicator. Happy teams don't leave. Happy teams do better work. Team contentness is a KPI that signals whether the deeper success factors are in place. When your team is deeply unhappy, no amount of velocity or story completion will save you from attrition and decline.   Self-reflection Question: How are you currently measuring your success as a Scrum Master—on process compliance, or on the outcomes, impacts, and wellbeing your team actually delivers? Featured Retrospective Format for the Week: Keep It Fresh—A Different Format Every Sprint Nigel's answer to the "favorite retrospective format" question is deliberately controversial: he doesn't have one. His approach is to use a different format every single sprint. Retrospective formats, he argues, "age like milk"—by Sprint 12, asking "what should we do differently?" with the same structure produces diminishing returns. Novelty creates energy. He sometimes gets teams to invent their own formats, which produces some of the most forensic and intense retrospectives he's seen—teams building "superweapons" and then realizing they have to turn those weapons on themselves. But Nigel's most practical tip is using retrospective techniques inside the Sprint Review. The Review is a product retrospective, and stakeholders shouldn't sit "like Roman emperors in the Colosseum, watching the developers as gladiators." Instead, use facilitation methods to extract "sweet, juicy, honey-flavoured feedback" from stakeholders about what they'd change in the product.   [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 Nigel Baker   Nigel Baker is a seasoned agile coach with a keen intellect, warm creativity, and thoughtful humour. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform. Outside work, he loves bold ideas, good conversation and a life well lived.   You can link with Nigel Baker on LinkedIn. You can also find Nigel at AgileBear.com.

Nigel Baker: The "Death of Agile" and Why It's Really the Death of Empowerment That Should Frighten Us Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "It's not so much the death of Agile that's killing me, or death of Scrum. It's the death of things like empowerment, the death of things like empiricism. Those are the things that frighten me in work." - Nigel Baker   Nigel brings a challenge that resonates across the entire Agile community: the so-called "death of Agile." But he quickly reframes the conversation in a way that cuts much deeper. The real issue isn't whether teams call what they do Scrum or Agile—it's that the industry is decaying back past waterfall to what Nigel calls feudalism, where a single "great man" dictates and everyone else follows.  He distinguishes between two kinds of popularity: the number of people saying they're doing Agile versus the number of people actually liking what they're doing—a gap he compares to Jira's massive subscriber base versus its actual user satisfaction. Through this lens, Nigel introduces his famous "Nigel Scale"—a joke he made on a Scrum Alliance forum 20 years ago that people took entirely seriously. The scale separates Scrum into three levels: core practices that break things if you skip them (like a surgeon disinfecting hands), contextual good practices that may or may not apply (like story points), and persistent anti-patterns that never work no matter how many times people try (like normalizing team measurements across teams).  Vasco and Nigel converge on an experiment: treat Scrum adoption itself as a backlog of changes, introducing practices incrementally based on feedback—but always with a compelling vision of why the change matters.   Self-reflection Question: When you hear "Agile is dead," are you defending a framework, or are you advocating for the underlying principles of empowerment and empiricism that teams genuinely need?   [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 Nigel Baker   Nigel Baker is a seasoned agile coach with a keen intellect, warm creativity, and thoughtful humour. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform. Outside work, he loves bold ideas, good conversation and a life well lived.   You can link with Nigel Baker on LinkedIn. You can also find Nigel at AgileBear.com.

Nigel Baker: When Teams Slowly Decay by Anointing a Hidden Dictator Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "The world won't end with a bang, but with a whimper. My great fear is not teams exploding like a bomb—that shows they care. The big thing for me is teams that decay slowly." - Nigel Baker   Nigel shares a pattern he has witnessed repeatedly: teams that self-destruct not through dramatic conflict, but through a slow, quiet decay. Referencing The Five Dysfunctions of a Team by Patrick Lencioni, he points to something even more insidious than inattention to results—teams that avoid taking responsibility for decision-making.  When teams struggle with self-organization, they often try to "self-organize themselves out of self-organization" by anointing a hidden dictator: the big brain, the big mouth, the tech lead, or the project manager who everyone secretly defers to. Nigel offers two practical tools to counter this pattern.  First, the "yes and" technique from improv comedy—instead of taking ownership away from team members, you accept their idea and add to it, keeping the ownership where it belongs.  Second, Socratic questioning, where instead of passing knowledge from you to them, you help them pass knowledge from themselves to themselves. But Nigel adds an important caution: the Agile community has swung too far into pure coaching mode. Sometimes people genuinely need help, not therapy—they need to know which server the files are on, not a deep coaching question about their feelings.   In this segment, we talk about Paul Goddard's work on improv comedy in Agile, and the power of the "yes and" technique for keeping ownership with teams.   Self-reflection Question: Is your team quietly deferring all decisions to one person, and if so, what practical steps can you take to redistribute that ownership? Featured Book of the Week: Leading Self-Directed Work Teams by Kimball Fisher Nigel's book recommendations reflect his belief that the most inspiring ideas come from adjacent fields rather than Agile literature itself. Leading Self-Directed Work Teams by Kimball Fisher stands out because it explores similar principles to the Scrum Master role but without any Agile jargon—showing how a completely different industry arrived at the same insights about empowered teams. Nigel also recommends the Strategyzer books by Alex Osterwalder, including Business Model Generation and Testing Business Ideas, for the business thinking that coaches need but rarely pick up at work. Scrum Mastery by Geoff Watts remains his go-to foundational text for new Scrum Masters. And the book he waited 4.5 years for—until Amazon cancelled the pre-order—is the latest edition of The Facilitator's Guide to Participatory Decision Making by Sam Kaner, a deeply practical reference guide that gives real people real tools for real situations.   [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 Nigel Baker   Nigel Baker is a seasoned agile coach with a keen intellect, warm creativity, and thoughtful humour. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform. Outside work, he loves bold ideas, good conversation and a life well lived.   You can link with Nigel Baker on LinkedIn. You can also find Nigel at AgileBear.com.

Nigel Baker: The Scrum Master Mistake of Copy-Pasting Success Instead of Recreating the Journey Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "I was trying to recreate the results of our team, not recreate the journey. And that is what killed me to begin with." - Nigel Baker   Nigel fell into Scrum Mastery almost by accident. Working at British Telecom in 2002—before most people had even heard of Scrum—his team adopted it not to speed up, but to add rigor to an already fast-moving tactical unit full of "pirates" who could get stuff done but needed guardrails. His first Scrum Master, Geoff Watts, got promoted and moved on, leaving a vacancy. Nigel was the third person asked—and the first to say yes. He loved the role, but his earliest mistake became his most enduring lesson.  On his very first daily Scrum, Nigel brought a big leather book and wrote down what every team member was doing, acting like a proto-project manager collecting status reports. The team already had all this information in their system—he was unconsciously positioning himself as the authority figure, having people report to him rather than to each other.  As Nigel evolved into an Agile Coach, the bigger failure emerged: trying to copy-paste the process that worked with his first team onto other teams, recreating the results rather than the journey that got them there. Each team needs to evolve its own process—there are no shortcuts to that growth.   In this episode, we refer to the importance of self-awareness and servant leadership in the Scrum Master role.   Self-reflection Question: Are you trying to replicate a successful process from a previous team, or are you investing in helping your current team discover their own path to effectiveness?   [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 Nigel Baker   Nigel Baker is a seasoned agile coach with a keen intellect, warm creativity, and thoughtful humour. With a career spanning software engineering, consultancy and global training, he inspires teams to thrive, not just perform. Outside work, he loves bold ideas, good conversation and a life well lived.   You can link with Nigel Baker on LinkedIn. You can also find Nigel at AgileBear.com.  

Lai-Ling Su: The Explicit and Implicit Layers of Unclear Decision Rights Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Building Impactful Relationships That Get Things Done "What made her great was the fact that she focused not just on her technical prowess, but on the people, politics, and the performance side of product. And she used that to turn ambition into reality, and she used that to move strategy to execution." - Lai-Ling Su   Lai-Ling describes a phenomenal product owner she worked with about 12 months ago. This woman wasn't just technically strong—she was a leader whose team of 10 loved her because she mentored them to be as strong or stronger than herself.  The business loved her because she was exceptionally commercial, thinking about customer value, revenues, expenses, profit models, and marketing long before anything was built. She held everyone true to doing the right thing even when pressure mounted. The executive team loved her because her greatest strength was building solid, impactful relationships that transcended boundaries.  She removed the us-versus-them mentality, broke down departmental silos, handled politically charged scenarios, negotiated with difficult personalities across technology, legal, compliance, sales, and operations. She removed impediments responsively and got stuff done when others couldn't. Her secret was focusing on people, politics, and performance—not just technical prowess.   In this episode, we refer to Esco Kilpi's work on interactive value creation, which describes how value in knowledge organizations is created through ongoing conversations—not just meetings, but emails, wiki pages, and corridor conversations that steward decisions over time.   Self-reflection Question: How deliberately are you investing in building relationships that transcend your immediate team and department? The Bad Product Owner: Unclear Decision Rights "Does your head of product know that he has the rights and the authority to make the types of decisions that you want him to?" - Lai-Ling Su   The anti-pattern Lai-Ling encounters most persistently is unclear decision rights. She illustrates this with a story about a GM in a multinational who effectively worked as a chief product officer. His biggest complaint was that his head of product kept coming to him for decisions that should have been made independently—even though he'd been given $10 million a year to run his teams.  When Lai-Ling asked one simple question—"Does your head of product know he has the authority to make these decisions?"—the GM sat in shocked silence for a full minute. But the pattern runs deeper: there's the assumption that people know their decision rights, there's knowing your rights but not knowing how to make those decisions, and there's knowing your rights but getting trumped every time you try, leading to learned helplessness.  Some product owners have never learned to make decisions because they always defer to someone who seems better at it. There are both explicit and implicit unclear decision rights—you might tell someone they have authority while implicitly sabotaging their decisions.   Self-reflection Question: Have you explicitly confirmed with your stakeholders what decisions you have the authority to make—and are those decisions being respected in practice?   [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 Lai-Ling Su   Lai-Ling fixes the gap between operating model design and real-world delivery through her interim executive, consulting, capability building, and executive coaching work. She also equips product and transformation leaders with the capability everyone expects but no one teaches - how to navigate the people, politics, and performance expectations that come with their jobs.   You can link with Lai-Ling Su on LinkedIn.

Lai-Ling Su: What Scrum Masters Must Do More of in 2026—Think Like a Business Owner Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Success is so contextual. And I think the definitions and measurements of success also change over time. So, only you can definitively say what success is at any given time and how to appropriately measure it for your situation." - Lai-Ling Su   Lai-Ling frames success for Scrum Masters around what she'd love to see more of in 2026: smart, strategic, and commercial decision-making. She observes a distinct gap in the business landscape—too few people are making decisions that balance customer value, revenues, expenses, and long-term sustainability.  This could mean reducing SKUs to enhance operational flow and reduce burnout, investing in change management from day one of a transformation, or cutting unused software licenses to save a colleague's job or fund product innovation. To help Scrum Masters develop this capability, Lai-Ling puts them in the shoes of a business owner—whether through simulations, shadowing business leaders, or pairing with product owners to understand the business side of products beyond just the build side.  She emphasizes the difference between learning strategy through theory (like an MBA) versus learning it through actually operating a business, where consequences are real and immediate.   Self-reflection Question: When did you last consider how a decision in your domain impacts the broader commercial viability of your organization? Featured Retrospective Format for the Week: LEGO Serious Play Lai-Ling loves using LEGO for deeply reflective retrospectives, and she's a certified LEGO Serious Play facilitator. The approach works beautifully for tender and courageous conversations because building with LEGO does several things simultaneously: it's fun, the physical act of building helps process and articulate thoughts you didn't have words for, and it depersonalizes what's said because participants talk about a physical object rather than directly about people. You don't need expensive certified kits—just grab basic bricks from a local shop, pose a reflective question, and let people build.  Lai-Ling notes that her best retrospectives have often been the most deeply uncomfortable ones for participants, because of how much personal and emotional truth emerges when you create that safe space for constructive dialogue. The kinetic and visual elements help crystallize ideas that would otherwise not come out so easily.   [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 Lai-Ling Su   Lai-Ling fixes the gap between operating model design and real-world delivery through her interim executive, consulting, capability building, and executive coaching work. She also equips product and transformation leaders with the capability everyone expects but no one teaches - how to navigate the people, politics, and performance expectations that come with their jobs.   You can link with Lai-Ling Su on LinkedIn.

Lai-Ling Su: When Leadership Changes—Supporting Teams Through the Uncertainty Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "We have a once in a generational or once in a lifetime type of opportunity to fundamentally work with these leaders to shift the workplace environments and the workplace dynamics in the way that we've been trying to craft in the world of product and agile for the last few decades." - Lai-Ling Su   Lai-Ling brings a systems-level challenge that has profound implications for Scrum Masters everywhere. Australia is on the brink of its largest intergenerational wealth transfer in history—$3.5 trillion over the next couple of decades—with 70% of private and family businesses planning to sell or succeed as part of this generational change.  This creates leadership vacuums as business leaders transition out and new ones step in. Some are family members stepping into roles without the full capability to lead; others are external CEOs facing resistance when they do things differently.  These transitions stall decisions, lose customer confidence, and fracture once tight-knit teams. Lai-Ling sees this as an unprecedented opportunity for Scrum Masters to support both outgoing and incoming leaders through succession planning, capability uplift, and protecting teams during the transition.  Teams need to be respected for what they've achieved, and Scrum Masters can serve as bridges—creating awareness about the team's strengths and facilitating dialogue between old and new leadership to ensure continuity.   Self-reflection Question: How might you proactively prepare your team to navigate an upcoming leadership transition, whether it's anticipated or unexpected?   [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 Lai-Ling Su   Lai-Ling fixes the gap between operating model design and real-world delivery through her interim executive, consulting, capability building, and executive coaching work. She also equips product and transformation leaders with the capability everyone expects but no one teaches - how to navigate the people, politics, and performance expectations that come with their jobs.   You can link with Lai-Ling Su on LinkedIn.

Lai-Ling Su: Why the Us-Versus-Them Mentality Is the Fastest Path to Team Self-Destruction Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "The quickest way to self-destruction is to have an us-versus-them mentality. Because it permeates into every behavior, every action or inaction, and it impacts every single outcome as a result of it." - Lai-Ling Su   Lai-Ling shares a compelling story about a leadership team in healthcare technology that was self-sabotaging their way into non-delivery—so much so that critical commercial outcomes were at serious risk. Yet the team themselves couldn't see it; it was invisible to them. She identifies three layers of the us-versus-them dynamic that needed unpicking.  First, recent M&A activity had merged a larger corporate entity with a smaller, more nimble one, and people remained ferociously loyal to leaders from their old organizations.  Second, business goals were separate from technology goals, causing people to fall back to people-pleasing within their direct reporting lines rather than collaborating on shared purpose.  Third, the tension between growth ambitions and addressing legacy activities created another divide. What struck Lai-Ling most was how these "classic" patterns were invisible to those experiencing them—they just accepted it as part of doing business. The destruction wasn't always stormy and visible; sometimes it was silent, with work piling up, nothing getting done, yet no one overtly upset.   In this segment, we talk about the importance of creating awareness and how Scrum Masters must be willing to point out these patterns, even at the risk of being seen as the odd ones out.   Self-reflection Question: What "classic" anti-patterns might be invisible in your organization right now because everyone has accepted them as just part of doing business? Featured Book of the Week: The Checklist Manifesto by Atul Gawande Lai-Ling approaches the book recommendation differently—she believes no single book has fundamentally influenced her, but books as a collective have made her who she is. She emphasizes reading far and wide across all topics and genres, looking for patterns in unexpected places. One standout is The Checklist Manifesto by Atul Gawande, which challenges the perception that checklists take away autonomy. Gawande writes about how checklists are a rapid-fire communication tool that can mean the difference between a seriously injured soldier dying on the battlefield or making it to a hospital with a good chance of survival. Lai-Ling also recommends When Breath Becomes Air by Paul Kalanithi, about a surgeon who became a cancer patient and had to navigate a massive identity shift—much like the identity shift we ask leaders to make during transformations.   [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 Lai-Ling Su   Lai-Ling fixes the gap between operating model design and real-world delivery through her interim executive, consulting, capability building, and executive coaching work. She also equips product and transformation leaders with the capability everyone expects but no one teaches - how to navigate the people, politics, and performance expectations that come with their jobs.   You can link with Lai-Ling Su on LinkedIn.

Lai-Ling Su: The Product and Service Story That Every Scrum Master Needs to Hear Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "It was kind of at that moment that I realized, like, community was about providing people with the opportunities that they otherwise wouldn't have had. And whilst you could technically execute your product or service well, the customer experience is fundamentally a deeply emotional one." - Lai-Ling Su   Lai-Ling shares a powerful story from when she was just 11 years old, running front of house at her family's restaurant inside an Australian workers' club. When a popular band was booked to play on a Saturday night, the venue reached max capacity—and almost everyone wanted food. With no ticketed order system and only her memory to match orders to customers, chaos ensued.  One father approached her, yelling about how long his food was taking. At the end of the night, Lai-Ling mustered the courage that only an 11-year-old possesses and asked him point-blank why he had reacted so strongly. His answer floored her: he only got to see his son every other weekend, and this evening was supposed to create a cherished memory together. Instead, they were hangry most of the night.  This moment taught Lai-Ling that customer experience is fundamentally emotional—it's not about the food, but about what the interaction means to the people we serve. For the next decade, she continuously inspected every aspect of their restaurant operations, always seeking to improve how they served customers while remaining commercially viable. In this episode, we refer to the "Scrum Masters are the future CEO's, and a podcast by the Lean Enterprise Institute" blog post by Vasco.    Self-reflection Question: When was the last time you paused to understand the deeper meaning behind a stakeholder's frustration, rather than just addressing the surface-level complaint?   [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 Lai-Ling Su   Lai-Ling fixes the gap between operating model design and real-world delivery through her interim executive, consulting, capability building, and executive coaching work. She also equips product and transformation leaders with the capability everyone expects but no one teaches - how to navigate the people, politics, and performance expectations that come with their jobs.   You can link with Lai-Ling Su on LinkedIn.

BONUS: From Combat Pilot to Scrum Master - How Military Leadership Transforms Agile Teams In this bonus episode, we explore a fascinating career transition with Nate Amidon, a former Air Force combat pilot who now helps software teams embed military-grade leadership principles into their Agile practices. Nate shares how the high-stakes discipline of aviation translates directly into building high-performing development teams, and why veterans make exceptional Scrum Masters. The Brief-Execute-Debrief Cycle: Aviation Meets Agile "We would mission brief in the morning and make sure everyone was on the same page. Then we problem-solved our way through the day, debriefed after, and did it again. When I learned about what Agile was, I realized it's the exact same thing."   Nate's transition from flying C-17 cargo planes to working with Agile teams wasn't as jarring as you might expect. Flying missions that lasted 2-3 weeks with a crew of 5-7 people taught him the fundamentals of iterative work: daily alignment, continuous problem-solving, and regular reflection. The brief-execute-debrief cycle that every military pilot learns mirrors the sprint cadence that Agile teams follow. Time-boxing wasn't new to him either—when you're flying, you only have so much fuel, so deadlines aren't arbitrary constraints but physical realities that demand disciplined execution. In this episode with Christian Boucousis, we also discuss the brief-execute-debrief cycle in detail.  In this segment, we also refer to Cynefin, and the classification of complexity.  Alignment: The Real Purpose Behind Ceremonies "It's really important to make sure everyone understands why you're doing what you're doing. We don't brief, execute, debrief just because—we do it because we know that getting everybody on the same page is really important."   One of the most valuable insights Nate brings to his work with software teams is the understanding that Agile ceremonies aren't bureaucratic checkboxes—they're alignment mechanisms. The purpose of sprint planning, daily stand-ups, and retrospectives is to ensure everyone knows the mission and can adapt when circumstances change. Interestingly, Nate notes that as teams become more high-performing, briefings get shorter and more succinct. The discipline remains, but the overhead decreases as shared context grows. The Art of Knowing When to Interrupt "There are times when you absolutely should not interrupt an engineer. Every shoulder tap is a 15-minute reset for them to get back into the game. But there are also times when you absolutely should shoulder tap them."   High-performing teams understand the delicate balance between deep work and necessary communication. Nate shares an aviation analogy: when loadmasters are loading complex cargo like tanks and helicopters, interrupting them with irrelevant updates would be counterproductive. But if you discover that cargo shouldn't be on the plane, that's absolutely worth the interruption. This judgment—knowing what matters enough to break flow—is something veterans develop through high-stakes experience. Building this awareness across a software team requires:   Understanding what everyone is working on Knowing the bigger picture of the mission Creating psychological safety so people feel comfortable speaking up Developing shared context through daily stand-ups and retrospectives Why Veterans Make Exceptional Scrum Masters "I don't understand why every junior officer getting out of the military doesn't just get automatically hired as a Scrum Master. If you were to say what we want a Scrum Master to do, and what a junior military officer does—it's line for line."   Nate's company, Form100 Consulting, specifically hires former military officers and senior NCOs for Agile roles, often bringing them on without tech experience. The results consistently exceed expectations because veterans bring foundational leadership skills that are difficult to develop elsewhere: showing up on time, doing what you say you'll do, taking care of team members, seeing the forest through the trees. These intangible qualities—combined with the ability to stay calm, listen actively, and maintain integrity under pressure—make for exceptional servant leaders in the software development space. The Onboarding Framework for Veterans "When somebody joins, we have assigned everybody a wingman—a dedicated person that they check in with regularly to bounce ideas off, to ask questions."   Form100's approach to transitioning veterans into tech demonstrates the same principles they advocate for Agile teams. They screen carefully for the right personality fit, provide dedicated internal training on Agile methodologies and program management, and pair every new hire with a wingman. This military unit culture helps bridge the gap between active duty service and the private sector, addressing one of the biggest challenges: the expectation gap around leadership standards that exists between military and civilian organizations. Extreme Ownership: Beyond Process Management "To be a good Scrum Master, you have to take ownership of the team's execution. If the product requirements aren't good, it's a Scrum Master's job to help. If QA is the problem, take ownership. You should be the vessel and ownership of the entire process of value delivery."   One of Nate's core philosophies comes from Jocko Willink's Extreme Ownership. Too many Scrum Masters limit themselves to being "process people" who set meetings and run ceremonies. True servant leadership means owning everything that affects the team's ability to deliver value—even things technically outside your job description. When retrospectives devolve into listing external factors beyond the team's control, the extreme ownership mindset reframes the conversation: "Did we give the stakeholder the right information? Did they make a great decision based on bad information we provided?" This shift from blame to ownership drives genuine continuous improvement. Building Feedback Loops in Complex Environments "In the military, we talk about the OODA loop. Everything gets tighter, we get better—that's why we do the debrief."   Understanding whether you're operating in a complicated or complex domain (referencing the Cynefin framework) determines how tight your feedback loops need to be. In complex environments—where most software development lives—feedback loops aren't just for reacting to what happened; they're for probing and understanding what's changing. Sprint goals become essential because without knowing where you're headed, you can't detect when circumstances have shifted. The product owner role becomes critical as the voice connecting business priorities to team execution, ensuring the mission stays current even when priorities change mid-sprint. Recommended Resources Nate recommends the following books:  Team of Teams by General McChrystal Extreme Ownership by Jocko Willink   About Nate Amidon   Nate is a former Air Force combat pilot and founder of Form100 Consulting. He helps software teams embed leadership at the ground level, translating military principles into Agile practices. With a focus on alignment, accountability, and execution, Nate empowers organizations to lead from within and deliver real results in a dynamic tech landscape.   You can link with Nate Amidon on LinkedIn and learn more at Form100 Consulting.