Beyond AI Code Assistants: How Moldable Development Answers Questions AI Can't | Tudor Girba
Scrum Master Toolbox Podcast: Agile storytelling from the trenches6 Okt

Beyond AI Code Assistants: How Moldable Development Answers Questions AI Can't | Tudor Girba

AI Assisted Coding: Beyond AI Code Assistants: How Moldable Development Answers Questions AI Can't With Tudor Girba

In this BONUS episode, we explore Moldable Development with Tudor Girba, CEO of feenk.com and creator of the Glamorous Toolkit. We dive into why developers spend over 50% of their time reading code—not because they want to, but because they lack the answers they need. Tudor shares how building contextual tools can transform software development, making systems truly understandable and enabling decisions at the speed of thought.

The Hidden System: A Telco's Three-Year Quest

"They had a system consisting of five boxes, but they could only enumerate four. If this is your level of awareness about what is reality around you, you have almost no chance of systematically affecting that reality."

Tudor opens with a striking case study from a telecommunications company that spent three years and hundreds of person-years trying to optimize a data pipeline. Despite massive effort and executive mandate, the pipeline still took exactly one day to process data—no improvement whatsoever. When Tudor's team investigated, they asked for an architecture diagram. The team drew four boxes representing their system. But when Tudor's team started building tools to mirror this architecture back from the actual code, they discovered something shocking: there was an entire fifth system between the first and second boxes that nobody knew existed. This missing system was likely the bottleneck they'd been trying to optimize for three years.

Why Reading Code Doesn't Scale

"Developers spend more than 50% of their time reading code. The problem is that our systems are typically larger than anyone can read, and by the time you finish reading, the system has already changed many times."

The real issue isn't the time spent reading—it's that reading is the most manual, least scalable way to extract information from systems. When developers read code, they're actually trying to answer questions so they can make decisions. But a 250,000-line system would take one person-month to read at high speed, and the system changes constantly during that time. This means everything you learned yesterday becomes merely a hypothesis, not a reliable answer. The fundamental problem is that we cannot perceive anything in a software system except through tools, yet we've never made how we read code an explicit, optimizable activity.

The Context Problem: Why Generic Tools Fail

"Software is highly contextual, which means we can predict classes of problems people will have, but we cannot predict specific problems people will have."

Tudor draws a powerful parallel with testing. Nobody downloads unit tests from the web and applies them to their system—that would be absurd. Instead, we download test frameworks and build tests contextually for our specific system, encoding what's valuable about our particular business logic. Yet for almost everything else in software development, we download generic tools and expect them to work. This is why teams have tens of thousands of static analysis warnings they ignore, while a single failing test stops deployment. The test encodes contextual value; the generic warning doesn't. Moldable Development extends this principle: every question about your system should be answered by a contextual tool you build for that specific question.

Tools That Mirror Your Mental Model

"Whatever you draw on the whiteboard—that's your mental model. But as soon as the system exists, we want the system to mirror you back that thing. We make it the job of the system to show our mental model back to us."

When someone draws an architecture diagram on a whiteboard, they're not documenting the system—they're documenting their beliefs about the system. The diagram represents wishes when drawn before the system exists, but beliefs when drawn after. Moldable Development flips this: instead of humans reading code and creating approximations, the system itself generates the visualization directly from the actual code. This eliminates the layers of belief and inference. Whether you're looking at high-level architecture, data lineage across multiple technologies, performance bottlenecks, or business domain structure, you build small tools that extract and present exactly the information you need from the system as it actually is.

The Test-Driven Development Parallel

"Testing was a way to find some kind of class of answers. But there are many other questions we have, and the question is: is there a systematic way to approach arbitrary questions?"

Tudor explains that Moldable Development applies test-driven development principles to all forms of system understanding. Just as we write tests after we understand the functionality we need, we build visualization and analysis tools after we understand the questions we need answered. Both approaches share key characteristics: they're built contextually for the specific system, created by developers during development, and composed of many small tools that collectively model the system. The difference is that TDD focuses on functional decomposition and known expectations, while Moldable Development addresses architecture, security, domain structure, performance, and any other perspective where functional tests aren't the most useful decomposition.

From Thousands of Features to Thousands of Tools

"In my development environment, I don't have features. I have thousands of tools that coexist. Development environments should be focused not on what exists out of the box, but on how quickly you can create a contextual tool."

