Scrum Master Toolbox Podcast: Agile storytelling from the trenches

BONUS: Why Your Plan Is Lying to You — #NoEstimates, Throughput, and the Superstition of Project Management This episode is a cross-post from The EBFC Show, Felipe Engineer-Manriquez's podcast exploring Lean and Agile in construction. In this conversation, Felipe interviews Vasco about the #NoEstimates movement, throughput-based planning, and why traditional project management is still stuck in the middle ages of managing creative work. The Human Side of Scrum That the Scrum Guide Doesn't Cover "When you go into a daily meeting and you start looking at the people in that room, maybe they are the exact same people that were there yesterday, but the team is totally different. Somebody might have had a bad night's sleep, somebody might have had an argument with their spouse. These are human beings. These are not machines that you can just distribute work to." Vasco's path to agile coaching started with a realization that most practitioners eventually reach: the problems in software development aren't technological. They're about people — getting agreements, sharing information at the right time, making the collective brain of a team actually function. The Scrum Guide gives you organizing principles — how many meetings, who's in them — but it says almost nothing about the real-time feedback cycle between humans that makes or breaks a team. That's why the Scrum Master role exists: to be the lubricant for human interactions, to break down complex ideas into items the collective mind can process. It's the piece that makes Scrum work, and it's the piece that's hardest to teach. From Project Manager to #NoEstimates — The Bet That Changed Everything "The PM wanted 15 items per sprint, and the team said 'yeah, we can do 15.' I said, this is not gonna happen. The team had been delivering between five and eight items per sprint. I said, I'm gonna be positive — I'm gonna say seven. And no surprise, by the end of the sprint, they delivered seven." Vasco started as a project manager — and not the easy certification kind. He went through IPMA, which means six months of training, a four-hour written exam, and an expert interview, just for the entry level. Planning and estimating was the job. Then he ran his first Scrum project, specifically to prove it couldn't work. By the second month, he couldn't understand how anything else could work. The team delivered something to show every single sprint — something that never happened with traditional project management. The turning point came when he made a bet with a product manager: the PM needed 15 items per sprint, the team committed to 15, but historical throughput was 5-8 items. Reality delivered seven. That moment crystallized the #NoEstimates insight: we can't fight reality, but we can choose which seven items to deliver. Reality Is a Bitch — Why Linear Predictive Planning Fails "Never believe the plan. Or as in Scarface — never get high on your own supply. It's so unbelievable how project managers still today believe their freaking plans." At Nokia, Vasco managed a program of 500 people across 100 teams on four continents. No way to get everyone in a room. So he tracked system-level throughput — features delivered to integration per week. Six months into a twelve-month project, the data said they'd be at least six months late. He told the program manager: cut scope now. The program manager did what every PMI-trained program manager does — sent an email asking all 100 teams if they'd deliver on time. Every single team said yes. Nobody wants to be first to admit they're late. Twelve months in, they discovered they were six months late. The project got canceled. 500 people, millions of euros, all because somebody believed the plan. Linear predictive planning is useful for exploring what might be possible if nothing goes wrong. It is not reality. The only tool that reflects reality is throughput — the number of items completed per unit of time. Earned Value Management — George Orwell at His Best "It's not earned, it's spent. It's not value, it's cost. It's not management, it's just observation. Monty Python could not have come up with a better name." Felipe shares a story that mirrors the absurdity: an industrial project with a dedicated 35-person earned value management department. Before the meeting even started, the department head announced, "Let's all acknowledge that earned value management is more an art than a science." Their charts were made up, the contractor's charts were made up, and the goal of the meeting was to agree that the project would finish on time — regardless of what any data said. This is where traditional project management ends up when it disconnects from throughput: a $30 million scope addition with zero additional time, defended by charts that a mediocre attorney can invalidate in the first week of litigation. Felipe knows — he spent a year being cross-examined by forensic schedulers whose full-time job is proving that construction schedules are fic

