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

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.

Jaksot(200)

From Waterfall to Agile—A Multi-Level Change Strategy | Pascal Papathemelis

From Waterfall to Agile—A Multi-Level Change Strategy | Pascal Papathemelis

Pascal Papathemelis: From Waterfall to Agile—A Multi-Level Change Strategy 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. Pascal describes a successful agile transformation where he collaborated with a fellow coach in the IT department of a large organization with a waterfall history and heavy documentation-driven processes. The two coaches worked together effectively, sharing information and scouting for opportunities to take action. They began with an assessment and discussions across IT, business, and management levels to understand the current state. Using the Cynefin framework to understand complexity, they conducted a two-day workshop to introduce Agile vocabulary, covering concepts like Push/Pull and process waste. The coaches operated at multiple levels simultaneously - working strategically with leadership who typically pushed excessive work to the organization, while also helping teams visualize their processes and clarify priorities. At the team level, they acted as Scrum Masters to demonstrate the role while mentoring the actual Scrum Master through one-on-one sessions. They also supported the Product Owner in understanding their role and used story maps to help visualize and organize work effectively. Self-reflection Question: How might collaborating with another coach or change agent amplify your effectiveness in leading organizational transformation? [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 Pascal Papathemelis Pascal is an Agile & Professional Coach that wants to make a positive impact to the people working with. Coaching in Finnish, German and English language. Focus areas are human factors, outcomes, effectiveness, flow, decision making, clarity and constant improvement. You can link with Pascal Papathemelis on LinkedIn.

9 Heinä 15min

The Hidden Cost of Removing Scrum Masters from High-Performing Teams | Pascal Papathemelis

The Hidden Cost of Removing Scrum Masters from High-Performing Teams | Pascal Papathemelis

Pascal Papathemelis: The Hidden Cost of Removing Scrum Masters from High-Performing Teams 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. Pascal shares a cautionary experience with mature Scrum teams that appeared to function flawlessly. These teams demonstrated excellent Scrum practices with minimal impediments, leading management to conclude that Scrum Masters were unnecessary. When management removed all Scrum Masters from the department, the previously high-performing teams began to struggle significantly. Team members had to absorb the responsibilities previously handled by their Scrum Masters, causing them to lose focus on their core value-creating work. Different teams adopted various approaches to fill the Scrum Master void, but none proved effective. Pascal reflects that the Scrum Masters could have made their value more visible by supporting Product Owners more actively and becoming more involved in team tasks. This experience taught him the importance of demonstrating the ongoing value that Scrum Masters provide, even when teams appear to be self-sufficient. Featured Book of the Week: Learning Out Loud—Community Learning and Networking Pascal draws his greatest inspiration not from a single book, but from active participation in the Agile community. He finds tremendous value in discussions within local communities, networking events, and sparring sessions with colleagues. Pascal particularly benefits from Agile Coaching circles in Helsinki, which provide practical knowledge and insights. He also gains inspiration from Agile conferences, but credits Agile Coaching Camps as having the biggest impact - these 2.5-day open space format events are intense and packed with valuable insights. Pascal recommends that Scrum Masters actively engage with their local Agile communities and attend coaching camps to accelerate their professional development and gain diverse perspectives. Self-reflection Question: How visible is the value you provide as a Scrum Master, and what steps could you take to make your contributions more apparent to your organization? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Pascal Papathemelis Pascal is an Agile & Professional Coach that wants to make a positive impact to the people working with. Coaching in Finnish, German and English language. Focus areas are human factors, outcomes, effectiveness, flow, decision making, clarity and constant improvement. You can link with Pascal Papathemelis on LinkedIn.

8 Heinä 19min

From Mechanics to Human Factors—How Scrum Masters Grow | Pascal Papathemelis

From Mechanics to Human Factors—How Scrum Masters Grow | Pascal Papathemelis

Pascal Papathemelis: From Mechanics to Human Factors—How Scrum Masters Grow 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. Pascal shares his evolution as a Scrum Master, moving from focusing purely on the mechanics of Scrum to understanding the critical importance of human factors. Early in his career, Pascal worked with teams that struggled to achieve sprint goals, with stories floating from one sprint to another. Through retrospectives and continuous improvement, he learned essential tips like not taking too much into sprints and making stories smaller. However, Pascal's biggest transformation came when he shifted focus to human elements - involving everyone in the team, improving collaboration during refinement, and developing people's skills and attitudes. He emphasizes that every person is an individual with the intention to be their best, and a good Scrum Master must sense when something is wrong and create safe environments for open conversations. Pascal highlights the importance of corridor conversations and coffee machine breakthroughs, especially before COVID, and stresses the need to invest effort in how teams start, using models like Tuckman's team growth model and Diana Larsen's Team Liftoff approach. In this segment, we also refer to the episode with Arne Roock, about the importance of team design and setup in the success of teams. Self-reflection Question: How might shifting your focus from Scrum mechanics to human factors transform the way you support your team's growth and collaboration? [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 Pascal Papathemelis Pascal is an Agile & Professional Coach that wants to make a positive impact to the people working with. Coaching in Finnish, German and English language. Focus areas are human factors, outcomes, effectiveness, flow, decision making, clarity and constant improvement. You can link with Pascal Papathemelis on LinkedIn.

7 Heinä 15min

Millions of Users, Multiple Stakeholders—The Art of Product Owner Navigation | Bernard Agrest

Millions of Users, Multiple Stakeholders—The Art of Product Owner Navigation | Bernard Agrest

Bernard Agrest: Millions of Users, Multiple Stakeholders—The Art of Product Owner Navigation 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 Stakeholder Navigator Bernard describes an exceptional Product Owner who managed a product impacting millions of people while navigating constantly evolving requirements from multiple stakeholders. This Product Owner excelled at understanding each stakeholder's unique needs and communicating effectively with all of them. What made this person truly great was their ability to come to the development team with a clear understanding of both the business case and user needs, having done the hard work of stakeholder management upfront. This Product Owner understood that their role was to be the bridge between complex stakeholder requirements and clear team direction. The Bad Product Owner: The Collaborative Hoarder Bernard identifies a dangerous anti-pattern: the Product Owner who adds everything to the backlog under the guise of being "collaborative." While this behavior appears inclusive and team-friendly on the surface, it actually demonstrates that the Product Owner isn't following through on delivering real value. These Product Owners become almost exclusively focused on authority rather than outcomes, making them particularly difficult to coach since they resist guidance. Bernard recommends using Cost of Delay as both a prioritization technique and a tool to help Product Owners understand why certain items shouldn't be added to the backlog at all. Self-reflection Question: Is your Product Owner truly collaborating by providing clear direction, or are they avoiding difficult prioritization decisions by adding everything to the backlog? In this segment we refer to the Coach Your Product Owner e-course that we created for everyone who needs to help their Product Owners succeed! [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 Bernard Agrest Bernard currently leads a major software implementation at University of Wisconsin—Madison Medical School, serving over 10,000 employees. Previously, he built a PMO and led Data and Learning at Teach For America. His journey began redesigning operations for a Veteran Service Organization, where he co-led national initiatives and launched a new alumni program. You can link with Bernard Agrest on LinkedIn.

4 Heinä 12min

Creating Conditions for Healthy Conflict and Continuous Improvement in Agile Teams | Bernard Agrest

Creating Conditions for Healthy Conflict and Continuous Improvement in Agile Teams | Bernard Agrest

Bernard Agrest: Creating Conditions for Healthy Conflict and Continuous Improvement in Agile Teams 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. Bernard believes successful Scrum Masters focus on creating conditions where tension and healthy conflict can emerge naturally, rather than maintaining artificial harmony. Too many organizations remain stuck in fear-based cultures where people avoid raising important issues. For Bernard, success means ensuring people regularly surface problems and engage meaningfully with each other—it's not enough to simply monitor green dashboards. He emphasizes that real leadership involves focusing on creating conditions for teams to discuss what truly matters, moving beyond surface-level metrics to foster genuine dialogue and continuous improvement. Self-reflection Question: Are the people on your teams regularly raising issues, or are you relying too heavily on dashboard metrics to gauge team health? Featured Retrospective Format for the Week: 4L's The 4L's retrospective format is simple yet powerful, examining what the team Liked, Learned, Lacked, and Longed for. Bernard particularly values the "Longed for" category because it asks people to connect the dots between how they felt and how they performed. In one memorable session, using 4L's helped his team understand what they were missing in their regular sync work, leading them to change how they conducted meetings to better support upcoming deliveries. This retrospective format had long-term organizational impact, helping teams realize gaps in their collaborative processes and make meaningful improvements to their working relationships. [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 Bernard Agrest Bernard currently leads a major software implementation at University of Wisconsin—Madison Medical School, serving over 10,000 employees. Previously, he built a PMO and led Data and Learning at Teach For America. His journey began redesigning operations for a Veteran Service Organization, where he co-led national initiatives and launched a new alumni program. You can link with Bernard Agrest on LinkedIn.

3 Heinä 12min

One-on-One Insights—Building Change Strategy Through Individual Conversations | Bernard Agrest

One-on-One Insights—Building Change Strategy Through Individual Conversations | Bernard Agrest

Bernard Agrest: One-on-One Insights—Building Change Strategy Through Individual Conversations 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. When faced with a tool that needed complete rebuilding rather than more "duct-tape" features, Bernard knew that disruption was inevitable—but where to start? Through extensive one-on-one conversations with employees and stakeholders, he discovered that teams didn't understand their work was cyclical, and more importantly, that the onboarding team was central to the entire process. By starting the transformation with this pivotal team and focusing on training and user adoption, the new tool provided immediate organizational impact with data-driven decision making. Bernard's approach demonstrates that successful change management starts with understanding the true workflow and identifying the critical connection points that can drive the most significant positive impact. Self-reflection Question: In your current change initiatives, have you identified which team or process serves as the central hub that could accelerate transformation across the entire organization? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Bernard Agrest Bernard currently leads a major software implementation at University of Wisconsin—Madison Medical School, serving over 10,000 employees. Previously, he built a PMO and led Data and Learning at Teach For America. His journey began redesigning operations for a Veteran Service Organization, where he co-led national initiatives and launched a new alumni program. You can link with Bernard Agrest on LinkedIn.

2 Heinä 13min

Avoiding Hard Conversations—When High-Performing Agile Teams Self-Destruct | Bernard Agrest

Avoiding Hard Conversations—When High-Performing Agile Teams Self-Destruct | Bernard Agrest

Bernard Agrest: Avoiding Hard Conversations—When High-Performing Agile Teams Self-Destruct 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. Bernard describes how a high-performing, fun-loving team began to unravel when a new member joined who wasn't delivering on their commitments. Instead of addressing the performance issue directly, team members started picking up the slack, avoiding the difficult conversation that needed to happen. As morale dropped and people checked out, Bernard realized the team was paralyzed by fear of confrontation and assumptions that raising the issue would be ignored. This experience taught him that individual performance problems quickly become whole-team problems when left unaddressed, and that strong relationships require the courage to have honest, supportive conversations. Self-reflection Question: What difficult conversation are you avoiding on your team, and what assumptions might be preventing you from addressing it? Featured Book of the Week: The 6 Types of Working Genius by Patrick Lencioni Bernard recommends The 6 Types of Working Genius by Patrick Lencioni because it helps leaders understand that everyone has specific "genius" areas in different phases of work. When people work outside their natural genius zones, they feel unfulfilled and frustrated. This framework has been invaluable for Bernard in understanding team dynamics—why some teams click naturally while others struggle. By recognizing each person's working genius, leaders can better position team members for success and create more effective, satisfied teams. [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 Bernard Agrest Bernard currently leads a major software implementation at University of Wisconsin—Madison Medical School, serving over 10,000 employees. Previously, he built a PMO and led Data and Learning at Teach For America. His journey began redesigning operations for a Veteran Service Organization, where he co-led national initiatives and launched a new alumni program. You can link with Bernard Agrest on LinkedIn.

1 Heinä 14min

When Stepping Back Becomes Stepping Away—A Leadership Failure Story | Bernard Agrest

When Stepping Back Becomes Stepping Away—A Leadership Failure Story | Bernard Agrest

Bernard Agrest: When Stepping Back Becomes Stepping Away—A Leadership Failure Story 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. Bernard shares a powerful story about a critical research project where his instinct to step back and empower his team ultimately led to project failure and personal burnout. When Bernard realized his team wasn't ready for the work ahead, he made the mistake of taking everything on himself rather than building proper feedback loops and ensuring true understanding. Working overtime and feeling guilty about not supporting his team properly, Bernard learned that empowerment isn't about stepping back—it's about creating space to work together. His key insight reveals that it's through doing the work that we discover what work actually needs to be done, and that having people say they "get" the plan doesn't mean they truly understand it. Self-reflection Question: How do you distinguish between genuine team empowerment and abandonment when stepping back from direct involvement in projects? [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 Bernard Agrest Bernard currently leads a major software implementation at University of Wisconsin—Madison Medical School, serving over 10,000 employees. Previously, he built a PMO and led Data and Learning at Teach For America. His journey began redesigning operations for a Veteran Service Organization, where he co-led national initiatives and launched a new alumni program. You can link with Bernard Agrest on LinkedIn.

30 Kesä 15min

Suosittua kategoriassa Politiikka ja uutiset

rss-ootsa-kuullut-tasta
aikalisa
tervo-halme
ootsa-kuullut-tasta-2
politiikan-puskaradio
viisupodi
rss-podme-livebox
et-sa-noin-voi-sanoo-esittaa
rss-vaalirankkurit-podcast
otetaan-yhdet
aihe
linda-maria
the-ulkopolitist
rss-polikulaari-humanisti-vastaa-ja-muut-ts-podcastit
rss-hyvaa-huomenta-bryssel
radio-antro
rss-valiokunta
rss-kaikki-paskaksi-ystavat
rss-kuka-mina-olen
rss-tasta-on-kyse-ivan-puopolo-verkkouutiset