Traditional development environments offer dozens of features—buttons, plugins, generic views. But Moldable Development environments contain thousands of micro-tools, each answering a specific question about a specific system. The key is making these tools composable and fast to create. Rather than building monolithic tools that try to handle every scenario, you build small inspectors that show one perspective on one object or concept. These inspectors chain together naturally as you drill down from high-level questions to detailed investigations. You might have one inspector showing test failures grouped by exception type, another showing PDF document comparisons, another showing cluster performance, and another showing memory usage—all coexisting and available when needed.

The Real Bottleneck To Learning A System: Time to the Next Question

"Once you do this, you will see that the interesting bottleneck is in the time to the next interesting question. This is by far the most interesting place to be spending energy."

When you commoditize access to answers through contextual tools, something remarkable happens: the bottleneck shifts from getting answers to asking better questions. Right now, because answers come so slowly through manual reading and analysis, we rarely exercise the skill of formulating good questions. We make decisions based on gut feelings and incomplete data because we can't afford to dig deeper. But when answers arrive at the speed of thought, you can explore, follow hunches, test hypotheses, and develop genuine insight. The conversation between person and system becomes fluid, enabling decision-making based on actual evidence rather than belief.

Moldable Development in Practice: The Lifeware Case

"They are investing in software engineering as their competitive advantage. They have 150,000 tests that would take 10 days to run on a single machine, but they run them in 16 minutes distributed across AWS."

Tudor shares a powerful case study of Lifeware, a life insurance software company that was featured in Kent Beck's "Test-Driven Development by Example" in 2002 with 4,000 tests. Today they have 150,000 tests and have fully adopted Moldable Development as their core practice. Their business model is remarkable: they take data from insurance companies, throw away the old systems, and reverse-engineer new systems by TDD-ing the business—replaying history to produce pixel-identical documents. They've deployed Glamorous Toolkit as their sole development environment across 100+ developers. Their approach demonstrates that Moldable Development isn't just a research concept but a practical competitive advantage that scales to large teams and complex systems.

Why AI Doesn't Solve This Problem

"When you ask AI, you will get exactly the same kind of answers. The answer comes quickly, but you will not know whether this is accurate, whether this represents the whole thing, and you definitely do not have an explanation as to why the answer is the way it is."

In the age of AI code assistants, it might seem like language models could solve the problem of understanding systems. But Tudor explains why they can't. When you ask an AI about your architecture, you get an opinion—fast but unverifiable. Just like asking a developer to draw the architecture on a whiteboard, you receive filtered information without knowing if it's complete or accurate. Moldable Development, by contrast, extracts answers deterministically from the actual system. Software systems have almost no ambiguity in meaning—they're mathematical, not linguistic. We don't need probabilistic interpretation of source code; we need precise extraction and presentation. The tools you build give you not just answers but explanations of how those answers were derived from the actual system state.

Scaling Through Language, Not Features

"You need a new kind of development environment where the goal is to create tools much quicker. You need some sort of language in which to express development environments."

The technical challenge of Moldable Development is enabling thousands of tools to coexist productively. This requires a fundamentally different approach to development environments. Instead of adding features—buttons and menu items that quickly become overwhelming—you need a language for expressing tools and a system for composing them. Glamorous Toolkit demonstrates this through its inspector architecture, where any object can define custom views that appear contextually. These views compose naturally as you navigate through your investigation, reusing earlier perspectives while adding new ones. The environment becomes a medium for tool creation, not just a collection of pre-built features.

Making the Invisible Visible

"We cannot perceive anything in a software system except through a tool. If that's so important, then the ability to control that shape is probably kind of important too."

Software has no inherent shape—it's just data. Every perception we have of it comes through some tool that renders it into a form we can reason about. This means tools aren't nice-to-have accessories; they're fundamental to our ability to work with software at all. The text editor showing code is a tool. The debugger showing variables is a tool. But these are generic tools built once and reused everywhere, which means they show generic perspectives. What if we could control the shape of our software as easily as we write it? What if the system could show us exactly the view we need for exactly the question we have? That's the promise of Moldable Development.

About Tudor Girba

Tudor Girba is CEO of feenk.com and creator of Moldable Development. He leads the team behind Glamorous Toolkit, a novel IDE that helps developers make sense of complex systems. His work focuses on transforming how teams understand, navigate, and modernize legacy software through custom, insightful tools. Tudor and Simon Wardley are writing a book about Moldable Development which you can get at: https://moldabledevelopment.com/, and read more about in this Medium article.

You can link with Tudor Girba on LinkedIn.

Avsnitt(200)

The Marathon Mindset—Building Agile Teams That Last Beyond Sprint Deadlines | Shawn Dsouza

The Marathon Mindset—Building Agile Teams That Last Beyond Sprint Deadlines | Shawn Dsouza