Bhavin Shukla: The Adaptable Product Owner — How Progress Over Perfection Drives Real Value in Scrum In this episode, we refer to story mapping as a key tool for maintaining focus and alignment. The Great Product Owner: Embedding Prioritization as a Daily Discipline 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. "She had this section called 'Not Required Anymore.' Every time, it was a very subtle and a very respectful way of saying to the team: great idea, but the goals changed. We don't need it anymore." - Bhavin Shukla Bhavin describes a Product Owner who turned prioritization into a living discipline. She built a culture of co-creation where everyone contributed ideas to the backlog, but she also saw the biggest risk coming early: misalignment from siloed ideas. Her approach was to use story maps extensively in refinements and planning, communicating weekly with customers to collect feedback. When the direction changed — and it regularly did — she articulated the shift clearly: "Goals changed, here's what we're doing now." Her stroke of genius was a section on the story map called "Not Required Anymore," where deprioritized ideas landed respectfully. Nobody felt offended; they understood customers' needs had shifted. This created a culture where people kept contributing ideas courageously, knowing that even if priorities changed, their input was valued. The result was a team that could adapt without chaos, maintaining focus while embracing change. Self-reflection Question: How does your Product Owner communicate changes in direction? Is there a respectful, transparent mechanism for showing the team what's no longer needed — and why? The Bad Product Owner: The No-Feedback Product 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. "I was looking for those keywords — a change in priorities, a change in the roadmap. Those conversations were missing. And when I asked about the roadmap, I got crickets." - Bhavin Shukla Bhavin shares the story of a Product Owner who was brilliant at articulating value in the backlog — customer-centric stories, well-structured work. On the surface, everything looked great: goals were being met, the team was delivering. But something subtle was wrong. The roadmap never changed. Priorities never shifted. There were no conversations about customer feedback changing direction. When Bhavin got curious and asked to see the roadmap, he realized it was a static delivery plan, not a living document. The Product Owner wasn't collecting feedback from customers, so there was never a reason to adapt. The team was essentially building in a vacuum — shipping features nobody was validating. It's an anti-pattern that's easy to miss when the team is performing well on internal metrics but disconnected from real customer value. Self-reflection Question: Is your team's roadmap a living document that changes based on customer feedback, or has it become a static delivery plan? When was the last time a priority genuinely shifted based on what you learned from users? [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 Bhavin Shukla Bhavin joins us from Australia. Bhavin is driven by unlocking potential and helping people thrive in ambiguity through clarity, honesty, and discipline. He believes growth comes from truthful conversations, thoughtful experimentation, and learning from failure. Guided by ownership, confidence, kindness, and purpose, he focuses on what matters most to build meaningful progress for himself and others. You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: Why Scrum Master Success Means Confronting the Ugly Truth With Data 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 not always good vibes, good environment for us as Scrum Masters. For me, it's about confronting the reality, the ugly truth, which takes the team to tougher conversations, more constructive challenges." - Bhavin Shukla Bhavin shares a pivotal moment in his career that redefined what success means for a Scrum Master. He was working with a fantastic team — great culture, people who believed in quality, knowledge sharing, strong bonds. But sprint goals weren't being met, and stakeholders were constantly chasing the Product Owner and Scrum Master for answers. Bhavin got his hands dirty with the data: lack of clarity on work, context switching, patterns emerging. When he presented the data to the team, he was met with silence — a confronting kind of silence. The team was essentially saying, "We were happy. Why would you do this to us?" Bhavin's response was direct: going for coffees and laughing together isn't the whole job. If he wasn't showing them reality, he couldn't look at himself in the mirror. The team eventually used that data to raise their own voice, pointing out systemic issues with external vendors and organizational constraints. The data gave them a platform to speak truth — not as blame, but as discovery. Self-reflection Question: What conversations did you avoid this week that could have unlocked progress for your team? Are you bringing data to those conversations, or relying on vibes? Featured Retrospective Format for the Week: Newspaper Headline Retrospective Bhavin shares an unconventional use of the newspaper headline technique — typically used for roadmaps and vision — as a retrospective format. The idea is simple but powerful: ask the team to write the newspaper headline they want to see about themselves. What would the story say when they succeed? By authoring their own headline, the team takes ownership of the narrative — they define what success looks like, what must go right, and what risks could derail them. "Putting them in that newspaper headline, they authored the story. They own the accountability to make it successful," Bhavin explains. He also shares a second technique for Kanban teams under pressure: a rolling two-column whiteboard — "Frustration of the Day" and "Success of the Day" — with no meetings required, just real-time data capture that becomes a continuous retrospective, reviewed every 2-3 weeks. [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 Bhavin Shukla Bhavin joins us from Australia. Bhavin is driven by unlocking potential and helping people thrive in ambiguity through clarity, honesty, and discipline. He believes growth comes from truthful conversations, thoughtful experimentation, and learning from failure. Guided by ownership, confidence, kindness, and purpose, he focuses on what matters most to build meaningful progress for himself and others. You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: De-Scaling an Agile Organization — Removing Bureaucracy Without Losing Consistency 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. "Before people understand what needs to change, and how they need to adopt, what it means to them in their day-to-day work, and how it's going to help and add value — those conversations are missing." - Bhavin Shukla Bhavin brings a challenge many organizations face but few talk about openly: de-scaling. He's working with an organization that adopted a scaling framework for consistency — shared language, standardized tooling, uniform processes across business units. It worked for alignment, but it also created bureaucracy. Now leadership wants to become leaner and more nimble. The problem? The de-scaling itself is happening cookie-cutter style. Changes are being rolled out — new framework versions, new tools, flow metrics — without explaining the "why" to the people affected. The result is burnout and two parallel ecosystems running simultaneously: the old meeting structures people never abandoned, and the new Scrum events layered on top. Bhavin and his coaching peers ran a "Million Meeting Minutes" workshop, collecting data on how much time teams spend in meetings, what decisions get made (or don't), and who dominates conversations. The data revealed the overlap and waste. The experiment now is mapping those parallel systems and working with teams to understand which problems each structure actually solves — consolidating where possible while maintaining the consistency of language the organization genuinely needs. Self-reflection Question: In your organization, are there parallel meeting structures addressing the same problems? What would it take to map them and start a conversation about consolidation? [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 Bhavin Shukla Bhavin joins us from Australia. Bhavin is driven by unlocking potential and helping people thrive in ambiguity through clarity, honesty, and discipline. He believes growth comes from truthful conversations, thoughtful experimentation, and learning from failure. Guided by ownership, confidence, kindness, and purpose, he focuses on what matters most to build meaningful progress for himself and others. You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: The Hidden Cost of Always Saying Yes — How a Helpful Scrum Team Nearly Self-Destructed 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 sort of making me feel as a Scrum Master, like it's a slow self-destruction mode they are in. Good intentions, but it wasn't helping them, and that's something that they were not able to notice." - Bhavin Shukla Bhavin tells the story of a banking team that looked like every Scrum Master's dream on day one — humming, cracking jokes, in the zone. But underneath the positive energy, the data told a different story. Sprint commitments kept overflowing, tech debt was rising, P1 and P2 production issues were climbing, and decision latency was immense. The root cause? This team of genuinely helpful people couldn't say no. They wanted to help everyone who came to them, and that desire was slowly drowning them. No one was giving them feedback about the consequences — missed sprint goals were met with "that's okay, we'll do it next sprint." Bhavin introduced two simple tools: an anonymous happiness meter on the wall (rate 1-5, leave a note if below 3) and a gratitude wall. The data revealed the truth — the team was burning out, handling weekend incidents with no escalation path. Armed with this data, Bhavin coached the team on negotiation techniques: you don't have to be rude to say no, you can negotiate the yes, you can negotiate the no. In this segment, we talk about the importance of collecting regular data to surface hidden patterns, and the anti-pattern of teams operating without feedback on the consequences of their decisions. Self-reflection Question: Is your team's positive energy masking underlying problems? What data would help you discover whether good vibes are hiding unsustainable patterns? Featured Book of the Week: Make Work Visible by Dominica DeGrandis Bhavin recommends Make Work Visible by Dominica DeGrandis because it goes beyond values and principles to put them into practice in a grounded, system-focused way. "One clear message I get from that book is it's not the people who are the problem, it's the system that we need to work on to improve ways of working," Bhavin shares. The book introduces concepts like the five thieves of time, visualizing work, dependencies, and bottlenecks — connecting lean thinking, Kanban principles, and behavioral patterns into a practical guide for any Scrum Master looking to understand the systems their teams operate in. [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 Bhavin Shukla Bhavin joins us from Australia. Bhavin is driven by unlocking potential and helping people thrive in ambiguity through clarity, honesty, and discipline. He believes growth comes from truthful conversations, thoughtful experimentation, and learning from failure. Guided by ownership, confidence, kindness, and purpose, he focuses on what matters most to build meaningful progress for himself and others. You can link with Bhavin Shukla on LinkedIn.

Bhavin Shukla: When Protecting Your Agile Team Becomes the Barrier to Their Growth 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 perception I had was safe space means insulation from creating that transparency. It was not about protecting the teams. It was actually about giving them the voice, giving them the platform." - Bhavin Shukla Bhavin shares a story from early in his Scrum Master journey, working with two teams building a BI and regulatory platform in Australia. When he arrived, team morale was low — people buried in their screens, going for coffee alone, no healthy debates happening. His natural instinct kicked in: protect the team, help them gel, get the best out of them. But his coach asked a question that changed everything: "What's the balance between protecting the team and creating visibility and transparency?" Bhavin realized he'd been shielding the team from stakeholders, keeping ceremonies closed and conversations siloed. When the team opened up their reviews to stakeholders with clear expectations, something shifted. The backlog started changing based on real feedback, healthy tension built up, and the team started humming. The lesson was profound — creating a safe space doesn't mean insulating the team from reality. Psychological safety isn't the absence of difficult emotions; it's the freedom to have them without destructive patterns. By isolating the team, Bhavin had actually been undermining their trust and growth. Self-reflection Question: Are you protecting your team in ways that might actually be preventing them from building the stakeholder relationships and transparency they need to grow? [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 Bhavin Shukla Bhavin joins us from Australia. Bhavin is driven by unlocking potential and helping people thrive in ambiguity through clarity, honesty, and discipline. He believes growth comes from truthful conversations, thoughtful experimentation, and learning from failure. Guided by ownership, confidence, kindness, and purpose, he focuses on what matters most to build meaningful progress for himself and others. You can link with Bhavin Shukla on LinkedIn.

Iryna Stelmakh: The Firewall Product Owner, Turning PO Anti-Patterns Into Opportunities for Growth 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: Market-Oriented and Vision-Driven "Great product owners don't just manage backlog items — they own the product vision and make sure the team understands how their work creates real value." — Iryna Stelmakh Iryna describes the best product owners she's worked with through three qualities. First, they understand the market and the users deeply. Second, they can explain the business logic behind decisions — not just what to build, but why it matters. Third, they work closely with the team and treat them as partners in solving problems, not executors of tasks. The best PO Iryna worked with was responsible for sharing the business mindset, giving the team perspective and the possibility to contribute beyond the technical work. Everything was organized around a shared goal, and the team understood how their work created real value. As Vasco observes, when a PO just drops tasks without explaining why they matter, the team becomes "just a pair of hands." Great product owners create allegiance through understanding. Self-reflection Question: Does your product owner share enough business context that your team could independently suggest features or improvements — or are they only able to execute what they're told? The Bad Product Owner: The Firewall Who Blocks All Business Context "We were working without the product mindset, without the product vision." — Iryna Stelmakh Iryna shares the story of what she calls the Firewall Product Owner — a PO who constantly said "I need to go ask someone" for every decision, but never brought back answers. The result: backlog items lacked clarity, priorities changed frequently, and the team couldn't understand the real product direction. They were working without a product mindset or vision. As Vasco frames it, this PO wasn't just a proxy — they were a firewall, blocking the team from accessing any business context or market knowledge. The team couldn't reach the market representatives because they didn't even know who was on the other side. Iryna's approach to this kind of situation: escalate with suggestions, not just complaints. Turn problems into opportunities and extensions — propose bringing in a business analyst to support the PO, or suggest restructuring the communication between the business and technical sides. In her case, the client eventually recognized the problem and replaced the PO with someone who could actually bridge the gap. The new PO changed everything. In this episode, we also refer to the concept of turning problems into opportunities. Self-reflection Question: When your product owner is unable to provide timely answers, do you escalate with specific suggestions for improvement — or do you simply wait and hope things get better? [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 Iryna Stelmakh Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts. You can link with Iryna Stelmakh on LinkedIn.

Iryna Stelmakh: The Almost Invisible Scrum Master, Why Team Independence Is the Ultimate Success Metric 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. "A successful Scrum Master is almost invisible — not because they don't contribute, but because the team is no longer dependent on them for every decision." — Iryna Stelmakh Iryna offers a powerful definition of success for Scrum Masters: becoming almost invisible. Not because the Scrum Master isn't contributing, but because the system works — with or without them. The team takes ownership of delivery, solves problems collaboratively, and continuously improves its own process. Each team member can propose, vote, and suggest changes because the environment has a high level of trust. When that happens, Iryna explains, the Scrum Master becomes more of a system observer and catalyst rather than a daily driver. As Vasco adds, this perspective is valuable because it looks beyond personal metrics — it examines behaviors across all the interactions the Scrum Master facilitates: between the team and the product owner, between the team and stakeholders during reviews, and within the team itself. The Scrum Master role sits at the nexus of many interactions, and success means those interactions work well even when you step back. Self-reflection Question: If you were absent for a full sprint, would your team maintain the same quality of collaboration, decision-making, and delivery — or would things fall apart without you? Featured Retrospective Format for the Week: The Energy Retrospective Iryna shares her favorite retrospective format — one she calls the Energy Retrospective. Instead of the standard "what went well / what didn't" framing, it asks three questions: What gave us energy this sprint? What drained our energy? And what should we start, stop, or continue doing to keep our energy at the right level? This approach shifts the conversation from purely technical task problems to real human dynamics. As Iryna explains, closing technical tasks and resolving issues is important, but so is the wellness of the team. The Energy Retrospective creates space for both. She also notes that retrospective format should match the team: for open, trusting teams, a straightforward format works fine. But for new teams or teams with high resistance — those still in the forming stage where the Scrum Master isn't yet a trusted figure — she uses metaphorical approaches, like asking team members to pick pictures that represent their feelings about the sprint. Even a happy, sad, or frustrated monkey picture can surface insights that direct questions might not. [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 Iryna Stelmakh Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts. You can link with Iryna Stelmakh on LinkedIn.

Iryna Stelmakh: Fighting Agile Theater, When Organizations Adopt the Ceremonies But Not the Mindset 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. "Transparency can be uncomfortable, but without transparency, there is no real improvement." — Iryna Stelmakh Iryna brings a challenge she calls "Agile Theater" — organizations that implement all the visible parts of Agile (the ceremonies, the boards, the terminology) while the underlying mindset remains unchanged. Decisions stay centralized, transparency is avoided, and problems are hidden. As she puts it: "Teams go through the emotions of Agile without actually benefiting from it." But her real challenge goes deeper. Iryna shares a story about building trust with outsourcing clients. Five days into a new assignment on a project the company had worked on for over ten years, she received an email listing team members to be removed — with no explanation. It was a red flag: the absence of transparency signaled that the client relationship lacked the trust bridge needed for genuine collaboration. Iryna's response was characteristically direct. She organized a call with stakeholders and discovered the client operated on quarterly budget cycles — these cuts could happen every three months. Instead of accepting the loss, she shifted the cut team members to other projects within the same account, turning the problem into an opportunity. A QA engineer moved to another project that needed one. A developer and two others got upsold into a team extension. Nobody ended up on the bench. Then came the systemic fix: Iryna set up one-on-one meetings with each stakeholder across different divisions to stay informed in advance. Prevention over reaction — because, as she says, reactions cost more. Self-reflection Question: In your current engagement, do you have direct relationships with the people who make budget and staffing decisions — or would a surprise email catch you completely off guard? [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 Iryna Stelmakh Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts. You can link with Iryna Stelmakh on LinkedIn.

Iryna Stelmakh: When Communication Clarity Matters More Than Technical Complexity, A Healthcare Project That Fell Apart 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. "Communication clarity is more important than technical complexity, because if you do not understand, it's pretty hard to execute." — Iryna Stelmakh Iryna shares one of her most painful career stories — a project in the healthcare domain focused on cancer treatment research data. When she joined, she was managing around 9 projects simultaneously and agreed to take this one on the condition that a strong technical lead would own the technical direction. The project began with a critical misunderstanding: sales had communicated that the client needed a database redesign, but the client actually needed a migration to a different database type. Similar words, fundamentally different work. For three months, the team worked through research and discovery phases, trying to understand the actual problem. But communication gaps — compounded by language barriers between the Ukrainian development team and the US-based client — prevented them from identifying the real need in time. Iryna trusted the technical lead's reports that everything was on track. She relied instead of checking. Eventually, the client lost confidence and left. It remains the only project in her career she considers a genuine failure. The lesson cuts deep: teams must have people who can ask the right questions early. As Vasco observes, the root cause was implicit assumptions that were never discovered or explored by the different people involved. In this episode, we also talk about the importance of the monitoring and controlling phase in project management. Self-reflection Question: When you trust a team member's assessment that "everything is fine," what verification steps do you take to confirm that understanding is truly shared across all stakeholders? Featured Book of the Week: Team Topologies by Matthew Skelton and Manuel Pais Iryna recommends Team Topologies by Matthew Skelton and Manuel Pais as a book that changed how she thinks about Agile leadership. "Great agile leadership is not only about frameworks, but it's about communication, influence, and the ability to align people around shared goals," she explains. The book helped her understand that Agile isn't just about team process — it's about organizational structure, team boundaries, and responsibilities. She also recommends Never Split the Difference by Chris Voss for Scrum Masters who want to sharpen their communication and influence tactics. As Iryna puts it, communication is one of the most important skills a Scrum Master must have. [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 Iryna Stelmakh Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts. You can link with Iryna Stelmakh on LinkedIn.

Iryna Stelmakh: When "Agile" Becomes a License to Change Everything, The Cost of No Rules in Backlog Management 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. "For me, it was pretty hard to explain that Agile is about cost reduction, and not about cost increasing." — Iryna Stelmakh Iryna shares a story from one of her first projects as a Scrum Master, working with a client from Israel who saw Scrum as an open invitation to add anything to the backlog at any time. For this client, agility meant unlimited flexibility — the freedom to extend not just the product backlog but the sprint backlog, multiple times per sprint. As Vasco points out, this is a pattern many teams recognize: when there's no cost to disrupting a sprint, it becomes effortless to keep piling on work, destroying the very predictability that sprints are designed to create. Iryna struggled to push back. It was one of her first projects, and the client was confident in his approach. But the experience taught her a lasting lesson: the collaboration with external clients must start with an agreement about how the team works. That means explaining the methodology during the pre-sale phase, documenting it in the contract, and teaching the client the benefits of the process before the work begins. As she puts it, when she checked back with the sales and engagement teams, she realized nobody had set those expectations. She relied instead of checking — and paid the price. Once she held sessions with the client to explain how Scrum works and what it delivers, things shifted. New tasks went into the product backlog and were prioritized properly through refinement, not dumped into active sprints. Self-reflection Question: When was the last time you verified that your client or stakeholders truly understand how your team works — not just the label, but the actual rules and commitments? [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 Iryna Stelmakh Iryna Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts. You can link with Iryna Stelmakh on LinkedIn.

BONUS: Why 98% of Innovation Fails Before It Reaches a Single Customer Lorraine Marchand has spent three decades helping organizations innovate in environments where failure carries real consequences. In this episode, she shares the frameworks, stories, and hard-won lessons from her time at IBM Watson Health and beyond — starting with the summer her father handed her a stopwatch and a problem to solve at a diner. The Sugar Cube That Started It All "At the age of 12, I learned that problem solving was fun. It was really safe to experiment, and it turned out to be lucrative, because we earned some revenue and royalties from our sugar cube." Lorraine's innovation journey began with her father — a serial inventor who challenged his kids to identify and solve real problems. One summer, he took Lorraine and her brother to the Hot Shops Cafeteria in the Baltimore-Washington area with stopwatches, graph paper, and 3-color pens. Their assignment: figure out what was slowing down table turnover. After three days of observation and interviews with waitresses, busboys, and the manager, they discovered that sugar packets were the culprit — granules spilling over the table and floor during cleanup. Their solution, the Sugar Cube, was prototyped, sold to the manager, and eventually adopted across the chain — which later became the Marriott Corporation. The lesson stuck: innovation starts with observing problems close to the core, not chasing abstract ideas in a vacuum. Inside IBM Watson Health: Customer Co-Creation Over Engineering Brilliance "We have fallen in love with our solution. And we have not done our true problem-solving dissection and customer research to make sure that we're solving a problem that a customer wants to pay us to solve." At IBM Watson Health, Lorraine worked with 250 world-class engineers building solutions for the biggest names in life sciences — Johnson & Johnson, Pfizer, Sanofi, Medtronic. The process started with "garage sessions" where the team would tackle problems directly with a reference customer. But a recurring tension emerged: engineering would want to take what they learned from one customer, disappear into a room, build the perfect solution, and then hand it to marketing to sell. Lorraine had to repeatedly pull them back. A reference customer is an N of 1 — solving their problem doesn't guarantee a marketplace need. The discipline was to keep the customer in lockstep at every stage and continuously open the aperture, bringing in more customers and more feedback to validate that the solution would work at scale. The Innovation Mindset: Four Components That Matter "Thinking outside of the box means that you step outside of your box and you step into someone else's box." Lorraine identifies four components of the innovation mindset: problem solving, insatiable curiosity, embracing change, and welcoming diversity. The diversity piece is where most teams fall short. Homogenous groups become echo chambers — smart engineers designing from a technology perspective rather than a customer use perspective. The most innovative organizations Lorraine has worked with embrace cross-functional, multidisciplinary teams where engineering, marketing, and customer experience all have a seat at the table. No idea is a bad idea at the brainstorming stage — the down-selection comes later through structured evaluation. The Golden Ratio: Why 10% Drives 70% of Future Growth "Five years later, 70% of your growth will come from that 10% that you invested in innovation. So there's an inverse correlation to where you're investing and where that growth is going to come in the future." Lorraine points to the Golden Ratio framework popularized by Sergey Brin at Google: invest 70% in core business, 20% in adjacencies and new markets, and 10% in net new, transformative ideas that might not work out. The data across companies over the last 15 years consistently shows that the 10% bet on innovation generates the majority of future growth. Companies that invest 100% in core and a little in adjacency stay stuck in single-digit growth. Making innovation a strategic imperative — with dedicated budget and dedicated talent — is what separates companies that break out from those that stagnate. Experimentation Done Right: Problem Statement First, Prototype Fast "You have to have a really solid problem statement. It has to be clear, measurable, significant, and actionable." Good experimentation follows the scientific method. It starts with problem deconstruction — using first principles, the series of whys, or reframing to break down the problem until the statement is sharp enough to act on. From there, brainstorm solutions, down-select to the most promising one based on customer input, and build a minimal viable product. Lorraine emphasizes minimal — test the smallest feature possible, get it in front of customers quickly, capture the feedback, and loop it back into the next iteration. The continuous loop of learning is where r

BONUS: Why Every Organization Reinvents Silos—And What to Do About It Today we speak with Roland Flemm, co-creator of Org Topologies and co-author of 10X Org — Powered by Org Topologies. Roland has spent decades in the trenches—first as a developer, then in infrastructure, and finally as a Scrum Master, trainer, and organizational design consultant. In this episode, he explains why even teenagers with zero corporate experience instinctively create departmental silos, why making every team faster doesn't make the whole organization faster, and how leaders can use the Org Topologies map to see their organization as it actually is—not as the org chart says it should be. From Developer to Org Designer: Four Decades of Hitting the Same Wall "I felt many, many times the limitations of organizational structures stopping me from using my common sense to make people work together in a proper way." Roland's career spans over 40 years, starting as a developer in 1984. After a decade writing code and another decade in infrastructure, he moved into Scrum and agile coaching. But even as a highly effective Scrum Master, he kept hitting the same ceiling: local team improvements couldn't break through organizational boundaries. You could have wins with your team, but the moment you needed multiple teams to work together, someone higher up would shut it down. That frustration led him to Large-Scale Scrum (LeSS) by Bas Vodde and Craig Larman, which offered a more educated approach to multi-team collaboration—and eventually to co-creating Org Topologies as a way to help leaders see and change the structures that block real collaboration. Bas has been on the podcast to share his view on scaling Scrum with LeSS, listen to his episode here. The Hydrogen Car That Built Its Own Silos "If you don't think about your org design—the way that you want to collaborate—then something like this happens." One of the most striking stories in Roland's book comes from the Technical University of Delft, where student engineers were thrown together to build a hydrogen racing car. These were teenagers—no corporate experience, no boss who'd worked in a traditional company. And within weeks, they'd organized themselves into departmental silos, each sticking to their specialty. The mechanical engineers stayed on their turf, the electrical engineers on theirs. It was automatic. Roland traces this instinct deep: from school, where you choose a specialty; from the army and the church, where hierarchy is the default; from society itself, where "you're a plumber, so then we know what you are." The pattern of drawing boundaries and appointing leads when faced with complexity isn't corporate culture—it's human nature. And the problem isn't that it exists. The problem is that we don't know there are alternatives. The Ferrari Effect: Why Local Speed Creates Global Congestion "It's not that people choose to do fewer things. They just push more into the system because it can handle it. And that's where things go wrong." Roland uses a vivid analogy from the book: swapping every car on the road for a Ferrari doesn't fix traffic congestion. The same principle applies in organizations. Everyone feels faster individually—teams are delivering, sprints are moving—but the whole isn't getting better. The HealthCare.gov story makes the case dramatically: 55 vendor firms, $1.7 billion in spending, and on launch day, six people successfully enrolled. Then a ten-person cross-functional team fixed it in six weeks. Roland sees this pattern repeat in banks that adopt delivery-oriented structures like SAFe: they create value streams, but because they don't make hard choices about what not to do, the freed-up coordination capacity immediately fills with new demands. The congestion returns, just at a different level. In this segment, we talk about the Cynefin Framework. Three Topologies: Resource, Delivery, and Adaptive "The third topology is interesting—that's where the hands and the heads are merged. They're no longer separated." Roland walks through the Org Topologies map, each suited to different contexts: Resource Topology — The "hands" are separated from the "heads." Coordinators design and direct; specialists execute narrow, deep tasks. This works in environments with low variability and deep technical expertise—think ASML's university-level hardware engineers, or a bank's core transaction processing team running COBOL. The focus is on utilization of expensive specialists. Delivery Topology — Still has coordination overhead, but teams are cross-functional and can handle more complex problems end to end. A team owns the customer page and does design, testing, and deployment. This model favors speed of delivery, but breaks down when new work doesn't fit neatly onto existing value streams—like needing a retention initiative when no retention team exists. Work falls through the cracks. Adaptive Topology — The hands and heads merge. People who coordinate can also do the work, a

BONUS: Katie Anderson, Toyota's Real Secret Isn't the Tools — It's the Attitude Towards Learning That Changes Everything Katie Anderson joins us to explore the real engine behind Toyota's legendary success — and it's not what most people think. Drawing from her years living in Japan and her close relationship with 40-year Toyota veteran Isao Yoshino, Katie reveals why tools alone will never create lasting transformation. We explore the Doer Trap, the Telling Habit, and why hansei (deep reflection) is the most productive practice leaders keep skipping. The Only Secret to Toyota "The only secret to Toyota is its attitude towards learning. We don't even notice, and we take it for granted." Katie moved to Japan over 11 years ago as a continuous improvement practitioner and got to know Isao Yoshino, a Toyota leader with 40 years of experience. After repeatedly asking him what made Toyota so successful, he finally offered an almost offhand answer: "The only secret to Toyota is its attitude towards learning." The deeper insight? Even inside Toyota, they barely noticed it — it was so embedded in how they worked that they took it for granted. Katie explains that most organizations copy the visible tools — the kanban boards, the value streams, the process maps — but miss the invisible layer underneath: people development. Without that foundation of learning, tools lead to project-based improvements that never sustain. The secret sauce is the quality of how organizations develop people to learn, contribute, problem-solve, and innovate. That system of people development underlies the system of process improvement, and without it, organizations stay stuck in what Katie calls "constant whack-a-mole" — fixing the same problems year after year. The Doer Trap and the Five Archetypes "The doer trap is when we're stepping in and doing things, or owning things that aren't ours to own." Katie identifies five archetypes of the Doer Trap that leaders and change agents fall into. The Hero is the firefighter who jumps from crisis to crisis — it feels good to save the day. The Rescuer can't stand watching people struggle, so they give answers too early, robbing others of the chance to develop their own thinking. The Magician works behind the scenes, subtly shaping outcomes without others' input. The Pair of Hands just jumps in and gets it done because "it's faster." And the Surrogate Leader fills a leadership vacuum that isn't theirs to fill — so when they move on, everything fades away. Each archetype feels productive in the moment but prevents the organization from building real capability. The shift Katie advocates is from command-based leadership to influence-based leadership: still setting direction, but creating the conditions for others to find the way there. Break the Telling Habit "The telling habit is when we're giving our answer instead of holding space for someone else to develop their answer." Closely linked to the Doer Trap, the Telling Habit is about how leaders — and change agents — default to providing their own ideas, suggestions, and solutions instead of creating space for others to think. Katie sees this show up even in well-intentioned coaches and consultants. The antidote aligns with what David Marquet calls intent-based leadership: instead of telling people what to do, you validate their thinking and ask questions when you spot gaps. Katie frames good leadership through three responsibilities drawn from Mr. Yoshino's example: set the direction (what goal needs to be achieved), provide support (create the capability and conditions for people to succeed), and develop yourself (because if you can't see the system, you can't help others see it either). Learning as Sustainable Competitive Advantage "We need to set up experiments. And experiments are fundamentally based on an attitude towards learning." Katie argues that as complexity increases, no single leader can hold all the answers. Organizations need to harness what you might call the collective brain — the hive mind of the team — and that requires an experimental mindset. This connects directly to Jeffrey Liker's concept of organizations as socio-technical systems: it's never just the technical processes that matter, but how people interact, influence each other, and navigate the formal and informal structures that actually get things done. Katie's advice to change leaders: develop your own systems thinking skills first. Help leaders see what's really driving behavior — reward structures, people development gaps, the difference between compliance and genuine capability. Everything starts with you. Hansei — Reflection as the Most Productive Practice "The study and adjust part of the cycle is where the learning happens. But we keep cutting it because the doing part feels more productive." Hansei — Japanese for deep self-reflection — goes far beyond the typical retrospective. Where most teams do a surface-level "what worked, what didn't, let's move on," hansei a

BONUS: How to Build Teams That Think, Own, and Execute Without Burnout What if the problem isn't your people—but how your leadership shows up? In this episode, Sid Jashnani unpacks how Agile thinking, EOS (the Entrepreneurial Operating System), and his DELTA Delegation Ladder can help leaders build teams that truly own outcomes, execute without micromanagement, and grow the business—without burning out leaders or teams. The Breaking Point: When Smart People Don't Own Outcomes "I realized that I was the system, I was the bottleneck. And I was the one orchestrating everything. And if I were to step away for just going for dinner with my family, I would still get a call from someone." Around 2014, Sid was running a thriving systems integration company with great people—people he trusted and loved working with. But they weren't owning outcomes. They were busy, but not always productive. Every decision fell back on Sid, and when the calls kept coming during family dinners, he started responding with irritation and sarcasm—a leadership pattern he knew was unsustainable. That moment of self-awareness became the catalyst for change. Sid realized the problem wasn't his team's competence; it was his inability to get them aligned, accountable, and clear on expectations. That's when he discovered EOS—a business operating system created by Gino Wickman that orchestrates how you set priorities, run meetings, connect with your team, and track your numbers. Over the next few years, implementing EOS across his organization brought the clarity, accountability, and discipline his business needed. Where Agile and EOS Overlap: Trust Through Structure "The real overlap is trust through structure. If there's no structure, then I'm not accountable to you. I can do whatever." Sid sees deep parallels between Agile and EOS. Both are allergic to hero culture. Both push decisions as close to the work as possible. Both rely on cadence—sprints, weekly meetings, daily stand-ups—to create rhythm without micromanagement. And both use visibility, numbers, and scorecards to keep teams aligned. But the real overlap, as Sid frames it, is trust through structure. In EOS, teams are structured through an accountability chart: who owns what outcome, who reports to whom, and how success is defined for each role. Without that structure, accountability becomes optional, and without accountability, trust never forms. Sid connects this directly to Patrick Lencioni's The Five Dysfunctions of a Team—where trust sits at the base of the pyramid, enabling healthy conflict, commitment, accountability, and ultimately results. The key anti-pattern Sid warns about: people picking only the comfortable parts of a system and relaxing the parameters so much that it becomes "SOS—Sid's Operating System—which is just an emergency call for help." In this episode, we also refer to Traction, by Gino Wickman, a foundational book for Sid in his career. The DELTA Delegation Ladder: From Command-and-Control to Co-Founder Mode "Delegation fails because leaders skip levels." Sid introduces his DELTA Delegation Ladder—a five-level framework for understanding where your team members sit and how to delegate accordingly: D — Do as I say: Pure execution of instructions. Sid notes this level is increasingly being replaced by AI. E — Explore the possible solutions: Research and present options, but the leader still makes the decision. Also increasingly delegable to AI. L — Lead with a recommendation: The entry point for real human value. The person researches, forms a hypothesis, and recommends a path forward. Sid considers this the minimum hiring bar. T — Take action with oversight: The person takes decisions and acts, keeping the leader in the loop. Trust has been built through coaching and mentoring. A — Autonomous execution: Co-founder mode. The person owns the outcome end-to-end. Full trust, full ownership. Delegation fails when leaders skip levels—expecting someone at "D" to operate at "A." It also fails when leaders abdicate rather than delegate, throwing someone into a role without investing time in coaching, clarifying expectations, or showing them what "great" looks like. As Sid puts it: delegation only works if you spend time with the person you're delegating to. Remote Teams: Written Clarity Beats Verbal Alignment "Trust comes from predictability, not proximity. I can be 1,000 miles across the world from you and trust you, because I can predict what your actions are gonna be." For distributed and cross-timezone teams, Sid's non-negotiables are clear: get good at writing, and over-communicate. Written clarity beats verbal alignment every time, especially across cultures where tone and directness vary widely—from British politeness to Dutch directness. Over-communication isn't a flaw; it's the standard for remote teams. Without it, accountability vanishes and culture erodes. Sid points out that trust in remote settings comes from predictability—can you predict that someone w

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 foundationa

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