Shawn Dsouza: The Marathon Mindset—Building Agile Teams That Last Beyond Sprint Deadlines 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. Shawn defines himself as a "people-first Scrum Master" who measures success not through metrics but through daily interactions and team growth. He contrasts two teams: one that hit deadlines but lacked collaboration (unsustainable success) versus another that struggled with deadlines but excelled in conversations and continuous improvement (sustainable growth). For Shawn, protecting deep work and fostering genuine team collaboration indicates true success. He emphasizes that product development is a marathon, not a sprint, and warns that lack of meaningful conversations will inevitably lead to team problems. In this segment, we refer to the book Clean Language by Sullivan and Rees. Featured Retrospective Format for the Week: Sprint Awards Shawn champions the Sprint Awards retrospective format, moving beyond viewing retrospectives as just another Scrum event to recognizing them as critical team development opportunities. In this format, team members give awards to colleagues for various contributions during the sprint, with each award recipient explaining why they were chosen. Shawn prefers face-to-face, offline retrospectives and always starts with ice breakers to gauge how the team feels—whether they feel heard and connected. He believes in experimenting with different retrospective formats since no single approach works for every situation. Self-reflection Question: How do you balance achieving deliverable outcomes with building sustainable team relationships and collaboration patterns? [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 Shawn Dsouza Shawn, a Mangalore native and Software Technology postgraduate from AIMIT, brings 8+ years of IT expertise, excelling as a Scrum Master fostering innovation and teamwork. Beyond technology, he leads SPARK, a social service initiative, and pursues his passion as an aquarist, nurturing vibrant aquatic ecosystems with dedication. You can link with Shawn Dsouza on LinkedIn.

18 Sep 13min

From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach | Shawn Dsouza

From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach | Shawn Dsouza

Shawn Dsouza: From AI Anxiety to AI Advantage: A Scrum Master's Experimental Approach 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. Shawn faces the massive AI transformation currently reshaping the tech industry, acknowledging both its benefits and the fear it creates among professionals questioning their relevance. In his organization, he witnesses AI delivering wonders for some teams while others struggle and lose projects. Rather than viewing AI as an overwhelming wave, Shawn advocates for experimentation. He shares practical examples, like helping a Product Owner streamline story creation from Excel to JIRA using AI tools, and leveraging MIRO AI for team collaboration. His approach focuses on identifying friction points where AI experiments could add value while keeping conversations centered on possibilities rather than fears. Self-reflection Question: Instead of fearing technological changes like AI, how can you create small experiments to explore new possibilities and reduce friction in your current work processes? [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 Shawn Dsouza Shawn, a Mangalore native and Software Technology postgraduate from AIMIT, brings 8+ years of IT expertise, excelling as a Scrum Master fostering innovation and teamwork. Beyond technology, he leads SPARK, a social service initiative, and pursues his passion as an aquarist, nurturing vibrant aquatic ecosystems with dedication. You can link with Shawn Dsouza on LinkedIn.

17 Sep 13min

The Database Migration Disaster— Why Software Development Teams Need Psychological Safety | Shawn Dsouza

The Database Migration Disaster— Why Software Development Teams Need Psychological Safety | Shawn Dsouza

Shawn Dsouza: The Database Migration Disaster— Why Software Development Teams Need Psychological Safety 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. Shawn worked with a skilled team migrating a database from local to cloud-based systems, supported by a strong Product Owner. Despite surface-level success in ceremonies, he noticed the team avoided discussing difficult topics. After three months of seemingly smooth progress, they delivered to pre-production only to discover 140 critical issues. The root cause? Unspoken disagreements and tensions that festered beneath polite ceremony facades. The situation deteriorated to the point where a senior engineer quit, teaching Shawn that pausing to address underlying issues doesn't cost time—it builds sustainability. In this segment, we refer to the episodes with Mahesh Jade, a previous guest on the Scrum Master Toolbox podcast. Featured Book of the Week: The Advice Trap by Michael Bungay Stanier Shawn discovered this transformative book when he realized he was talking too much in team meetings despite wanting to add value. The Advice Trap revealed how his instinct to give advice, though well-intentioned, was actually self-defeating. The book taught him to stay curious longer and ask better questions rather than rushing to provide solutions. As Shawn puts it, "The minute you think you have the answer you stop listening"—a lesson that fundamentally changed his coaching approach and helped him become more effective with his teams. Self-reflection Question: When working with teams, do you find yourself jumping to advice-giving mode, or do you stay curious long enough to truly understand the underlying challenges? [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 Shawn Dsouza Shawn, a Mangalore native and Software Technology postgraduate from AIMIT, brings 8+ years of IT expertise, excelling as a Scrum Master fostering innovation and teamwork. Beyond technology, he leads SPARK, a social service initiative, and pursues his passion as an aquarist, nurturing vibrant aquatic ecosystems with dedication. You can link with Shawn Dsouza on LinkedIn.

16 Sep 13min

When Scrum Masters Forget to Listen - A Team Trust Crisis in Agile Implementation | Shawn Dsouza

When Scrum Masters Forget to Listen - A Team Trust Crisis in Agile Implementation | Shawn Dsouza

Shawn Dsouza: When Scrum Masters Forget to Listen - A Team Trust Crisis in Agile Implementation 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. Shawn shares a powerful lesson about the importance of listening before implementing. Working with a young, talented team drowning in firefighting, he rolled out Scrum in "full" without taking time to understand the team's context. Going through the motions of Scrum ceremonies without genuine team ownership led to dropping energy levels and lost trust. The turning point came when Shawn realized the team had lost faith in his approach, prompting him to rebuild the process collaboratively with team ownership at its core. This story highlights how good intentions can backfire when we prioritize frameworks over people. Self-reflection Question: Before implementing any new process or framework, how do you ensure you truly understand your team's current challenges and context rather than jumping straight to solutions? [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 Shawn Dsouza Shawn, a Mangalore native and Software Technology postgraduate from AIMIT, brings 8+ years of IT expertise, excelling as a Scrum Master fostering innovation and teamwork. Beyond technology, he leads SPARK, a social service initiative, and pursues his passion as an aquarist, nurturing vibrant aquatic ecosystems with dedication. You can link with Shawn Dsouza on LinkedIn.

15 Sep 14min

Problems vs. Solutions: The Great Product Owner Distinction | Bernie Maloney

Problems vs. Solutions: The Great Product Owner Distinction | Bernie Maloney

Bernie Maloney: Problems vs. Solutions: The Great Product Owner Distinction 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: The Strategic Problem Solver Bernie describes an exemplary Product Owner from a stealth program sponsored by a CTO, where the company needed to create new intellectual property. This Great Product Owner understood that Agile operates in three dimensions: most organizations only focus on outputs and delivery (first dimension), some reach outcomes (second dimension), but the truly great ones operate in the third dimension of strategic or business agility - defining problems worth solving. This Product Owner knew that high-performing teams need to understand what problem is worth solving rather than just receiving solutions to build. They embraced the Mobius loop approach, focusing on discovering the right problems rather than jumping straight to solutions. In this segment, we refer to the Mobius Loop, and to Steve Blank's work on the job of a startup. We also refer to the episode with Elliott Parker on the critical importance of the "startup mindset" to foster innovation in larger organizations. The Bad Product Owner: The Backlog Jockey with Authority Issues Bernie identifies the anti-pattern of Product Owners being treated as mere "backlog jockeys" by their organizations, which forces them into solution-building mode rather than problem-solving mode. These Product Owners don't understand the importance of saying "no" and lack clarity about intent and goals. The worst case Bernie encountered was a team manager who also served as Product Owner, wielding positional authority that shut down team communication. This person would interrupt daily scrums, causing teams to revert to waiting for direction rather than self-organizing. The combination of unclear intent and positional authority creates a toxic environment that destroys team autonomy and psychological safety. Self-reflection Question: Is your Product Owner focused on defining problems worth solving, or are they primarily managing a backlog of predetermined solutions? [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 Bernie Maloney Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun. You can link with Bernie Maloney on LinkedIn, and visit Bernie's website and YouTube Channel.

12 Sep 19min

From Permission-Seeking to Forgiveness-Begging—Agile Team Evolution in Self-Management | Bernie Maloney

From Permission-Seeking to Forgiveness-Begging—Agile Team Evolution in Self-Management | Bernie Maloney

Bernie Maloney: From Permission-Seeking to Forgiveness-Begging—Agile Team Evolution in Self-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. Bernie defines success for Scrum Masters as creating teams that can thrive and do their best work independently. His ultimate goal is to make himself unnecessary - developing self-directing teams that step out of waiting for direction and instead seek permission or even beg forgiveness when needed. Using the "Circles and Soup" framework, Bernie helps teams stretch their circles of influence and control. He recognizes that every manager wants teams to succeed but may lack the necessary tools, making it crucial for Scrum Masters to coach managers as well. Bernie recommends building a backlog of organizational impediments and focusing on the top priority that will move the ball forward most effectively. Featured Retrospective Format for the Week: Sailboat Bernie champions the Sailboat retrospective format for its simplicity and adaptability. While the basic format is straightforward, he appreciates that you can add layers of complexity as needed. Bernie tends to keep retrospectives simple and also mentions the "What the Duck?" technique as another valuable retrospective tool. He suggests incorporating creative elements like having people build LEGO representations of what they're discussing, which helps teams visualize and engage with concepts more effectively. To know more about LEGO Serious Play, check out the Serious Play book. In this segment, we also refer to Dissociation in Psychology, which helps with "third position" coaching/thinking, and Bernie's video on creative retrospective formats. Self-reflection Question: How are you measuring whether your teams are becoming more self-directing, and what specific behaviors indicate they're ready to operate with less guidance? [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 Bernie Maloney Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun. You can link with Bernie Maloney on LinkedIn, and visit Bernie's website and YouTube Channel.

11 Sep 14min

Mastering Complexity Through Systems Thinking and NLP Coaching | Bernie Maloney

Mastering Complexity Through Systems Thinking and NLP Coaching | Bernie Maloney

Bernie Maloney: Mastering Complexity Through Systems Thinking and NLP Coaching 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. Bernie addresses the constant challenge of mid-sprint changes by asking the crucial question: "what do you want to trade in for that new request?" His approach centers on recognizing that everyone is trying to do their best with what they have, using techniques from NLP and the three coaching positions to help people see the whole system. Bernie emphasizes rapport building as a key skill for Scrum Masters and warns against the anti-pattern of becoming judgmental when challenges arise. He advocates for moving from a plan-and-predict mentality to sense-and-respond thinking, highlighting the importance of conducting retrospectives once challenges are solved. Bernie's coaching philosophy revolves around helping people step into the "third position" - a dissociated perspective that enables better problem-solving and systems thinking. In this episode, we refer to Neuro-linguistic Programming (NLP), and to Instant Rapport by Michael Brooks, a primer on NLP. We also refer to the plan-and-predict vs sense-and-respond mentality. Self-reflection Question: How effectively are you helping your teams and stakeholders see the whole system when challenges arise, rather than just focusing on individual pain points? [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 Bernie Maloney Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun. You can link with Bernie Maloney on LinkedIn, and visit Bernie's website and YouTube Channel.

10 Sep 18min

The Triangulation Technique—Coaching Agile Teams Through Challenges | Bernie Maloney

The Triangulation Technique—Coaching Agile Teams Through Challenges | Bernie Maloney

Bernie Maloney: The Triangulation Technique—Coaching Agile Teams Through Challenges 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. Bernie identifies critical patterns that cause teams to self-destruct, with lack of clarity about intention being the most common culprit. When teams are treated as mere "task workers" without clear vision, strategy, or goals, they become depressed and directionless. Some teams seek forgiveness after failed experiments, while others get stuck seeking permission without taking enough self-leadership. Bernie emphasizes that waiting for direction is fundamentally self-destructive behavior, and Scrum Masters must create safety for teams to reach high performance. He introduces the coaching technique of triangulation, where problems become a third point that coach and coachee examine together, side by side, rather than facing each other in opposition. In this segment, we talk about "What the Duck", a Lego Serious Play workshop. Featured Book of the Week: Start with Why by Simon Sinek Bernie champions "Start with Why" by Simon Sinek as essential reading for Scrum Masters working to transform team culture. He explains that compelling stories are how leaders truly influence others, following the sequence of Attention-Emotion-Reason. This book helps Scrum Masters understand that their job fundamentally involves changing culture, and leaders must demonstrate the change they want to see. Bernie connects this to the broader leadership challenge of developing coaching and mentoring skills within organizational structures. During this segment, we also refer to the following books: Drive, By Dan Pink Change the Culture, Change the Game, by Connors et al. The Secret Language of Leadership, by Denning Too Many Bosses, Too Few Leaders, by Peshawaria The Geek Way, by McAfee Right Kind of Wrong, by Edmondson Self-reflection Question: What patterns of self-destructive behavior might your teams be exhibiting, and how could you help them move from seeking permission to taking ownership? [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 Bernie Maloney Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun. You can link with Bernie Maloney on LinkedIn, and visit Bernie's website and YouTube Channel.

9 Sep 16min

Populärt inom Politik & nyheter

aftonbladet-krim
svenska-fall
motiv
p3-krim
flashback-forever
fordomspodden
rss-viva-fotboll
rss-krimstad
aftonbladet-daily
rss-sanning-konsekvens
rss-vad-fan-hande
spar
rss-krimreportrarna
rss-frandfors-horna
blenda-2
olyckan-inifran
dagens-eko
krimmagasinet
rss-flodet
rss-expressen-dok